Known Limitations

Release: January, 2021

The EnterWorks 10.3 release has the following known limitations. Numbers in parentheses indicate Mantis tracking tickets associated with the issues.

  • In the Multi-Editor, there are UI issues on the repeating attribute Code Set selection screen. (EW-892)

  • There are missing detailed capabilities in the New UI for Import with or without Advanced Options, and in selecting a defined template. (EW-1038)

  • The wrong record count is exported when a preference (with Code Set description enabled) and a column filter (Code Set) are applied. (EW-1084)

  • All repository records are being updated when a filter is applied, all records are selected, then Update Variants is triggered. (EW-1099)

  • EnterWorks 10.2 is unable to Import .xlsx files with greater than 14,000 rows. (EW-1297)

    • Workaround: Import a CSV file instead of an .xlsx file.

  • Issues related to adding and editing a Saved Set (EW-1415):

    • A newly added Saved Set is not displayed in the Saved Set panel. The panel is not getting refreshed.

    • If a Saved Set is open and the user creates another Saved Set by using the displayed records, then the previous Saved Set remains selected, but the Edit button gets enabled. On clicking Edit, the newly added Saved Set gets edited.

  • Issues with applying a Column Filter to Taxonomy attributes. (EW-1417)

  • In EnterWorks on Linux, record values are not being updated when an Event occurs. (EW-1524)

    • Workaround: The event will be executed successfully if the event's status is changed from the default of "pending approval" to "approved". This can be done in the Classic UI, but not in the New UI.

  • In Export Templates, changing the order of attributes in an output file layout is very cumbersome. The user is not able to change the order of attributes across page boundaries; the user is able to drag and adjust rows in a single grid only; the user cannot change the order of attributes if the attributes count is more than 200 because the maximum page size is set to 200. (EW-1694)

    • Workaround: The user can export the template, change the order of attributes (xmlAttrColumnPosition) in the downloaded .xls file, then import the template.

  • In the Import widget, if an import process dialog is closed before the import process job finishes, when another file is imported, the dialog will not appear. (EW-1723)

  • In the Import's advanced options there are a number of differences between the Classic UI and the New UI. (EW-1842)

  • In the Classic UI, if an Import Template is created and Content Replacement is checked, the Update/Create options are not displayed. (EW-1874)

  • In the WorkFlow Task Manager in the New UI, you cannot sort by Work Item Id. (EW-1883)

  • In the WorkFlow Task Manager in the New UI, if you go to All Completed Work Items and click Submit, an empty dialog appears. (EW-1884)

  • In the New UI, Cloning is not working when All is selected. (EW-1906)

    • Workaround: Select individual records per page.

  • Records shared across Security Context should not be editable in the New UI. (EW-1910)

  • In the New UI when Export Templates are defined, if the Output Type is set to Indesign CSV, the option "Only Show Nodes that Have Mappings Defined" does not appear. (EW-1932)

    • Note: Currently this is not supported due to its impact on performance.

  • When editing a value for an attribute in an associated group, the values are not changing. (EW-1990)

  • When exporting a Current View in the New UI, if a preference is in effect that has "Add Category Attributes of Selected Taxonomy Node" checked, the export behaves like an export performed with the advanced option "Separate Files For Category Attributes Based on Control Value". A Zip file is produced that contains a separate file for each taxonomy node. In addition, one file will be created that holds any records that are not assigned to a taxonomy node. However, if all the records in the export are assigned to taxonomy nodes, the additional file will be empty. EnterWorks should not generate the empty file. (EW-2062)

  • When editing multi-language attributes in the New UI, if the user logged in using a language other than the default language, they are not able to edit a value for the default language. (EW-2092; Mantis #6747)

  • No matter which language a user selects during login, when associated or repeatable group values appear, they are appearing in English. (EW-2125; Mantis #6739)

  • On EnterWorks running on Linux, when category attributes are assigned to a taxonomy node, they are not being displayed. (EW-2167; Mantis #7332)

  • In the New UI, the user should not be able to edit or create Export Templates with an output type of Demandware, Preview, or Custom XML. (EW-2232)

  • In the New UI, if an Import Template is in the process of being created and an attempt is made to use the Template before it is saved, any addition or removal of attributes from the Template will not be reflected in the output. In the Classic UI, a Template could be used before it was saved. (EW-2364)

    • Workaround: Save the Template before you use it.

  • When an Export Template is being created or edited, the Basic Search box does not work in the Output File Layout tab. (EW-2374)

  • When viewing a linked repository's repeatable attribute that has more than one value, the values are not displayed. (EW-2391)

    • Workaround: Click the attribute value and the values will be displayed.

  • In an Export using a defined Template, in the Advanced options, the "Publication Data" field appears in the New UI but not in the Classic UI. (EW-2543)

  • In the New UI, when performing an Export using a defined Template, in the Publication Plan dropdown, all Export Templates appear. (EW-2550)

    • Note: EnterWorks 10.3 does not support the Publication Plan feature.

  • In the New UI, if a user is logged in for a long time and there are many concurrent users, it takes a long time for the repository tree to open. (EW-2574)

    • Workaround: Refresh the workspace or the browser.

  • If a hierarchy or taxonomy node is edited or renamed, all records assigned to the node will be removed from the node. (EW-2585)

  • When creating an Import Template in the New UI, if the user opens a dropdown list, information from cookies from other sites appears. (EW-2633)

  • If the user creates a dynamic association for a Code Set, goes to the repository and chooses a value in the control attribute (Code Set), observes the dropdown values of Code Set and applies ones, saves, then changes the value in the control attribute and saves, an error message should be generated for incorrect binding. (EW-2641)

  • If multi-edit is used to edit a an dynamic Code Set attribute value, the value does not appear. (EW-2675)

    • Note: Multi-edit is not supported for dynamic Code Set association.

  • When adding or editing an Export Template in the New UI, on the Output File Layout page, if the user changes the order of an attribute, the page footer count and page number do not update. (EW-2700)

  • When adding or editing an Export Template, Global Search does not work on the Output File Layout page. (EW-2711)

  • If a line break exists in the record content and it is exported to a CSV file, the resulting file will have values in incorrect columns. (EW-2732)

  • When Exporting 10k records using the option "Separate Files For Category Attributes Based on Control Value", the export job gets stuck at approximately 9k records. The records keep failing with the error "java.lang.OutOfMemoryError: Java heap space". (EW-2745)

  • In the Import Template's Attributes Mapping page, if you go back and de-link a child repository, the Categories field disappears. (EW-2798)

    • Workaround: Click the Refresh button to refresh the page.

  • When managing a record's state, if the Security Context value is changed, then the Manage Record State is reopened, the new value is not shown. The user must click the refresh button to see the new value. (EW-2801)

  • If an Export using a defined Template to an XML file is performed, even when "Include Empty Attributes" is unchecked, the empty attributes still appear in output file (EW-2809)

  • In the New UI, when managing a Hierarchy and adding a node in tree view, default property values do not appear. In the Classic UI, they do. (EW-2811)

  • Filter and Advance Search does not work for an Invalid code set code. (EW-2840)

  • If an Export using a defined Template is performed, then the Template is modified and the Export is performed again, unless the user clears the Cache, the Export process will use the previous version of the template. (EW-2875)

    • Workaround: When an Export Template is modified, clear the Cache before using it.

  • If a file is deleted from DAM then multiple files are selected and downloaded, the deleted file appears in the Download dialog. (EW-2876)

  • When simultaneously editing multiple Import Templates that pull from different repositories, on the Attributes Mapping page, attributes from the other Import Template's repositories are appearing. (EW-2878)

  • In the New UI, in the Taxonomy Sidebar, Taxonomy nodes are showing an incorrect number of assigned records. (EW-2886)

  • After applying a saved search, the column filter button is not working for the Taxonomy control attribute. (EW-2904)

    • Workaround: Remove the applied Saved Search then use the column filter.

  • After adding a record and entering a value for a category attribute, when the record is edited again, the category attribute value disappears. (EW-2917)

  • In the New UI, when a user clicks the Impersonate icon then selects a user to impersonate, the UI is getting stuck in an infinite loading state. (EW-2936)

    • Workaround: After impersonating a user, refresh the dashboard by clicking the dashboard's Refresh button.

  • Cannot edit an Export Template property if the "Separate Files For Category Attributes Based on Control Value" settings is unchecked in the New UI. (EW-2952)

  • Capabilities relating to Import Templates and Preference are not behaving as they should for existing groups. (EW-2960)

  • In the New UI, in the Export Template tab, the Add button is disabled for users assigned to the Administrator group. (EW-2999)

    • Workaround: Do a hard refresh on the browser.

  • A user in the Administrator group is unable to edit an Import Template. (EW-3001)

    • Workaround: To edit an Import Template, the user must be a system user or own the template. Other administrative users cannot edit the Import Template.