OIM Provision Problem--Create User or Update User

Question

How can we control the provision process to meet the following requirement?
If the target application exits the user, there is no need to call the createuser task, just establish a link with the user of target application. But if it is a new user, we must complete the createuser task to provision the user to target application.
At first, thanks for everyone's advice, I should restate my requirement in order to make it clear.
The provisioning scenario is as follows:
If the user exists in target application, update the user of target application. Otherwise, create the user.
Thanks!
Message was edited by:
user627209

Answer 1

I think it would be very helpful if you restated your exact requirements.
As a general rule it is not advisable to just map the "object already exists" adapter return code to a task status that gives the object effect of provisioned as in some cases there is a need to copy a unique object identifier back to the process form (i.e. in AD you need to have the GUID(?)) from the target system. Without the identifier the update tasks will not be able to find the object in the target system.
You could of course copy the identifier manually in another task but you have to make sure that you have done everything that you need to do to actually get object into a linked state.
Another alternative is to trigger a recon task using the APIs when you run into the "object already exists" situation.
Hope this helps
/M