Difference between an Event (workflow change status event) and Custom Action(initiated from Workflow state) ???
Difference between an Event (workflow change status event) and Custom Action(initiated from Workflow state) ???
I’m not sure I understand the question completely.
An Event simply identifies a specific action that occurs within the system
An Event Handler specifies a Custom Action or Notification that should be executed based on the occurrence of an Event.
An Event Subscriber ties the Event and the Event Handler together (When X Event occurs – Do Y Custom Action)
The Event Subscriber “watches”the system for the Event to occur and then executes the Custom Action accordingly.
So I think you are asking the difference in executing a PX through Event Management vs a Traditional PX added to a Workflow Status.
While you may be able to acheive the same result for a single PX using the traditional method – Event Management provides additional flexibility/functionality:
– Many different event types can be utilized (and customized) to trigger the PX.
– Synchronous Execution mode can be used to trigger multiple automations in a particular sequence.
– The same PX can be triggered under different scenarios and/or for different object types
– The use of Event Monitor provides more visibility within the system
A Custom PX is always executed AFTER the action has occurred (after the workflow enters the status).
In the Event Framework – a Pre triggered automation executes prior to the occurrence (completion) of the action. A Post triggered automation executes at a point immediately after the action has occurred.
If you have both Custom PX and Java PX configured for the same Workflow Status Change – the Java PX is always executed before the Custom PX.