Order Editor Events Tab

Use the Order editor Events tab to create order milestone event notifications. You select the order milestone that triggers the automation and then configure the automation plug-in that will perform the work.

You can configure the properties of automations. See "Configuring Automation Plug-in Properties" for more information.

The following table describes the fields on the Order editor Events tab.

Field	Use
Milestone	The Milestone column displays the milestones for which you have defined automation events. When the order reaches the corresponding milestone, the OSM server triggers the automation event plug-in.
Name	In the Automation column, the Name field displays the name of automation plug-in.
Automation Type	Displays the automation plug-in type. See "Working with Automation Plug-ins" for more information.
View	Click an automation, and click Select in the View field to choose a query task to use with the automation. You must define an OSM user in the automation plug-in Run As Property field to run the automation plug-in and configure one or more roles and default query tasks using the Order editor Permissions tab. Associate the roles with the OSM user using the OSM Administrator application. If the Run As OSM user has more than one role, each with a different default query task, then multiple query task views are available to run the automation plug-in. You can select a query task to allow OSM to predictably use one query view to run the automation plug-in. If only one default query task is available in the Order Editor Query Task tab, then this query task is automatically added to the View field when you create a new automation. See "Order Editor Permissions Query Tasks Tab" for more information. If the query task view has already been selected, click Open to view the query task. To create a new query task, click New to start the New Studio Entity wizard. Note: You must configure the View field if you are creating an OSM 7.2 cartridge. You can deploy older cartridges with the OSM 7.2.0 server, but random selection of query task views may occur if an OSM user has more than one role, each with a different default query task.