Hi All,
I have a scenario involving a Web Services connector where all CRUD operations are configured under HTTP Operations. The Create Account and Attribute Sync sections are mapped accordingly, and everything is working as expected, except for one particular scenario.
When the firstname attribute is empty, the downstream API returns an error. For this particular downstream system, the requirement is to send # as the value whenever firstname is empty.
The firstname attribute is mapped to the firstname identity attribute in the Create Account configuration and is also enabled in Attribute Sync.
To address this, I decided to handle the transformation through the Create and Update Provisioning Policies. I followed these steps:
-
Using the API, I updated the Create Provisioning Policy to include a transform for
firstnameand covered all other mappings. This worked as expected for account creation. -
However, updates were still failing.
-
I then unticked all attributes under Attribute Sync and created an Update Provisioning Policy, using the same rules and attribute mappings as the Create Provisioning Policy, including the transformation to handle an empty
firstname.
With this configuration, both account creation and updates appear to be working as expected.
I also noticed a difference in the provisioning events:
-
When Attribute Sync is enabled for all attributes, the events behave differently.
-
With the attributes unticked and the Update Provisioning Policy handling the updates, the event shows a single successful downstream update entry, with no errors.
I also verified that the downstream system was successfully updated.
My questions are:
-
Is this a recommended approach for this type of requirement, i.e. disabling Attribute Sync and managing all attribute updates through the Update Provisioning Policy?
-
By unticking all attributes under Attribute Sync, is there a risk of missing any attribute updates?
-
Given that my Update Provisioning Policy covers all the attributes previously mapped through Attribute Sync, including the required transformation to replace an empty
firstnamewith#, should this approach be sufficient?
I would prefer not to introduce an additional identity attribute just to handle this downstream-specific requirement.
Would appreciate any suggestions or alternative approaches.
Also note we got ISC and for above connector we got BP rule defined as well to do other things which I did not touch for above need.
Regards,