search results

(...) Hi, in the Information Panel, steps that have the path parameter option “Set current step as finished” enabled are currently displayed with a checkmark once the path is taken. This works well for paths that lead to an intermediate step or positive completion of a process. However, it can be misleading when such a path leads to a negative final step (for example: rejected, cancelled, declined). (...)

(...) gner Ideally, opening a historical version would launch a separate dialogue with a read-only version of the workflow designer. In this mode, users could: - see the full workflow diagram - inspect steps and paths - review configuration settings of elements - analyze parameters and logic used in that version This would allow devs to fully review previous configurations even after many subsequent c (...)

(...) e workflow (sql)", but it is not possible to move the workflow you are in at the moment) (there is only one path after the system step and it es marked as default path) (the article covering system steps did not help me to understand) (I set up a simple workflow for testing, see picture) Thanks already for your help.

(...) s "any collection" and "data source" where the "Colums collection" gets displayed? This would be more intuitive imho. Moreover it seems to be "previewed" from a technical perspective. Follow these steps to reproduce the behavior: 1 Create for each with "any connection". 2 Add an action and use the entry "Value" under the entry "Columns collection" 3 Click OK and go back to the place where the f (...)

(...) n in the field matrix so that it gets always displayed even when horizontal scrolling is needed/used. Right now the field column disappears if the scrollbar gets moved to the right side. With many steps one can get lost and select the bad field row. Kind regards Sébastien

(...) tion after action execution "cancel" => Timer throws an error: field validation "Comment" on path "cancel". 1. idea: I make a special cancel-path for the timer => problems: * I have more such steps => would result in many workaround paths * Some cancel path do have flow-control behind, to determine the correct final step 2. Idea: I disable "comment required" in that path and create a form- (...)