The following issues have been resolved in this release:
Administration and Security
- EW-19763
- Users were unable to delete certain repositories from the UI, even after recreating them for testing. Attempts to delete the repositories resulted in errors, preventing cleanup of the target folder. This issue has been resolved. Repositories can now be successfully deleted from the UI without exceptions. If a DSN is associated with a repository, the system displays an appropriate message, and once the DSN is removed, the repository deletes as expected.
Content Management
- EW-19760
- When a user with only read and edit permissions attempted to delete a taxonomy node, the deletion failed without displaying any permission-related error message.
- EW-19761
- Previously, category-specific and dynamic attributes with subset restrictions did not
generate validation errors when imported with values outside the allowed subset. Records
assigned to child taxonomy nodes incorrectly appeared valid, even when the inherited
attribute value did not conform to the defined subset.
This issue has now been resolved. When invalid subset values are imported, the record is correctly flagged as invalid, and the validation details are logged properly in the validation database table.
- EW-19768
- The Update Distinct Child Values callout was incorrectly converting
DATE attributes to a datetime format when copying values from a parent record
(PDC) to its child record (VDC). For example, a date stored as MM/dd/yyyy in the
PDC was being inherited by the VDC as yyyy-MM-dd hh:mm:ss.
This behavior has been corrected. DATE attributes are now inherited in the proper date format defined in the repository, while other data types continue to function as expected.
- EW-19769
-
The values for the
plt.map.mssql.BINARYandplt.map.mssql.BITproperties were being interchanged, resulting in incorrect configuration behavior. This issue has been fixed. These shared configuration values are now preserved and will not change. - EW-19770
-
Setting a null value through the API did not append the expected default value, resulting in incomplete RAF data. This issue has been fixed. When a user sends a null or
0value, the system now correctly applies and appends the default RAF value. - EW-19779
-
The Copy action in the Link Table editor behaved inconsistently between the Classic UI and the New UI. When users with read-only permission on the join attribute attempted to copy a linked child record, the New UI displayed a success message but did not actually create the copied record, while the Classic UI handled the operation correctly.
This issue has now been resolved. The New UI consistently copies the child linkRelationship record and includes the join column value regardless of whether the user has edit permission on the join attribute matching the expected behavior observed in the Classic UI.
Digital Asset Management
- EW-18079
- Previously, the DAM Trigger did not use the correct default value for the Image
Context attribute when creating new DAMLink records. This caused the attribute to
always default to the Profile-level setting instead of the repository-level
configuration.
This issue has now been resolved, and the DAM Trigger correctly applies the default Image Context value based on the repository configuration.
Job Processing (Import/Export/Validation/Promotion)
- EW-19759
- Previously, the Import option to process a specified number of lines (using the stop row setting) did not function as expected, resulting in more records being imported than intended. This has now been corrected. When a stop row value is provided in the import template, the system correctly imports only that number of records, even when the source file contains additional lines.
Workflow and Services Framework
- EW-19762
- The Import widget in HomeConfig did not retain its assigned import template during
migration. After migrating out and migrating in the HomeConfig, the widget appeared
without the configured template.
This issue has been fixed, and the Import widget now correctly preserves and displays its assigned import template across Enable2020 UI (group and user configurations) and Classic UI (group configurations).