Community
Possibility to reuse server side helper functions in PUG before switching to Helix?
Until we switch to Helix it would be helpful to be able to put the server-side helper functions for all PUG forms in a separate file to avoid redundancy and versioning problems.
prepareDescription in itemTempalate.json
I want to move "item.description" from "subtitle1" to be within the accordion within "information".
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
Possibility to change the 5 minute limit of "Short running synchrone (non persistent) workflows"?
We have a subflow consisting of a few tasks, that takes anything from 1 to approx 9 minutes to finish.
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.