Hi @gauravsatyawanb, this behaviour is expected in ISC, and even in IIQ.
When a provisioning policy is configured for attribute sync, ISC generates a provisioning plan that includes (only the attributes that have changed) since the last aggregation or provisioning event. Therefore, if only the phone attribute is modified, the plan will not include firstName, lastName, or email unless they were also updated.
Since your target system’s API requires firstName, lastName, and email as mandatory fields - even for partial updates - you’ll need to ensure those fields are always included in the provisioning plan.
To address this, you can implement a rule tied to the Update operation that inspects the identity object and programmatically adds the mandatory attributes (firstName, lastName, email) to the provisioning plan - even if they haven’t changed. This ensures the target system receives all required fields.
Check these links out:
Hope that will help/support you, and in case you need anything further, don’t hesitate to let us know please!
Regards,
Mustafa