This site requires JavaScript to be enabled

IncidentLookup using list
How can we help?

Solution Suggestions

Please enter your question to get suggestions.
Boolean Operators
OR or vertical bar symbol (|)
Finds a match if either the terms exist in a document (a union using sets).
Finds a match if both terms exist in a document (an intersection of sets).
NOT, minus (-), or exclamation point (!)
Excludes documents that contain the term after NOT (a difference of sets).
Asterisk (*)
The asterisk symbol performs a multi character wildcard search.
Percent sign (%)
The percent sign performs a single character wildcard search.
Quotation marks (")
Use quotation marks to search for an exact phrase with multiple terms.
For examples and more information look at our Knowledge Base: Advanced Search On The Support Portal

Working with Incidents

This article gives helpful information on creating Customer Support incidents.


You are about to create a Customer Support incident.  The incident-based approach is fundamental to how Customer Support handles problems, so it is important to understand how to use it.  Attention to the following points will help your contact with Customer Support progress is the best possible way.


How Customer Support works

You create incidents to report problems, feature requests, and to ask questions.  Customer Support works on these incidents until they are resolved.  An incident can be created directly at the Support Portal (see Create Incident).

I need an answer, now

Take advantage of the online Webhelp here, and the dynamic Solution Suggestions which appear as you create an incident Title.  Many issues have been seen before, solved, and documented.  Make use of this growing body of experience.

Why create an incident?

Incidents are central to how Customer Support operates.  All artifacts related to your issue, such as a problem description, screenshots, and log files, are attached to an incident.  All work done on that issue is done via the incident.  A summary of the issue, log of communications, its current state, analysis work, the responsible agent, and processing metrics, are all kept with the incident.  The incident is preserved for future reference.

What makes a really “good” incident?

Start with a descriptive title.  Describe the problem clearly.  Remember, we must understand the problem, before we can solve it.  Here are some questions we often ask.  If you can tell us this information up front, we can get to the real problem that much faster.

  • What versions of Windows, Tosca, and Tosca Server are being used?
  • If applicable, what technology is being steered, e.g. SAP Fiori, Java FX, HTML on Chrome?
  • Was this previously working, and if so, what changed?
  • Is the problem repeatable or intermittent?
  • Does the problem show-up on one machine or multiple machines? 

What attachments will help you work on my incident?

Try to anticipate first-round debug data which would be helpful in understanding and analyzing the problem.  Here are some helpful attachments to consider:

  • A SupportInfo file (see KB0011946)
  • Stack traces (sometimes these are available via a “Details” button in an error dialog), the full stack trace is best
  • Screenshots
  • Subsets (see Importing and exporting subsets).  When possible, these should contain an executed ExecutionList with execution results
  • Logfiles (see KB0011252)

What else will help keep my incident moving?

Here are some guidelines that will make your incident easier to focus on, and easier to solve:

  • Limit the incident to the reported topic; create different incidents for different problems.
  • Keep incident-related communication within the incident.
  • When an incident has been resolved, close it.  Incidents will get closed automatically if we are waiting on you for information, for two weeks.  When this happens, we do not know if you found a solution, or just lost interest.

My problem is especially critical!

When you ask for increased priority, we look at the degree to which the problem impacts your ability to work, and at the number of the users impacted by it.  Increased priority is the exception, and not automatically granted.

If you feel that your problem is urgent, and you have a Platinum Support contract with us, in addition to creating or updating the incident, you can contact your designated Platinum Support Representative or your assigned Customer Success Manager.  Alert them to the urgency of the situation, and provide them with the number of the corresponding incident.

If an incident is escalated, please be correspondingly responsive in working with us to solve the problem.


Here are some additional resources which are often helpful.

  • How to create a Support Info file:  KB0011946
  • How to create a subset:  Importing and exporting subsets
  • How to run a Tosca workspace healthcheck:
    1.  cd %TRICENTIS_HOME%  (or %TRICENTIS_HOME\ToscaCommander, for Tosca versions < 10.0)
    2.  TCShell.exe -workspace <WORKSPACE_PATH>.tws -login <TOSCA_NAME> <TOSCA_PASSWORD> -healthCheck
    3.  See copy of report in latest log file in workspace directory.
  • How to enable various types of logging:  KB0011252
  • Possible debug questions, by topic:  KB0010738
  • Tips for working with large common repositories:  KB0012199
  • How to do a full uninstall of Tosca Testsuite:  KB0011746
  • How to do a full uninstall of Tosca Server:  KB0013101
  • Training:  Core Training Courses
1 0

Simi Kuzhikandiyil

Created: 2018-10-03 22:27:50

Currently unable to select the version while creating an incident. So unable to raise incidents . Please help


Tosca is the perfect solution

Optimize - Manage - Automate

Download Trial