Hello Team,
In ISC we have identities with specified end date.
Target give users manager to give possibility to extend Identity end date.
Idea was to achieve this with forms and workflow.
We send form to manager, if extension of end date is needed manager in form picks up calendar date or types it in and than workflow kicks is and updated “End Date” attribute in ISC for specified identity.
But after research seems that the workflow does not support the account/identity update (Only Delete, Disable, Enable and Unlock are allowed) .
Any ideas on this. Is there a way to cover such a use case in ISC ?
I can see one possible solution, but it is a bit complicated and restricted.
I’m seeing an extra lifecyclestate = “extended”. The workflow could then send a HTTP request to the V3 endpoint /identities/:identity-id/set-lifecycle-state.
The end date identity attribute could then be utilizing a transform with pseudo-code:
if (lifecyclestate == "extended") {
endDate = now + 14 days
}
It would then only extend a set period of time at once, but maybe you could configure this in another way. I’m not entirely certain you could make this work, or if it would be a satisfactory solution to your problem. It was just an idea I had.
Perhaps there is a way easier solution to your problem, but I don’t think you can change the End Date immediately as per your proposed solution.
You can use the HTTP Request Action in workflow to update the transform. Just provide the connection details and API details like URL, Body to configure the HTTP action.