Defect #2424
Updated by Alena Peterová over 3 years ago
Version 10.4.1 When synchronization of identities creates a new identity and some of the mapped EAVs have default value, then the default value is saved in the identity, instead of the mapped value. The second run of the synchronization updates the identity it correctly. Steps to reproduce: * Create an EAV of IdmIdentity with some default value - "false" in our case. * Map the EAV in the synchronization of identities, set "Transformation from" to some different value - Boolean.TRUE in our case * Run the synchronization * Identity was created, but the value of the EAV is "false". (wrong) * Run the synchronization again * The EAV was changed to "true". (OK) (Our use case: We want to "flag" identities created by one special synchronization as "System accounts". By default, the identities are not system accounts.) Tested for Boolean and ShortText, the result is the same.