Example of Configuring MDF Pre-Approval Validation

Since brand owners don't have identical approval processes, MDF provides a flexible and quick way to create pre-approval validations that meet your specific business needs. If your business processes change, you're able to change your validations accordingly.

Sales administrators can use Application Composer to create customer-defined validations that run before an approver takes action on a submitted MDF request or MDF claim. In this example, a sales administrator for a brand owner creates a validation that ensures MDF requests can only be approved if a budget is associated to the request. When this validation is activated, approvers receive an error message when they try to approve a MDF request that doesn't have an associated budget.

Each human task action requires a separate validation. After you create the validation in Application Composer, you must create a profile option whose value is the name of the object function that will be invoked when the human task action executes. You can configure validations for the following human task actions:

• Return

• Approve

• Reject

• Withdraw

To create the pre-approval validation, sales administrators must:

• Create the validation in Application Composer as an object function under the MDF request object, server scripts link.

• Create a site level profile option with a value that's the same as the name of the object function that will be invoked.

Create and Configure the Validation

Use the following steps to create and configure a validation for MDF requests that ensures a MDF request can only be approved if a budget is associated to it.

1. Sign in with your sales administrator credentials.

2. Ensure that you're in a sandbox.

3. Navigate to Application Composer.

4. From the list of Standard Objects, select MDF Request.

5. Select Server Scripts, then select Object Functions, and click Create.

6. On the Object Function page, provide the following:

   • Function Name: type a name for the function, such as validateMDFRequest.

   • Return: select String.

7. In the Parameters area, click Create and provide the following:

   • Name: type a name for the parameter, such as parameter.

   • Type: String.

8. In the Function Body area, type the following:

   def context = parameter?.tokenize(';='); // Replace 'parameter' with whatever parameter name is defined in the object function, in this case it is 'parameter'. .

   def stage = context[1];

   def participant = context[3];

   def user = context[5];

   if(BudgetId ==null && stage == 'SoaOLabel.RequestBudgetFundRequestApprovalStageTwo'){ // This condition is on the second stage which is final stage for the seeded flow

   return "A Budget must be associated to Fund Request before the final approval"; // Error message to be shown on UI if the validation fails

   }

   return null; // Return null otherwise, which means the validation is successful.

9. Validate the script and click Save and Close.

Create and Configure the Profile Option

Use the following steps to create and configure the profile option for the previous validation.

1. Sign in with your sales administrator credentials.

2. Ensure that you're in a sandbox.

3. Navigate to Setup and Maintenance.

4. Search for and select Manage Profile Options.

5. Create a new profile option with the following values:

   • Profile Option Code: MKT_FUNDREQUEST_APPROVE_VALIDATION_OBJFUNC (This is the code for Fund Request approve validation; the codes are predefined for object/action validation and must be defined exactly the same)

   • Profile Display Name: Fund Request Approve Validation Object Function

   • Application/Module: Marketing

   • Start Date: Provide a start date for the validation.

6. Click Save and Close.

7. Select the Enable check box for the profile option at the Site level only and select the Updatable check box at the site level only.

8. Click Save and Close.

9. Test the validation by approving the FundRequest without providing the Budget. It should display the message what was returned in the groovy. Once you complete the testing you can publish the sandBox.