The opproach which is mentioned here to complete disable operation works perfectly when there is a need to make two calls. I want to check will this also support for other operations like Update Account. Like do a GET first and then PUT in the similar way which is mentioned here.
Also when the second Disable Account-2 operation is completed and if there is response mapping to update account attributes like isActive I do not see that being updated. Can you provide some more examples on how to update account attributes along with turning the account to disabled status in IDN.
In my before and after operation rules I have other logic to make some endpoint calls nothing to manipulate the response that I receive from disbale account operation.
We integrated the same Blackline application in our project too. For disable endpoint, except for isActive value all others are not required to be changed.
As the values are not changed, except for isActive other values are not expected to be present in the plan. Eg: $plan.firstname$ will always return empty. Here is what you should do to achieve the usecase:
Declare Two operations for Disable Account
Use the first one as a Get Single user endpoint and capture the needed attriubtes like firstName, lastName, etc
Define the second endpoint of Disable Account as the actual disable operation. Populate every other attribute using the previous response as, eg: $response.firstName$ etc. Declare isActive value alone as false. You do not need a webservice rule for this one.
Thank you for the suggestion. Yes, you are right and I am already using two operations for Disable Account as BlackLine endpoint need firstname, lastname, timezone, etc., attribute when disabling the account. I followed this approach
As I have mentioned earlier the purpose of the rules is a specific use case and I need them.
Well since you have integrated BlackLine I want to understand this. When you trigger disable operation and when the operation is completed/commited. Are you seeing both Account status changing from Enable to Disable and account attribute isActive changing from true to false without any single account or full account aggregation?
In my case i see only account status changing to Disable but isActive attribute is not changing to false. To see the change in IDN I have to run single account aggregation. There is no error and isActive attribute is properly set in target system.
If you are able to see both changed without any aggregation can you suggest what should be done to fix this.
You are right, it needs full aggregation or single aggregation to have the isActive value pulled back to IdentityNow and updated on the account level.
But, if you are concerned about not having the immediate update, you can add a 3rd endpoint for Disable/Enable Account operation with a single account aggregation after the actual disable/enable operation. This will fetch you the updated data immediately.