Configurable webhook payloads

We’ve introduced configurable webhook payloads, giving you greater flexibility when integrating with external systems.

When creating or editing a webhook, you can now choose between sending the standard payload (default) or defining a custom payload using a Twig template. This allows you to structure webhook data to meet the specific requirements of downstream services.

If Custom is selected, a Payload Template field will appear, where you can define the webhook body using Twig syntax. Templates support the same placeholders as case email templates and are validated before saving to ensure correct syntax. Available variables depend on the webhook trigger, such as cases, fields, users, or attachments.

An advanced header setting is also available for custom payloads, allowing you to define additional request headers when needed. If no custom headers are provided, the default headers will be used. Some system headers remain reserved and are always set by Connect, X-Hook-Event, X-Hook-Signature. X-Hook-Delivery and User-Agent.

Existing webhooks will continue to use the default payload to avoid any breaking changes.

These changes make it easier to tailor webhook requests while maintaining compatibility with existing integrations.

Improvement

Webhook errors now displayed in logs

We’ve improved the webhook log UI to make failure reasons clearer and easier to diagnose. Previously, when a webhook request failed, the log did not display detailed error information, making it difficult to understand the cause of the failure.

Error messages including from underlying cURL errors are now shown directly in the webhook logs. This provides clearer insight into issues such as connection failures or invalid endpoints, helping you identify and resolve problems more quickly.

More reliable Connect version detection for Jadu Assist

We’ve improved how Jadu Assist detects the Connect version to ensure features continue to work reliably.

Previously, Assist retrieved version information from the /q/login page. In environments using SAML with “bypass login page” enabled, this endpoint could redirect externally, preventing Assist from accessing the required data.

Version information is now consistently available, even when the login page is bypassed, ensuring Assist can accurately determine feature compatibility. The /q/login page will continue to expose version details when accessible as normal.

Bugs

Case timeline now loads all entries correctly

We’ve fixed an issue where some older entries could be missing from the case timeline, particularly for cases with a large number of history records.

This was caused by certain entry types not being rendered in the timeline. Because these entries were excluded from the UI but still included in pagination, it could result in empty responses while pagination continued, preventing earlier entries from loading.

The timeline query has been updated to exclude these entry types at source, ensuring pagination behaves correctly and all visible entries are loaded as expected.

• Fixed an internal server error that occurred when removing form pages with repeatable elements mapped to Workview actions.

Fixes

• OnBase Date parsing issues for PHP 8.2

• Reporting: Fixed an inconsistency in form reporting by standardising date range calculations, ensuring Popular Forms and Received Forms reports now return matching completion totals.

The FeatureOS notification option has also been removed. If you would like email notification of releases, you can sign up for Jadu Central Changelog notifications.

The OAuth request has now been corrected to meet Echo’s expected format, ensuring successful authentication across all environments.

Fixes

• Onbase Date parsing issues for PHP 8.2

• WISP migrations: Resolved an issue where Central 3 deployments on WISP could fail during migration due to incorrect handling of empty rewrite rules in Web.config, ensuring migrations now complete successfully.

• Reporting: Fixed an inconsistency in form reporting by standardising date range calculations, ensuring Popular Forms and Received Forms reports now return matching completion totals.

The FeatureOS notification option has also been removed. If you would like email notification of releases, you can sign up for Jadu Central Changelog notifications.

This occurred because cases were ordered only by their created_at date. When multiple cases shared the same creation timestamp, which commonly happens during case imports, the ordering became undefined, leading to inconsistent results.

To resolve this, we’ve added an additional sort order using the case ID. This ensures a stable and deterministic ordering of cases, preventing duplicates and missing records as you navigate between pages.

• Fixes an issue where signing in to a site via an external authentication provider caused an error for Classic templates.

• Fixes an issue where signing into a site via Jadu Connect caused an error if the user had missing optional details such as birthday for Classic templates.

• Fixes migration issues when a custom dataset module was previously installed.

Features

Smart-mapping between Jadu Connect and Jadu Central

Smart-mapping, available as a standard feature in Jadu Central 4.1.0, introduces automatic synchronisation between Jadu Connect and Central Forms, removing the need for administrators to manually recreate and maintain matching fields across both platforms.

By allowing form builders to select a case field directly from a pre‑populated Jadu Connect list, Smart-mapping ensures that any changes made in Connect are automatically reflected within the Central Forms mapping interface, significantly reducing administrative effort and improving data consistency across systems.

Origin Theme for Galaxies

The Origin theme for Galaxies sites, introduces an expanded set of no‑code customisation options that allow administrators to easily control the design of headers, footers and key layout sections such as news, events and homepages, while still offering advanced creators the ability to apply custom HTML and CSS through the Jadu Central Control Center; by enabling faster, more flexible and code‑free site creation with greater variation in look and feel across subsites and microsites, the Origin theme helps customers reduce delivery times and build visually distinct Galaxies sites more efficiently.

Datasets for Forms

The new Datasets feature allows administrators to centrally manage large sets of selectable options for Forms by importing key‑value data via CSV files, exporting datasets when needed, and controlling access and editing through admin‑level permissions.

Form creators can easily add datasets to forms and choose whether they appear as standard select fields or typeahead fields, improving both usability and speed for end users - especially when working with large lists such as departments, service codes, locations or predefined responses.

By enabling updates to propagate instantly across all forms that use a dataset, and by providing visibility into how many and which forms depend on each dataset, this feature reduces duplication, lowers administrative overhead, improves data integrity, and delivers a more efficient form‑building experience.

Configurable webhooks in Jadu Central Forms

Configurable webhooks in Jadu Central Forms enable administrators to create custom real‑time integrations with back‑office systems by using a guided Form Action Template to map form fields into a webhook payload.

With access controlled through admin‑level permissions, users can create, edit and delete webhooks securely, while an audit log tracks all administrative interactions for accountability. The system also shows how many forms use each webhook, with direct links to those instances, helping teams manage dependencies easily. By sending data instantly and without manual intervention, configurable webhooks allow issues to be identified and resolved quickly and ensure that external systems receive up‑to‑date information as soon as a form is submitted.

Improvements

• Dormant accounts and password complexity

  • Passwords at registration and when changing passwords can now be validated based on a configurable regular expression rule.

  • A new dropdown is available on the User detail page to set user accounts as Active or Disabled. Disabled accounts will be prevented from logging in.

  • A site setting to enable automatic locking of dormant user accounts. When enabled, administrators can define a dormancy period for front-end users, and a scheduled daily task will automatically mark accounts as dormant if the last login exceeds this period. 

  • A site setting to enable password history restrictions and define a reuse period for front-end users. The restrictions will be enforced whenever the policy is active. 

  • Administrators will be able to enable lifecycle management and specify a password expiration period for front-end users. Users will be redirected to the change-password workflow if their password has expired. 

• Onbase

  • Introduced component-based answer validation and retracing.

• Bottomline

  • Prefilling of fields: Address 1-4 an txtAddressTown

• Replaced strftime in JaduDateTimeFunctions with modern date equivalents.

• Forms

  • Added ability to retrieve checkbox field values from a predefined logic

  • Extra logging added for Office365 integrations

  • Category path used for form breadcrumb

  • Added component-based answer validation and retracing

Fixes

• Fixed an issue when prefilling repeatable questions when the same page template is reused on subsequent page 

• Fixed an issue with data retention scheduled tasks failing with orphaned records.

• Fixed an issue where meeting attachments with slashes weren’t accessible.

• Fixed an issue where files couldn’t be removed from resumed forms.

• Fixed an issue with robots metadata settings not being retained when saving invalid metadata.

• Fixed an issue where a form using Perceptive or Onbase was not listed on the form archive and submitted form links resulted in an error.

• FIxed an issue where an imported Workview dataset component was not editable

• Fixed an accessibility issue with the pagination of the Central/OnBase filter results widget.

• Fixed an issue where a form creates a console error when an integrated component is used on an embedded form and the Next button is pressed without any form answers added.

• Fixed an issue where a form creates a console error when a repeatable component is used on an embedded form and the Next button is pressed without any form answers added.

• Fixed an issue where remapping 'Uploads' to templates was not working when removing and adding a new page.

• Fixed an issue when incomplete forms exist for the same form, clicking Complete Form on either form takes the user to the most recent incomplete form, not the one they selected.

We’ve implemented a set of internal changes to improve platform stability and performance. These changes do not affect system behaviour or user experience.

These changes address an issue where parts of the page could appear off-screen due to how existing CSS and transitions handled reflow. This update improves consistency across devices and orientations without affecting functionality.

We’ve implemented a set of internal changes to improve platform stability and performance. These changes do not affect system behaviour or user experience.

Attachments now use an updated redirect URL to ensure files continue to download correctly, even if the case page has been open for a while.

Dependency updates

We’ve updated internal dependencies used across the platform to ensure compatibility with the underlying technology that powers Jadu Connect. This change does not affect system behaviour or user experience.

Search update

We’re updating the service that sits between Connect and OpenSearch that populates and searches data, to ensure compatibility with the underlying technology that powers Jadu Connect. During deployment, there will be a short period of downtime for search functionality. Aside from this temporary interruption, the change does not affect system behaviour or user experience.

Login and logout event handling update

We’ve updated the internal login and logout event request to ensure compatibility with the underlying technology that powers Jadu Connect. This change does not affect system behaviour or user experience.

• OnBase

  • Added “Object ID” as option of “Attribute value to return” setting of the “Hyland OnBase - WorkView Object Attribute Value“ logic.

Fixes

• OnBase

  • Fixed an issue where an error was reported when using a OnBase WorkView Filter Result component within repeatables

• Forms

  • Fixed an issue where forms with high number of repeatable rows (>=400) timeout during submission

  • Fixed an issue where an error was reporting when uploading files within repeatables

  • Fixed an issue where Postcode (Integrated Component) disappears when validation message triggered

Two-way integration with Symology Aurora

Jadu Connect now offers a two-way integration with Symology Aurora, enabling organisations to exchange case data securely between the two systems.

With this integration, cases can be created in Aurora directly from Jadu Connect, either when a case is created or later in the case lifecycle, depending on the workflow. Once created, case references are stored in both systems to support easy cross-referencing.

This integration is not enabled by default and is currently available to selected accounts only. Please contact Jadu if you want to learn more about this integration. 

Improvements

Case History now clearly indicates hidden events

We’ve updated the Case History view to make it clearer when events exist but aren’t visible due to permission restrictions.

Previously, users might see gaps in the case history without realising this was caused by their access level, which could lead to confusion or support queries. Now, when an event exists but the user doesn’t have permission to view it, a placeholder row is shown indicating that the event details are hidden.

