-
Notifications
You must be signed in to change notification settings - Fork 470
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update timer cycle definition to support cron expression #3061
Comments
Are there changes needed for the property itself, or are only documentation/description updates required? |
@pinussilvestrus I don't think so. For the |
We decided to split it up:
@nikku mentioned that he can pick up the first part. |
Split up validation into separate topic: #3084. That one goes beyond duration but shall cover different mentions of times, durations and intervals, as well as CRON expressions across our app(s). |
@barmac |
@barmac |
Do we want to update the description for C7 too? As noted in the Zeebe issue, C7 also supports cron expression and it's documented: https://docs.camunda.org/manual/7.17/reference/bpmn20/events/timer-events/#time-cycle |
Yes, let us do it! |
The example comes from the docs: https://docs.camunda.io/docs/next/components/modeler/bpmn/timer-events/#time-cycle |
This looks fine! I assume this is parsed at Zeebe, and no additional flag necessary to pass so Zeebe knows what to expect? |
I confirmed that a timer with exactly this expression is successfully deployed to |
OK, so I will proceed with the contents as on the screenshot. |
This will be implemented via bpmn-io/bpmn-js-properties-panel#772 |
What should we do?
Update timer cycle definition to support cron expressions.
Inspiration can be retrieved from the docs (once those are completed).
Why should we do it?
Camunda Platform 8.1 introduces the following
Note that we can define a CRON expression, but that the description specifies the ISO 8601 repeating intervals only:
Related to https://github.com/camunda/product-hub/issues/300.
The text was updated successfully, but these errors were encountered: