Our understanding of IMG access request workflows was that for collected applications you include a Wait for Verification node at the end of the process. This then waits until the requested change (add OR remove) is collected - only then will the changes be marked as Complete and the associated change request completed (assuming no other pending changes).
Question is - what is it in the workflow that changes the state of a change detail from Pending Action to Pending Verification? We want to identify changes that have gone through all the configured activity in the fulfilment workflow and are just waiting for the changes to be made on the endpoint application and collected back into IMG.
I understand the different states but how do changes get moved from one state to another? What is it that makes that change?
Hi Andy,
The change requests go through these states:
1) From request creation, until the first approval phase is entered, the request is in an OPEN state (you might not even see this state if you don't have logic that executes prior to approval).
2) From first approval phase to the time the first fulfillment phase workflow is entered, the request is in PENDING APPROVAL.
3) From the beginning of the first fulfillment workflow, the request is in PENDING ACTION. There's 2 ways it can make it from pending action to pending verification:
a) AFX fulfillment handler- If you use the default AFX fulfillment handler, it will automatically update any line items that it didn't see an error for to pending verification
b) Manual fulfillment nodes- if you are using manual fulfillment, those nodes also update to "pending verification".
4) To move to a completed status, you either need to use a "Mark complete" node in the workflow, or allow the data collectors to close them out for you.