Processes in the Lunch Scheduler application

The Lunch Scheduler application uses three separate approval processes that run serially. Approval processes that are designed to run serially are referred to as a chained approval process. Two of the processes run conditionally, using a condition statement to determine whether the process is required for each request. To see how each process is initiated and how the processes are chained together, see Chaining-approval-processes.

Related topics

Using-the-Lunch-Scheduler-sample-application

Chaining-approval-processes

Management cost authorization

This process is a Parent-Child process that runs first and acts on every request. It uses Auto Approval and Self Approval rules to determine if the requester has authority to approve his or her own request. If not, the approval process routes the request to the manager by using the AP-Sample:Signature Authority form. The Approval Server routes the request to subsequent managers until a manager with sufficient authority signs the request. If no one with sufficient authority can be found for an individual, or if an individual has no manager, the process terminates with an error.

The filter AP-Sample:Start Cost Approval starts the Management Cost Authorization process. This filter uses the following application command:

Application-Command Approval New-Details -t "Management Cost Authorization"

In this command, the -t option identifies the name of the process to run. For more information, see Process-commands.

Major account level approval

This is a Level process that runs if the request is for lunch with a major or enterprise account. The process uses a Completion rule to stop lunch requests for major accounts from advancing beyond the major account level. Only enterprise accounts need to go to both the major account and enterprise account levels. The Account Type field on the request form identifies the account as a major or enterprise account.

The filter AP-Sample:Start Level Approval starts the Major Account Level Approval process. The Run If criteria in the filter must be met for this filter to run. The filter uses the following command:

Application-Command Approval New-Details -s "$SCHEMA$" -e
"$Request ID$" -t "Major Account Level Approval"

In this command, the -s option identifies the name of the approval request form, the -e option identifies the request ID for the current request, and the -t option identifies the name of the process to run. For more information, see Process-commands.

Special overdue approval

This process is a Rule-Based process that runs only if the company currently has an overdue account. This process includes an example of using Prep Get Next Approver rules, which retrieve and set data for Get Next Approver processing. The Account Overdue check box on the AP-Sample:Company form identifies whether the account is overdue.

The filter AP-Sample:Start Overdue Approv starts the Special Overdue Approval process. The Run If criteria of the filter must be met for this filter to run. The filter uses the following command:

Application-Command Approval New-Details -t "Special Overdue Approval"

In this command, the -t option identifies the name of the process to run. For more information, see Process-commands.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*