Skip to main content
Version: Cloud

Resolved Issues and Bug Fixes

Read more about resolved issues and bug fixes in this release.

Enterprise Server​

Issue with filter expression combinations​

We have changed the handling of unsupported combinations of filter expressions. Instead of blocking the saving of a new filter with an error message, it now shows a warning in the list of filter expressions.

INC-277956

Issue with changeset saved after session timeout​

We have fixed an issue where a changeset was saved after a session timeout. Now, if you leave the Create changeset view open and click the OK button, the changeset will not be created if the session has expired.

INC-275110

Issue with expired identities​

In the Enterprise Server, expired identities were not removed as an owner of identities, contexts, and resources. The ownerships were transferred to unresolved identity. The issue has been resolved by expiring the ownerships with the identity.

INC-274989

Role and Policy Engine​

The risk score calculator was crashing for certain identities​

We have fixed the errors related to the asynchronous calculations of the risk score, which were introduced by enabling the AsyncRiskScoreUpdates option on the RiskScoreCalculator2 RoPE extension.

INC-272925

RoPE calculates Pending Update when attribute is empty​

We have fixed an issue where the RoPE Provisioning extension generates a PendingUpdate when an attribute is an empty string in both the actual state and the desired state.

Governance for Omada Identity​

Task Mappings and Data Model are overwritten with CU35 update​

We have resolved an issue where updates to the Omada Identity Connector Data Model and Task Mappings were being overwritten during the update of the Omada Identity connectivity package:

  • The Omada Identity Connector Data Model and Task Mappings are now treated as templates when installing the Governance for Omada Identity feature.
  • A new update process has been introduced that creates copies of the existing Omada Identity Connector Data Model and Task Mappings for systems where the Governance for Omada Identity feature is already installed.
  • The latest version of the Omada Identity Connectivity Package has been enhanced to register the Omada Identity Connector Data Model and Task Mappings as templates.

INC-279146

Issue with custom groups with self-management​

When the Governance for Omada Identity feature is installed, the migration of self-management roles will now ensure that resource types for custom self-management roles are updated to include child resources. Consequently, a child resource is added to the self-management resources.

INC-277563

Issue with reconciliation for Users​

We have fixed an issue with attribute reconciliation for the FirstName, LastName, and Email provisioning attributes. This fix adds FirstName and LastName to the OIS Account query and converts the User's FirstName, LastName, and Email properties into EXTENSIONATTRIBUTES with HISTORY.

If you have Governance for Omada Identity already installed, it is necessary to update the OIS system queries and mappings for the Account object type:

Removed dependency​

We have removed the dependency from the feature package Governance for Omada Identity to the Business Contexts feature package.

INC-277494 INC-277497

Surveys​

Unable to change admin form on existing survey template​

We fixed a bug in the survey template UI that prevented users from changing the administration form to a different one.

INC-278519

Event definition: Update Survey assignees' bug​

We have fixed a bug that prevents completed activities being reactivated when the RecalculateSurveyAssignees method is executed, particularly in cases where these activities lack assignees and questions.

INC-275107

Mass update data object fails for XML with utf-16​

We have fixed a bug that caused an error when attempting to update the XML property of a Survey template using the XML retrieved from the Survey template UI.

INC-278520

Other​

Missing resource logic key​

There was an issue with the resource logic key missing, when the import threshold was exceeded. The issue has been resolved and resource logic key is retained.

INC-277344

Inconsistencies in analytics processing​

For Horizons functionality, all Account and Resource assignment extension attributes configured in both Queries and Mappings for all systems, as well as Resource Type attributes, will be transferred to the Omada Data Warehouse.

Setting up delegation to a technical identity​

Till this point, you could select a technical identity as the delegation target. We have added filtering that excludes technical identities.

INC-278044

Can't view data object as a manager​

We fixed a bug that prevents viewing data objects as a manager.

Documentation​

Missing documentation for setup Azure KeyVault for Omada Vault usage​

We have updated the documentation for the Azure Key Vault connection:

  • We have clarified the Authmethod parameter description when creating a connection to an Azure Key Vault.
    • We have added the information about the requirement for the Key Vault Secrets User role assignment on the Azure Key Vault resource for proper permissions.

INC-278891

Governance for Omada Identity - Technical identities​

We have added a new procedure that describes the steps required for creating a technical identity for service accounts. See Activation postrequisites in the Governance for Omada Identity Activation section.

INC-277402

Governance for Omada Identity feature is missing default culture and default language for newly created users​

We have updated the documentation to clarify that when creating a new account, if the culture, langId, or timeZoneId properties are not specified in the task mappings, their values will default to the corresponding settings in the customer configuration: DefaultCulture, DefaultLanguage, and DefaultTimeZone.

For more information, refer to the following documentation:

INC-277580