0
Not a bug

"Active Directory User to Person" Link is processing a Locker and creating an Outgoing Change even though there is no corresponding linked (or able to be linked) Adapter object and Outgoing Provisioning is disabled

Adrian Corston 3 months ago in UNIFYBroker/Plus updated by Beau Harrison (Software Developer) 3 months ago 2

I am using Broker/Plus to only join to objects from Aurion to AD, and not to provision (i.e. Outgoing Provisioning is disabled).  For a user in Aurion (with corresponding Locker record) where there is no corresponding AD record (i.e. the join criteria are not met for any existing AD adapter objects) the Link still reports an Outgoing Change for that object.

I have 7 Lockers:

I have four users in AD:

When I run a Baseline Synchronization on the AD Link, I see this:

Note that there are 7 Outgoing Changes, even though there are only 4 objects in the AD Adapter, and Provisioning is disabled so it should not be provisioning new ones.

Log file attached:

UnifyLog20190624.csv

Affected Versions:
Fixed by Version:

Answer

Answer
Not a bug

Hi Adrian,

This is the intended behaviour. As the information message states

... Ensure that either the field/s used in the join rules are correctly mapped or, if this link is not responsible for provisioning, the joining entities already exist. ...

Meaning that of the 7 entities being synchronized, 4 were OK since the mapped adapter entities existed. The remaining 3 have no mapped adapter entities, and cannot provision them since that is disabled, so are considered incomplete and not processed.

As long as the intended behaviour is for those three entities to not be synchronized, then you can ignore that information message.

GOOD, I'M SATISFIED
Satisfaction mark by Adrian Corston 3 months ago
Answer
Not a bug

Hi Adrian,

This is the intended behaviour. As the information message states

... Ensure that either the field/s used in the join rules are correctly mapped or, if this link is not responsible for provisioning, the joining entities already exist. ...

Meaning that of the 7 entities being synchronized, 4 were OK since the mapped adapter entities existed. The remaining 3 have no mapped adapter entities, and cannot provision them since that is disabled, so are considered incomplete and not processed.

As long as the intended behaviour is for those three entities to not be synchronized, then you can ignore that information message.

OK, I thought it was an error message.  Thank you for letting me know that it's an information message.