I have an issue on IIQ 8.4p2 where my webservice connector is not emptying the value when that attribute is null on the IdentityIQ’s side. The attributes are mapped through IdentityMapping (ObjectConfig Identity) without any transformations.
Example to better illustrate the problem:
Identity has an orgCode attribute with ‘randomValue’. This attribute is populated to the ‘orgCodeInternal’ attribute on the connector correctly.
Any changes to the orgCode attribute are reflected on the connector’s side, apart from when the orgCode attribute is removed from the identity.
In that case - orgCode is null, but orgCodeInternal on the connector still has the previous value and running refresh with ‘synchronize attributes’ or any other options does not change a thing. BeforeProvisioning rule also cannot help because… there is no provisioning happening at all.
Is there any way to force an attribute to be mapped to an application even when it’s null on the Identity?
Thank you in advance for any input, I’ll also be happy to provide some actual code if necessary.
Hi @bartosz_drzewiecki Its the current OOTB behavior, Try using ‘transformation rule’ and pass ‘empty’ or ‘space’, not sure both will work or not but you can give it a try.
Turns out the main issue I had was that I was trying to fix it on the AttributeTarget rule in mappings, but it could not get there because the source value is null.
Creating a rule for the AttributeSource allowed me to check for nulls and add an empty space which I could further correct in the TargetSource rules. Not very straightforward, but it works