Selecting View details explains that an event has occurred but cannot be viewed due to insufficient permissions, and advises the user to contact an administrator if they believe access is incorrect. Event details, including dates and system-calculated values, remain protected and are not exposed to users without the appropriate permissions.

Multiple exports of the same case filter are now blocked

We’ve improved the case export process to prevent users from starting multiple exports for the same case filter at the same time.

If an export is already in progress for a filter set, additional export attempts will be temporarily blocked until the existing export has completed. This helps prevent unnecessary duplicate processing, reduces queue congestion, and ensures exports complete more efficiently and reliably.

The interactive target size has been increased to ensure it meets the minimum touch target requirements, making it easier to use for people with motor or dexterity impairments. This change was identified during a recent accessibility audit and results in no noticeable visual difference for users.

SAML-based Single Sign-On (SSO) for non-staff users

We’re introducing SAML-based Single Sign-On (SSO) for non-staff users - external users who are not part of an organisation’s internal workforce for example citizen accounts. 

This enhancement allows organisations to authenticate non-staff users using a SAML 2.0–compatible Identity Provider, including Microsoft Entra External ID, providing a secure and streamlined sign-in experience for external audiences.

The feature will be enabled initially for selected accounts, with wider availability planned at a later date.

To get started enable and configure the integration under: Settings > Integration Hub > SAML User Authentication.

Email delivery library update

We’ve updated the underlying library used to send emails to ensure it remains well supported and reliable. This is an internal update with no impact on how emails work in Jadu Connect.

User registration settings now work correctly alongside SAML Admin Authentication, including:

• Displaying the “Enable user registration” option in Settings → User Administration → Registration

• Showing the Register link on the login page when registration is enabled

• Correctly displaying the registration form (or redirecting to login) when accessing the registration page by URL

As part of our ongoing commitment to maintaining a secure and reliable platform, we’ve carried out essential maintenance to upgrade the underlying technology that powers Jadu Connect.

This upgrade improves overall performance and strengthens security across the service. The work was completed with no downtime, and Jadu Connect remained fully operational throughout.

There are no changes to functionality and no action is required from you.

Adding Fields to Large Case Forms

We’ve fixed an issue where users couldn’t add new fields to case forms that already had a large number of fields. Some forms were showing a “The results could not be loaded” message when trying to add more fields.

This has now been resolved, and you can continue adding fields to large case forms without any errors.

Added telephone number validation for person records

We’ve added validation to the telephone fields when creating or updating a person record in the Connect UI and Service API, ensuring only valid telephone numbers can be entered.

Maintenance

This release includes maintenance to improve future compatibility with upcoming platform updates.

There’s no impact to current functionality, but these changes help keep the platform secure, reliable and ready for future enhancements.

• Updated Blue Badge Service integration to comply with the latest published API guidelines.

• Updated repeatable prefilling to allow data from conditional and literal logic. 
  

Fixes

This release includes security improvements and fixes the following issues:

• Forms

  • Fixed an issue where integrated components in internal forms were rendered with the front-end Twig template, causing incorrect styling when the Origin theme was registered.

  • Fixed an issue where a Flexible Event Booking question could be added to a repeatable despite this being unsupported. 

  • Moved Prefill tag validation from SaveQuestionAction to BaseComponentSettingsService to centralise and standardise question setting validation.

  • Moved Repeatable Prefill test logic to the TestHelperBundle to prevent it from being exposed to users during form creation.

  • Fixed an issue where repeatable prefill logic could exceed column length in JaduXFPUserFormLogicResultLog by truncating the result before logging.

  • Fixed an issue where clicking next in the remapping flow did not move focus to the next question.

  • Fixed a 500 error when deleting logic with a configured repeatable prefill, ensuring the remapping modal appears as expected. 

  • Fixed an issue where repeatable rows were incorrectly prefilling after validation errors, ensuring data is reconstructed from the request and prefill only applies on first visit. 

  • Fixed repeatable prefill logic to remove duplicate tags across questions and updated the logic description to inform users that duplicates are ignored. 

  • Fixed an issue where integrated components fail to render when displayed in an embedded form. 

• OnBase and Workview integration

  • Optimised repeatable dataset components to prevent duplicate API requests by caching configuration per request and ensuring dataset values are loaded consistently. 

  • Fixed an issue where unmapped or unanswered repeatable fields caused incorrect values when using the “Create multiple objects” action for OnBase.

  • Improved selection of WorkView attribute placeholders in the object details widget to support complex relationships and enhance usability. 

  • Fixed an issue where the Document List widget displayed the current date/datetime when a keyword from a keyword group had no value.

• Galaxies

  • Fixed an issue where Photon Galaxies theme settings, such as logo or background image, were not loaded on the frontend. 

• Templates

  • Edit and Remove buttons in a repeatable question control now have appropriate margin applied in all themes. 

  • Refactored JaduUrlGenertor to avoid calling Router::getRouteCollection(), preventing routing cache rebuilds and improving front-end performance when using modern templates (Photon).

  • Origin theme

    • Margin is now shown between the progress bar and the resume form notification in a form. 

    • Margin is no longer added to the first control of a form. 

    • Appropriate margin is now added between the individual controls of an integrated form component. 

    • A space now appears between progress bar elements when the form has multiple branching routes. 

    • Fixed an issue where the accessibility checker was not visible when previewing content.

• Resolved an issue where exceptions returned by the O365 integration were suppressed.

• Control Center User Interface

  • Updated changelog widget in the Control Center.

  • Several unused javascript files have been removed.

• Galaxies

  • Fixed issue where border and padding changes are not reflected in the preview window. 

  • Removed references to Apache running under Windows as this architecture is no longer supported. 

  • Updated Galaxies site change details form to use the main home directory constant. 

• Multimedia

  • Removed classes related to FFMPEG as no longer in use. 

• Homepages

  • Updated homepage designer javascript to use JSON.parse()

• Resolved an issue where widgets could not be added to rows in the homepage designer.

• Forms

  • The “Form Modified Date” field is now automatically prefilled with the current date, reducing manual input and improving data accuracy.

  • Fix added to locate private services when registering validation routines in compiler pass.

  • Fixed an issue where importing a form did not display a Page Template Warning modal if an imported template shared the same title as an existing template, but had different questions or other variations. Users are now informed of page templates that will be imported as form specific.

• Event Bookings

  • Improved Office 365 calendar integration by increasing the event retrieval cap from 50 to 200 and adding support for a configurable subject prefix for blocking events. This ensures all blocking events are recognised when determining bookable days. 

  • Updated form import logic to skip matching of configuration ID and calendar ID for event booking questions when comparing page templates, preventing unnecessary mismatches during import. 

  • Improved logging coverage for Event Booking operations. Additional logs have been added to capture delete actions and other scenarios, making it easier to troubleshoot event booking issues. 

  • Event configuration duration field now correctly shows the interval in minutes between events. 

• Blue Badge integration

  • Updated Blue Badge Service integration to comply with the latest published API guidelines.

• Installer

  • When installing, non-alphanumeric characters can now be included in the passwords for system users.

• Photon

  • Improved front-end performance by refactoring route generation to remove use of Router::getRouteCollection().

Upgrade OpenSearch Version

We’re upgrading our Amazon OpenSearch Service. This update ensures continued support, stability, and security for search functionality within Jadu Connect.

Search will be temporarily unavailable during the maintenance window while the upgrade is applied. All other platform functionality will remain available.

Allow “Email List” fields to be used in “Set case value” rule actions

You can now use “Email List” field types in the “Set case value” rule action. This allows these fields to be selected and updated through workflow rules.

Bugs

Fixed bulk redaction silently failing 

Resolved an issue where the bulk redaction API could fail silently. The query handling has been updated to ensure all eligible cases are correctly fetched and redacted.

Fixed issue preventing valid ‘Assign to a user group’ rules from saving

Fixed an issue where some “Assign to a user group” rules could not be saved, showing an invalid value error even when a valid group was selected. All valid user groups can now be saved as expected.

Fixed export/import errors for rules with empty field values

Fixed an issue where case types containing rules with empty field value conditions or actions could not be exported or imported. Rules that check or set empty values now export and import correctly without errors.

Fixed import silent validation failure

Fixed an issue where, in some instances, validation failures during case type import would occur silently with no feedback in the UI. The UI will now correctly display validation errors.

Field visibility settings are now correctly applied to case list filters, ensuring users only see filter options for fields they have permission to view.

If any filters still appear incorrectly, re-saving the affected case fields will refresh their visibility.

• Forms

  • Fixed an issue where importing a form did not display a Page Template Warning modal if an imported template shared the same title as an existing template, but had different questions or other variations. Users are now informed of page templates that will be imported as form specific.

  • Added a script to flag potential variable picker issues. The script highlights areas where unsupported mappings are used and identifies instances where integrated component label variables are applied to incorrect question operators. 

  • Added support for Repeatable mappings in the Healthcheck service, to flag issues where changes to the structure of a repeatable cause mappings to become invalid. 

  • Fixed an issue in the Location component where conditional sections were not triggered after answering a location question, causing console errors and browser instability. Sections now load correctly without errors. 

  • To ensure consistency and stability when prefilling repeatables, only logic designed for repeatable prefilling will now be executed when determining a prefill. 

  • The fields in an email action template can now correctly handle multiple form variables. 

  • Validation Routines and Definitions pages now handle corrupted question data safely, preventing errors during usage checks. 

• Workview Integration

  • Improved the “WorkView Filter Results Repeatable Prefill” and “Document Keyword Group Repeatable Prefill” logics to support prefilling of WorkView Filter Results, WorkView Cascading Datasets, and Matrix components, when used inside repeatables.

  • Improved performance for the “Mapping” tab in the “WorkView: Create Multiple Objects” mapping template. The tab now loads and saves significantly faster. 

  • Fixed an issue where “WorkView Cascading Dataset” and “Filter Results” component answers were not fully available as mapping options in the “Workview: Create Multiple Objects” mapping template. All levels and metadata are now correctly exposed for mapping, including when used inside nested sections or repeatables. 

  • Updated the “Cascading Datasets” component to ensure the required field indicator matches the form’s standard styling across template sets. 

• Event Bookings

  • Improved Office 365 calendar integration by increasing the event retrieval cap from 50 to 200 and adding support for a configurable subject prefix for blocking events. This ensures all blocking events are recognised when determining bookable days. 

  • Updated form import logic to skip matching of configuration ID and calendar ID for event booking questions when comparing page templates, preventing unnecessary mismatches during import. 

  • Improved logging coverage for Event Booking operations. Additional logs have been added to capture delete actions and other scenarios, making it easier to troubleshoot event booking issues. 

  • Event configuration duration field now correctly shows the interval in minutes between events. 

