Designing Your Approval Profiles

The following points describe a recommended design process:

• Create logical groups of adjustment types where each group has the same monetary hierarchy and approvers. An approval profile will be required for each of these groups.
• The number of To Do types (if any) that need to be created is dependent on how the adjustment approval To Do entries should be organized on To Do lists. For example, if all approval request To Do entries can appear in the same To Do list, you can use the base-package adjustment approval To Do type. However, if your organization prefers each approval profile's To Do entries to appear in a distinct To Do list, a separate To Do type will be needed for each list. Note that the base-package is supplied with a To Do type called C1-ADAPP that should be used as the basis for any new approval request To Do type.
• The number of To Do roles is dependent on who approves your adjustments. At a minimum, you will require a separate To Do role for each level in your approval profiles. Remember that every user in a To Do role will see its entries (and receive email if you've configured the system to do such).
• Refer to Monitoring and Escalating Approval Requests for how to configure the system to escalate approval requests that have been waiting too long.
• If your implementation requires email notification when an adjustment requires approval, the following setup is required:
  • Set up an outbound message type, external system, and message sender. Refer to To Do Entries May Be Routed Out Of The System for the details.
  • Every To Do type referenced on your approval profiles should be configured as follows:
• Define the F1-TDEER batch process as the To Do type's routing process
• Set up an algorithm that references the C1-ADJAREQEM algorithm type and plug it in the External Routing system event.