Resolved Issues
The following issues have been resolved.
APIs
- Resolved: The
templateSearch
API endpoint returns empty attributes even when the passed in value "incNullAttr" specifies it shouldn't.
Data Management
- Resolved: When a record attribute's history is displayed in a staging repository, if the record has been promoted, the first row of the history displays the attribute's current value in the production repository, but it is not labeled and it has a rollback icon.
- Resolved: In a repository view, if a record contains a URL and the Go button is clicked, a "Same-Origin Policy" error occurs if the client's website is hosted on a different domain than the EnterWorks application.
- Resolved: If a link is added to a record, then you change tabs while attempting to add a second link to the record, the Add Link option disappears.
- Resolved: If a code set is modified using the Classic UI, a history record will
be generated for all the code set's records.
- This has been partially fixed. The new behavior is: In the Classic UI, if a code set is selected, then Edit is clicked, changes made will result in history records being generated for all the code set's records. If a code set is selected, then Open is clicked, changes made will result in history records being generated for only the affected code set records.
- Resolved: When a date or timestamp attribute is cleared, then the record history's Show Diff feature is opened to compare the current and previous version, Show Diff appears blank.
- Resolved: When a required category attribute has no value, the Detail editor displays two error messages instead of one.
- Resolved: In the New UI, code set descriptions are not appearing for linked records when they are included in a preference.
Data Model
- Resolved: When a profile is edited, a snapshot table job is always started even if no attributes were modified.
- Resolved: Code set detail items that have uninitialized multi-language descriptions can cause the Detail editor to display errors and sit in a processing state for several minutes.
Digital Asset Management (DAM)
- Resolved: A scheduled image export indicates that it completed successfully but no files are uploaded to S3.
Hierarchies and Taxonomies
- Resolved: If you try to remove a record from a hierarchy, a confirmation dialog appears that asks if you are sure you want to delete the record. If you select No, the record still is removed.
- Resolved: The last record in the Hierarchical Codes Report is always broken.
Imports and Exports
- Resolved: In EnterWorks 10.5.3, if an import's source file is .XLSX format and its header row starts at line #2 and data rows start at line #3, the import fails.
- Resolved: Export templates downloaded via the Generate Import Export Template widget with an Output Type of Excel Workbook with Format complete, but the output does not have the formatting and code set list of values.
- Resolved: When a template is downloaded via the Manage Import/Export template feature and the last attribute (or last column) is a code set, the dropdown list of values do not appear for that code set.
- Resolved: Whitespace is added to the end of all titles in templates that are exported through the Generate Import Export Template widget, which causes uploads to fail.
- Resolved: Exports are not including data in all specified languages.
- Resolved: If an option is selected in a custom Generate Import Export Template widget then a tab is opened, when you return to the dashboard you are unable to select the option again in the widget.
- Resolved: When exporting using a defined template of XML/JSON type, empty attributes are included even when Include Empty Attributes is not selected.
Migration
- Resolved: If a group is migrated from one environment to another, and capabilities have been removed from that group in the Migrate Out, the Migrate In to the target does not remove those capabilities. It appears to only add any new capabilities set in the migration file.
Publication
- The publish process fails to complete and it generates the error "Exception: Error storing the search config object. The name is already being used by another search config object."
Searches and Filters
- Resolved: When a column filter search is edited as an advanced search, if the Search Criteria field is changed, the search value is removed from the Advanced Search window.
- Resolved: Saved Set import fails when more than one primary key is used to identify records in an import template.
- Resolved: If a column filter is applied in a repository view, then in some of the filtered records the column's values are changed so that records no longer meet the filter criteria, those records disappear from the filtered repository view but they are still included in the list of records that will be edited if all the records in the filtered view are selected and opened to multi-edit.
- Resolved: In the New UI, when an IN search is performed in a repository, entering a comma separated list of values does not return records. In previous versions of EnterWorks, it would return the expected records.
- Resolved: When a comma separated list of numerical values is entered into a column filter IN search, they are treated as one number value instead of a list of values. The search is not applied correctly. If the list of values is entered into an advanced IN search, the search is correctly applied.
Validation
- Resolved: The B_SNAP_VALIDATION_% table's "message" field is not populated with JSON validation error messages.
Known Issues
- Fusion is not displaying sources for existing applications.
- In Fusion, if a user exports an existing application or attempts to disable encryption, Fusion returns an "illegal base64 character 7b" error message.
- If the Upload Digital Assets widget is not configured to open in a pop-up
window, if the information icon is clicked then Clear is selected, an
empty window appears.
- Workaround: To close the empty window, click anywhere outside the widget.
- In the Classic UI, if a code set is selected, then Edit is clicked, changes made will result in history records being generated for all the code set's records instead for only the affected code set records.
-
If an Advanced Search using the In search criteria is performed on a numeric attribute, search terms manually entered are not applied, are not retained, and are not displayed in the breadcrumbs.
- Workaround: Open the Advanced Search, select the attribute, and in the Search Criteria field, select In. Open the Lookup function and select any value. It will be added to the Search Term field. Remove it from the Search Term field. Now any search terms you enter manually will work as expected.
- Workaround: Use a column filter instead of Advanced Search.