Defining the Approve workflow step

CRM Workflows supports an Approve action step that can be added and defined in the CRM Workflow Designer tab. The Approve step replaces the Approval step and used to define the required approval or set of approvals. You can define multiple approvers or observers and set the approval requirement based on a number or percentage.

  1. Click the Workflow Designer tab. See, Workflow Designer Tab.
  2. Click the Add icon to add an Approve step that proceeds the Approve step you want to add. The Insert New Workflow Step window is displayed.
  3. Select the Approve step. The Approve step is added to the workflow. See, Inserting a new CRM workflow step.
  4. Double click the Approve step or right-click the Approve step and click Edit in the Icon view to view the Approve step editor.
    Note: You can also click the Settings icon in the upper right corner of the card in the Card view.
  5. Specify this information on the General tab:
    Caption
    The text that displays as a label.
    Delay Duration
    The numeric value for a number of days, hours, or minutes after the previous step to delay before this step is generated.
    Delay Increment
    The Days, Hours, or Minutes after the previous workflow step to delay before this step is generated.
  6. Click Edit Condition to define the condition based on which the step is triggered. See, Defining CRM Workflow step conditions.
  7. Specify this information on the Template tab.
    Subject
    The text that must be displayed in the email subject. Use the @- mention user interface to include dynamic CRM content in the subject content.
    Note:  The @ mention token menu is not displayed if the @ character is preceded by an alpha or numeric character without a space. Examples:
    • Typing name@ does not display the @ mention token menu.
    • Typing name @ displays the @ mention token menu.
    Email Body
    The text that must be displayed in the email body. Use the @- mention user interface to include dynamic CRM content in the email body.
    Note:  The @ mention token menu is not displayed if the @ character is preceded by an alpha or numeric character without a space. Examples:
    • Typing name@ does not display the @ mention token menu.
    • Typing name @ displays the @ mention token menu.

    Format date, date/time, numeric, and currency properties for a specific regional format by adding the @ character and standard locale code after the CRM content you want to format. For example, DateOpened @fr-fr

    Format the text content of the email template. Possible values:

    • Bold, italic, or underlined content
    • Numbered or bulleted lists
    • Multiple font sizes supporting heading levels of 1 through 6, along with the normal paragraph font size
    • Font color and background color selections
    • Standard browser fonts of Sans Serif and Serif
    • Left, right, and center text alignment
    Note: Use the Tx icon to clear all formatting from the selected text.
  8. Specify the email recipient related data on the Recipients tab:
    1. Specify in the To(CRM Approvers) or CC(CRM Observers) fields one or more email addresses or use the @mention user interface to include CRM users, teams of users, or departments of users in the set of CRM Workflow approvers. Possible scenarios:
      • Adding a User: Enter @ followed by a user field. For example, AccountManager or Owner.
      • Adding a Team: Enter @ followed by the name of the team to send the email to all users on the team. For example, @Global
      • Adding a Department: Enter @ followed by the name of the department to send the email to all users on in the department. For example @Marketing
      Note: 
      • Multiple addresses must be separated by semicolons.
      • Properties and the related entity email properties are available displayed only if the Expose to Workflow field or property attribute is set to True. For example, for the Return.Returned By field to be available, the Return.ReturnedBy relationship to the Expose to Workflow Contact entity attribute must be set to True.
      • For custom email properties the data Type property or field must be set to Email. All standard email properties have a type of Email.
    2. Press Enter or click out of the field to add the entries to the distribution list.
    3. Use the check boxes in each grid row to determine if the intended recipient of a user or owner field token is the user, user’s manager, or both. If the token field is a user or owner field, and you clear all of the check boxes, then there will be no recipients for that token.
      Note: These check boxes are editable only for user or owner field tokens. If the owner of a record is a team or department, the Send to user’s manager selection is not considered since departments and teams do not have a manager. Possible scenarios:
      • Sending an email to the user: Select the Send to check box and clear the Send to user's manager check box.
      • Sending to an email to the user’s manager: Clear the Send to check box and select the Send to user's manager check box.
      • Sending the email to user and the user’s manager: Select the Send to check box and select the Send to user's manager check box.
    4. Click Remove, to remove an item from the grid.
    5. Click the Maximize or Minimize arrow to display or hide a grid
  9. Perform one of these actions to define the approval criteria for the Required to Approve field:
    • Select the Percentage of approvers option and specify the minimum percentage value in the Value field to define the minimum percentage of the CRM Approvers required to approve the step.
    • Select the Number of Approvers option and specify the minimum number in the Value field to define the minimum number of CRM Users required to approve the step.
      Note: You can also use the Number of Disapprovers field to specify the minimum number of CRM Users required to disapprove the step, if required. For example: The To (CRM Approvers) field contains 3 approvers and Number of Approvers is set to 1:
      • If Number of Disapprovers is not specified, then all 3 approvers must disapprove in order to deny the step.
      • If Number of Disapprovers is set to 1, then if any one of the approvers disapproves, the step can be denied.
  10. Specify the number of days for the approval step in Days To Expire field.
    Note: 
    • Expired approval steps result in an approval status of Expired.
    • You can use the @mention value of @$ApprovalStatus Equals Expired, Approved or Disapproved when defining conditions of subsequent workflow steps.
  11. Click OK to save the approve step.
    Note: 
    • Create and define the next step if the approve step is approved:
      1. Click the Approve Add icon after the Approve step.
      2. Select the required step action.
      3. Define the step.
    • Create and define next step if the approve step is canceled:
      1. Click the Cancel Add icon after the Approve step.
      2. Select the required step action.
      3. Define the step.
    • Create and define next step if the approve step is denied:
      1. Click the Deny Add icon after the Approve step.
      2. Select the required step action.
      3. Define the step.