Reject a Request

A Role Processor can reject a request (a role > task combination) for a Review role.

Before performing this task, a request must have been submitted via the Content WebApp. The request must have passed to the Review role after all dependencies are complete for the Application role and the final Application role (the role with the highest priority) is finished.

Refer to Review a Request Overview for general information about the review process.

A Reviewer may enter a reject reason for a Review role. The Reviewer may then click Reject for the Review role. At that rejection time, the user assigned to the Application role for the request receives a notification about the rejection depending on how the user and role are configured. That email contains a link to the Request Role page, so that the user can update the request as needed and finish the Application role again.

When a Review role is rejected, the review role is reset. Refer to Reset a Role with a Review Role Type for more information.

NOTE: If the User Response Required on Warnings option is enabled at the Role or Scenario role level, after a user clicks Finish for the role, any validation failures require a user response to continue the process.

To reject a request in dspConduct™:

  1. Select dspConduct > Requests in the Navigation pane.

  2. Click the Roles icon for a request.

  3. Click the Tasks icon for a Review role.

    NOTE: The Tasks icon for the Review role is disabled until the Application role(s) with the highest priority is finished.

  4. Click the TASK ID button to review changes entered by the Application role(s).

  5. Navigate back to the Request Role Task page.

  6. Click the Reviewer Workbench icon on the Page toolbar.

    NOTE: The Request Review Task page opens in a new tab so that the Role Processor can review the task while working on the rejection.

  7. Click the Roles icon for the task.

    NOTE: The count on the Roles icon is the number of roles for the request. The count may not reflect the number of roles that display on the Request Role page for the current user. The current user can only access roles to which that user is assigned and roles that have the Auto Extend Display setting enabled.

    NOTE: The request is not rejected until this icon is clicked. The Request Role Task page displays all of the Application tasks that are assigned to Application and Display roles in the scenario. Application tasks are the only tasks that display, as these are the only tasks that can be edited.

    NOTE: If the same task is assigned to multiple roles, the Review role can reject a specific role > task combination.

    NOTE: To search for a field in the request and the roles that can access that field, the user can click the Column Search icon. Refer to Search for Scenario Role Task Column Assignments while Reviewing a Request for more information.

  8. Click the Review Changes icon on the Request Review Task page to display the updates to the task to determine whether to approve or reject them.

  9. Click Edit for a role assigned to the task to reject.

    NOTE: Multiple roles can be assigned to a task and rejected individually.  

    View the field descriptions for the Request Review Task Roles page.

  10. Click the REJECTED check box to enable it.

  11. Enter the reason for the rejection in the REJECT REASON field.

    A rejection reason is required when rejecting a role.

  12. Click Save.

  13. Click the Reject icon in the Page toolbar of the Request Review Task page.

    NOTE: The request is not rejected until this icon is clicked.

The Application role is reset. The Finish icon for that role is active and the request must be updated and finished again.