Define General Properties for a Simple Action/Event Automation Process

Use the Simple Action/Event Automation Process window to define general properties for the process.

To define general properties for a Simple Action/Event Automation Process:

Create a Simple Action/Event Automation Process.

Define general properties:

Provide a display name and brief description.
Select the type of Business Object against which the process will operate.
Select a priority level, which provides a hint to the Business Process Server as to the importance of the Automation Process. This allows the system to attempt to execute higher priority processes before normal or low priority processes.

Select an event to use to activate the Automation Process.

Event Type	Description
<Business Object> Created	The Automation Process starts when a <Business Object> is created.
<Business Object> Changed	Any Change: The Automation Process starts if any change is made to the <Business Object>. Events that trigger based on any change made to Business Objects can greatly impact system performance. For best results, use the Field Changed option rather than the Any Change option. Field Changed: The Automation Process starts if the selected field is altered. You can choose to define if the Automation Process should operate when any change is made to the field, if the field changes to a value, if the field changes from a value, or if the field changes from one value to another. If you select Field changes from one value to another, ensure you complete the To: and From: fields. Use the Legal Values button to choose a value. If you don't complete these fields, the Automation Process doesn't run.
<Business Object> Created or Changed	The Automation Process starts when a <Business Object> is created or changed.
<Business Object> Closed	The Automation Process starts when a <Business Object> is closed. You can include this same functionality in lifecycles created using the Example: Create a Lifecycle by using transition rules and post-transition actions. See About Transitions and Add a Post-Transition Action.
<Business Object> Reopened	The Automation Process starts when a <Business Object> is reopened. You can include this same functionality in lifecycles created using the Example: Create a Lifecycle by using transition rules and post-transition actions. See About Transitions and Add a Post-Transition Action.
Related Child Event	Select the relationship, and then select the type of change that triggers the Automation Process to operate: <Business Object> Added For relationships that use direct links, events are created when the parent Business Object is saved. For relationships that use join tables, events are created when each link is saved. For one-to-many relationships, you can select the First <Business Object> Only checkbox to trigger the event for only for the first Business Object child created for the relationship. <Business Object> Record Modified <Business Object> Record Field Change You can define if the Automation Process should operate when any change is made to a specified field, if the field changes to a value, if the field changes from a value, or if the field changes from one value to another. Also, the event will only fire if the Business Object is modified while working on the parent. For example, if you edit an Approval in the arrangement below a Change Request, the event fires, but if you edit the Approval by alone it doesn't). If you encounter either scenario, then a direct event associated with an Approval should be created.
Queue Event	Queue Event: Select the type of queue event that triggers the Automation Process to operate (Record added to queue or Record removed from queue). Which Queue: Select the type of queue that should be considered (Any queue, Any user queue, Any team queue, or Specific queue).

Select OK.