• Deployer integration

  • Fixed an issue where Deployer rollback failed to start on Central 4.0. 

• Installation

  • Fixed an issue where system user passwords containing non-alphanumeric characters cause post-installation scripts to fail. 

• Content Portal templates

  • Resolved repeatable component user interface issues in classic Content Portal templates - fixed button spacing, loading spinner rendering, and checkbox for attributes for accessibility compliance.

We’ve added validation to the telephone fields when creating or updating a person record in the Connect UI, ensuring only valid telephone numbers can be entered.

We've made behind-the-scenes updates to keep our platform secure, reliable, and up to date.

• Importing a case type would fail if it included an “Assign to user” rule.

• Cloning an account would fail if any of its case types included this rule.

Both actions now work as expected, so you can import case types and clone accounts without errors.

With this fix, administrators can now successfully reassign ownership of Shared Filter Sets even if the previous owner’s account has been deleted.

Extended webhook URL length support

We’ve increased the maximum length of webhook URLs from 255 characters to 2000 characters.

This improvement ensures compatibility with longer URLs generated by services such as Microsoft Power Automate, preventing issues where URLs were previously cut short and caused webhook authentication failures.

Validation has also been added, so when creating or editing a webhook you’ll be notified if a URL exceeds the new 2000-character limit.

• Added a theme setting to control whether a user is redirected to the account page or the homepage after logging into their user account from the homepage.
  

Fixes

• Deprecation notices

  • Resolved an issue where dynamic properties were generating deprecated notices

  • Resolved a deprecation warning caused by the use of a dynamic property DataMapper::$logger. The logger is now handled in a way that is compatible with current PHP standards.

  • Fixed a deprecation warning related to the dynamic property Component::$inputs. This ensures compatibility with newer PHP versions and removes unnecessary warnings from logs

• Directories

  • Resolved an issue where submitting a public directory record with an image caused an error. Frontend users can now successfully submit records that include images without encountering errors.

• Forms

  • Validation error highlighting has been corrected. Previously, when a row in a Repeatable question contained a validation error, the following row was incorrectly highlighted. The system now accurately highlights the row with the actual error.

  • Alphanumeric validation is now correctly enforced in repeatable questions. Inputs containing invalid characters (such as commas) are rejected as expected.

  • Matrix row data is preserved when adding rows to repeatable questions. Values now remain aligned with the row where they were originally entered.

  • The system will now flag invalid updated variable picker mappings as Health Check warnings.

  • Date Calculation definitions can now be used in placeholders and logs. Previously, attempting to insert a Date Calculation definition into form instructions or logs would fail to render as expected. This has been fixed so relative dates (e.g., today) defined in /jadu/xforms2/definitions now work correctly in both placeholders and log entries.

  • Fixed an issue where it was not possible to edit a JavaScript snippet inserted into the document editor while editing a form page. 

• Perceptive Integration 

  • The Perceptive workflow document details page now displays as expected. 

• OnBase & WorkView Integration

  • OnBase mapping has been corrected to ensure data is accurately mapped, resolving misalignment issues caused by the previous row-handling bug in repeatable questions.

  • Resolved an issue where default values in the Object Details widget were not always used correctly. Fixed a formatting issue where defaults were ignored if they did not match the attribute’s datatype. Corrected logic so that content is displayed when:

    • The object exists and the filter returns exactly one result.

    • The object’s class matches the widget’s configured class.

    • At least one placeholder in the content is replaced by a valid attribute value or default value.

  • Fixed an issue where WorkView filter and WorkView component were not validating the required settings on the component. The system now shows page warnings when the required setting is enabled. 

  • The WorkView object is now updated correctly when a checkbox field with value 1 is mapped using the “WorkView: Update Object” mapping template.

• Added a theme setting to control whether a user is redirected to the account page or the homepage after logging into their user account from the homepage.

Fixes

• Dates on the review page are now localised in a consistent and configurable way 

• Resolved an issue where dynamic properties were generating deprecated notices

• Resolved a deprecation warning caused by the use of a dynamic property DataMapper::$logger. The logger is now handled in a way that is compatible with current PHP standards.

• Fixed a deprecation warning related to the dynamic property Component::$inputs. This ensures compatibility with newer PHP versions and removes unnecessary warnings from logs

• Resolved an issue where submitting a public directory record with an image caused an error. Front end users can now successfully submit records that include images without encountering errors.

• Resolved a deprecation warning caused by the use of a dynamic property DataMapper::$logger. The logger is now handled in a way that is compatible with current PHP standards.

• Fixed a deprecation warning related to the dynamic property Component::$inputs. This ensures compatibility with newer PHP versions and removes unnecessary warnings from logs

Improved Add Fields modal performance and usability

We’ve re-implemented the Add Fields modal to better support accounts with very large numbers of fields (10,000+). The updated modal delivers faster performance with pagination and searching when browsing case fields, and provides a clearer workflow where fields can be selected, reviewed in the “Selected fields” table, and added or removed as needed. 

These improvements make adding fields to case forms smoother, faster, and more reliable.

Bugs

Case counts now match between reports and filters

We fixed an issue where the “All cases created” report and the case dashboard filters sometimes showed different results when using date ranges. Case counts are now consistent across reports and filters.

Shared filter sets retain visibility when renamed

Previously, renaming a shared filter could unintentionally change its visibility to match the group of the user making the change. The filter will now keep its original visibility settings when renamed.

OAuth error handling no longer causes failures

We resolved an error where missing account context during OAuth authentication could cause a system failure (500 error). This has been corrected to ensure stable behaviour.

HUBis integration sends requests without field mappings
We fixed an issue where HUBis integration requests were not being sent if no field mappings were present, even when only reference mappings were required. Actions such as “Cancel Worksheet” now work as intended.

Maintenance

Webhook and integration log clean-up enabled

In Jadu Connect 1.228, we introduced automated log clear-down for webhooks and integrations but kept it disabled. Since then, historic data has been cleared manually. With this release, the automated jobs are now enabled, ensuring old webhook and integration logs are removed regularly without manual intervention.

• Forms

  • Fixed an accessibility issue where you could not tab correctly around the variable picker.

  • Fixed an issue where “Total of column” repeatable variables did not work as intended when used with checkboxes.

  • It is no longer possible to add a prefill tag to text block form components in repeatable questions.

  • Fixed an issue where placeholders could incorrectly be copied and pasted between forms. 

  • The confirm answer field now saves correctly as a user progresses through a form.

  • Fixed an issue where the page would scroll to a repeatable section on initial load instead of the beginning of the page.

  • The form is no longer prevented from progressing when a repeatable is in a hidden section and has a minimum number of rows.

  • Fixed an unintentional backwards compatibility break with respect to the format of started and submitted date variables. 

  • When accessing variables programmatically, variables are now offered for repeatables that are inside sections. 

  • The “Add row” button is now correctly hidden when editing or adding a row in a repeatable question. 

• Integrations

  • Fixed an issue where editing Perceptive Display Sets could trigger an error. 

  • An error is no longer shown when a user import file with character length under 1000 characters is imported in the OnBase User Import function. 

  • Fixed an issue where a date property in a display set could trigger an error when viewing details of a Perceptive Worklist item. 

  • Duplicate users are now correctly prevented when using the MyAccount user integration.

Automated Cleanup of Integration & Webhook Delivery Logs

A new automated process now removes integration and webhook delivery logs older than six months. This helps maintain system performance, reduce storage use, and support data governance best practices.

Note: This feature will be disabled on deployment. Log cleanup will begin from Monday 24th August 2025. This release only puts the underlying code in place.

Improvements

Optimised Case Field Filtering to Prevent Out of Memory Errors

Improved how case field filter types are loaded when displaying dashboards resulting in better performance and stability for dashboards with complex case filtering.

Increased Transition Selection Limit for Case Forms

The “Show form on these transitions” setting now supports pagination. This enhancement removes the previous limit of 100 transitions and applies to both:

• Adding a new case form

• Editing an existing case form’s transitions

• Fixed an issue that could cause a 500 error when validating remapping fields while deleting a logic.

• You can now reliably drag and drop a variable into the Amend Booking action.

• Fixed an issue where rule clauses were not removed properly when multiple clauses existed in a rule.

• Fixed a problem where labels could disappear in integrated components when clicking lookups.

• Fixed an issue where data migration incorrectly converted “all day” configurations to “slot” (and vice versa).

• Fixed a migration where slot configuration for event bookings were incorrectly converted to “All day”

New Form Variable Picker

The current form variable picker requires an upgrade to Variable Picker 3 (VP3) to improve flexibility, user experience, and maintainability. This update introduces transformations, enhanced repeatable variable support, and better integrations with form logic and calculations.

Prefilled repeatable components

We’re introducing a powerful new enhancement to Jadu Central forms: Repeatable Component Prefills, designed in direct response to customer feedback from users. This feature significantly expands the ability to dynamically prepopulate data in repeatable form elements, enabling more intelligent, integrated, and efficient form behaviour.

• Prefill from OnBase Keyword Groups. Repeatable components can now be prefilled directly from OnBase Keyword Groups, allowing seamless integration with external data sources. The enhancement includes:

  • Support for multi-instance, single-instance, and standalone keyword types.

  • Built-in logic to retrieve and parse OnBase keyword data into repeatable rows.

  • A new mapping interface in the Control Centre, enabling administrators to visually select and bind OnBase fields to specific fields within a repeatable component.  

• Prefill One Repeatable from Another. This release also introduces the ability to prefill one repeatable component from another within the same form: 

  • A new “Add Prefill Tag” setting allows repeatables to be matched and linked.

  • Matching is based on consistent field tagging, enabling structured data transfer. 

  • Maintains consistent JSON data structures, ensuring compatibility with downstream workflows and exports. 

• Frontend Refactor - JavaScript-Based Repeatables.  The internal repeatables architecture has been refactored to rely on JavaScript for better performance and responsiveness:

  • AJAX-based logic now powers the addition, update, and removal of repeatable rows.

  • Eliminates full-page refreshes, delivering a smoother user experience when interacting with dynamic or integrated components.

  • Simplifies and accelerates future enhancements to repeatables behavior and rendering. 

• Control Centre Enhancements.  The Control Centre UI has been updated to support the new prefilling capabilities:

  • The Variable Picker (V3) now includes support for repeatable component fields.

  • A new dropdown-based field mapping UI lets users configure how external or internal repeatables are linked. 

  • A live JSON preview shows what data will be inserted before applying the mapping, improving transparency and confidence for administrators. 

• Backward Compatibility and Safety.  We’ve designed this feature with full backward compatibility in mind:

  • Legacy prefills will continue to function without changes. 

  • Incompatible or deprecated mappings will be flagged with a “Removed” state in the UI.  

  • A prebuilt SQL query is included to help support teams identify forms using unsupported or outdated prefill configurations.

