Change order status when job is FROZEN

I think it should be possible to change it to unsubscribed in the object browser, I just did that in my v6 environment.

I would suggest you look at the order of steps in your process. Try to mark the PersonWantsOrg as assigned only after the script has finished executing. I believe you can do this if you invoke an event (using EX) in your workflow, let that event trigger a process which first calls the script then sets the PersonWantsOrg as assigned. That way until the script has finished running the PersonWantsOrg will remain in the order state.

One question, why do you have the need to change the order state of a finished request, when a subsequent process will fail?

Imagine that at IdM side product is "Assigned" but there is no change in Target System until one of a process step is FROZEN. It might be confusing for an end user because he sees in IdM that he should has it but in fact he does not.

Ok, but when you will change the value of the request it normally has been finally granted. So, all subsequent jobs were already generated (e.g. info mail for the requester that the product has been assigned).

What I will say is, you should better leave the request in its original state and should get in touch with the customer / employee / requester / whatever to tell him the special situation, that there is currently a technical Problem and that you are working on it .

I would never change the request state, when a subsequent job fails. When we have FROZEN jobs we will see that we fix them asap and if we have a greater problem where more than one user is affected and where we need a longer time to fix it, we will publish a notice on the main site of our intranet page.

-
Regards
Sven

I agree with Sven, hence my suggestion that you don't mark the request as Assigned till you have confirmation that the request has been completed in the third party.