Understanding Events and Routings
This section lists common elements and provides an overview of events and routings.
|
Field or Control |
Definition |
|---|---|
| Name |
Enter a unique name for the system to display in dialog boxes that list routings. By default, the routing name also appears as the display text under the icon on the map. |
| Icon Descr (icon description) |
(Optional) Enter text to appear under the icon if you do not want to use the default name. Include line breaks in the icon display text by pressing Enter. |
When you create a business process in PeopleSoft Application Designer, you specify which activities form a business process and in what order they must be completed. The map provides an overview of the process, but it doesn’t provide a link between the activities. To link the activities to a workflow, you add routings, which automate the delivery of information to other activities and other users.
Events are conditions that have associated routings. Define the condition in PeopleCode, which is attached to the record definition underlying a step in a step map. When a user saves the page, completing the step, the system runs the PeopleCode program to test the condition. If the condition is met, the system performs the routings.
Routings can deliver data in two forms: worklist entries and email messages. To create a routing, specify the routing type, who should receive the data, and which data you want to send. The data is usually a subset of the data from the step that triggers the routing.