Start Event - Time recurrence

RE: Start Event - Time recurrence

Yogi Patel — Sat, 29 Jun 2024 06:00:02 GMT

From the generated XML, it seems that we can configure intervals using the month's configuration. Following XML generated is when we configure "The 1st Tuesday of every 1 month(s)":

RE: Start Event - Time recurrence

Chris — Fri, 28 Jun 2024 19:42:16 GMT

[quote userid="50400" url="~/discussions/f/process/35342/start-event---time-recurrence/137377"]This approach is cleaner, though I can never quite get over how much harder to actively test it is. With the "XOR method" you merely launch an instance whenever and watch it bomb out.[/quote]

You just have to have faith sir 🙂

I do agree on, liking to be able to actively test everything. For these, I'll typically make a non-prod expression rule to run test cases on my timer condition, then make reminders to verify on test servers/production at those times for the first set of runs to ensure all goes well. I like to avoid extra starts in general as a habit. I do still have a few that use the XOR method, it is low overhead especially if you have a parent process which only handles the Start->XOR->End OR Start Process for your main PM.

6 of 1, index() of property() 🙂

RE: Start Event - Time recurrence

Mike Schmitt — Fri, 28 Jun 2024 18:56:07 GMT

This approach is cleaner, though I can never quite get over how much harder to actively test it is. With the "XOR method" you merely launch an instance whenever and watch it bomb out.

RE: Start Event - Time recurrence

Chris — Fri, 28 Jun 2024 18:12:22 GMT

Agree with Mike, I believe that input is looking for an integer value only.

Additionally, instead of the XOR method we can also used the Advanced Timer Conditions, still set the process to attempt to start every 1 month, then add a condition which will stop the process from firing unless the current month is in your list:

contains({1,4,7,10},month(today()))

RE: Start Event - Time recurrence

Mike Schmitt — Thu, 27 Jun 2024 19:11:35 GMT

I don't believe that's how it works. I will be surprised if this runs without error for you - that field (as far as I know) requires a single integer to mean "every 2 months" etc; an array of numbers will thus be nonsensical to it.

If you want to use a specific set of months, and you can't just tell it to do like "every 3" (after delaying the initial start to fall on the appropriate month), then just make it launch every month and check (i.e. in a subsequent XOR node) whether the current month is one of the "in crowd" months, and if not, then immediately exit the process flow.