Tiny Release, Big Impact

Yes, you are reading this right, a brand new release! We’re shipping a production release extremely close to the last release to address an important issue. This release does not include any new features, but solves a key frustration that has plagued users since the v2.3.0 update. All the updates for this release affect the front-end.

Goodbye Incognito to View Files

An unintended consequence of the caching added in v2.3.0 to improve performance is refresh tokens were also being cached causing users to “log out” when viewing the file, thus always resulting in an error page. A quick workaround was to view the files in Incognito (Chrome) or Private Browsing (safari).

Today we fixing this oversight so documents can be seen as you’d expect.

Fixes and improvements

• Front-End: Removed the legacy Winstuff Service which is no longer used.
• Front-End: Fixed an issue when the Collections index did not display its children documents until the user manually refreshed the page. We fixed the collection count so documents can be seen at once.
• Front-End: Fixed an issue where users could not open documents in Redacted.ai due to an invalid token ID. We now start a fresh session with OneTrust Authentication.
• Front-End: Fixed an issue relating to file scrubbing and update causing extra storage trigger of type BlobCreated. This result was causing unexpected checks of content item, which fail and invalidate the document. We now check if the document is in the expected state in advance.
• Front-End: Fixed 2 grammar mistakes. Thanks to all our dictionary warriors and friends from the grammar police.
• Small changes to the way our organization update method works. This change is required for the new upcoming ‘review modes.’ – WHAT ARE REVIEW MODES?! – Shhh, we’ve said too much already. Remember no features this release, but stay tuned.
• Added ‘gh token’ and testing action. If you know, you know. 👍