Resolved issues - SmartTemplate_Pro - Precisely_EnterWorks - Sales_and_Services_Portal - EnterWorks - Fusion - Match_and_Merge - Latest

EnterWorks™ Release Notes
Product type
Software
Portfolio
Verify
Product family
EnterWorks™ software
Product
EnterWorks™ software
Version
Latest
ft:locale
en-US
Product name
Precisely EnterWorks
ft:title
EnterWorks™ Release Notes
Copyright
2025
First publish date
2007
ft:lastEdition
2026-05-21
ft:lastPublication
2026-05-21T06:48:36.613000
L1_Product_Gateway
Verify
L2_Product_Segment
Data Quality
L3_Product_Brand
Precisely Enterworks
L4_Investment_Segment
Precisely Enterworks
L5_Product_Group
Precisely Enterworks
L6_Product_Name
Enterworks

The following issues have been resolved in this release:

Administration and Security

EW-17874
Previously, profiles containing linkRelationship attribute groups with special characters (such as "&") could not be migrated due to special characters not being escaped correctly in the migrateOut XML file. Now, these profiles can be migrated successfully, with special characters handled correctly.
EW-18251
The hamburger menu failed to display all repositories when a repository folder contained more than 20 repositories, causing some to disappear when expanding groups. The issue was fixed, and now all repositories are displayed correctly, even with large numbers.
EW-18810
When a numeric attribute with a code set assignment is added to a profile, a common attribute is also created with the code set assigned. In previous versions, removing the code set assignment from the attribute did not remove it from the common attribute, which prevented the code set from being deleted. Now, the code set is removed from the common attribute when it is unassigned from the profile attribute, allowing the code set to be deleted if it is not assigned to any other profile attribute.
EW-18929
Resolved a migration error during the Services Framework upgrade that occurred when the Change Notification Registry profile XML description fields contained the "<" or ">" characters. These characters are now replaced with "[" and "]" to prevent the issue.

Content Management

EW-4488
When configured to create a saved set through the Import widget in the New UI, it did not generate the designated saved set after a file was imported.
EW-17537
Issues with filtering columns using the IN clause have been addressed. When selecting multiple values from the grid interface (ag-Grid), the column filter now correctly retains all selected values, even when additional filters are applied.
EW-17755
Configuring multiple Linked Content Report widgets on the same dashboard no longer produces duplicate temporary saved sets, which resulted in errors being logged.
EW-17948
Decimal attributes with identical scale and precision, like DECIMAL(3,3), no longer cause validation errors for valid values such as .555.
EW-17988
When viewing the linked digital assets (associated with a record in SKU/part/item repository via linked relationships) using the Open Link Table in Tab feature, single-click cell-level editing was not allowed even when the Editor button was enabled (as it can be in the Repository Gallery view). This has now been resolved, allowing users to perform cell-level edits directly from the Open Link Table in Tab view.
EW-18266
Including the control attribute for dynamic attributes in the display list of a link relationship no longer causes a duplicate column error when viewing the linked list in the detail editor for the parent repository record.
EW-18552
When using multi-edit in the 2020 UI, integer attributes that used a codeset could not be saved as the Save button stayed disabled. This is resolved now.
EW-18557
Resolved the issue where records in the Repository List view were not correctly flagged according to validation rules assigned to specific languages on multi-language attributes, and their details were not recorded in the B_SNAP_VALIDATION table after the Validation job ran.
EW-18559
Resolved an issue where the attribute list failed to populate when adding composite indexes in a repository.
EW-18748
The default maximum Metaspace memory settings for EPXJboss, EnableServerWildflyController, and EnableServerWildflyWorkerX services have been updated to a maximum of 512m when their configured values are lower.

Digital Asset Management

EW-18079
The DAM Trigger feature did not apply the configured default value for the Image Context attribute in the DAMLink record it created, instead using Main. Now, the DAMLink record is created with the default value for Image Context.
EW-18585
DAM processing no longer attempts to generate variants for non-image files, which used to take a long time to process and sometimes get stuck in the DAM working folder. Now, only PDFs and image file types have variants generated.
EW-18849
DAMDrop no longer leaves uploaded files in the working directory. Files are now cleaned up automatically after upload.
EW-19581
Resolved an issue to ensure non-image asset originals are saved during job uploads.
EW-19487
Added a validation to generate variants for PDF files only when configured in the file extension code set.
EW-18849
DAMDrop now automatically cleans up uploaded files from the working directory, preventing leftover files after upload.

