Hi All,
Currently, I have created a custom BRF+ rule which has below mentioned configurations:
The path is simple: Requester->Manager->RoleOwner
The action for "New Account" request type is: Assign Object
The action for "Change Account" request type is: Assign Object
I have below provisioning settings:
This way request is getting created successfully. However, what is happening is that, if a user is already created in the back end system and now try to raise and submit another request for him in the same back end system with request type "New Account", system does not object and simply modifies the existing user account with the details mentioned in the request. This seems not to be the ideal scenario. Actually, system should give me error for this user's available and request should not be allowed to submit. If a "Change Account" request type is submitted, then it is normal and user should be updated in the back end system accordingly.
I changed the provisioning settings to:
and the actions for "New Account" is: Create User and Assign Object. For "Change Account", it is: Assign Object.
If now I try to raise and submit a request of "New Account" type for a user who is already available, then system stops and and gives error. However, for another user who is not available in back end system, the workflow is getting failed citing: "No Role Owner Found".
Not sure why this is failing. Any idea?
Regards,
Faisal