- Declare Trigger runs an
activity when instances of a specific class are created, updated, or
deleted in the database.
- This implements a form of
forward chaining.
- For each Declare Trigger rule,
the Pega Platform monitors database operations for objects of the Applies
To class (and concrete classes derived from that class)
- During database commit
processing, forward chaining processing may trigger — start execution of —
the activity identified in this rule.
- Declare triggers are always
executed before the object is committed to the database.
- Trigger activity can execute
immediately or on background .
- If you define Declare Trigger's execution
method as Background, then Pega creates child requestor and then executes
the Declare Trigger in that requestor. The reason for this option is to
consider the performance impact of the application.
- Declare Trigger runs an
activity when instances of a specific class are created, updated, or
deleted in the database.
Split Join - Use the Split-Join shape to require that multiple subflows of your flow be completed before the current flow continues execution. This allows subflows to execute asynchronously, in parallel. For an example, see the standard flow Work-.ParallelWork. Split For Each - The Split-ForEach task provides a form of searching or enumeration over the pages in a property. Use a Split-ForEach shape to iterate over the pages of a Page List or Page Group property. For each page, you can conditionally start a flow execution for the work object. Spinoff- When a work object advancing through a flow reaches the Spin-off shape, Process Commander starts execution of a different flow, using the current or a different work object. Processing in the current flow rule continues in parallel, without waiting for the other flow to complete.
Comments
Post a Comment