Known Issues

Read more about the issues that are known to still exist at the moment of introduction of the Omada Identity update.

📄️ Popular resources are always displayed first

The arPopularityEnabled customer setting enables customers to enable sorting resources by popularity on Resources Search field in Access Request flow. Introducing the filtering version for the resources autocomplete, coexsting with the exisiting paged version, can be configured with the EnableSearchFiltering setting. Configuring it to true results in replacing the Paged version with Filtering version.

📄️ Multiple activities in the survey process template

Configuring duration for the activities in the survey process template, requires ensuring that appropriate amount of time is allocated for each of the activities. Currently, when a survey is launched, all activities start simultaneously. This may result in lack of sufficient time for assignees in subsequent activities to complete their tasks effectively.

📄️ After hiding all columns rows are clickable

On the new UI Tasks, Access Requests and Delegations views, if you hide all of the rows and columns you can still click on the rows. When hovering over a row, the row is highlighted and the pointer is changed to indicate that the row is clickable. When clicking, it navigates to the details of the hidden items. To fix it, always show at least one column.

📄️ Resource status update issue

When either ValidFrom or ValidTo fields are empty in a Resource object (but not both), the Resource status is not updated correctly with the associated event definitions.

📄️ Configuration imports fails due to unsupported operations that write to the log file

In case you are using SQL Server 2014 or older in standard edition, the Configuration import profile might fail with:

📄️ Attribute values in the legacy access request process

In the legacy request access process, you will be asked for an account type when the resource allows more than one account type, the resource has visible attributes, and a request is being made for the resource for more than one identity, where each identity has one valid account.

📄️ Attribute type property

In the new UI, for an attribute type based on the Integer data type, if you set the Max. length value to 0, you won't be able to enter any number. You need to leave the field value empty.

📄️ Access Request date pickers

In the Access Request process, the date picker for Valid from to Valid to dates will display according to your language browser and not the language is chosen in the 01.

📄️ Preview update button is missing

We have identified an issue where the preview update button is missing in System Queries & Mappings. If you encounter an error during upgrading, you'll need to perform the update manually by adding the script jsinc/OIM.SystemOnboarding.DataMapping.Preview.QandM.js to System onboarding > Script files.

📄️ Onboarding guide tooltip reloads whole page

In the new UI, on the Access page with the Onboarding guide tooltip opened, if you click OK in the tooltip, the whole grid will reload.

📄️ RoPE fails to calculate identities

It is not possible to recover references between resources and resources assignments once they have been deleted. If you have deleted them, then you should create them again. The issue extends to all references between data objects.

📄️ Multiple import threads issue

Transferring a large volume of identities between organizations may result in an import issue. It is caused by multiple import threads updating transfer surveys from a single manager.

📄️ First request for technical mailbox fails due to missing account

The first request for a mailbox fails with a warning due to a missing account. The request is successful in a second attempt using the same mailbox name.

📄️ Submission not allowed in Access Approvals with hidden columns

If you hide a required column, such as the Approve/Reject column in the access approvals grid before adding a value to the column, then clicking the Submit button won't produce any action.

📄️ Survey questions are assigned to a user but the respective activity is not

There is an issue in the Access Request approval process in the new UI. While using the text description of the resource, you use the Cannot find the resource? link, where you can write your description of the resource you want. When submitted, the request interpreter gets a task but the description is not copied over and it only displays "test".

📄️ Access request for technical identities

We have found an issue when requesting access for technical identities in the new UI. Please, use the old UI if you need to request access for technical identities.

📄️ Verdict is not expired after E-Role was assigned containing the CARA as child role

The assignment will be disabled due to the revocation if it has been explicitly revoked from the assignments grid or from the survey, and it has been assigned with a new direct assignment or an assignment policy before the deprovisioning has been confirmed.

📄️ Discrepancy in ValidTo datetimes possible

For consumers using Omada Identity Graph API version 2.3, all datetimes will adhere to the UTC time standard. A known issue arises concerning the ValidTo date of a resource assignment displayed in the Extend Access process versus other places in the system; the dates may not match.

📄️ Unable to set days in forms

We've identified a known issue related to setting the number of days in a form when using the Timespan format for the value property. Please, use the legacy UI if you want to set days.

📄️ Left-side menu option is blank

We have identified a known issue within the left-side option menu in my Access Staging environment. Some group permissions, such as Employee or Manager, may not display all available options in the menu.

📄️ Account types are not displayed

There is a known issue when selecting account types in the Resource step when requesting access. If the account type in a resource doesn't match the account type associated with the identity you are requesting access for, then the dropdown will be empty.

📄️ Access request validation when parameter is unchecked

We've identified a known issue related to Access Request, where a validation message is erroneously triggered when the Reason field is empty and the Requires Value checkbox is unchecked.

📄️ Classification tags are not displayed

Some classification tags used in the classification process do not have multilingual functionality, and they always display in English, even if you have configured your regional settings and your language settings are in a different language. We are actively working to address this issue in upcoming releases.

📄️ Cannot add custom process to service shortcuts

We have found a known issue that prevents the addition of custom processes to service shortcuts in Omada Identity. To avoid this, before upgrading, back up the UIHomePageActions value in the customer settings to preserve customizations made in the JSON value of the customer setting. The value of the customer setting will be overwritten. Once the upgrade is complete, you can add the changes back into the JSON.

📄️ Error in accessApprovalPolicyChecks in GrapghQL v2.7

We identified a known issue in GrapghQL API version 2.7. You will get an error when trying to query the createdBy field of the identity, resource or context fields in the accessApprovalPolicyChecks query. We are working to fix this in the next release.

📄️ Lack of distinction for Extend Access Requests in Audit Log

Currently, there is an issue where Extend Access Requests in the audit log are logged simply as Request Access, without proper distinction.

📄️ Homepage link does not redirect to Access approval tasks

We've identified a known issue with the See all tasks button link on the Homepage. Clicking on it redirects to the Task list view but fails to display links for Access approval.

📄️ Policy check shows violation from all steps

We have identified a known issue in the Policy Check for Access Approval. The policy checks currently display violations for resources in all steps of the survey, rather than just the selected step. We are actively working to address this issue in upcoming release.

📄️ UTC Timezone discrepancies

We have identified a known issue when switching timezones from user settings (to the day before or after), the dates entered during the submission of an Access Request may differ from the dates displayed in the access list or resource assignments list.