I have two disable operation first operation fetches id from a endpoint, fetched id is used in 2nd disable operation which calls different endpoint.
Basically, my ask is can we call the 2nd disable operation only if ID is found from first operation? Is it possible without before operation rule?
Currently if id is not found from first operation then it gives Disable Account Failure which I don’t want.
Hi @Amrit1897,
If you do not want to use a beforeOperation rule then, there is no way to stop the operation as the operation is same and probably you have parent child relation for the HTTP operation.
But if you do not want to see an error then you do a hack just add the error response code to your success code.
For e.g. if it’s throwing 400 then add it in your success code in the operation. But in that case even if you’re account is not disabled in target you will see account is disabled in IDN, but next aggregation you will see it as enabled.
If you don’t want to see that account as disabled until next aggregation the add another child operation as single account aggregation.
By this way you won’t see that particular error and account will still be enabled.
Hope this will help!
@shekhardas1825, Can you please suggest how can we achieve by using before operation rule?
Hi @Amrit1897 If you want to use beforeOperation rule then you do not need 2 operations configured for disable. You can configure one and attach the beforeOperation rule to it.
You can have two methods where you will execute API:
First method will get the id, if id is returned true then execute the second method.
Here is the SailPoint documentation for beforeOperation rule:
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.