Compatibility with Connect Email List field

The field type is basically a text/textarea field, it accepts a comma separated list of email addresses and Connect validates each email before accepting the passed value. 

PHP 8.3 Compatibility

This release introduces full compatibility with PHP 8.3, ensuring your application can take advantage of the latest performance improvements, syntax features, and security patches available in the PHP ecosystem. 

Microsoft Garnet Compatibility

We now support Microsoft Garnet, Microsoft’s high-performance in-memory caching system. This provides an alternative to Redis and Memurai for customers using  Microsoft Windows Server.  Further information is found in our User Manual. Setting up Microsoft Garnet in Jadu Central

Microsoft Server 2025 Compatibility

Your applications can now be deployed and run on Microsoft Server 2025, ensuring long-term platform support and access to the latest enterprise-grade performance, scalability, and security enhancements.

MariaDB 10.11 Compatibility

We have added support for MariaDB 10.11, allowing customers to take advantage of the latest long-term support (LTS) release, which includes stability, performance improvements, and extended lifecycle support.

Machine names added to Homepage Widgets
You can now assign machine-readable names (machineName) to homepage widgets. This enhancement removes the dependence on auto-incremented database IDs for identifying widgets. 

Key benefits include:    

 •    Better alignment between widget configuration and source code,    

 •    Easier widget management across environments, and    

 •    Improved support for version control and automated deployment.

Dark Mode in Control Centre (Beta Feature)

A Dark Mode option is now available within the Control Center interface. To enable it, users must activate the Beta Features toggle. 

Improvements

Replaced Klein Routing with Symfony Routing

We’ve fully migrated from the Klein routing library to Symfony Routing, improving maintainability, testability, and route configuration consistency.

Encryption Enhancements

We’ve made extensive updates to improve platform security and align with modern encryption practices. Affected data includes authenticator keys for users and administrators, and integration credentials. As part of this work we have: 

• Discontinued encryption of constant values with type “secure”.

• Stopped encrypting cached data

• Disabled caching for user data.

Updated Moment.js 

Upgraded the Moment.js dependency bringing in the latest timezone and locale updates, along with minor bug fixes.

Doctrine Type Annotation Fixes

Resolved deprecation warnings related to outdated annotation syntax in Doctrine type methods.

Apache 2.4 Compatibility for Site Themes

Site themes using virtual directories now support Apache 2.4. This expands support for modern server environments and improves compatibility with newer hosting platforms and cloud infrastructure.

Also:

• Updated Grunt to remove dependency on older Node versions.

• Adds formID as a Foreign key in Form pages to ensure better data consistency

Fixes

• Installation

  • Fixed web.config issues on new install for WISP photon

  • Removed XForms Standalone mode from the XFP installer

  • Updated installer to remove & update the legacy Forms Content types.

• Maintenance scripts

  • Removed references to classic forms from the maintenance scripts.

• Control Center User Interface

  • Flag updated to bookmark for search page, with flag icon changing to star icon

  • Making search result type column keyboard accessible

  • Changing the links to buttons on search results page

  • Added a visually displayed or hidden <caption> for Search results

  • Accessibility: improvements to the search results row select checkbox.

  • Accessibility: Improvements to the accessible landmarks of the search results page.

  • Fixing accessibility on history links on search results page

  • Setting keyboard focus on the first interactive element on search result page

  • Adding a short status message to screen reader users on search result page

  • A11y fixes of search results filter sidebar

  • Updating the markup to follow the ARIA accordion pattern on search result page

  • Updated the page title to “Search results" to be more descriptive

  • Replacing hardcoded actions button with Pulsar component

  • Remove CMS Continuum version from CC dashboard and error page 

• Forms

  • Added temporary workaround to fix Microsoft SQL PHP driver issue with 5.12 and PHP 8.3

• Events

  • Resolve event location table filter selecting all results

• Directories

  • Fixes directories deletion of user submitted records

• Content Schedule

  • Resolved content schedules for shared admin on XFP sites not populating schedules table

• Homepages

  • Resolves issue where Homepages may become broken in the Homepage Designer if they contain a Widget that has been deleted using the Widget Manager.

• Galaxies

  • Shared galaxies site details now updated across the main site and galaxies

• Blogs

  • Fixed Blog Posts page when loading large datasets by limiting records and count queries 

• Modern templates

  • Resolves issue where setting placeholders were not always being replaced in Legacy Widgets for Photon sites

Resolved Server Error on /q/login/ Pages

Visiting the /q/login/ URL (with trailing slash) was resulting in a server error. This has now been fixed to ensure the login page loads correctly.

Improved CSV Import Handling for Files with BOM

CSV files created in Excel often include a Byte Order Mark (BOM) at the beginning, which prevents the system from correctly identifying header columns during import. We now automatically strip the BOM when performing data imports.

Seamless Transition from Native to SAML Admin Accounts

We've enhanced the SAML login flow to better support users transitioning from native authentication. When a user logs in via SAML and their email matches an existing native (non-SAML) account, Connect will now automatically link the account instead of blocking access.

If the user’s email matches a native account that does not already have a SAML External ID, the system will:

• Link the account by storing the SAML NameID as the External ID.

• Authenticate the user and grant access as normal.

• Log the event in the SAML Admin Authentication log, e.g.:
  "Linked user [email] to SAML account with NameID [NameID]"

Once an account has been linked to a SAML login, the user will only be able to sign in using SAML. Native authentication will no longer be available for that user.

New Account Setting to Disable "Assign Email List" Invitations

To support more flexible preferences, we've added an account-level setting that controls whether email invitations are sent when assigning users to a case using the “Assign email list” rule action.

Default behaviour (unchanged): Email invitations are sent to email addresses that don’t already have a user account in Connect.

New behaviour (when disabled): No emails are sent. Assignment still occurs silently.

This setting only affects invitations sent via the “Assign email list” action. All other user invitation emails are sent regardless of this setting.

Bugs

Email Alerts Enabled for New SAML Users

We've fixed an issue where new admin users created via SAML authentication did not have the "Enable email alerts" setting turned on by default. This meant those users were not receiving email notifications unless the setting was manually enabled on the user account. 

The "Enable email alerts" checkbox will now be automatically checked for all new users created via SAML login.

This fix only applies to users created after the update. Existing users created via SAML prior to this fix are unaffected and will need the setting enabled manually if required.

Timeline Updates for Address Field Changes

Previously, updating an address field on a case did not trigger an entry in the case timeline or generate a visible diff, even though the address value was correctly updated. This made it difficult for users to track changes to address information over time.

What’s changed:

• Editing an address field on a case now generates a timeline entry showing the before and after values.

• Diffs for address field changes are now visible in the timeline, ensuring better auditability and change tracking.

This improvement enhances transparency and ensures all changes to critical address data are properly recorded.

Clearer Feedback After Exporting Case Type

The export modal now shows clearer feedback when a case type download starts.

Theme Configuration Updates  

We’ve introduced new branding and metadata options to give teams more control and flexibility:

• New upload fields for SVG logos, favicons (ICO, PNG, Apple Touch, Safari pinned tab), and Open Graph images.

• New toggle to hide the categories dropdown menu.

• Updated favicon.ico option: now supports direct file uploads instead of requiring a full URL.  
  

These changes simplify asset management, improve brand consistency, and enhance the site’s appearance across devices and platforms.

Switcher for Jadu Central configuration

We’ve introduced a new CLI tool that allows you to switch your Jadu Central site between predefined configurations (such as Lite and Full) instantly and safely. This command applies consistent module configurations based on centrally defined presets, eliminating manual database updates. It’s fully rerunnable, supports automation via a --no-interaction flag, and takes effect immediately.

Switcher for Photon templates

You can now convert your Jadu Central site from Classic templates to Photon templates using a simple CLI command. This tool applies the new out-of-the-box Origin theme and automatically migrates any existing Content Portal theme settings, ensuring a smooth transition with minimal manual effort. The command allows you to modernise your site quickly and reliably, enabling access to the latest Photon features without the cost and complexity of a full redevelopment. 

Support for Load-Balanced Hyland OnBase Environments

Jadu Central now supports integration with Hyland-hosted load-balanced OnBase environments. This enhancement ensures compatibility for enterprise customers using Hyland’s hosted infrastructure. 

Added compatibility for upcoming changes to the Blue Badge API

This release introduces compatibility for the latest release of the Blue Badge API which will update a number of previous endpoints. 

Fixes

• Site settings

  • Removed Control Center Logo and Badge fields as they are non-functional in the latest version

• Widgets

  • Resolves issue where setting placeholders were not always being replaced in Legacy Widgets for Photon sites

• Integrations

  • Fixed an issue in OnBase integration where mapping a static value of 0 could be ignored during a document update

  • Resolved an issue where when trying to import a form which has a Workview Filter Result, if the filter configuration no longer existed, an error occurred

  • Resolved an issue where only the first relationship attribute for a given class was available in the placeholder picker in the WorkView Object Details widget

  • Fixed PHP warnings of undefined array offset in OnBaseWorkviewFilterQueryCriteriaFactory

  • Resolved an issue where an inconsistent number of results could be shown in the OnBase Filter Results widget if duplicate Objects were present in the Filter results

• Photon

  • Homepage banners

    • Homepage banners without a link no longer show an empty link

  • Integrations

    • Fixed a number of warnings and errors for Hyland OnBase widgets when using Photon templates

    • Fixed an issue where the “Hyland OnBase - WorkView Object details” widget could error in a Photon environment

    • OnBase widgets now use a required indicator consistent with other areas of the site

    • Removed multiple focusable table wrappers from OnBase widgets

    • Resolved validation issues in the Perceptive widgets

    • Fixed accessibility issues found in the Perceptive widgets

    • Submitting the Perceptive Search widget with an empty value no longer throws an error 

    • Hash validation no longer fails when following an action link from the WorkView Filter results widget to the Object details widget

  • My Account

    • Resolved an issue where logout was not functioning as expected on a Galaxies site using Jadu Connect for authentication

  • Origin theme

    • The search role is no longer duplicated by the hero search and the header search.

    • The header search now functions as a focus trap when expanded.

    • Sa11y and JQuery are properly included in npm dependencies

    • AAA colour contrast implemented for links in the event calendar widget

    • Menu links are now styled appropriately when in dark mode

    • Date range fields are now shown side-by-side rather than stacked in the OnBase Document List widget

    • A loading state has been added to the OnBase Document List widget and the OnBase WorkView Filter Results widget

    • Fixed alignment of OnBase widget search buttons

    • Improved the styling of the OnBase widget action links

    • Margin added around success and alert messages and forms

    • A hover effect is now shown for submit inputs

    • Button styles are now consistently applied

    • Improved the styling of supplements on a one-column layout

    • Improved position of the form supplement button

    • Fixed an issue where the next and previous links could overlap an image with a long caption

    • Removed duplicate focusable table wrappers in OnBase and Perceptive widgets

    • Primary colours are now used for table header rows

    • Form controls now use consistent spacing

    • Form elements now use the full page width

    • Repeatable form label is now shown in bold

    • Resolved an issue with image captions overflowing the description section of the form

    • Fixed an issue with incomplete form submissions being visible by default in the user form widget

    • Fixed an issue with widgets in a grid being inconsistently sized

    • Made sure links in the user form widget are at least 24px tall

    • Ensured that the OnBase Document List widget dates input is correctly aligned when applied to an independent homepage

