Print

5.87 Release Notes – Week Commencing 8th December 2025

A software update will be released to SHIP and selected SRS environments

Please note: Some of the features outlined in these release notes depend on configuration options. If you identify a feature from these notes that interests you, but is not currently available in your configuration, please contact Infoxchange on 1300 366 516, (03) 9418 7487 or via email at [email protected]

Release v5.87 contains:

      • New standard lists for reporting:

        • DSS Client and Case information

        • DSS Contact Notes and Outcomes information

    • DSS Client and Case Record Enhancements

      We’ve improved the DSS Case workflow to ensure accurate reporting and better user guidance when creating cases and related records.

      Key Changes

      1. Prompts for Missing DSS Client Records

        • When creating a DSS Case for a person without a current DSS Client record, you’ll see a message advising that a DSS Client record should normally be created first.

        • You can still proceed with creating the case after acknowledging the prompt.

      2. Clear Warnings on Case Pages

        • If a case includes clients without DSS Client records, a message appears at the top of the case page for each affected client.

        • When navigating away from such cases, you’ll be reminded to ensure all clients have DSS Client records for successful DSS reporting.

      3. Association Behaviour

        • Adding a person without a DSS Client record to a case triggers a warning message.

        • No message appears if the person already has a DSS Client record.

      4. Navigation with Unsaved Changes

        • If you try to leave a case with unsaved changes, you’ll first see the standard “unsaved changes” warning.

        • If the case also includes clients without DSS Client records, you’ll then see an additional reminder about DSS reporting requirements.

      5. Notes and Outcomes Validation

        • For DSS Session Records:

          • Notes: A Service Type must be selected before saving. If not, changes will not be saved.

          • Outcomes: A DSS Session must be selected before saving. If not, changes will not be saved.

        • For other session types, these validations do not apply.

          What This Means for You

          • Always create DSS Client records before DSS Cases where possible.

          • Pay attention to prompts—they help ensure compliance and accurate reporting.

          • Select required fields (Service Type for Notes, DSS Session for Outcomes) to avoid losing data.

Shutdown period

During the holiday period from 25 December to 5 January, our support team will operate with reduced coverage, excluding national public holidays. We still expect to respond to and resolve most enquiries within our usual time frames, though minor delays may occur.

 

Bug Fixes & Improvements: 

Groups

Fixed a bug of duplicating Alerts been part of the export list when a client has multiple aliases

Notes API

Fixed an issue with client notes API not returning records from merged client

Session Handling

Fixed a bug that was causing session to expire after 1 hour of inactivity even when configured to be longer than 1 hour.

Session renew pop-up will now show automatically within 5 minutes of session expiry in addition to after attempting to save a record.