EnterWorks 10.1.8 Release Notes

Release: Sept, 2020

The EnterWorks 10.1.8 release has resolved 67 known issues. Numbers in parentheses indicate Mantis or Jira tracking tickets associated with the resolved issues.

  • In the EnterWorks 2020 UI, in Code Set Maintenance, Last Updated shows the User ID rather than the User Name. (#3068)

  • Attribute Properties are not functional on a repository with 10,000 attributes. (#3140)

  • Shortcuts of Type 'Record Edit' do not work with a Saved Search. (#3371)

  • Custom Widget reinitializes after switching views. (#3440)

  • Cannot cancel Send to Workflow on multi-edit. (#4002)

  • The EnterWorks 2020 UI needs to be able to display the environment name on the header. (#4154)

  • Job Monitor users should only be able to see their own jobs. (#4155)

  • A non-admin login attempting to Add Link / Remove Link from a child to a parent should not require Edit permissions for the parent. (#4636)

  • When an apostrophe is used in a summary attribute, the apostrophe is escaped in the tab name and the value displayed when you hover over the tab name. (#4845)

  • When a folder structure is created within the DAMDrop folder, the DAMHierarchy hierarchy node should be created if it doesn't exist, and the DAMHierarchy attribute in DAMMaster should be populated. (#5203)

  • In the EnterWorks 2020 UI, the Job Monitor shows icons when it shouldn't. (#5674)

  • Lookup Possible Value is not working in Advanced Search. (#5584)

  • Only administrators are able to edit Saved Searches. (#5682)

  • In the EnterWorks 2020 UI, if the user uses the Generate Import Export Template widget to generate a template, category attributes associated with a taxonomy node are not included in the template. (#5695)

  • In the EnterWorks 2020 UI, users cannot complete an import using the Import Widget. After uploading the file, the widget spins like it is processing the import, but it never completes. (#5788)

  • In the EnterWorks 2020 UI, after creating the first record in a linked repository and then using the copy option (viewing in a link table) to create additional records, an error occurs that states the primary key cannot be created. Additionally, if the user has a repository open and tries to copy, it indicates there is a duplicate record with the same primary key even though there is not. (#5962)

  • When the user selects an export template of type .XLSX, they need to have the formatting option "XLSX with Format". (#5979)

  • Export Template displays incorrect Code Set values. (#5995)

  • Shortcuts are only visible to an administrator if the administrator is in only one group. (#6097)

  • Hiding a tab that contains attributes assigned default values results in an error when it is saved. (#6131)

  • If a Preference's option to Display the Attribute Name before the Repository Name is set, each time the Preference is edited, the option will have to be edited again -- it does not persist. (#6277)

  • If the user has a repository opened in a tab and specifies a filter, then switches to a different tab that has a opened repository, when the user returns to the original tab, the filter has been changed. (#6278)

  • When exporting using a catalog hierarchy from PIM, some SKUs export without the hierarchy data, causing issues with the data grouping and sorting in InDesign. (#6320)

  • Code Set owner security sometimes prevents an owner from editing the Code Set. (#6365)

  • If a user impersonates someone who has a different set of security permissions, sometimes not all attributes are editable that should be. (#6366)

  • In the Detail Editor, if the user sends a record to workflow, the resulting pop-up windows displays truncated messages. (#6419, #EW-357)

  • Tomcat service is crashing. (#6422)

  • On repeating fields containing Code Sets, the code and description should be saved as "Code - Description" if the code and description are different, and as "Code" if the code and description are the same. But repeating fields with Code Sets that have more than 100 codes are being saved as "Code" whether or not the code and description are the same. (#6433)

  • Validation Reports invoked through a Scheduled Export are missing Summary Attributes. (#6453)

  • If an attribute is repeatable and contains a hierarchy, the EnterWorks 2020 UI does not allow the user to drill down to nodes. (#6478)

  • In EnterWorks 2020, users can edit or delete a Saved Set, even if it is not owned by the user. The system should only allow Saved Sets to be edited and deleted by the owner or a user with the administrator group/role. The EnterWorks Classic UI does not allow a Saved Set to be deleted by someone else. (#6490, #EW-346)

  • In the EnterWorks Classic UI, impersonated user details are not visible in the user's configuration window. (#6494)

  • When promoting large repositories, the Snapshot population process fails. (#6511, #6422)

  • In the EnterWorks 2020 UI, for all repositories with an Attribute Security Filter assigned, if the attribute value is NULL it will appear as read-only, even if the user has edit permissions to for the attribute. (#6534)

  • The API is not loading the LDAP/S CA certificate correctly. (#6594)

  • The EnterWorks Classic and 2020 UIs are no longer setting defaults on read-only attributes when creating a new record. (#6642)

  • In the Link Relationship Editor, a Max Link Count of 1 is not respected. (#6664)

  • After installing the 10.1.7 patch, the login screen for the EnterWorks 2020 UI is hanging with a spinning wheel on the dashboard tab. None of the controls are active. The browser console shows the error: "Cannot read property 'currentLanguage' of null". (#6667)

  • In the EnterWorks 2020 UI, attributes for which Code Set security is defined are displayed as locked, although they are actually unlocked. (#6679)

  • When exporting data using an Export Template, Code Set values of one record are 'copied' to subsequent records. (#6725)

  • In EnterWorks running on Linux, variants are not being generated. (#6786)

  • The primary key is changed to {} if the user does not have write access. (#6825)

  • After applying the EnterWorks 10.1.7 patch, which resolved an issue with customers using SSO and the impersonate feature, users are unable to log into the EnterWorks 2020 UI. (#6830)

  • The impersonation feature is using incorrect permission settings for DAM related repositories. (#6877)

  • When using a Category type of Import Template containing more than 1,000 mapped attributes, any Snapshot attributes that happen to be in a mapped column position greater than the 1,000th position are not getting updated in the snapshot table; i.e. only snapshot attributes in the first 1,000 column positions are getting updated. (#6943)

  • In EnterWorks running on Linux, an SSO configuration setting appends an extra "http://". (#7035)

  • System Health Widget uses the culturally-insensitive terms Master/Slave for the controller and workers. (Note: EnterWorks is in the process of replacing all Master/Slave references appearing anywhere in the UI, folder and file structures, and service names. However, these terms may still appear in older versions of EnterWorks. For information on replacing these terms in your system, please contact the EnterWorks support desk.) (#7084)

  • Poor promotion performance coincides with an extraordinarily high number of database connections. (#7091)

  • When SSO is configured to not need an IDP signature, the key should not still be required. (#7119)

  • Database transactions are being kept open, which prevents the transaction log from being truncated. (#7292)

  • In the EnterWorks 2020 UI, search filters are not working for Code Set attributes in a linked repository. (#7340)

  • In the EnterWorks 2020 UI, opening a repository from the hamburger menu or from the Shortcuts widget sends the same query twice. (#7365)

  • The Impersonation button takes a long time to appear when a large number of users are assigned. (#7366)

  • Job Monitor: By default, the admin user filter is displayed after a browser refresh. It should not be. (#7383)

  • The System Health Widget does not include Jboss Worker URLs. (#7405)

  • When using LDAP authentication, EnterWorks does not differentiate between an expired password and an invalid password. Therefore, there is no way to tell the user that they need to update their password, as opposed to having an invalid password.  (#EW-1)

  • Clone: Custom widget reinitializes after switching views. (#EW-308, #EW-331)

  • Shortcuts: In the Shortcut widget, if a user impersonating another user selects a Custom URL link, the browser does not redirect to that URL. (#EW-323)

  • Promotions: Record state is not being updated after running promotions. (#EW-392)

  • Impersonation: EnterWorks does not retain user details in the impersonation configuration window. (#EW-508)

  • Events: The user is not able to edit or update an Event. (#EW-529)

  • Saved Search: Unable to edit and save an already existent Saved Search. (#EW-530)

  • API: When a user attempts to delete a template, it is not deleted and an error is generated: "A different object with the same identifier value was already associated with the session. " (#EW-555)

  • Saved Sets: In the EnterWorks 2020 UI, if a user other than the owner or admin drags and drops records into a Saved Set, a permission error is generated but the records are displayed as added to the Saved Set. The EnterWorks Classic UI allows a user other than the owner or admin to drag and drop the records into the Saved Set without generating any permission error message. (#EW-558)

  • Widget: The action toolbar is not being displayed when the user hovers over a newly added widget. (#EW-571)

  • Users should only be able to validate records they own. (#EW-644)

  • Multi-Edit functionality gets stuck and the loader keeps spinning endlessly. (#EW-689)

  • In the Detail Editor, if a user selects a record and clicks on set validation level, the pop-up dialog is empty. (#EW-691)