Optional Address Requirement on Person Records

We’ve introduced a new account setting to support non-UK markets by making the address requirement on “Person” records configurable.

By default, Connect continues to require an address when creating a Person record (current behaviour). A new account-level feature flag allows disabling this requirement for organisations operating outside the UK.

When Address Requirement is Disabled:

• The “Addresses” section is not present in the UI when creating a Person record.

• The “address_reference” field becomes optional in the following Service API endpoints:

  • Person - Create a new person

  • User - Register incomplete user with person

  API changes are fully backward-compatible.

• Users registering through the platform are no longer prompted to provide an address.

• The Person details page no longer displays an address section.

• Person matching that relies on UPRN is disabled, as no address data is collected.

This change improves flexibility for international implementations while maintaining compatibility for UK deployments.

Fonts Updated

We’ve refreshed the look and feel of the application by updating our core font stack.

Bug Fixes

Case Date Definition timeouts

We’ve fixed an issue where updating commonly used, larger case date definitions would time out. These updates now complete much more efficiently.

Case Type Import: Incorrect Status After Header Validation Fails

Fixed an issue where modifying a form after a dry-run import but before the consumer runs caused the import to remain in "Queued for Tests" without a "Started At" timestamp, despite showing a "Completed At" timestamp.

Case Type Import Fails for “Assign to a User” and “Assign Email List” Actions

Resolved an import error where case types using the “Assign to a User” or “Assign Email List” rule actions failed to import correctly.

Case Creation on Behalf of Organisation Fails to Set Reference

Fixed a bug where raising a case on behalf of an organisation failed to populate the organisation reference in a hidden field, requiring users to re-select the organisation during form submission.

Address Lookup: Unnecessary Requests Causing Errors

Prevented additional invalid address lookup requests using Connect-specific address references, which resulted in errors such as invalid input syntax for type bigint.

Field Label Changes Not Reflected in Case Filter Options

Fixed an issue where updating a field’s label did not update the corresponding label in case filter options, even after saving the case type.

Shared Filter Group Display Mismatch After User Group Change

Fixed a display issue where filters created by a user who changed groups appeared to belong to the new group in the UI, even though the filter’s group was unchanged in the system.

Shared Filters Page Fails to Load if Owned by Deleted User

Fixed a bug where the Shared Filter Sets page returned a 404 error when a filter was owned by a deleted user. The page now loads correctly and shows filters without an owner.

Shared Filter Group Not Saved

Resolved an issue where updates to a shared filter’s group were not saved correctly when editing the filter.

• Calendar configuration periods are now accurately reflected on the calendar.

• The “Number of repeats” field is now shown when the “Restrict number of repeats” toggle is enabled.

Multiple User Assignment via "Assign Email List" Rule

We've introduced a new Rule Action called "Assign Email List" that allows you to grant case access to multiple users by simply providing a comma-separated list of email addresses. This action supports both existing and new users: if a user already exists in the system, they are added to the case; if not, an Incomplete User is created and linked to the case. When that user later completes their account and logs in, their case access is automatically transferred to their full user account. Invalid or duplicate email addresses are ignored. 

The rule accepts an Email List Case Field and includes a new configuration option to determine how permissions are assigned to new users - either using the standard user registration settings or those defined under SAML integration.

https://docs.jadu.net/connect/cxm-admin-guide/workflow/case_types/rules/#assign-email-list

Integration with Cloudpass Vehicle Access Control

Connect now supports integration with Cloudpass, a vehicle access control service, enabling automated vehicle bookings based on case activity. This integration helps organisations manage gate access seamlessly. When a case is created or updated with a vehicle registration, a corresponding booking is made or updated in Cloudpass. If no registration is provided, or if it’s marked as "Unknown", the system still initiates a booking using a default value.

Changes to the registration field will automatically update the existing booking, and when a case is cancelled, the associated booking is removed from Cloudpass. External references to Cloudpass bookings are stored within the case for traceability.

Bugs 

Antivirus False Positives

We’ve updated our antivirus configuration to prevent some false positives to ensure smoother operations when processing known safe files.

Following valuable customer feedback, we’ve disabled the One-Click Unsubscribe Link for Emails feature in Jadu Connect. While the feature aimed to simplify unsubscribe options for recipients, it did not meet expectations in its initial implementation.

We’re taking this time to review your feedback and improve the functionality. The unsubscribe link will no longer appear automatically in emails sent from Jadu Connect until a revised version is ready.

• Unsubscribe Feature Re-Enabled. The unsubscribe functionality is now active again, allowing users to opt out of communications as expected.

• Confirmation Step Added. Clicking the unsubscribe link now leads to a confirmation page. This helps prevent accidental unsubscriptions.

One-Click Unsubscribe Link for Emails

To comply with inbox protection requirements, we’ve added a one-click unsubscribe link to all emails sent from Connect. This allows recipients to easily opt out of further communications by clicking the unsubscribe link, which takes them to a branded confirmation page confirming their unsubscription. In the background, this action disables the “Enable email alerts” setting on their user profile. 

Bugs 

Service API User Search: Support for Spaces in User Names

We’ve fixed an issue where users with spaces in their first or last names were not returned in Service API user searches unless their names were searched without spaces (e.g., “OneTwo” instead of “One Two”).

Please note that it may take some time to fully populate the index, and user selection via the Service API User Search may be temporarily unavailable while indexing completes.

Choice Fields Now Visible on Case Details Tab

Resolved an issue where choice fields (Dropdown with multiple options, Checkboxes) were not appearing on the Details tab of a case, even when they had values.

Echo Integration: Create Event: Support for Complex Extended Data Types

We’ve enhanced the Create Event action in the Echo integration to support complex structured data.

Echo Integration: New Perform Event Action

A new Perform Event Action mapping has been introduced, allowing actions to be performed on existing events such as cancelling a bulky collection request directly from a Connect case.

Echo Integration: Create Event: Task Reservation Support

We’ve added support for task reservations when creating an Event, supporting bulky waste collections.

In the case of Bulky slot reservations, event creation logic now includes intelligent handling of reservation slot expiry::

• If the reservation fails due to expiry, Connect will attempt to re-reserve the same slot

• If re-reservation fails, the Event will still be created without reservations

A new incoming mapping, Created Task Reservations, returns a boolean value indicating whether the Event was created with a valid reservation. This can be used to manage follow-up actions in workflows that rely on successful slot booking.

Send an Email Rule Action: Support for Email List Fields

The "Send an Email" rule action has been enhanced to support Email List fields, making it easier to send messages to dynamic groups of recipients. New capabilities include:

• A new "Email List Field" option in the "To" dropdown.

• Conditional display of the "Field" and "Recipient Filter" options when "Email List Field" is selected.

• "Field" dropdown lists all available case fields of type Email List.

• "Recipient Filter" lets users choose to:

  • Send to all email addresses in the list, or

  • Send only to email addresses that belong to registered users.

These improvements offer greater flexibility and control over email recipient selection based on form and case data.

Improvements

SAML Integration: SHA1 Logging
Connect now logs an error in the integration log when SAML requests or responses are signed using SHA1, which is not supported.

Echo Integration: Enhanced HTTP 400 Response Logging
Error responses from Echo (especially with the new Suez Core integration) now include detailed messaging in the Integrations log. This replaces the previous generic error and makes debugging integration issues significantly easier.

Confirm Integration: Attachment Upload Error Reclassified
When file attachments are uploaded before the associated enquiry is created, the log will now show a warning instead of an error. This reflects the expected sequencing behaviour and avoids false positives in the logs.

Confirm Integration: Missing File Names in Logs
File uploads submitted through forms are now correctly logged in the Confirm integration. File names will appear in log messages, aiding in troubleshooting and audit trails.

Bugs

Pagination Issue for Users Without Dashboard Access
Resolved an issue where pagination in the case list did not work for users without access to the home dashboard. The system now correctly handles page navigation.

User Registration Fails When SAML is Enabled
Fixed a bug where the registration page returned a 404 error when SAML authentication was enabled. This impacted both direct registrations and sign-ups via invitation emails. Users can now register as expected.

Menu Manager Enhancements

• All menu item types now support a description field with a rich text editor, making it easier to add styled content and helpful information directly in the Menu Manager.

• You can now manage multiple menus within the Menu Manager, offering greater flexibility for complex site structures.

• The menu importer has been updated to support importing multiple menus at once, streamlining the setup process.

• Symfony caching has been added to the Menu Manager service to reduce database interactions and improve front-end load times.

• The Menu Manager has been moved out of Beta and into general availability.

• A new Photon design system component has been created for the Menu Manager, ensuring a consistent and accessible UI.

• You can now assign a custom CSS class name to each menu entry for tailored presentation.

• Menu entries can now include an image, giving you more options for visually rich navigation.

Flexible Event Booking

• Introduced a new rule action to generate .ICS calendar files for Flexible bookings, including a variable to download the file and a new toggle in the Attach file action.

• Added a link to associated Pricing Rules on the Calendar Group details page.

• Added a customisable label setting to the Flexible bookings component.

• Dates on the Blocked Times List page are now localised for better clarity.

• Users can now select alternative and remove bookings in both available and unavailable states in the availability table.

• Flexible bookings calendar now shows the first bookable date on load.

• Introduced a slot duration field on the Flexible configuration page to control calendar interval display.

• Adjusted flash messaging on the Pricing Rules Edit page for accuracy.

• Added two new variables: Reserved Bookings and Confirmed Bookings (comma-separated), and corrected the Repeats variable to reflect actual booking data.

• Removed duplicate AM/PM labels in calendar time display and made a wording tweak in the Repeat label field.

• Enabled creation and amendment of Flexible booking events via Office365 batch requests.

Perceptive Content Integration

• Added a link to Perceptive documents from the Actions menu.

• Added Photon equivalents for Perceptive widgets to ensure consistent styling.

OnBase Workview Integration

• Enabled filtering options for OnBase Workview configurations and custom queries.

