- New Organization Designer user interface -
The first step in using workflows with Position Management is to set up one or multiple workflows in Workflow Administration > Workflow Designer. Each workflow defines an approval process for a change. If you’re using a single workflow for all position changes, you need to set up only one workflow. If you’re using different workflows for different types of changes, you can create as many as you need.
You must follow these guidelines when you build a workflow to be used with Position Management:
- The workflow must not have a process node.
- The workflow must have an observing class notification node with the Position Approval observer class type. This node must be added immediately after the final decision node, on all output paths. For example, if your workflow has multiple levels of approval, then the observing class notification node must be added after the reject and accept links after the final approval decision node.
- Not all routing and notification options are supported (see the following list).
Only the following routing and notification properties are supported when building a workflow to use with Position Management:
- Send to User
- Send to Submitter
- Send to Authority Type Relative to Submitter
- Send to Role Relative to Submitter
- Send to Submitter's Manager
- Send to Position’s Manager
- Relative Level of Position’s Manager
- Relative Level of Submitter's Manager
- Use Form Effective Date for Routing
The following table contains an example of a workflow before and after it’s configured to be used with Position Management. Note that observing class notification nodes have been added after the reject and accept links after the decision node. Also, the workflow doesn't contain a process node:
| Workflow before Position Management Configuration | Workflow after Position Management Configuration |
|---|---|
|
|
|
For more detailed information about configuring workflows, see the Self Service Guide.