Manage Offer Approvals

You can use the preconfigured approval flow in Launch to run your offers past the approvers within your resource organization.

The approval flow for an offer traverses up through the resource hierarchy where the default approver is the reporting manager; however, you can override this default approver when confirming the offer design.

Note: The Initiative associated with the offer must be configured for approvals for the approval process to run.

Here’s the high-level approval flow for offers:

1. While confirming the offer design, you are prompted to either override the default approver or submit the offer to the default approver. After you click Submit, the offer moves to the Design Complete status.
2. To trigger the approval process, go to the Initiatives landing page, click Confirm for the associated initiative, and then click Initiate Approvals. This action sends email notifications to the approvers.
3. The approvers must view the offer that requires approval and approve (or reject) the request on the UI itself and optionally provide the supporting comments.

Configure Approvals

Use the profile options to configure the type of approval and the criteria for the completion of an approval depending on the approval type.

The following profile options are available to configure approvals:

Profile Option	Description and Values	Is Mandatory?
ORA_ATC_LAUNCH_APPROVAL_TYPE	Defines the approval type for offers. The default is parallel. Parallel Sequential Note: If you define the approval type as sequential, you must not override the default approver during offer confirmation. Doing so will change the approval type to parallel.	No
ORA_ATC_LAUNCH_APPROVAL_VOTE_PERCENTAGE	The percentage range is between 0 and 100. Defines the voting percentage required to mark the request as approved during parallel approvals. The default is 100 percent, which means all approvals are required.	No

Remember that these profile options would work only if the associated initiative is configured for approvals.

An approval type can be sequential or parallel. As the name suggests, a parallel approval is when the designated approvers of an offer can simultaneously approve the offer. In this type of approval, you can also define the voting percentage required to move an offer to the next stage. For example, if you configure the voting percentage as 50 percent, only half of the specified approvers are required to approve an offer.

In a sequential approval flow, an approvals must happen in a queue wherein the previous approver must approve before the next approver receives the email notification. This is similar to any organization hierarchy where the immediate next approver is the line manager and then the approvals move up the management chain.

Here are some considerations while working with offer approvals:

• You can’t edit an offer that’s in the approval stage. Offers in approvals stage have an interim status of Approvals Pending. You can see this status when you view an offer that requires an approval.
• Offers that do not require approvals directly move from Design Complete to Ready to Publish status when you confirm the offer design
• If you change the default approver in a sequential approval process, the type of approval reverts to the default approval type of parallel approval. This is because you would be changing the default resource hierarchy for a resource.
• You can define multiple overriding approvers for an offer but there can be only one default approver.