Fixes

• Downloads

  • Set correct filetype on Downloads file page

• A to Z

  • For A-Z Direct Record List page, shows 404 page  for Non-alphanumeric & Multiple alphanumeric chars in URL

• Directories

  • For A-Z Direct Record List page, shows 404 page  for Non-alphanumeric & Multiple alphanumeric chars in URL

• Friendly URLs

  • Allow Friendly URL with slug which have been removed from categories.

• Category List

  • Increases the maximum limit of published category version number.

• Widgets

  • Change the settings Widget Manager Last Modified table column to Date created and fix bug that erroneously changes the 'Uploaded by' field to the logged in user

• Forms

  • Resolved a 500 error that occurred in Photon embedded forms when clicking "Next" after file upload completion.

  • Ensured reCAPTCHA displays correctly as enabled after activation.

  • Improved the Logic results modal to display long strings correctly.

  • Ensured the summary row displays in matrix components when numeric columns are present.

  • Fixed a bug causing embedded forms to jump to the top of the page after certain actions.

  • Fixed an issue on the data export page causing 500 errors when using weekly or monthly schedules.

  • Updated orphaned data script for WISP compatibility.

  • Fixed 500 errors caused by components like postcode lookup sending postback requests after selecting a booking slot.

• Event booking

  • Fixed the issue where the Existing Bookings component didn’t show bookings for impersonated users in internal forms.

  • Fixed a 500 error when creating a calendar with an existing name.

  • Corrected issues where the availability table didn’t respect blocked or unavailable times.

  • Improved error messaging for the buffer duration field on the Flexible configuration page.

  • Disabled the Max slots option in the Event configuration modal for Flexible bookings.

We've made updates to our server infrastructure to improve performance, scalability, and security. These changes are behind the scenes and won't affect how you use the service, but they help ensure a faster and more resilient experience.

As part of this update, Connect will be placed into maintenance mode briefly during the deployment window and you may notice a short period of downtime while the update is applied.

If you'd like more detail about these updates for compliance or technical purposes, feel free to get in touch with us.

Case Fields – User Group Visibility

A new feature has been added to extend Case Field visibility controls to User Groups. Previously, Case Field visibility could only be restricted based on user Roles. Administrators can now specify which User Groups can view and interact with specific Case Fields.

Key Enhancements:

• New "Visible to User Groups" Setting: Allows administrators to define visibility for specific User Groups.

• Default Behaviour: Case Fields remain visible to all User Groups unless explicitly restricted. Existing fields will retain their current visibility settings.

• Visibility Controls Apply To:

  • Filters: Fields restricted to certain groups will not be available as filter options for users outside those groups.

  • Case Viewing: Users will only see fields assigned to their user Group.

  • Case Form: Users will only interact with fields assigned to their user Group.

• Exceptions: Workflow Management & Search: Restrictions do not apply when managing Case Type workflows and in search - users can see all fields in these contexts.

Improvements

Optimised Integration Log Query Performance

Integration log browsing performance has been improved by removing the ORDER BY ID constraint in the query. This results in significantly faster load times. However, logs created with the same timestamp may not always appear in the exact order of creation. This behaviour can be disabled on a per-account basis if required.

Faster Case Redaction Processing

Case redactions were experiencing slow performance or timeouts due to inefficient DELETE operations. Query optimisations have been implemented to improve processing times.

Bugs 

Fixed 403 Error on User Edit Page

Users without permission to manage integrations were encountering a 403 error when accessing the User Edit page if the cache had not been preloaded by another user with higher permissions. This issue has been resolved to ensure users can edit user accounts without requiring prior cache warming by another user with integration permissions.

• Fix an issue where records were duplicated in the output CSV when a directory was exported

• Ensure Whitespace site collections are valid when calculating the next collection date within the "Whitespace - Next Collection Date" logic.

• Ensure that empty strings denoting unspecified fields are handled correctly in Bottomline plans

• Now ensure that Whitespace site collections are valid when calculating the next collection date within the "Whitespace - Next Collection Date" logic.

Letter Template Placeholders Now Correctly Display '0' Values

Previously, placeholders in letter templates did not display the value 0 when generating letters, instead appearing as an empty value. This issue has been resolved, ensuring that fields with a value of 0 are correctly rendered in generated letters.

Bulk Invite Option Now Available for Imported Users

A bug that prevented the "Bulk Invite" option from appearing in the Action dropdown on the imported person details page has been fixed. The system now correctly detects imported users, allowing bulk invitations to be sent as expected.

New Mapping Fields for Echo Integration

We have introduced two new mapping fields, Source Node Latitude and Source Node Longitude to enhance location-based event processing in the Echo integration.

SAML Integration Available on All Existing and New Accounts

SAML Admin Authentication is now a standard feature available across all Connect accounts. It has been enabled for all existing accounts, and new accounts will have SAML integration available by default. This ensures seamless access for all users requiring SAML authentication.

Improvements 

Maintain Login Page Consistency After Session Expiry and Sign Out

Improved login behavior by ensuring that users are redirected to the same login page they originally used when their session expires or when they sign out. This enhancement is particularly beneficial for SAML users, ensuring that the correct login options are consistently presented.

Enforce SAML Authentication for Linked User Accounts

Users with SAML-linked accounts can no longer log in using native Jadu Connect email/password credentials. If a login attempt is made using email and password, an error message will prompt the user to sign in via their SAML provider.

Add Notification Option to Webhooks

Enhanced webhook error handling by introducing a notification option. If the webhook email field is populated, an error notification will now be sent via email. 

Corrected Case of "SAML" in Data Import

Standardized the capitalization of "SAML" in Data Import to ensure consistent representation.

Optimised Confirm Code List Lookups

Improved the performance of code list lookups against Confirm to prevent integration failures due to a large number of configured codes. To take advantage of this improvement, the Confirm web base URL and API key must be set in the integration settings.

Updated SAML Account Messaging

We've updated the messaging related to SAML account linking to improve clarity and user-friendliness. These updates apply to both the User Management section and the My Settings page.

Bugs

SAML Update Existing User Details URL Incorrect

Resolved an issue where updating existing user details failed. The correct route is now used, ensuring accurate user detail updates.

SAML Login Error

We resolved an issue where some users encountered a 403 Forbidden error when logging in with a cold integration data cache.

Cached DNS Record Items Incorrectly Set with Infinite TTL

Addressed an issue where DNS cache items were stored indefinitely instead of adhering to the expected expiration time of one second. With this fix, DNS records now expire as intended, ensuring proper connectivity.

Phone Numbers Using Default GB Region in Non-GB Locales

Corrected an issue where phone numbers were defaulting to the GB region in non-GB locales. Phone numbers are now parsed correctly based on the appropriate locale.

Shared Filter Sets - Ownership Issue When Renaming Filters

We’ve fixed an issue where renaming a shared filter set caused an unintended ownership change. Previously, if a user created a filter and shared it with their group, and a system administrator renamed the filter, ownership appeared to transfer to the administrator. While the filter still displayed the original owner under the 'Shared Filter Sets' menu, it was no longer accessible to them.

With this fix, renaming a shared filter no longer affects ownership, ensuring that shared filters remain available to the original owner and their group as expected.

New Origin theme

We are excited to introduce Origin, a fully customisable out-of-the-box theme designed to empower customers with an intuitive, no-code approach to website design. Origin simplifies branding, ensures built-in accessibility compliance, and enables real-time customisation—all without requiring advanced technical expertise.

Key Features of Origin Theme

• Real-Time Customisation
  Make live changes and instantly preview updates to your website’s appearance. No extensive testing or debugging is required—just seamless customisation.

• User-Friendly, No-Code Design
  A straightforward interface allows non-technical users to update key design elements effortlessly, ensuring brand consistency without relying on developer resources.

• Built-in WCAG 2.2 Accessibility Compliance
  Origin meets the latest accessibility standards by default, ensuring digital inclusivity for all users, including public sector and higher education organisations.

• Hassle-Free Updates
  Origin is included as part of Jadu’s product updates, meaning customers receive ongoing improvements and fixes without the need for professional services or additional costs.

Fixes

• Language pack

  • Directory postcode search label will read “Search by postcode” on new installs.

  • Search label will read “Search this site” on new installs.

  • Login error message will now read “Please try resetting your password again from the forgotten password page.” on new installs.

• Modern templates

  • Metadata

    • Added Contributor and Source metadata elements to pages

  • Sign in

    • “Error:” is now prepended to the page title when an error is detected in the submitted login details

    • A summary of errors is now shown when the page is submitted with login details that do not match a registered user

    • An inline error is shown by form fields when the page is submitted with login details that do not match a registered user

  • Forgot password form

    • Autocomplete value added to the email field

    • Invalid email addresses are now correctly highlighted as errors

    • Forgot password form now redirects to the index page if a user tries to access it directly and the authentication adapter specifies an external page to use instead.

  • Register form

    • Error messages are now shown if targeting questions are not completed

    • An appropriate error message is now displayed when the email field is left empty

  • Change details form

    • Change details now redirects to the account page if a user tries to access it directly and the authentication adapter specifies an external page to use instead.

  • Change password form

    • Change password form now shows appropriate error messages if a short or long password is entered

    • Change password now redirects to the account page if a user tries to access it directly and the authentication adapter specifies an external page to use instead.

  • Directory A to Z

    • Non-numeric page parameters are now handled gracefully and no longer trigger an application error

  • Directory search

    • “Error:” is now prepended to the page title when an error is detected in the submitted search details

    • A summary of errors is now shown when an error is detected in the submitted search details

    • An inline error is shown by form fields when an error is detected in the submitted search details 

    • The postcode field is now populated with the browser profiles “postal-code” value, where set.

  • Directory category

    • Fixed an issue where the canonical URL of a directory category was incorrect

  • Directory record

    • Fixed an issue where the wrong category is shown in the breadcrumb is a directory category and taxonomy category have a corresponding ID. 

  • Directory record submit

    • Fixed an issue where multiple choice questions were not correctly validated

  • Documents

    • A summary of errors is now shown when an error is detected in the document password form

    • An inline error is shown by form fields when an error is detected in the document password form

  • News list

    • Page title now includes the page number. 

    • Filterbar form now includes a fieldset and legend

  • Event list

    • Page title now includes the page number. 

    • Filterbar form now includes a fieldset and legend

    • Fixed an issue where the filter options could be lost when navigating between pages

  • Search results

    • Aria-label attribute removed from search result elements as unnecessary

  • Widgets

    • The Latest News widget heading order is now correct

    • The Latest News widget no longer shows an empty list if only one news article is present in the application

    • The Opinion Poll widget now shows error messages appropriately

    • The What’s New widget heading order is now correct

    • The External Feed widget heading order is now correct

    • The Right Advert widget now uses a p tag rather than a h2 for the advert title 

    • The Image widget now only wraps any link set around the caption if one has been set

  • Alpha theme

    • Mobile navigation menu is now correctly marked up as a list

    • Fixed colour contrast issue in mobile navigation menu

    • Added a visual indicator for main navigation links

    • Accessible focus state added to main navigation links

    • Updated JQuery to version 3.7.1

  • Dopetrope galaxies theme

    • Navigation widgets no longer cause a HTML validation error

    • Mobile navigation menu is now correctly marked up as a list

    • Fixed colour contrast issue in mobile navigation menu

    • Added a visual indicator for main navigation links

    • Updated JQuery to version 3.7.1

  • Editorial galaxies theme

    • Improved the colour contrast of the latest news widget

    • Added a visual indicator for widget heading links

    • Made the sidebar untabbable when inactive

    • Sidebar can now be closed by pressing the escape key

    • Updated JQuery to version 3.7.1

  • GDS galaxies theme

    • Aria-describedby attribute is now correctly rendered for select form controls

    • Autocomplete value added to the email field of sign in form

    • Poll widget now uses headings appropriately

    • Navigation widgets now use the heading set in the Control Center appropriately on the website.

    • Search label colour is now black

    • Accessibility settings now set the search button to an appropriate colour

    • Increased target size of directory A to Z navigation

    • Increased target size of breadcrumb links

    • Removed aria-label from Menu button as duplicates visible label

    • Increased target size of event calendar widget

    • Fixed an issue where Google Maps would not appear on directory record pages

    • Fixed an issue where an announcement could include an empty link

  • Phantom galaxies theme

    • Added support for “prefers-reduced-motion“ browser setting

    • Updated JQuery to version 3.7.1

  • Spectral galaxies theme

    • Mobile menu label now has an accessible name 

    • Updated JQuery to version 3.7.1

  • Blogs

    • Fixed an issue where an error could be caused after a blog author was deleted

