Does anyone know what this option does within the manual fulfillment node?
Complete work assigned if activity is verified
Haven't tested it, but I can assume based on the wording that if you have a task assigned to someone and the system collected that item (which should be provisioned) then this activity will closed and manual work will not be required.
I've tried to add a manual fulfillment after a fulfillment handler completes its verification but the manual fulfillment or activity in the workflow always gets completed without assigning the task.
Can you share a screenshot of the workflow please?
What is the purpose of a manual node after the fulfillment handler? Has the manual node been configured to assign the task to an individual?
The fulfillment handler below fires off and eventually gets marked verified after collection.
After the above workflow completes we wanted to assign an individual activity or fulfillment to 2 users to go verify something and then either mark the manual fulfillment completed or no longer needed.
But no matter what i do the manual fulfillment task always gets marked completed automatically or throws an error if i don't give it an automatic path to follow.
Based on that it sounds as though the change is already completed by the time it reaches manual fulfillment.
Are you seeing and changes listed against the runtime data for the manual fulfillment node?
Yes the change is completed prior to the manual fulfillment.
Any idea's for a workaround?
Did you ever get a workaround for this issue? I'm facing a similar problem.
Clive Morrish and Boris Lekumovich what do you recommend in cases like this where one may need to have a sub-process after verification occurs? For example where you need to validate if specific attributes on an account were successfully set after the account was created. It doesn't seem like a manual fulfillment node is designed to accommodate for that after reading this thread.
Additional detail: I need a way to ensure an attribute is always set and if it failed (for whatever reason) have it assign activity within IGL to a user to manually complete. Then when they complete that activity the request would continue on within the sub-process.
Is this a real scenario? An account is provisioned successfully but one if the account's attributes is not set?
One approach to consider.
Just before the Stop node, add a SQL node and check if the collected account has the relevant attribute configured as expected.
If not, use a provisioning node to update that attribute (update command).
If yes, then proceed to stop.
Retrieving data ...