Webservice After operation rule for Account Aggregation

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

Hi I am trying to update group attribute in the whole account schema though webservice after operation rule. The issue is other schema attributes are getting blanked after rule execution is it expected

2

Hi @SrideviJaya
In your after operation rule, there must be something amiss with how the processedResponseObject is being updated.

Can you ensure the response mapping is as you’d expect, and try printing the raw response JSON for validating your JSONPaths used? If the paths are correct and your response attributes are getting updated as expected in the processedResponseObject, check if you’re overwriting the map entries in your rule which might be causing this.

3

Do you mind sharing your rule?

4

Hi , Now passing the remaining schema attributes from the raw repsonseobject

5

Hi,

It is not an expected behavior for other account schema attributes to get blanked when you update just the group attribute using a Web Service After Operation Rule. The problems could be:

  1. Full Account Object is Overwritten
    If your rule is using a web service call (like PUT or PATCH) and you’re sending only the group attribute, but the target system expects a complete payload, then all unspecified fields may be overwritten with null.

PUT usually replaces the entire object — this can lead to blanking of other attributes.

PATCH is safer for partial updates — but only if the endpoint is implemented to support it properly.

  1. Connector Configuration
    If you are using custom connectors or rules for updating, and the full account object is fetched before modification, an improper manipulation or omission might result in the unintended clearing of data.

  2. Improper Cloning or Use of Identity/Account Objects
    If you are modifying the AccountRequest or ProvisioningPlan objects and not cloning or preserving the original values, the downstream provisioning might send nulls inadvertently.

Regards,
Anusha Nallagorla

1 Like
6

Hi

It depends how your after operation rule is providing the response.

Print the responses to know how it papulating and add the schema attributes path accordingly.

If other attributes are missing in your code chrcj your code to get all attributes along with custom attribute.

1 Like
7

Hi , I am now adding all the schema attributes along with the calculated group attribute as part of rule to the aggregation endpoint.

Initially I passed only calculated group via rule and thought other attributed will be fetched as part of the actual account aggregation endpoint configurtion

1 Like