Slow synchronization with Localities (slow synchronization with HR) (4381255)

Change of one Locality entails changes on hundreds of Person-objects which in turn entails hundreds and hundreds of changes of ADSAccount-objects and other UNSAccount-objects. This means a huge amount of calculations (templates calculation, jobs generation etc.) and SQL-statements. Because of a necessary open transaction on the Locality-object, all these actions will be done within one transaction and adding the network latency, this takes so much time.  It is required to minimize the network latency.

For this particular case of Localities, the idea is to move all those calculations outside of the transaction from the on-prem closer to the cloud.

1. Open Designer | One Identity Manager Schema | Tables | Type: Table | Person | Schema Editor > Show column definition
Select AuthentifierLogins | Value calculation tab | change the value of "Threshold (async)".

The idea is to define a threshold for a number of objects that can be directly changed by the value template. If this number is reached, the templates will be calculated via current One IM cloud Jobservice. A best suitable number for this can be determines with real tests but we can start with a low one (10) to make sure the calculation will be via the Jobservice.