| Work Item Type | Title | Release Notes |
|---|---|---|
| Issue | Make displaying thumbnails in asset list view optional |
To improve performance, thumbnails are now hidden by default in list view only. You can optionally enable the visibility of small asset thumbnails in list view to show a small thumbnail in the first column of the list view.
![]() |
| Issue | Gather Baseline Performance for Loadless Steps |
Results available here: https://docs.google.com/spreadsheets/d/1RM_jGQxEQnNuXu6-zsFry5uc8bPunRS8KHjYp7DFI-I/edit#gid=0
|
| Issue | Establish Performance Baseline for Query Workflows |
Results Available Here: https://docs.google.com/spreadsheets/d/1RM_jGQxEQnNuXu6-zsFry5uc8bPunRS8KHjYp7DFI-I/edit#gid=0
Testing Materials Available Here: https://github.com/levelsbeyond/reach-testing-materials/tree/master/workflows
|
| Issue | Establish Baseline Performance for SaveAssetStep | Results Available Here: https://docs.google.com/spreadsheets/d/1RM_jGQxEQnNuXu6-zsFry5uc8bPunRS8KHjYp7DFI-I/edit#gid=0 Testing Materials Available Here: https://github.com/levelsbeyond/reach-testing-materials/tree/master/workflows |
| Issue | Unlock facets when searching |
Previously a facet selection could not be updated until search results were loaded completely. Facet selections can now be modified and updated up to every 100ms, improving the speed at which you can refine searches. Note that in situations where search results are delayed, it may be possible to select an option that is not valid after the results of the previous selection are returned.
|
| Issue | Enhance ansible playbook to deploy and configure nginx |
Our deployment process is updated to account for the separation of the UIs from the core platform.
|
| Issue | Display UI Versions in About Modal |
The About modal in Spartan now displays the version of Access and Spartan
![]() |
| Issue | Implement write-through cache for Context Data Def Values |
Levels Beyond has implemented a write-through cache which resulted in more than a 75% reduction in workflow completion time between 2.8.0 and 2.9.0.
Details:
To give multiple workflow runtime nodes access to the active context data, we must write to the database workflow_context_data_value table. To reduce the number of times we read from the database, only a single workflow runtime node at one time will write entries for WorkflowContextDataValue. Only the webapp on the executing node will read from the database, which allows us to use a local cache for the executing runtime and not worry about distributed caching or eviction policies. We can read from the database if no value is yet cached, and with a write-through approach, write to the database as necessary while simultaneously writing the new value to the cache and avoiding reading from the database.
|
| Issue | [REACH-34423] (Spike) Audit Vantage Connector Using Vantage 8.0 |
Tested Reach Engine's default ingest workflows running under Reach Engine 2.8 against Vantage 8.0. All workflow testing was successful. Additionally, Vantage Profiles are now synchronized into Reach Engine 2.8.
|
| Issue | Improve Collection Modal 'Submit' Experience |
Collection modals now provide you with visual feedback to indicate your submission is processing. The "Confirm" button animates and shows "Working on it" while the action is processing. The additional feedback will help you avoid duplicate submissions of the modal.
![]() |
| Issue | Improve Change Password Modals 'Submit' Experience |
When changing your password, you now see visual feedback that indicates your submission is processing. The "Confirm" button animates and shows "Working on it" while the action is processing. The additional feedback will help you avoid duplicate submissions.
|
| Issue | In App Feedback |
You can now provide direct feedback about Reach Engine from within the application. When enabled, a new top level “Feedback” menu displays directly below the user icon--look for the bullhorn icon. The menu allows you to "Give Feedback" and answer some questions and provide feedback in a survey. The menu also allows you to "Request a Feature" in the Reach Engine Feature Portal, where you can submit new feature requests, see other feature requests, vote on features, provide insights for other feature requests, and see what is currently in progress and recently released.
This feature is optional per installation and can be toggled with the dynamic property “feedbackEnabled=true/false”
|
| Bug | Spartan users page name is "Access Users" |
The Access menu option and Access Users page have been renamed to "Reach Engine Users".
|
| Bug | Image Single Asset View | Not able to re-size the image as expected. |
Sources and Proxies now resize properly, based on user selection.
|
| Bug | [REACH-34563] Access not reading proxies with special characters in file name |
Enhanced URL Encoding can now handle additional special characters in Proxy filenames.
|
| Bug | Collection Palette does not Auto Update Asset Counts on Remove from Collection |
When assets are removed from a collection, the Collections Palette update now happens in less than one second (on systems with standard usage). Note that the Assets count in the header may take longer to update, especially when a large number of assets are removed. Generally, updates occur within 2-4 seconds.
|
| Bug | rqlQueryStep sizeExpression and offsetExpression are ignored |
sizeExpression and offsetExpression now work correctly in the RQL workflow querystep.
|
| Bug | System and Technical Fields are included in Batch Update Field Options |
Technical and System metadata fields are now read-only for users and no longer available for Batch Update. They are also not available on regular inspector panel edit.
|
| Bug | Browser tab - Spartan browser tab info update |
The text displayed in a browsers tab now accurately reflects the user's page.
|
| Bug | FacetGroups API does not return correct range header |
range-header added to facet group API to allow proper pagination through facet groups.
|
| Bug | Drop Frame flag incorrect when creating drop frame timeline |
Timelines are now created with appropriate timecodes. Dropframes now display semi-colon ";" and non-dropframes now display colon ":"
|
| Bug | [REACH-34840] Filenames which include non ISO-8859-1 characters cannot be ingested on a system using S3 temp |
Non-ISO-8859-1 characters can now be ingested on s3.
|
| Bug | Ingests failing immediately with null fileToIngest value |
Assets now ingest as expected and no longer stall or fail.
|
| Bug | Filesystem migration fails for empty s3.perms entries |
preventing null values from being added to the migrator map
|
| Bug | Right Hand Panel - Workflow file selection: Long file names cut off at edge of browser |
Filename now wraps as expected, with no horizontal scroll bar present. Access still has the filenames in one line with a horizontal scroll bar.
|
| Bug | When trying to load Categories in admin tab Reachengine UI crashes |
The Categories page now calls the API more efficiently when populating the list of Roles associated with a Category. This fixes the problem where, in environments with many Categories and many Roles associated, too many requests caused certain browsers to block the API requests.
|
| Bug | Make System Workflows more resilient Storage Directory trailing slash changes |
A new joinPath function is now used to combine paths in app-workflows, studio-system-workflows, and collaborate-workflows.
Changed workflows in app-workflows:
Changes workflows in studio-system-workflows:
Changed workflow in collaborate-workflows:
|
| Bug | Metadata Group / Role Association -- unable to add any NEWLY created metadata groups to roles. |
Allow large numbers in security_role_permission_context to account for environments where certain identifiers have grown past the maximum value of an integer field.
|
| Bug | Aspera Connect SDK requirements have changed and broke our integration | |
| Bug | Webapp doesnt load workflow sdk correctly on some fresh installs |
Updates to the Ansible deployment playbooks were made to solve the scenarios where a critical entry to Reach Engine's context.xml file was not inserted.
|
| Bug | Asset edit curtain displays incorrect Date Time Format |
Previously Date/Time values displayed in the UI in a format that was difficult to decipher. Dates and times now display in a more clear format, for example: 2020-01-21 at 5:00:00 PM
|
| Bug | Spartan Batch Download System Workflow is not working |
The Batch Download System workflow is authored as shown in the user interface false and should only be called by the batch download system action and not directly by a user.
|
| Bug | Non-admin users unable to see assets/left & right hand panels |
Non-Admin users can now see the right and left panels as expected.
|
| Bug | Error on edit of different picklist in group after single picklist value deletion |
Although a rare occasion, it was possible that the UI would display picklist values that had recently been deleted. This would result in a log entry like Query for metadata field option '98fa3308d9274b19b8d7eb35221dbb39' on metadata field 'singleToBeDeleted' returned '0' results instead of 1. Picklist option selections are removed on single picklist when selected option is not found, as its being done with multiplicklist.
|