Import SAML User Mappings via Data Import

We have added the ability to import SAML user mappings using the standard data import process, streamlining the initial setup of SAML authentication in Connect.

Key Features:

• An upload option, "Import SAML User Mappings", is now available under Settings > System > Data Import > {ACTION MENU}. This option is only accessible when the SAML Admin Authentication integration settings have been configured.

• The import process accepts a CSV file containing Connect user email addresses and corresponding SAML identities, for example:

  email, saml_identity  
  user-1@acme.net, 098adbef-470c-4eb4-c25c-ce4fe10b84ca  
  user-2@acme.net, 345adbga-220c-7be1-d26a-ce6fc10c84de  

• The system validates the structure of the CSV before processing. If duplicate email addresses or SAML identity values are detected, the import will be halted, and an error message will be displayed. Rows where the email does not match a Connect user will be skipped, allowing the rest of the import to proceed.

• The system will process valid rows even if some contain errors. If an import is retried after correcting errors, only new mappings will be added - existing valid mappings will not be duplicated.

This enhancement simplifies the process of setting up SAML authentication by allowing bulk imports of user mappings.

New Rule Action: "Remove all User memberships"

We've introduced a new rule action, "Remove all user memberships," which automatically de-links all users included in the case membership list at the moment the action is executed.

How It Works

• When triggered, this action removes all users from the case membership list.

• Only users present in the list at the time of execution are affected.

• If users need to remain assigned, they can be re-added via a rule.

This update enhances flexibility in managing user assignments by allowing automated removal while still enabling re-assignment through additional rules.

Selected Interventions Echo Waste Management System Integration

A new integration with the Echo Waste Management System (by Selected Interventions) has been added to Jadu Connect. This two way integration allows Events to be created in Echo at any point in the Connect case lifecycle, and Connect cases to subsequently be updated, potentially triggering ongoing workflow, when updates are made in Echo.

Improvements 

Improved Date Deletion Process

We've made it easier to delete dates in Settings > Communication > Dates. Previously, when attempting to delete a date, the system would block the action due to an automatically created filter referencing the same date. This required users to manually delete the filter before proceeding.

With this update, dates can now be deleted without needing to remove the associated filter manually.

Bugs

Fixed an issue where failures to upload file attachments to a Confirm Enquiry would sometimes not be retried.

• Fixed the manual link for anonymous direct debits to point to the correct page in the Jadu Central manual for Update and Cancel Subscription templates.

• Added a migration to ensure that Bottomline BPS integration fields are always present.

• Direct Debit Payment Adapters: Direct debit payment adapters can now be installed.

• Anonymous Direct Debit Actions:

  • The direct debit action no longer requires users to be signed in.

  • The direct debit cancel and update actions now include a toggle for anonymous access. When enabled, non-signed-in users can execute these actions by completing the relevant form without the system verifying if the reference number is associated with their account. This setting is disabled by default.

• Multiple Payment Provider Instances: Multiple instances of the same direct debit payment provider are now supported.

• Direct Debit Service Provider Selection:

  • A new dropdown has been added to the Direct Debit Service Details page, allowing users to select a payment service provider for direct debit transactions.

  • This dropdown lists all available direct debit payment service providers installed on the system.

• Database Structure Improvements:

  • A new pspID column has been added to the JaduPayBridgeUserDirectDebits table to store the payment service provider associated with each subscription.

  • The mandate table and its associated code have been removed from the application.

  • A new plan abstraction database structure replaces the previous JaduPayBridgeDirectDebitPlans table.

• Terminology Update:

  • The term "Direct Debits" is now referred to as "Recurring Payments" to accommodate potential future integrations with recurring card payment providers.

• Bottomline BPS Integration Updates

  • Configuration & Settings Changes:

    • The First Capital integration page has been removed from the Integration Hub. Settings are now configured within the relevant payment adapter, enabling multiple adapters for the same service provider.

    • The initial plan setting has been removed from the Bottomline BPS integration.

    • References to First Capital have been updated to reflect the updated name of the application: Bottomline BPS.

  • User Experience Improvements:

    • Users with an active Bottomline BPS mandate are now redirected to the Bottomline page for every transaction.

    • The Bottomline BPS adapter now passes the specific plan selected in the Direct Debit Service Details page, along with all plan fields, to Bottomline during transactions.

    • The adapter no longer makes an API call upon transaction completion to register the user for an additional subscription.

    • One-Off Payments: The one-off payment action no longer relies on an active mandate but instead uses the subscription reference created by the Bottomline page.

• Hyland OnBase WorkView integration: Create Multiple Object action

  • As well as the “WorkView: Create Object” action, a new action has been added which can create multiple WorkView objects based on the value of a repeatable form component. 

• Hyland OnBase WorkView Hash as form variables support

  • Two new variables have been introduced to be used in building forms:

    • OnBase hash of first WorkView object

    • OnBase hash of last WorkView object 

  • These values can be used to generate a link at the end of a form on the completion page, to redirect the user to view details of the WorkView object, for example on a separate homepage. They could also be used to prefill a hidden value in a form. 

Changes in Behavior

• The existing skip logic in the Bottomline adapter, which bypassed the Bottomline page for users with an active mandate, has been removed. Users will now be redirected to the Bottomline page for every transaction.

• Previously, only the initial plan was passed to Bottomline during transactions. Now, the specific plan selected in the Direct Debit Service Details page, along with all plan fields, will be included.

• The system no longer makes an API call upon transaction completion to register the user for an additional subscription. Users will now be automatically registered for the appropriate plan when plan information is passed to the Bottomline page.

• The direct debit action no longer requires users to be signed in. This requirement will now be controlled by the form’s settings.

Fixes

• Forms

  • A default value is now set for the “Data Export Job lifetime” when the system is patched if it is currently empty. 

  • Updated cache warming scripts have been added to reduce issues after patching the application 

  • Matrix questions now require a minimum number of columns to be added. 

  • Resolved an issue where by validation rules for URLs submitted with forms and cases could be out of alignment

• Integrations 

  • Workview Filter Results component now stores the selected value correctly when moving between form pages

• Supplements

  • Existing supplements can now be successfully added to other pages on the website.

SAML-based Single Logout (SLS) integration for Staff users

We have now implemented SAML based Single Logout (SLS) functionality. How SLS behaves depends on what is supported by the Identity Provider (IdP). 

New field type “Email List” 

We have introduced a new field type, Email List, allowing users to store and manage multiple email addresses within a single field.

The Email List field type enables the input and storage of multiple email addresses. Initially,  this will be displayed as a comma separated list in the case timeline and case details. Users can populate and edit the field using a textarea input. Each email in the list is validated to ensure it is a correctly formatted email address. If any entry fails validation, an error will indicate the problematic item.

Improvements

Admin Login Page for Jadu Central Users

Users accessing the Jadu Central Control Centre login page via the "Sign in with Jadu Connect" option will now be redirected to the Admin Login page. This page includes alternative sign-in options if SAML Admin Authentication is configured in Jadu Connect. By selecting the alternative sign-in option, users can log in to both Jadu Connect and Jadu Central simultaneously using their SAML-enabled account.

Non-admin users, such as Citizens or Students, will continue to use the standard Jadu Connect login page without access to the alternative sign-in options.

For organisations using OAuth authentication with Jadu Connect, enabling the Admin Login page requires adding a new parameter (login_type=internal) to the OAuth redirect. This ensures users can access the Admin Login page and its alternative sign-in options during the OAuth flow.

Link to Identity Provider Account Settings from User Profiles

Users with accounts linked to a SAML Identity Provider can now access their SAML account settings directly from their user profile or account settings pages. The "Account URL" configured in the Identity Provider SAML settings is used to generate the link to the SAML account management pages.

Case imports

Updated case import background process to account for long running import tasks

Error When Logging Out with Redirect URL
Resolved an issue where users encountered a “Something went wrong” error when logging out if a Redirect URL was configured for their role.

SAML Login Error
Fixed an issue that prevented some users from logging in using SAML credentials. The error occurred when synchronisation of user details between the Jadu Connect user account and the SAML user account failed, causing a “Something went wrong” message when attempting to record the log entry.

SAML-based Single Sign-On (SSO) integration for Staff users 

We are excited to announce the release of SAML-based Single Sign-On (SSO) integration for staff users. This enhancement simplifies authentication processes, offering seamless and secure access to Connect. With support for SAML 2.0, Connect now integrates with major Identity Providers (IdPs) such as Microsoft Azure AD, Shibboleth, and more. Staff users can log in using their organisation’s existing credentials, eliminating the need to manage separate passwords for Connect.

To get started with SAML SSO in Connect enable and configure the integration under: Settings > Integration Hub > SAML Admin Authentication. 

Manage Shared Filter Sets 

