Community

We have a subflow consisting of a few tasks, that takes anything from 1 to approx 9 minutes to finish. When calling any subflow with /api/v2/my/workflows/run/{key} it is limited to a runtime of 5 minutes before it fails as of <https://support.onify.co/reference/postmyworkflowsrunkey> This seems to be a hardcoded value, and probably set to be enough for most of such task. But having such a limit will in our case force us to move the logic from a subflow to our main flow to not have timeouts, which is unfortunate in terms of maintainability etc. Is there any possibility to change set this limit to another value within our own Onify instance? In return I can provide you with an enhanced and more reliable version of this blueprint. ;) <https://github.com/onify/blueprint-cloudblue-commerce-change-subscription>

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. 😊  \<bpmn:serviceTask id="sendEmailTask" name="Send Email Task" camunda:asyncBefore="true" camunda:failedJobRetryTimeCycle="R3/PT30S"> \</bpmn:serviceTask>

I noticed something about custom routes in the latest API release. Seems interesting and I'd like to understand how they work. <br>

We have 50 old flows which all has modeler:executionPlatformVersion="7.18.0" or earlier, as can be seen in the XML. When you create a brand new BPMN Diagram (Camunda 7) with Camunda (5.21.0 or later) it will default to modeler:executionPlatformVersion="7.20.0". And from that version and up it is obligatory to set "time to live" under under "History cleanup, Time to live" in the properties panel, or you will have it listed as a problem in the problems panel, as in the screenshot in <https://docs.camunda.io/docs/next/components/modeler/reference/modeling-guidance/rules/history-time-to-live/> So setting any value (number of days) will get rid of the listed problem in the panel, alternatively going in to the XML and changing executionPlatformVersion to anything before 7.20. My question is - will this value be used by Onify or will it just be ignored at the time being? And if it is used, or will be in the future, do you have a recommended "default" value for it?

Is there a way to add a custom theme to Helix? If so, how is it done?

I am have a Onify Helix App repo and have the following in `package.json`: ```json json ... "@onify/helix-components": "*", "@onify/helix-core": "*", "@onify/helix-pages": "*", "@onify/helix-themes": "*", "@onify/helix-tools": "*", -... ``` How do I know what version I have installed?

I have been struggling a bit getting Onify Helix up and running on Openshift. Any tips?

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. And in an opposite situation - many times a lot of the fields which are shown are not interesting to me at this point and just adds cognitive noise. So it would be great if the tables as default showed the fields as of today but - You could chose to show additional fields or hide visible fields as of your liking - Possibly also save your own presets with different visible settings for different purposes - In an utopian world also make it possible to include the search query in the presets :heart-eyes: (This is very similar to how Airtable has solved it with different views for the same data and that is a killer :skull:feature.)

In the search page we can sort ascending or descending by the properties such as name, key, createdate, modifieddate and \_score (relevance) for example /search?term=\*&filter=tag:produkt&sort=createdate,asc How can we make it possible to sort by other keys existing in the item template, such as price or article number?