Skip to main content
All CollectionsProduct Updates
Rethink Winter 2023 Release Notes - v3.24
Rethink Winter 2023 Release Notes - v3.24
Updated over 6 months ago

Table of Contents

New Functionality

  • New Command Center for Buildout Integration

  • Increased Number of Properties in Portfolio Search Lookup

Minor Fixes/Bug Fixes

  • Integration Re-rendering Documents on Data Push from Rethink to Buildout

  • Rethink Help Center Link Updated

  • Improved API Failure Logs

New Functionality

New Command Center for Buildout Integration Sync Log

An improved UI has been introduced within Rethink Settings.

Previously, integration sync messages and errors were displayed together in one large running log. Now, users have the ability to sort sync messages using the Command Center within Rethink Settings.

Increase Number of Properties in Portfolio Search Lookup

Previously, when searching for existing properties to add to a portfolio (via the "Add Property" button), only the first five properties with a matching name appeared. Because of this limitation, some users were unable to locate specific properties to add to their portfolio.

There is now an option to show additional results. Users can now select the "Show all results for...." option in the drop-down to see additional matching properties.

Minor Fixes/Bug Fixes

Integration Re-rendering Documents on Data Push from Rethink to Buildout

Prior to this update, whenever a sync occurred, even listings that had not been updated would still re-render. At best, it was a waste of cloud resources. At worst, for larger documents, users were forced to wait a few minutes for no obvious reason. This has been corrected.

Rethink Help Center Link Update

The link to the Rethink Help Center on the "Rethink Resources" home page component has been updated to point to the new help center website. This change only applies to new orgs that are provisioned after this update. Existing orgs can manually update the component by going into Setup > Edit Page, and editing the hyperlink to: https://rethink.help.buildout.com/en/

Improve API Failure Logs

Previously, API failure logs were only stored for seven (7) days. We have extended this to 15 days. Having a longer timeframe to analyze failures will help us draw necessary conclusions and triage issues more effectively.

Did this answer your question?