In the process of enhancing our software, we have identified behavioral changes between EnterWorks versions that we want to bring to your attention to help customers know what to expect when they upgrade to a newer version. By proactively communicating these known issues, we aim to foster smooth transitions between versions and to empower users to maximize the benefits of our latest releases.
The EnterWorks 11 release has the following known limitations.
- Applying an IN search on a comma separated list of INTEGER or BIGINT numeric control type attributes converts the list of search terms into an expression, such as '"1E+23 ".
- Applying an IN search on a comma separated list of DECIMAL numeric control type attributes converts the list of search terms into a single value.
- When a repository record is created using the Update Repository Record BIC activity if the option to validate records is set to true, the record is created but it is not validated.
- When EnterWorks is installed, when the
install-part2script completes processing, it asks you to press any key to continue, then a warning message appears that states what to do if there was an error when PIM Web services were deployed. If a key is pressed before the warning message is issued, an error message appears that directs you to restart EnterWorks services and run theredeployPimWebServicesscript, even if PIM Web services do not need to be re-deployed. - When the records assigned to a repository's hierarchy node are displayed and the option to include children or include parents is selected, if the same records are assigned to more than one of the nodes displayed, an incorrect record count is given.
- Digital asset files in the DAMDropOnDemand folder are processed but the originals are not deleted from the DAMDropOnDemand folder.
- If a repository view is filtered on a saved set and one of the records is opened in the Detail editor, you cannot send the record to workflow.