Document toolboxDocument toolbox

Nexus Documentation
CURL vulnerability information (CVE-2023-38545) - Nexus awareness advisory on Microsoft's update KB5014754

Cards - Approval handling

Owned by Ann Base (Deactivated)
Last updated: Dec 08, 2023 by Ylva AnderssonVersion comment
2 min read

Use case scenario

Approval handling for use cases where changes need to be approved before they can be executed.

This article describes the approval handling for the Cards package. The approval step is used in different use cases for Smart ID Identity Manager, such as Request card, Deactivate card, Reactivate card, Lock card, and Request multiple cards. Read more here: Smart ID Workforce use cases

The approval handling is used when someone else has to approve something before you can proceed with the use case.

Approval handling and step-by-step instruction

  1. An information text is shown in Identity Manager Operator that an approval is needed.

  2. The approver receives an email with information that there is an approval request.

  3. The approver logs in to Identity Manager Operator.

  4. Go to the SEARCH tab.

  5. Select Requests from the drop down menu and click Search. A list with all open requests appear. 

  6. Select the request you want to approve and click Card approval. A card approval form appears with:

    1. Request information -  with the request itself (that is, what the requested change is about)

    2. Card information - with information about the card

    3. Requester information - the person that is asking for the approval (the 'requester').

  7. The approver clicks one of the buttons:

    1. Approved → The approver approves the request.

      1. The requester receives an email notification that the request is approved.

    2. Reject → The approver rejects the request and must add information in the Reason for rejection text field.

      1. The requester receives an email notification that the request is rejected.

    3. Postpone → The task is visible in the "What do you want to do" list and the approver can do the task later.

Use case details



Sub process description

As an operator I want to have a general sub-process for all approval scenarios

Outcome

  • The approvers receive an email notification that there is an open request for approval

  • If the request is approved, the end state is "approved"

  • If the request is rejected, the end state is "rejected"

  • The requester receives an email notification that the request is approved or rejected

Symbolic name:

CardsProcApproval

Process name:

Card approval

Component:

Identity Manager Operator




Related information

Copyright 2024 Technology Nexus Secured Business Solutions AB. All rights reserved.
Contact Nexus | https://www.nexusgroup.com | Disclaimer | Terms & Conditions