Workflow Rejection Reasons

You can configure the rejection reasons that appear for selection on the Reason drop-down list of a change.

For the rejection reasons to appear on a change in the UI, you must do the following:
  • Create lookup codes for rejection reasons
  • Add the rejection reason to a change type
  • Add task in the BPM Worklist

To create lookup codes:

  1. Search for and click the Manage Workflow Rejection Reasons task in the Setup and Maintenance work area.
  2. In the page that opens, click Actions > New or the plus (+) icon to create a new lookup code for rejection reasons. You can create multiple codes.
  3. Enter a value in the Lookup Code field and a number in the Display Sequence field.
  4. Select the Enabled checkbox.
  5. Enter a Start Date, End Date, Meaning, and Description.
  6. Click Save and Close. Now that you've created a rejection reason, you must add it to a change type.

To add the rejection reason to a change type:

In the Setup and Maintenance work area, go to the following:

  • Offering: Product Management
  • Functional Area: Change Orders
  • Task: Manage Change Order Types
  1. Open the change type for which you want to configure rejection reasons (ECO or CCO).
  2. In the Edit Change Order Type page, navigate to the Rejection Reasons table.
  3. Click the Create (+) button.

    When you create or edit a change order type, the Policy tab displays the Rejection Reasons table with the following attributes: Sequence Number, Rejection Reason, Inherited, Enabled, Start and End Date.

  4. Search and add one or multiple rejection reasons to the Rejection Reasons table.
  5. Click OK.
  6. Click Save and Close.

    You can delete a rejected reason in the table, but you can’t delete the inherited rejection reasons in the table of the child change order.

To add the task in the BPM worklist:

  1. Navigate to the Setup and Maintenance and navigate to Tasks.
  2. Search for and click Manage Approval Groups task. The BPM Worklist opens.
  3. Click Task Configuration. Search and access ChangeOrderApprovalTask > Configuration.
  4. Set the ‘Require reasons for rejection’ attribute as Optional and Rejection Comments as Required and click Save.
  5. Click Commit Task.

When the user clicks the Reason drop-down list from the Reject button of a change type, the rejected reasons that were added appear in the list. You can configure the rejection reasons on change orders, change requests, problem reports, and corrective actions.

Note: Rejected reasons are inherited down the hierarchy of change types.