The Manage Shared Filter Sets feature, gives administrative control and visibility over shared filter sets. 

Key Features: 

• A dedicated control centre page under Settings for managing shared filter sets which displays all shared filter sets, their names, and their respective owners, including those with disabled accounts.

• Editing Capabilities:

  • Modify the name of a filter set.

  • Reassign ownership of a filter set.

  • Ownership is restricted to one owner per filter set.

  • Batch edit allows assigning ownership to multiple filter sets simultaneously.

• Optimised for efficient loading, even with a large number of filter sets.

Two new permissions have been added (disabled by default for all roles):

• View Manage Shared Filter Sets Page: Grants access to view the list of shared filter sets.

• Manage Shared Filter Sets: Allows editing filter set names and reassigning ownership.

We recommend reviewing role permissions to enable this feature for the appropriate user roles within your organisation.

Improvement

New registration setting “Cancel registration redirect url” 

The 'Cancel' link on the registration page now uses the URL defined in the 'Cancel Registration Redirect URL' setting under Settings > User Administration > Registration. If this setting is not configured, the link defaults to redirecting users back to the login page.

Standardised hiding empty values on Case Details

Empty values for case fields and dates are no longer displayed under the case details tab, previously some empty values were displayed as “N/A”, all field/date values are now not shown. 

Integrations help text location: 

The integration help text has been relocated above the tab headers for better visibility and enhanced user experience.

Bugs

Incorrect case item counts after redaction

Fixed an issue where, after redaction, item counts (e.g., notes, files, messages, and letters) incorrectly included redacted items in tab headings.

Error highlighting on integration hub pages 

Resolved an issue where the User Type - User Group - Role pair fields did not display red error highlights when validation errors occurred.

Missing user group when inviting a new user 

Addressed an issue where user groups were missing when inviting a new user. This was resolved by adding pagination to the invite user form for the User Types, Groups, and Roles fields.

Case reports not removed when case type is deleted 

Fixed an issue where auto-generated case reports were not removed after the associated case type was deleted.

URL field validation

Improved validation on the URL field to ensure only URLs starting with https are accepted.

Maintenance 

The following updates and optimisations have been implemented to enhance system performance, stability, and resource efficiency across environments:

• Server Configuration Changes: Improved process availability and reduced latency.

• Upgraded Memcached Instance Types: Increased cluster size for better performance and scalability.

• Storage Performance Enhancements: Upgraded disk types for improved storage efficiency.

• Optimised FastCGI Processes: Better alignment of the maximum number of FastCGI application processes with resource availability.

• Content Caching Adjustments: Disabled caching for PHP files to ensure real-time content delivery.

• Process Management Improvements: Prevented simultaneous stopping and starting of critical processes.

These changes collectively aim to optimise resource usage, reduce overhead, and improve overall system stability and responsiveness. No behaviour changes are expected as a result of these changes. 

Important Notice: User Sessions Will Be Reset

During the deployment of this update, all active user sessions will be reset. This means users will need to log in again after the update is complete.

What to Expect:

• Any unsaved changes in active sessions may be lost.

• Users will be prompted to log in upon returning to the system.

We recommend saving your work and logging out before the deployment begins to avoid any disruption.

• PDF Generation no longer fails if text mapped to a field contains a single parenthesis

• Forms

  • Form tabs are now disabled when creating a new form 

  • Fixed a gateway timeout issue when the progress bar was enabled on complex forms.

  • Entering a long answer in a matrix component no longer causes an error. Max answer length has been increased to 500 characters. 

  • Resolved an issue where the first checkbox field may not be populated when a PDF of the form response was generated.

  • Added a setting, “Data Export Job Lifetime”, to define the number of days data export jobs are kept on the server since their last executed date. Jobs beyond this limit are now removed by a scheduled task. 

• Hyland OnBase integration

  • Fixed a memory leak when uploading and downloading large files from or to Hyland OnBase

• Flexible event booking

  • Fixed an issue where deselecting a date still keeps the booking date, added a friendly message to the Pricing component when no bookings are made.

  • Added a link to Page template for usages modal on Calendar group page, added a form link to the Page template details page

• Control Center User Interface

  • The number of items on the content schedule list page can now be changed to allow more items to be shown.

  • Google analytics cookies are now marked as secure in the Control Center. 

• Images

  • Errors are now correctly shown when a title, alternative text or keyword value is 255 characters but contains multibyte characters

• Metadata

  • Subject, description, creator, publisher, rights, source, status and coverage fields are now limited to 255 characters. 

• Directories

  • Resolved an issue where exporting a directory with no metadata would cause columns to shift in CSV file.

  • Fixed an issue where exporting a directory after a new field had been added would cause columns to shift in CSV file.

  • An error is now triggered when attempting to import directory records with the metadata option set to “no” when the source CSV file contains metadata columns.

  • When importing directory records with the metadata option set to “no” the parent directory metadata is now used for the imported record metadata details.

  • When importing directory records with the metadata option set to “yes” and metadata present in the source CSV file, valid columns are imported, but invalid or missing data is ignored. 

  • Directory adverts are no longer duplicated when amendments are saved. 

• Supplements

  • If the supplement placement field has been set before the type of supplement is selected, the selected value is now retained rather than defaulting to the first location in the list.

• Events

  • Users with “Can only view own content” permission can now successfully create a new event record. 

• Integrations

  • The number of pages of results shown for the Google Programmable Search adapter is now limited to 10, reflecting the limitations of the Google API.

  • SAML Control Center adapter now uses the “User Identifier Attribute” where set, rather than defaulting to the user’s email address in all cases. 

• Utilities

  • The status message on the link checker broken link report page now shows the date and time of the next scheduled link checking job.

  • Admin DataMapper updated to use “order by” rather than “group by” syntax. 

• Forms

  • Email alerts marked as text-only are now sent using the appropriate type. 

• Modern templates (Photon)

  • Searching for directory records filtered by a specific directory category has been optimised and now completes successfully where there are more than 1000 records in a category. 

  • Meeting attachments are now shown in the same order on the website as they are ordered in the Control Center. 

  • Forms now uses a separate entry point to other site pages to allow more resource intensive processes to be supported appropriately.

  • Registering a theme now works correctly in a Windows environment,  where different values are used for the PrimaryAppPool and PrimarySite variables

  • An email notification is now sent when a user submits a community event on the website.  

  • Use Jadu event listeners for user updates event and remove Symfony listeners for user updates from photon

Performance improvements 

We have implemented performance optimisations to address intermittent issues observed on Jadu Connect UK. During these occurrences, high CPU load has been reported. The key changes made to improve overall system performance are:

• Reduced filesystem access during web requests by adding caching 

• Environment files and variables are now cached in memory 

• Validation metadata is now cached in memory

• Optimised DNS lookups, DNS query results are now cached therefore eliminating the need for repeated system calls and I/O operations for frequent domain resolutions

These improvements aim to reduce the overall CPU load, optimise file system and network operations, and provide a more responsive and reliable experience for users.

Cancel login option 

A new “Cancel” button on the login page has been added that will return the user back to their origin if the user is logging in via an OAuth request for example from the website or the Jadu Central 

This release enhances the Event Bookings interface with new functionality to define customer segments that impact pricing, allowing admins to create tailored pricing options for different customer types, such as business, charity, or community rates. A new "Segments" tab has been added, enabling users to manage segments by creating, editing, and deleting entries. Each segment includes a unique name and an identifier, or slug, which is used to adjust pricing in the pricing summary component.

Pricing rules can now be configured with segment-specific logic, including options to apply percentage-based adjustments or a flat fee. When calculating booking prices, the form designer passes the relevant customer segment using conditional logic and the system adjusts the price based on the assigned segment-specific rule. If no segment matches, the standard pricing is applied.

Flexible event booking: enhanced navigation options
This release introduces enhanced navigation options within the event booking component’s calendar, allowing customers to quickly select and jump to specific dates using a date picker and button control. This feature streamlines navigation for users booking events further into the future, eliminating the need for repetitive clicks to reach later months or years. When a date is selected and the button is pressed, the calendar updates to display the chosen date. If an invalid or past date is selected, or if no date is chosen, the calendar view remains unchanged, and an error message prompts users to select a valid date.

Flexible event booking: more options for repeating bookings

This release enhances the event booking component by introducing more flexible options for setting up repeating bookings. Customers can now specify both the frequency and the number of repetitions for their bookings. A new control labelled "Repeat frequency" has been added to the booking form, allowing customers to choose between daily, weekly, or monthly repetitions. The default option is set to "Weekly," and the frequency control is positioned directly below the existing "number of repeats" field for easy access. 

Flexible event booking: filter blocked dates list
This release introduces a new filtering option to the blocked time list, allowing users to easily narrow down blocked entries by start date, end date, and reason for blocking. 

Fixes and improvements

• Flexible event bookings

  • Fixed an issue where bookings outside a pricing rule's designated hours incorrectly applied the rate from the previous rule.

  • Corrected pricing logic to ensure no rate is applied when bookings fall outside any defined pricing rule.

  • The icon for payment now uses a credit card symbol instead of a dollar sign in Received Bookings.

  • Pricing groups will now always show two characters after the decimal point, even where the final character is a 0

  • The administrator who created a blocked time booking is now visible in the user interfac

  • The date format used for the flexible event booking components is now “Day Month Year”. 

  • The flexible event booking existing booking component now lists the calendar and calendar group in the entry for a given booking. 

  • Unwanted space characters have been removed from the Flexible event bookings account widget

  • The total price column is now aligned with the prices above in the pricing summary component

  • If the flexible event booking calendar is viewed in a 320px viewport, days are now shown such that the calendar fills the full width of the screen

• Classic templates

  • Fix 404 on downloading pdf from MyAccount classic template pages 

• Integrations

  • The Hyland OnBase Document List and Workview Filter Results widgets buttons now update to show “Loading” when clicked while search results are retrieved.

  • The correct error message is now shown when configuring ESRI ArcGIS Enterprise Data Loader integration and the related endpoints are not accessible.

User permissions are now updated after a case import 

User group service permissions cache is now cleared when importing a new case type allowing users to access the newly imported case type and not receive a ‘Not found’ error message. 

Role label now displayed in the page title

The selected role label is now displayed in the page title on the role settings page instead of the role identifier 

Inconsistent column ordering in the Case List Column selector 

In Jadu Connect 1.202 we released improvements to the Case List Column selector, we’ve fixed an issue where the order of the columns was inconsistent following this change. 

Date field filters now accepts dates pre 01/01/2000

The date picker for date field filters has been updated to allow dates pre 1st January 2000

Maintenance 

In preparation for upgrading the database engine reserved words in the new version have been identified and updated. No changes in functionality or behaviour are expected.