Defect #1204
Updated by Alena Peterová over 5 years ago
Version 8.1.2. Situation: 1) The identity had has valid contract in HR -> => identity was is enabled 2) The Some time in the past the contract was excluded in HR -> synchronization set => the contract state to Excluded -> the identity was disabled by HR processes 3) The contract was removed from exclusion in HR -> synchronization set the contract state to null -> HR processes did nothing to the identity Expected behaviour: Contract has state null, identity is enabled. Real behaviour: Contract has state null, identity is disabled. I guess there is some problem with the implementation of HrEnableContractProcess. It remembers the contract of the identity from enabling in the step 1, so it doesn't handle it again in the step 3. When I manually remove the contract from the HrEnableContractProcess queue, then the contract is processed and the identity is enabled correctly. Manual changing of the contract state works fine, the issue is only with automatic processes.