Job Processing (Import/Export/Validation/Promotion)

EW-17135
The EDI Preprocessor was retaining data when moving from one section to a sibling section if the original section was not marked as an output row. This caused incorrect data to appear in subsequent output.
EW-17756
Configuring multiple Linked Content Report widgets on the same dashboard no longer produces duplicate temporary saved sets, which resulted in errors being logged.
EW-17804
Previously, category-specific attributes linked to taxonomy nodes could not be deleted. Such attributes can now be deleted.
EW-17834
Previously, the Classic UI displayed all attributes from the import template, even if they were not present in the uploaded file, which could result in data being overwritten. Now, only the attributes present in the uploaded file are shown during attribute mapping, preventing unintended data loss.
EW-17940
Previously, when using Edit All to update records, the system would also include read-only fields, which caused permission errors (as user did not have edit access). With the latest fix, only the fields users are allowed to edit will be included in the save operation.
EW-17996
When exporting repository records with the Separate Files for Category Attributes option, the export header displays the selected language names if they are defined and the Shared Configuration property EXPORT.MULTILANG.HEADERS.USE_LANG_EXT is set to false. If names are not defined in the selected language, or if the property is set to true, the export header displays the attribute names with the language extension as a suffix.
EW-17999
During migration, attribute name references in syndication template mapping detail formulas were not resolved correctly if the attribute IDs differed between the source and target environments. This issue has been resolved.
EW-18267
The REST API call for adding savedSets was causing database blocking when adding a large number of records to a saved set while other operations were running. The performance was improved by processing inserts in batches and using WITH (NOLOCK) for selects. So now it may take more time to reflect all records in saved sets as records are updated in batch.
EW-18297
When using SmartTemplatePro to create records with en-US set as the default language, the system was incorrectly adding an _en-US extension to attribute names (e.g., F_xxxxx_en-US instead of F_xxxxx). This caused data not to appear correctly in the UI or snapshot tables, even though it was saved in the database. The issue has been resolved and now records are created correctly without adding any extra extension.
EW-18373
Multi-language exports now support both the new translated header format and the legacy suffix format. Setting the Shared Configuration Property: EXPORT.MULTILANG.HEADERS.USE_LANG_EXT to true will display the language extension suffix for each multi-language attribute. Setting the property to false will display the language-specific names if defined for each attribute in the Profile. If the language-specific name is not defined, the language extension suffix will be used. Use EXPORT.MULTILANG.HEADERS.USE_LANG_EXT to control export header language display.
EW-18404
Publication jobs now use an in-memory system user session instead of creating a separate user session for each root repository record multiplied by the number of linked repositories in the publication. This greatly improves performance and also significantly reduces the growth of the user session table. This change improves both performance and system resource usage.
EW-18485
Previously, editing an import template with a name or description for a deleted language caused an error. Now, templates can be edited and saved successfully even if a referenced language has been removed.
EW-18593
Import job resulting status (i.e. Complete or Error) will be set to Error if there is any instance where a record could not be inserted/updated due to user permissions and/or import job specifications. In previous versions the job status would have said Complete, and in that case users that don't check the import job log would not know something wasn't processed. The processing of the Import job has not been changed - only the resulting job status. Always check the import job log for details if the job status is Error.
EW-19007
Improved processing performed by the Scheduled Import Pre-Processor: PreProcessXLSXAddFields when importing large XLSX files. Prior to this update, the pre-processor used a lot of memory and took a long time to finish.
EW-19049
Scheduled Exports with Delta saved set creation now fail as expected when record additions to a saved set encounter errors, preventing the export from continuing with incomplete data.
EW-19050
When running the Populate Missing Records job for a repository with no missing records, the job completed successfully but displayed an incorrect closing status message showing "null" causing confusion. Now it displays an accurate message indicating that the process completed successfully and that 0 records were processed.
EW-19589
Fixed an issue where records assigned to a child taxonomy node were not deleted after changing the parent node

Workflow and Services Framework

EW-18380
A work item opened from the Workflow Task Manager widget by a user no longer locks the work item for that user, which prevents other users assigned to the same group from completing it.
EW-18776
The Send to Workflow option in the Repository View widget now successfully sends the associated work item when the checkbox for a repository record is selected. Multiple records can be selected to launch work items in a workflow, but advancing records already in workflow must still be done one record at a time. To advance records already in workflow, process them individually.