Share all details related to your problem, including any error messages you may have received.
Recently the system was upgraded from v8.1 to v8.3 p3, after the upgrade the role approvers were complaining that the approve button does not work straight forward.
After clicking multiple times (more than 10 times) the complete approval screen comes and approvals are done. This behaviour is not seen in the earlier version.
Approver having more than 40 approval requests to complete. As there is no bulk approval button in approval screen, approver has to click multiple times which is creating a bad user experience.
It looks like after the approval an provisioning actions is taken place and this provisioning is now running the the foreground, while before the upgrade it was configured to run in the background.
What I would do is to copy the OOTB workflow and change provisioning to run in the background using the following steps (please first test this in a lower non-production environment as a wrongly configured workflow could produce a lazy-initialization error when running in the background):
Copy workflow/Business process
Goto Setup->Business processes
Select āLCM Provisioningā Business Process
On the bottom right click āSave Asā
Provide a new name for the Business Process like <customer abbreviation> - LCM Provisioning
Change foreground to background provisioning
For the new Business process goto tab āProcess Variablesā
In section āAdvanced Settingsā uncheck option āRun provisioning in the foregroundā
Save the Business Process
Use new Business process for Access Requests
Goto the gear ā Lifecycle Manager
Goto tab Business Processes
Change request Access to use the newly created Business Process <customer abbreviation> - LCM Provisioning
Save
Test this new setting by requesting a Role and approve the request.
Can you enable logging for the workflow? This might give an indication on what the (adjusted) āLCM Provisioningā-workflow is doing during the āApprove and Provisioningā-step.
Enable logging by adding the following lines to the log4j2.properties file:
Normally, the things that @Remold suggested apply, making the submittersā and approversā experience smoother. In this case, if it is related to the upgrade to 8.3, it may indeed be a known issue.
Engineering is working on a fix that will make the plan compilation run faster. Weāve seen that larger requests for identities with already larger amounts of access may take a bit longer than expected. This affects multiple places of the request, approval and provisioning process as the plan is (re-)compiled several times.
If your situation is urgent, work with the CSM team and get the customer name added to SET-15328. There is a temporary, non-official fix that may be applied in the meantime. UPDATE: The fix is included in the latest patches: https://community.sailpoint.com/t5/IdentityIQ-Server-Software/ct-p/IdentityIQ
Thanks @menno_pieters for the update. We have raised a case for the same. will let the case engineer know if they can add the customerās name to SET-15328