Support
Support
Breadcrumbs

Known Issues and Limitations

This page lists the Known Issues and Known Limitations of Anjana Data Platform in its Supported Versions, in order to:

  • help you quickly identify whether a behavior you are observing has already been identified by Anjana Data;

  • provide you, when available, with a reasonable mitigation (workaround);

  • indicate the status of the issue and, where applicable, the version in which the fix is delivered;

  • support your deployment and upgrade decisions.

It is useful to distinguish between two concepts:

  • Known Issue: a confirmed product defect in a Supported Version, subject to correction under the bug-fixing policy (§9 of the Anjana Data Support Policy). It has a lifecycle and is expected to be resolved.

  • Known Limitation: a behavior by design, or a scope not yet supported. It is not a bug and may never be corrected (or may only be addressed via the roadmap).

Only issues affecting Supported Versions are documented here (within the Support Window, §9.2 of the Support Policy). When a version reaches EOS/EOL, its open issues are moved to the historical archive and are no longer actively maintained.

How to use this information

Before opening a support ticket:

  1. Locate your exact version (format YY.N and, if applicable, YY.N Patch P; for example, 26.1 or 26.1 Patch 2).

  2. Filter the table of known issues by your version, module, and deployment type.

If your case matches a known issue:

  • apply the indicated workaround, if any;

  • if you need assistance, open a ticket in the Support Portal referencing the identifier of the issue (the "Identifier" column in the table).

If your case does not appear, open a «Technical Support», «Incident» (SaaS), or «Query» ticket as appropriate, providing the minimum information required by the Support Policy (§4.3).

Known Issues & Known Limitations

Identifier

Type

Description

Affected Version(s)

Fix Version

Workaround

S1644

Known Issue

The "Insert default translations" button in the Portuno configuration panel does not insert the default records into the translations table when the table is empty.

25.x

26.1

Contact Support

S1637

Known Issue

An attribute configured as INPUT_DECIMAL does not allow values such as 0, 0.00, or X.00, showing the restriction "Minimum decimals allowed: 1".

25.x

26.1

Lower the validation to 0 in the template attributes and in APP_CONFIGURATION.

S12680

Known Issue

The NEW_DSA notification is being delivered to all users who have the role configured, without filtering by the object's OU.

25.x

26.1

—

D13332

Known Issue

In the workflow screens (My Tasks, My Access Requests, My Governance Requests, and All Workflows), when changing the interface language, the "Reason" and "Last comment" fields keep showing the text in the previous language instead of updating to the selected one. The content is available in both languages and displays correctly after reloading the screen.

26.1

26.2

Manually refresh the screen.

D13330

Known Issue

In the Marketplace, the "Object subtype" filter also shows subtypes of type RELATIONSHIP, when it should only offer subtypes of type ENTITY. Relationship subtypes do not represent Marketplace assets, so selecting them returns no results.

26.1

26.2

Not applicable.

D13314

Known Issue

When adding a Dataset Field to a Dataset in "Rejected" status, the screen does not update to reflect the new "Draft" status, nor does it enable the "Submit" button. After reloading the screen, the status and the button appear correctly.

26.1

26.2

Manually refresh the screen.

D13131

Known Issue

In certain operations on datasets, the internal identifiers of dataset_fields may be unexpectedly modified.

26.1

26.1 (patch)

—

D13310

Known Issue

In the workflow screens, values overlap in the "Object" column when scrolling horizontally.

26.1

26.2

—

D13312

Known Issue

The message shown when an entity already has an organizational unit assigned needs better wording.

26.1

26.2

—

D13316

Known Issue

Editing a deprecated object via Excel may end with an internal error.

26.1

26.2

—

D13404

Known Issue

Inconsistent behavior has been detected in certain authentication and authorization scenarios across identity providers. Under review.

26.1

26.2

Contact Support referencing the identifier if you observe unexpected behavior.

D13463, D13349, D13451

Known Issue

Isolated cases have been detected in which certain access control rules or field-editing restrictions are not applied consistently. Under review.

26.1

26.2

Contact Support referencing the identifier if you observe unexpected behavior.

D13355

Known Issue

In Excel upload, a boolean value left empty is interpreted as null.

26.1

26.2

—

D13362

Known Issue

In the Jobs module, when a load error is caused by the ARIs, insufficient information about the cause is shown.

26.1

26.2

—

D13364

Known Issue

In the Marketplace API, previewing a non-existent object returns an error code other than 404.

26.1

26.2

—

D13375

Known Issue

Reloading the "Sample Data" tab may show an incorrect insufficient-permissions message.

26.1

26.2

Reload again or re-access the object.

D13376

Known Issue

The "Sample Data" tab is not disabled when the dataset has expired.

26.1

26.2

—

D13389

Known Issue

The text of the "Export lineage as image" action does not have a native translation.

26.1

26.2

—

D13391

Known Issue

The change view (snapshot comparator) for datasets with a very large number of fields has issues.

26.1

26.2

—

D13392

Known Issue

In the adherence flow, when requesting a new combination, the final signature step may fail.

26.1

26.2

—

D13395

Known Issue

A warning message in the adherence flow does not replace the text placeholder with the corresponding information.

26.1

26.2

—

D13396

Known Issue

When previewing an object with an empty description, "null" is displayed instead of an empty value.

26.1

26.2

—

D13397

