Which IIQ version are you inquiring about?
8.4
8.4
Try running “Perform Maintenance” task.
Could you please elaborate a bit more? If the task is currently waiting on a manual work item, I wouldn’t consider it to be “hung,” since there is a dependency that must be completed before the task can close or move forward.
Is the issue that the task is still not completing even after the manual work item has been fulfilled?
You can track down the workflow case for the request, and then check the current step of that workflow case to see where it is waiting on.
@AJGibson76 Please provide more details to your request like whether it is awaiting manual response or it is waiting for server to assign a thread. Also, is it happening for all requests belongs to all apps or only to a specific application.
Note: Found a fix? Help the community by marking the comment as solution. Feel free to react(
,
, etc.) with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.
Tried that, still hung.
The root of question is this: how do I get provisioning tasks to complete, even if manual work is still outstanding? I tried backgroundprovisioning, but that didn’t help. What does endOnManualWorkItems do?
If the workflow variable endOnManualWorkItems is set to “true” and the provisioningProject returned by the Initialize step includes an unmanagedPlan, which required creation of an IdentityIQ work item assigned to a user to complete the provisioning action, this step sets an error message which will be reported to the requester through the user interface, and the provisioning process terminates.
can refer to the LCM doc here: https://community.sailpoint.com/t5/Technical-White-Papers/Lifecycle-Manager-Workflows/ta-p/71301
Hey Andrew, following up on Robert’s post. I think the flag you want here is optimisticProvisioning.*
Flag which makes the workflow treat the provisioning process as successful even when it is in a queued status; usually used for demo mode, but occasionally used for systems managed through a ticketing system or provisioning system which are not frequently reaggregated into IdentityIQ
You can try setting that to true and see if it accomplishes the functionality you’re looking for.
@AJGibson76 backgroundprovisioning is for a different purpose where you want to decide how you want to execute your provisioningplan/request. Whether you want to execute it immediately or background it by adding it to the queue picked up by Perform Maintenance task.
In your case, if request is open when manual work item is getting generated, you need to close it first to mark request as completed. You might want to give it a try with : optimisticProvisioning as suggested by @ronald_davis .
Note: Found a fix? Help the community by marking the comment as solution. Feel free to react(
,
, etc.) with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.