This page is updated continuously as development progresses and provides a living record of what has been delivered and what is planned next.

 

Each release brings a range of improvements — from new functionality and performance enhancements to stability fixes — informed by customer feedback gathered through support interactions, roadmap discussions, and feature requests.

 

Releases are published on the first Monday of each month. Items listed under What's Planned in the Next Release represent our current development intent, though individual items may move to a later release if they are not completed or do not pass testing in time.

 

Our published roadmap is available on the Roadmap page.


What's Planned in the Next Release

(Phase: Development/Testing - June 2026)

Fixes

  • Benefits - List field default item not pre-selected for employee - (BD-689/21986)

    List items in benefits can have a default selection defined. This was not working in some themes

  • PreviousSelection expression logic can cause error under certain conditions - (BD-781/22031)

    PreviousSelection expression when used with anytime benefits was sometimes creating a failure


What's Available in 2.40.1

(Phase: General Release - May 2026)

Features / Changes

  • Ciphr Benefits Theme - Look & Feel Parity - (BD-306)

    New CipHR theme which needs to be added to deployment builds.

Fixes

  • Enforce MFA - Email OTP - Functional Failures - (BD-812)

    Fixes for Email One Time Passcode development

  • Add dependant form — missing Required indicator on Title field and misaligned Middle name field - (BD-1019/22170)

    Required indicator added to title field on dependant form when adding to a benefit on custom theme


What's Available in 2.30.13

(Phase: General Release - April 2026)

Fixes

  • Custom Theme - not showing benefit footer on enrolment process when dependants are not required - Hot Fix - (BD-816)

    Fix to footer on custom theme

  • Data Triggers Condition Types JS fix - (BD-862)

    Fix to JS reduce function which was losing .type property.