Known Issue

User-type attributes do not warn that search results are partial (limited to 20 results).

26.1

26.2

Refine the search to narrow down the results.

D13398

Known Issue

Some "reason" request dialogs do not enforce the 255-character limit.

26.1

26.2

—

D13400

Known Issue

In the language selector of the Personal Area, if an error occurs during the operation, the language may remain incorrectly selected.

26.1

26.2

—

D13424

Known Issue

The "Edit access information" action is only available from the object detail view, not from the Catalog actions.

26.1

26.2

Edit the access information from the object detail view.

D13427

Known Issue

The workflow screens are missing sorting options for "Last participant" and "Total duration".

26.1

26.2

—

D13429

Known Issue

In certain cases, multiple-taxonomy attributes send an incorrect value.

26.1

26.2

—

D13431

Known Issue

Bulk workflow approval may display objects that the user should not be validating.

26.1

26.2

—

D13432

Known Issue

Bulk rejection of workflow tasks may return a validation error.

26.1

26.2

—

D13433

Known Issue

The save button is enabled when changing the language of an international rich-text attribute, even if its content has not been modified.

26.1

26.2

—

D13434

Known Issue

When deleting a dataset from the "Sample Data" tab, the user receives a 404 error.

26.1

26.2

—

D13443

Known Issue

Very long numeric values may fail during indexing.

26.1

26.2

—

D13444

Known Issue

The owner of an object sees the option to unsubscribe, even though that action does not apply to them.

26.1

26.2

—

D13446

Known Issue

In the Zeus API, language resolution is intermittent and the "description" field may return untranslated translation keys.

26.1

26.2

—

D13449

Known Issue

When adding or removing languages, users who are already logged in may experience issues editing templates until they log in again.

26.1

26.2

Log out and log back in after the language change.

D13452

Known Issue

The minimum decimal precision validation has issues when the decimal part is 0.

26.1

26.2

—

D13456

Known Issue

The user audit does not sort correctly by the "Object" column.

26.1

26.2

—

D13459

Known Issue

The expiration proximity notice shows errors in certain cases.

26.1

26.2

—

D13460

Known Issue

When specifying a duplicate name in a dataset field, the error message shown is not sufficiently clear for the end user.

26.1

26.2

—

D13464

Known Issue

From a workflow's detail view, it is not possible to navigate directly to another workflow.

26.1

26.2

Return to the workflow list and access the desired workflow.

D13469

Known Issue

The "Load default translations" action does not include the COMMON.CHANGE_ORGANIZATIONAL_UNIT key.

26.1

26.2

Manually add the translation for the key.

D13470

Known Issue

The completion notification for the bulk user unsubscription process does not always behave as expected.

26.1

26.2

—

D13471

Known Issue

In the Participants tab, sorting the "Role" and "Participant type" columns by the translated value is not consistent.

26.1

26.2

—

D13472

Known Issue

When changing the organizational unit, it is possible to select the same OU the object is already in.

26.1

26.2

—

D13478

Known Issue

Excel-based editing does not validate the data type in date fields.

26.1

26.2

—

D13482

Known Issue

In the workflow screens, the "Pending time" column does not sort correctly.

26.1

26.2

—

D13484

Known Issue

In the workflow screens, filtering by object (entity type) may show other objects with the same name.

26.1

26.2

—

D13485

Known Issue

In the workflow screens, the "Participant role" filter only shows the values of one of the participant roles.

26.1

26.2

—

D13486

Known Issue

In the workflow screens, during bulk validation with scrolling, the progress bar and the object name may overlap.

26.1

26.2

—

D13489

Known Issue

During Excel upload, an error message may be shown that does not match the actual cause of the problem.

26.1

26.2

—

D13492

Known Issue

From the Marketplace, it is possible to add to the cart a DSA the user is already adhered to.

26.1

26.2

—

D13494

Known Issue

Resubmitting objects in Imported status for validation does not behave correctly in certain cases.

26.1

26.2

—

D13510

Known Issue

The search box in the "Configuration/Settings" section of the new Administration Panel does not filter results correctly.

26.1

26.2

—

D13227

Known Issue

In the creation/edit Excel template, the "reason for submission" column appears highlighted as if it were mandatory, when it is actually optional.

26.1

26.2

The field is optional: it can be left empty even though it appears highlighted.

D13235

Known Issue

In the Marketplace, the "Recently added" section may show older DSAs that have had recent activity, instead of showing only the most recently added ones.

26.1

26.2

—

D13274

Known Issue

When changing the user's language to one the administrator has disabled, the portal may stop showing translations.

26.1

26.2

Select the previous language again, or log out and log back in.

D13278

Known Issue

In notifications with long texts, the "See more" link may occasionally disappear when reading the notification.

26.1

26.2

—

D13388

Known Issue

Sorting the participants list by username may not work correctly in some cases.

26.1

26.2

—

D13457

Known Issue

When creating several relationships from an object, after creating the first relationship the source object may stop being shown in the creation wizard.

26.1

26.2

Use the swap button to show the source object again.

D13461

Known Issue

After deleting a non-engine-type process instance, it may be necessary to reindex the process before it can be used again in another instance.

26.1

26.2

Reindex the process before reusing it.

D13467

Known Issue

In bulk workflow validation, deselecting all visible items may cause the screen to stop responding correctly.

26.1

26.2

—