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

No more option for cycle in timer intermediate events #792

Closed
benhoffmann opened this Issue Apr 26, 2018 · 8 comments

Comments

Projects
None yet
3 participants
@benhoffmann

benhoffmann commented Apr 26, 2018

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.

bildschirmfoto 2018-04-26 um 15 33 14

@nikku nikku added the wontfix label Apr 26, 2018

@nikku

This comment has been minimized.

Member

nikku commented Apr 26, 2018

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 😉.

@nikku nikku closed this Apr 26, 2018

@benhoffmann

This comment has been minimized.

benhoffmann commented Apr 26, 2018

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

This comment has been minimized.

Member

nikku commented Apr 26, 2018

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

@nikku nikku reopened this Apr 26, 2018

@nikku nikku added this to the M22 milestone Apr 26, 2018

@benhoffmann

This comment has been minimized.

benhoffmann commented Apr 26, 2018

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

This comment has been minimized.

Member

nikku commented Apr 26, 2018

We'll bring it back then.

@benhoffmann

This comment has been minimized.

benhoffmann commented Apr 26, 2018

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

This comment has been minimized.

Member

nikku commented Apr 26, 2018

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

This comment has been minimized.

benhoffmann commented Apr 26, 2018

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.

@philippfromme philippfromme self-assigned this May 18, 2018

@philippfromme philippfromme added in progress and removed backlog labels May 18, 2018

@wafflebot wafflebot bot removed the in progress label May 18, 2018

@nikku nikku reopened this May 25, 2018

@nikku nikku added the needs review label May 25, 2018

@nikku nikku closed this in b0d1e9b May 25, 2018

@wafflebot wafflebot bot removed the needs review label May 25, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment