Reach Engine 2.9.0 Release Notes

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. 

Results available here: https://docs.google.com/spreadsheets/d/1RM_jGQxEQnNuXu6-zsFry5uc8bPunRS8KHjYp7DFI-I/edit#gid=0

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

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.

Our deployment process is updated to account for the separation of the UIs from the core platform.

The About modal in Spartan now displays the version of Access and Spartan

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. 

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. 

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. 

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. 

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”

The Access menu option and Access Users page have been renamed to "Reach Engine Users".

Enhanced URL Encoding can now handle additional special characters in Proxy filenames. 

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.

sizeExpression and offsetExpression now work correctly in the RQL workflow querystep.

The text displayed in a browsers tab now accurately reflects the user's page. 

range-header added to facet group API to allow proper pagination through facet groups. 

Assets now ingest as expected and no longer stall or fail.

preventing null values from being added to the migrator map

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. 

A new joinPath function is now used to combine paths in app-workflows, studio-system-workflows, and collaborate-workflows.

Changed workflows in app-workflows:

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. 

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.

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.

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.