No more option for cycle in timer intermediate events

[benhoffmann]

Why did the cycle option disappear from the property panel? That's very useful for cron expressions and also it's supported by the engine.

[nikku]

It was removed via #501 upon user request.

Timer catch events fire once which continues the process execution. Because of that the cycle type makes no sense for them.

As always, correct us, if we're wrong 😉.

[benhoffmann]

It makes sense for cycles of one :) Because otherwise it's hard to say something like "wait for the beginning of the next day" without having to use a Java Date.

[nikku]

Could you provide us with an actual example? What cycle duration would you configure to more concisely express this behavior?

[benhoffmann]

The one you can see in the screenshot.

Because otherwise it's hard to say something like "wait for the beginning of the next day" without having to use a Java Date.

[nikku]

We'll bring it back then.

[benhoffmann]

Well, I agree that cycle can be confusing for intermediate events, maybe there is a better approach to this requirement. The cron thing is a bit of a dirty hack here. Discussions are going on in consulting right now ...

[nikku]

Two better solutions (exclusive):

• Rename the Cycle option to something reasonable, less confusing in the context of intermediate catch events
• Support CRON expressions in Date field (new engine feature)

Regardless of this we'll bring the cycle back.

[benhoffmann]

Support CRON expressions in Date field (new engine feature)

That would be my preferred solution. But it seems like no one else wished for it yet.