Community
Best practice regarding flows that should not be run in parallel with itself?
Some flows are perfectly fine to run in parallel with itself.
Feature request: Use a generic or assignable username for flows triggered by timer
In /admin/processes the column "User" shows
Feature request: Implement retry cycles for servicetasks (failedJobRetryTimeCycle)
It would be great if we could use the Camunda function "retry cycle" in Onify to retry a task, that sometimes fails, a specified number of times with a specified time apart. Now we need to build this logic ourselves around tasks that need such "safety net" to not exit a full flow because of some intermittent downtime or unreliable service e t c. 😊
Feature request: In Onify admin - show ALL data in the tables and make it possible to select which fields to show/hide
For example in /admin/configuration/shortcuts I have a lot of shortcuts and when I add a new one the "key" is of course an obligatory field. To keep the naming conventions structured I here need to look at the other keys and it would be so easy if they were in the table, but they are not. 😪 Instead I now have to open the posts one by one to look at the keys for each.