Share all details about your problem, including any error messages you may have received.
We are integrating an application with IIQ. But, instead of using the OOTB “Manage Access” role-based workflow, we have designed a quicklink which prompts a form to the user to make the required entitlement selection, which invokes the LCM provisioning workflow to submit the access requests. On the form, if the user selects 4 entitlements, 4 different access requests are submitted due to the requirements on the approvals. But, when the user submits the form, IIQ is taking almost a minute to submit the requests and sometimes it is throwing a severe error without any error codes. Even though we are getting severe error, the requests are getting submitted. Is there a way for us to increase the time for the request to error out or any inputs to have this optimized?
This is intermittent and is not happening all the time. One thing we tried was using foregroundprovisioning as true in the WF, but that is requiring performance maintainance to be run everytime to get the actual provisioning triggered.
Once your form is submitted how do you trigger the access request workflow for each entitlement selected. Are you using RequestManager to schedule the workflows or using any other approach.
The best approach would be to set the foregroundprovisioning as false and let the perform maintenance trigger provisioning in background to provide better user experience.
We are creating the plan in the workflow and in the step of building the plan, we are triggering the LCM Provisioning workflow via a rule library using the workflow launch method
I believe the workflowlaunch call waits for a return response from the workflow and hence you may be facing this issue. The following thread highlights similar issue. You can either try to launch the workflow with foregroundprovisioning false or use RequestManager to schedule the workflow.
@mbommakanti3298 - the “severe error” from the UI is so frustrating, so if the foreground provisioning takes more than 30 seconds you will see it. Definitely setting set the foregroundprovisioning to false as Sanjeev mentioned is a good way to prevent that.