Running Process model on Dynamic time

RE: Running Process model on Dynamic time

Jamuna — Sat, 04 May 2024 05:44:03 GMT

Hy Sri,

We have to go with running wrapper process at every 15/30mins or max of 1hr timeframe.

In that process you can check for the requests which needs to be notified within next 15/30mins or 1hr & In MNI you can call scheduled email node process (call it as start process so that wrapper will get terminated quickly).

If you run at 6/12/24 hrs once, then only it will affect memory as it will be active for longer time due to scheduled email nodes. But if we run wrapper at lesser than 1 hr, child instances will be active at max of next wrapper get triggers which will free up the memory frequently.

RE: Running Process model on Dynamic time

MK0001 — Mon, 08 Apr 2024 16:23:22 GMT

In this case, the main process model will live for longer run right?

RE: Running Process model on Dynamic time

daisyMSingh — Mon, 08 Apr 2024 13:08:40 GMT

One of the Best way would be to Use Parent Process as Scheduler and Capture all the Process of that day and Run an MNI orve then .

In Sub Process Also Add an XOR Gateway to Check if the Process had Been Triggered Or Not So in case of Failure Also Non Triggered Instances will Be triggered .

RE: Running Process model on Dynamic time

Mike Schmitt — Fri, 05 Apr 2024 17:16:13 GMT

[quote userid="276123" url="~/discussions/f/process/34586/running-process-model-on-dynamic-time/132715"]However, if you need dynamic recalculations based on database values, you might need to explore other event types[/quote]

I'm really not following what you're trying to say here. We're talking about Start Process nodes, not other event types. As Stefan also mentioned, what you've described here originally, as far as I can tell, just doesn't work the way you described. If I'm missing something I hope you can clarify.

RE: Running Process model on Dynamic time

Shubham Aware — Fri, 05 Apr 2024 17:13:42 GMT

Got it! I'll whip up a working example over the weekend and get back to you.

RE: Running Process model on Dynamic time

Shubham Aware — Fri, 05 Apr 2024 17:12:02 GMT

You're correct that for Start Process timers, the starting time is typically calculated at publish or import time, based on the static value provided in the configuration. However, if you need dynamic recalculations based on database values, you might need to explore other event types(ex. rule event) after starting a process at some interval.

RE: Running Process model on Dynamic time

Stefan Helzle — Fri, 05 Apr 2024 17:05:19 GMT

What you describe does not work this way. Can you share a working example of this?

RE: Running Process model on Dynamic time

Mike Schmitt — Fri, 05 Apr 2024 16:48:29 GMT

No - he means to kick off a fresh instance every so often (once or twice daily perhaps), query the DB to see whether any notifications fall into that time range, and if so, send them. Then that instance will end. It won't consume any (or much) extra memory, as it'll be short-lived.

RE: Running Process model on Dynamic time

MK0001 — Fri, 05 Apr 2024 16:31:09 GMT

So, the process model should run continiously? Will it cause any memory consumption?

RE: Running Process model on Dynamic time

Mike Schmitt — Fri, 05 Apr 2024 16:19:27 GMT

[quote userid="276123" url="~/discussions/f/process/34586/running-process-model-on-dynamic-time/132698"]Configure the timer to "Delay until the date and time specified by an expression."
Use an expression that calculates the reminder date based on the date stored in the database.[/quote]

I'm not sure this will work for a Start Process timer. As far as I know, the starting time is calculated at publish time (or import time) and not re-calculated dynamically again until re-publishing - the assumption being that the start time will be some static value stored in the "Delay until the date and time specified by this expression:" configuration, then a static interval (if any) for the "recurrence" configuration.

RE: Running Process model on Dynamic time

Shubham Aware — Fri, 05 Apr 2024 16:04:22 GMT

Timer Event:
Create a process model with a start event set to a timer event.
Configure the timer to "Delay until the date and time specified by an expression."
Use an expression that calculates the reminder date based on the date stored in the database. You can use built-in functions like addDays or addHours to manipulate the date.

RE: Running Process model on Dynamic time

Stefan Helzle — Fri, 05 Apr 2024 15:41:57 GMT

Run a process in a short interval which then checks whether to manage any reminders configured.