Restrict approval for all Remove Requests

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Which IIQ version are you inquiring about?

8.4

Share all details about your problem, including any error messages you may have received.

Team,

We have a requirement to restrict approval for all Remove Requests (via Manage Access) to only the Manager approval. This means that while the Add Requests should follow both “manager” and “owner” for a two-level approval process (approvalSchema: manager,owner), for Remove Requests, the Owner’s approval should be Ignored/Skipped.

We have a variable to define from UI, even though the value sets “true”, we should skip the second level of approval for Remove requests.

<entry key="additionalApprovalRequired">
        <value>
          <Boolean>true</Boolean>
        </value>
</entry>

Any suggestion/Ideas to implement this use-case?

2
  • For Add Requests: The approval schema would be manager, owner.
  • For Remove Requests: The approval schema would only be manager, skipping the owner’s approval.
  • Use the additionalApprovalRequired variable to conditionally adjust the flow based on whether the request is an “Add” or “Remove”.
2 Likes
3

Modify additionalApprovalRequired Based on Request Type: You may need to ensure that when it is a “Remove” request, you effectively set the additionalApprovalRequired to false, overriding any default behavior for additional approvals. If it’s an “Add” request, the behavior will follow the two-level approval process.

4

Conditional Logic in Approval Flow: Use the logic in your code to check if the request is a “Remove” request. If it is, you can modify the approval flow by skipping the owner approval, otherwise, follow the default two-level approval process (Manager → Owner).

example code :



manager <#else> manager,owner ]]>


1 Like
5

Thank you Chaitanya!

6 
   ;;;;;;;;;;;;;;;              welcome    harish
7

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.