📄️ Issue with calculated assignment for deleted resources
An issue has been solved in the OData API for calculated assignments. If the scope of the call contained an assignment for a deleted resource, the whole API call was failing. This is contrary to how the calculations look in the user interface. This has been improved.
📄️ Unresolved identity fails to calculate with NullReferenceException in ManualProvisioning Extension
The Manual Provisioning Extension had an issue where, upon disabling an Orphan Account, Omada Identity would check for the Previous Calculation of the Unresolved Identity and incorrectly assume that the Orphan Account Calculated Assignment also had a prior Calculated Assignment. We resolved this by fixing the logic, ensuring accurate handling in such scenarios.
📄️ Survey verdict incorrectly prolongs CRA validity
For CRAs with no actual state, a survey verdict will not extend its validity through the using the days before verdict expires field in the survey form. Instead, it will maintain the initial validity established on the direct assignment.
📄️ Highwater mark missing for master data import from RoPE
There was an issue when the highwater mark was missing in the master database for the master data import from RoPE. It resulted in the import not storing the new highwater mark. The issue has been resolved.
📄️ Manual provisioning tasks
Resolved an issue in the AssignmentAttributeValueDifferentiator that was creating duplicate provisioning tasks due to an extra assignment when the differentiator value is empty, as it pertains to provisioning claim reasons.
📄️ Rope gives warnings prior to PreValidity
We have enhanced RoPE for identities with a validity period starting after the PreValidity. Previously, the calculation of such identities could trigger a warning related to a missing account. With this update, the warning has been eliminated, and assignments are still not generated.
📄️ RoPE failure of validity and parent context
Fixed an issue in the context of a Parent/Child relationship where no overlap existed in their validity periods. This problem resulted in calculations failing due to an invalid validity period.
📄️ Issue with deprovisioning jobs
An enhancement has been implemented in the calculation of the provisioning statuses Pending Deprovisioning and Deprovisioning Failed.
📄️ Issue in the RoPE Initial Password extension
We've fixed an issue within the RoPE Initial Password extension. Previously, only newly created account assignments would receive an initial password attribute value. With our recent fix, existing account assignments, without a direct reason, will now be assigned an initial password by the RoPE extension during the provisioning task. This adjustment ensures a seamless notification flow and successful completion of the process.