2025.6.1.1869 – Production Deployed 7/31/2025
Includes updates from both versions 2025.6.1.1865 and 2025.6.1.1869, noted below.
Client Reported Issues
2025.6.1.1865 – Stage Deployed 7/14/2025
-
Service contact smtp logs in Review App envelope details are incorrect ESS-22192, ESS-22199
-
Issue: Incorrect SMTP logs returned when there are multiple service contacts.
-
Fix: The same query was applied from the Review app service contacts panel to get the correct related service SMTP log for the Envelope Details.
-
Slowness reported from time of envelope acceptance to cases generating in Odyssey ESS-19720, ESS-20936
-
Issue: Clients were experiencing long wait times while accepting envelopes.
To accommodate document processing time, the application was originally waiting 5 seconds between polls to begin processing the next document.
For example, the minimum for 10 documents to process was 50 seconds.
-
Fix: The polling time has been reduced to 1 second between polls. For example, 10 documents will now only take a minimum of 10 seconds.
2025.6.1.1869 – Stage Deployed 7/15/2025
-
Review History Not Pulling any Envelopes ESS-21632
-
Issue: Review History does not display envelopes after the user has accepted envelopes when CSM is enabled.
-
Fix: When CSM is enabled, newly added users do not have locations saved the same way non-CSM-created users do, and the query to display Review History
did not account for the change. The fix involved passing the locations for the CSM users as needed.
New Functionality
2025.6.1.1865 – Stage Deployed 7/14/2025
-
Indicate Agency for Notifications in Review REV-3375
- In support of a process where agencies need to receive notifications about filings in a case, Review now displays the Agency field for configured case types and locations.
- Only one agency can be verified on a case, but the reviewer can add, update or remove the agency until the agency is verified.
- Once the reviewer accepts one or more filings on an envelope with an agency selected, that agency is verified and cannot be updated or removed in Review.
- The verified agency displays on the Case tab during envelope review and on the Envelope Details page.
- For further details about configuration (including associating a firm to an agency for notifications), filer behavior, and EFM messages, see Tyler EFSP and EFM documentation and Release Notes.
- NOTE: Agency notifications require EFM 2025.3 and EFSP 2025.6.
Internal Updates
2025.6.1.1865 – Stage Deployed 7/14/2025
-
Newly-selected Agency/Filer Type/PRFF does not always save when user clicks End Review REV-3770
-
Issue: When the user clicks End Review immediately after changing the Agency (in the Case panel), the Filer Type (in the Envelope panel),
or the Party Responsible for Fees (in the Fees panel), the change is not always saved when the envelope is reopened.
-
Fix: A code change was made to change the order of the save process, which reliably saves the newly-selected options when the reviewer clicks End Review.
Performance Updates
HOTFIX to Prod 2025.6.0.1865, Stage 2025.6.1.1869 – Deployed 7/24/2025
-
Improve code description translation from cache REV-3812 - Deployed to Stage and Prod 7/24/2025
-
Code cache retrieval has been optimized to speed up queue loading and move-to-next-envelope functionality.
-
Review History Proc update REV-3785 - Deployed to Stage and Prod 7/24/2025
-
Improve loading performance of Review History.
-
Review Queue Proc update REV-3784- Deployed to Stage and Prod 7/24/2025
-
Improve loading performance of Review Queue.
-
Increase Performance Profiling in SaveFilingAction Endpoint REV-3804 - Deployed to Stage and Prod 7/24/2025
-
Consolidated logs for entire endpoint to be a single log.
-
Remove redundant calls to IsBatchReviewer REV-3822 - Deployed to Stage and Prod 7/24/2025
-
Call isBatchReviewer only at sign in instead of continuously, reducing calls by around 10 percent.
-
VSC Connections to review-hub are being stalled REV-3834 - Deployed to Stage and Prod 7/28/2025
-
Issue: Users were experiencing wait times up to 30 - 50 seconds for each request due to multiple connections causing the load balancer to spike.
Fix: Review now maintains a single connection, and the wait time experienced by users has been removed once the first connection is made.