Is the purpose of the repeat gateway to execute a script until a certain condition meets? If so, what's the way of configuring the gateway?
I was thinking about creating a script that executes the necessary logic and then checks if a parameter was changed or not. If the parameter didn't change, the logic will get execute it again.
But how this would be different from a script task that has that same logic?
Sebastian,
In case you want a process to be run on a regular basis, you should use the Timer Start Event or external code to push tokens in the process.
Repeat gateway can be used inside the process itself. When a token arrives on such a gateway, it will generate one or multiple tokens based on the repeat rule you've defined. Repeat rule is defined in a profile instance:
- PA GW Repeat Type :
- limited : limited number of tokens will be generated ( TotalAmount and Interval must be populated)
- time-limited : tokens will be generated during a period of time ( Interval and Duration must be populated)
- unlimited : tokens will be generated forever (Interval must be populated)
- PA GW Repeat TotalAmount
- PA GW Repeat Interval
- PA GW Repeat Duration
that’s correct!
Hi Sebastian, could you describe your use case in more details? Depending on the use case, it is sometimes easier to embed the 'retry' logic in the script task.
More than a use case, I’m generally curious about the repeat gateway functionality.
From your comment, I understand that not all repetitive logic should fall under this function type, but which is scenario that this should be used?
Thank you for the update, Emmanuel.
That’s very interesting and if I understand it correctly, the gateway itself does not contain any logic associated like a scrip task does, but instead its only purpose is to generate multiple tokens.