Here you find an overivew of how to share ideas, vote, get updated on your ideas and the workflow until one idea becomes a feature and finally is released.
Improved error message in code editor for calculated fields
The code editor for calculated fields, which was introduced in SR19, does not provide helpful error message, if the entered code has a grammar syntax. It some case it just shows an "internal error". It would be good to have hints how to improve th...
the IF ELSE statement right now can take only one input for the the IF condition. it is time consuming when we have multiple AND statements for the IF.
In a table were there is column for observations (called testName) and the value for the observation (called value). This is so called unpivoted table. We need to store results in this format since list of observations may different across differe...
Request from {customer_name} A waterfall chart is a form of data visualization that helps in understanding the cumulative effect of sequentially introduced positive or negative values. These intermediate values can either be time based or category...
When adding any dimension (or measure in case of a distribution cart) the step width is automatically determined. For some charts there are some options to influence this (e.g show top 10) A helpful functionality would be to allow a user to determ...
Process Explorer: Toggle to visualize full process, don't aggregate steps
Currently steps are visually aggregated within the process explorer app even if they occur more then once within a variant. If this occurs you will see loops/connections going back into the same step which as a result makes it very difficult/impos...
Scenario: Request 1 Event 1 Request 2 Event 2 Event 3 Desired Outcome: TPT 1: Request 1 - Event 1 TPT 2: Request 2 - Event 2 TPT 3: Request 2 - Event 3 So as we want to calculate the TPT btw the event and the last request we wanted to know In a ca...