Following is this list of resolved issues in this release:
- EW-7861
- The "Send to Workflow" submission header in the new UI has been improved to display:
"WorkflowName - TaskName. - EW-14819
- The Edit button can now be enabled, and the attachement can now be uploaded to the
work item using the configuration property
attachement.enabledin Config.property file. - EW-15271
- Rules duplication issue during profile migration has been resolved.
- EW-15346
- Values will now be stored in the database without dashes for custom patterns.
- EW-15347
- The issue with the dropdown list failing to filter values when updating an attribute has been resolved.
- EW-15349
- The "Send to workflow" option, which was previously enabled when "All" was selected, has been disabled. However, it will continue to work with current page selection.
- EW-15375
- The error that occurred while sorting the State Attributes added to a preference is resolved.
- EW-15394
- Read only/non editable attributes based on attribute security filter will be greyed out in the Business UI.
- EW-15395
- The issue where several DAM master date attributes, including DateTime, DateTimeOriginal, and LastUpdateDate, failed to populate after the upgrade, has been resolved.
- EW-15423
- Filtered records saved into a saved set were not being successfully sent to the workflow are now correctly sent to the workflow.
- EW-15433
- The issue causing email links to be truncated in the HTML editor, resulting in problems with the Send Email BIC, has been resolved.
- EW-15450
- Added Debug flag to the MQCommunicationsManager and DBQueryPool class file to enable logging only when debug flag in set to true.
- EW-15460
- Invalid Query issue resulting from EpimUtils.isImportActive(). IsImportActive() has been resolved.
- EW-15484
- When a new repository record was created using the Update Repository Record BIC activity with the trigger option enabled, the trigger was not being invoked. This issue has now been fixed, and the trigger is properly invoked.
- EW-15494
- When importing a file with the multi-repository import template, the key column linking the repositories was not being populated due to Migrated Templates. This issue has now been resolved.
- EW-15496
- Presave callout issue introduced due to migration has been resolved.
- EW-15499
- When a scheduled export is based on a template, the Image Type and Image Context fields are not required, and attempting to include them can cause errors. Now, the export job will run successfully with the image parameters defined by the template.
- EW-15501
- For Scheduled Exports, the image type and image context are now not mandatory, and the parameters defined in the template are used instead.
- EW-15532
- All special characters will now be allowed when creating a user preference in the Classic UI.
- EW-15535
- The issue of category attributes not being populated in the snapshot_KV table during imports using a Category type template into the repository has been resolved.
- EW-15536
- In the 2020 UI, grouped attributes that were not appearing in the preference view, even when selected to show, are now visible.
- EW-15570
- The issue of Primary Keys exceeding the maximum length in Services Framework repositories has been resolved.
- EW-15571
- The displayed record count for a specific node was inaccurate, showing more records than existed. This issue has now been resolved.
- EW-15576
- Previously, the cleanup job that did not remove images from the Azure container after uploading and deleting them now successfully deletes the images from the container.
- EW-15578
- Triggers are now enabled for Scheduled export repository.
- EW-15713
- The New button under the Actions tab now enables you to create new folders within various sections including Repository, Code Set, Taxonomy, Hierarchy, Export Style Map, Export Template, Publication Style Map, Syndication Template, and Exchange Template folders in the Classic UI.
- EW-15725
- The Audit History page can now handle null pointer exceptions when attributes are deleted from the Repository.
- EW-15802
- The New button under the Actions tab now enables you to create new folders within various sections including Repository, Code Set, Taxonomy, Hierarchy, Export Style Map, Export Template, Publication Style Map, Syndication Template, and Exchange Template folders in the Classic UI.
- EW-15809
- If there are no records to validate, the validation job will no longer process any records.
- EW-15848
- Snapshot job failed when adding a new attribute and making it a relational column in Repository > Edit > Attribute Properties without clearing the cache. This issue is now resolved.
- EW-15871
- Case sensitivity has been disabled for Primary Key attributes during the import process.
- EW-15909
- Digital assets with in their filenames using
;and%, which previously could not be downloaded by users from the UI, are now fully accessible and downloadable as expected.
Performance issues
- EW-15440
- A few deadlocks that occurred when multiple jobs ran concurrently with promotion jobs
have been resolved. Set shared configuration property
job.controller.promoteJob.runAsTopSysJobto true for many jobs running concurrently with promotion jobs. - EW-15454
- Sleeping sessions issues corresponding to
calloutbic.setPropertiesandExport cleanup jobhas been resolved. - EW-15468
- Import jobs were stopping due to code exceptions when a large number of work items accumulated in the lock workflow Business Identification Code (BIC) and the EPX services were restarted. This issue has now been resolved.
- EW-15511
- Scheduled jobs were remaining in the Workers even after being aborted or failing, preventing Workers from accepting new jobs. This led to a significant amount of jobs accumulating in the queue. This issue has now been resolved.
- EW-15523
- The repository listing page in the Classic UI that experienced performance delays when containing large export templates has been resolved.
- EW-15809
- The validation job completes successfully without errors when there are no records to validate, resulting in no processed records. Additionally, when invalidated records are present, the job handles them but still completes successfully. This issue has been resolved.