EnterWorks 10.4 Resolved Issues

Resolved: When a migrate out was performed, the selection of server properties were not preserved in the migration specification file. (Support 52716, Jira EW-3791)

Resolved: In the Job Monitor, when a user was being impersonated, the jobs were not being filtered for the impersonated user. (Support 52873, Jira EW-3792)

Resolved: In the New UI, if a record is open in the detail editor and the user is editing a DATE/TIMESTAMP field in a linked record, the field will not show the new value until the linked record is refreshed. (Support 49856, Jira EW-3794)

Resolved: In the New UI, a user was unable to add more than one link search condition in an advanced search. (Support 52293, Jira EW-3796)

Resolved: After Unified Parent Child View (Merge View) setup, EnterWorks became non-responsive for repository views and searches. (Support 53282, Jira EW-3803)

Resolved: When DATE attributes were validated, invalid dates were not being marked as invalid. (Support 50040, Jira EW-3805)

Resolved: When a link relationship was defined, Open Link Table in Tab with Preference was not working. (Support 54132, Jira EW-3829)

Resolved: In the New UI, global default preferences were overriding local user default preferences. (Support 53371, Jira EW-3867)

Resolved: When a date format was set as "dd MMMM yyyy", the date was displayed as "20 09September 2020" in the EnterWorks UI. If Evolve fetched the date using the EnterWorks API, the date was fetched as "20 09September 2020". When a date format was set as "dd-M-yyyy hh:mm:ss", the date was displayed as "02 January 2018" in the EnterWorks UI. If Evolve fetched the date using the EnterWorks API, the date was fetched as "02 January 2018". (Jira EW-3870)

Resolved: When a repository view was filtered, if an export current view was attempted, an error was generated. (Support 52702, Jira EW-3896)

Resolved: When a multi-repository import template was used to a import a file to multiple repositories, even though the import was successful, validation was not completing and all the imported records in all the repositories were set to the invalidated state. Sometimes the import status showed an error and other times it showed complete, but the logs showed that validation was not complete. (Support 43334, Jira EW-3912)

Resolved: In the New UI, when a record is in the Detail Editor, when a non-administrator user views a table (grid) of linked records, URL attributes do not display a "GO" button. (Support 53350, Jira EW-3968)

Resolved: When a record was being cloned, the security context was not copied over correctly. A workaround was to run a job periodically that set the correct security context. (Support 54109, Jira EW-4001)

Resolved: When a user was being impersonated, the Shortcuts widget was not being populated correctly. (Support 45649, Jira EW-4196)

Resolved: When a repository view was filtered by a linked attribute value, the resulting records could not be dragged and dropped into a saved set. (Support 52902, Jira EW-4206)

Resolved: In the New UI, when a multi-repository import was being performed, not all the columns in the file were getting mapped as defined in the attribute mapping screen. Also an error was reported that said two columns had the same PkeyInd, which was not the case. The attributes referenced in the error kept changing. (Support 52476, Jira EW-4208)

Resolved: During multi-edit, when certain types of code set attributes are being edited, the Clear option was not appearing. (Support 52176, Jira EW-4209)

Resolved: After editing a code set, the data cache had to be cleared before all the edits were available for use. Now edits to code sets are immediately available. (Support 51907, Jira EW-4211)

Resolved: In the New UI, if an advanced search using the IN operator was performed and it returned more than 50 results, the export would fail. (Support 55197, Jira EW-4400)

Resolved: When a number of repository tabs are opened and closed, then a new repository tab is opened, search calls for the previously closed repositories repeat. Over time this causes a significant system slow down. (Support 55470, Jira EW-4440)

Resolved: In some instances, opening a repository record in workflow took a long time. (Support 53452, Jira EW-4444)

Resolved: Sometimes custom preferences were acting inconsistently erratic in a variety of ways. (Support 55277, Jira EW-4478)

Resolved: When a saved set was imported with more than one primary key selected, the import would hang the system. (Support 46297, Jira EW-4479)

Resolved: In the New UI, in the Linked Content Report widget, when a one to many link relationship with composite join conditions was selected, only the last join condition was actually used to obtain the linked record counts. (Support 45870, Jira EW-4524)

Resolved: When a record was being edited in the New UI's Detail Editor, a tab other than the first tab was selected, then the record was saved, the screen refreshed to show the first tab and its contents, followed by the contents of whatever tab was selected. (Support 55391, Jira EW-4532)

Resolved: Sometimes when a PSD image was uploaded it would be converted into a white JPG image. (Support 56037, EW-4651)

Resolved: Editing an HTML field inserts two periods at beginning of the HREF link. (Support 54528, Jira EW-4760)

Resolved: In the New UI, when promoting records, if the option for promoting all records was selected, only one page of records were promoted. (Support 49584, Jira EW-4776)