📄️ Access request shows the same context multiple time
We fixed a bug that showed the same context multiple times. Now multiple context assignments with the same ContextId will no longer appear in the business context selection dropdown on the Access Request form.
📄️ Access request slow performance
We fixed a bug that slowed down the functioning of the access request process validation stage for resources with child resources. This was fixed by modifying the order of conditions and implementing a queries cache.
📄️ Issue with filter
There was an issue with the Requested by filter in the Access Request. The problem has been resolved. Currently, the values searched for using the Requested by filter in the RequestedBy column align with those displayed in this column.
📄️ New Access Request UI doesn't show entire attribute names
There was an issue with displaying long attribute names in the Access Request UI. This problem has been resolved, and we now fully support and accurately display unusually long attribute DisplayNames.
📄️ Break tag is displayed in Approval Status
There was a formatting issue that displayed unintended `` tag in Approval Status on Access List.
📄️ Issue with error on missing system ID from resource
An issue occurred when working on a process that generates identities of the type "secondary." Upon requesting access to a custom resource through Legacy Access Request, an error occurred indicating that system id was missing from resource. This issue has been resolved, and Technical Identity Validation will no longer be triggered for custom Identity Types.
📄️ Invalid validation for Access to field
There was an issue with incorrect validation when attempting to input an invalid date range that resulted in inconsistent error handling. Initially, entering a valid from value that higher than the valid to value appropriately triggered a red border and displayed the following error message: Access to must be higher than Access from. However, upon subsequently entering a valid to value higher than the valid from value, the red border persisted, and the error message failed to disappear when it should.
📄️ Context is hidden in Access Request
We fixed a bug that hid a context. Now, even when the context field is hidden, the default identity context is added to Access Requests.