search results

(...) I have form-validation s that work correctly and catches errors correctly. It would be nice if I could sat the HTML-form focus on that particular element that was validated wrong! Any suggestions , I find it hard because form-validation only returns true or false i cant use it afterwards anymore

(...) d that save. So far so good break with condition and background change on value-change works too! But ... is there any (simple) possibiliy that I could change the fields afterwars / also after form validation AND /OR break condition. So that can specifiy which fields are incorrect filled out? Thanks in advance and have a nice weekend! ~Phil

(...) imagine a workflow with on start (cyclical) automation that starts the workflow itself. This can be a sync of an external data source with a dictionary. If the sync returns an error a step for error validation gets entered. Having this on dev, test and prod would then generate a task on all environments. I expect to have a task creation only in production environment if the process already exists on pro (...)

(...) "housekeeping" timer in that step. The timer exections an action (Change field value => [System]Comment) and has path transistion 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-co (...)