The July 2025 release of Alinity was deployed to Test environments on July 8th and will be deployed to Production environments on July 17th. A summary of the changes included in this release appear below.
Verification of the shared features of Alinity on each upgrade is taken care of by our development team. These are features appearing primarily in the Administrator Portal area of the system. Our team does not, however, verify the custom configured components on your Registrant Portal since requirements for these are often unique and cannot be addressed within the monthly upgrade period. Therefore, we recommend that you review and verify all registrant and public-facing features on your system before each upgrade. Please see our Verification Introduction article for further details and guides for testing.
This list is incomplete, please check back shortly.
Product Release Webinar – Coming Soon!
New Features
Registration Person Forms Data Source | Database Management
A new export data source titled “Registration Person Forms” has been added to the Registrations search page. For those using the newer style of form, this export provides access to basic registrant information, along with details such as the type of form linked to the registration, the originating and destination registers, invoice date(s), and more.
Feature Improvements
Exam Results Import Permission | Exams
We’ve updated the permission structure for importing exam results based on feedback from admins who manage exam data. Previously, this functionality was tied to the “Utilities Administrator” permission, which granted access to all utility functions. To improve control and reduce unnecessary access, the import permission is now tied to “Assessments Management”, which aligns more appropriately with exam-related functionality. This change helps minimize permission grants and reduces the risk of unintended access for users.
Bug Fixes
Email Triggers “Next Scheduled” Inaccurate | Email Triggers
Most email triggers are scheduled to run every 15 minutes. This means that when the conditions for a trigger are met, the corresponding email will be sent within that timeframe. Previously, the user interface incorrectly displayed the next scheduled run time as 10 minutes after the last. This has now been corrected to accurately reflect the 15-minute interval.
Long Sandbox email addresses running off the page | Admin
In some cases—such as organization pages in the test system—the sandbox email address was too long to fit the available space. Unlike on the registrant profile, where the address wraps correctly, it was being cut off. This issue has now been resolved.
Special Characters in Sandbox Emails | Admin
To address issues with sending emails to sandbox email addresses containing special characters, it was determined that accented characters in the email addresses were causing the problem. To prevent this, the team implemented a solution that replaces accented characters with their unaccented equivalents in the Test systems.
Complaint Status Change Time | Complaints
The team identified an issue with complaint status change tracking where only the date was being recorded, without the time. While the database was originally designed to store both, the time component was not being captured as it was not in the user interface. After reviewing the issue, it was decided to reintroduce time tracking for complaint status changes. Historical records were updated with a default time set to the end of each recorded day, and the user interface has been enhanced to prompt for a specific time during manual status updates.
Message when removing someone from a group | Group Management
The warning message displayed when removing someone from a group using the trashcan icon was found to be unclear and potentially misleading. To improve clarity, the message has been updated to read: “Remove ‘{name}’ from {group}?”
For example: “Remove John Smith from Volunteer Group?”
System Default to Hide VOR’s from non-active practice registers | Verification of Registration Forms
Previously, the system defaulted to showing the option to select a Verification of Registration (VOR) form to all registrants. However, in most cases, individuals who are not in active practice should not have access to this option. The default behavior has now been updated: By default, VOR forms will no longer be visible to registrants without an active practice or a valid registration record. This setting can still be overridden in specific cases if necessary.
CIHI residence state province code | CIHI
Previously, the UI sometimes displayed the wrong state/province when multiple regions shared the same CIHI code across different countries. This occurred because the UI matched only on the state/province code and ignored the country. Although the underlying data was correct, the display was misleading. The issue has now been fixed by updating the UI to consider both the state/province code and the country.
Person-form admin reg changes not appearing on registrations page | Admin
When an administrator completed a registration change using a person-form type, the registration change form was appearing on the person’s profile but not on the registrations search page. This issue has now been resolved, and the form correctly appears in both locations as expected.
Closed date not saving on consultation creation | Consultations
Previously, if a closed date was entered during the creation of a consultation, it was not being saved. However, adding or editing the closed date after the consultation was created worked as expected. This has now been fixed so that the closed date is properly saved even when added at the time of creation.
Unable do delete dashboard widget | Admin Dashboard
Previously, if you added a new widget to your admin dashboard, you couldn’t delete it immediately if you changed your mind. You had to refresh the page before the delete option became available. This has now been fixed so that widgets can be deleted right away without needing to refresh.
Org invoice creation default | Accounting
Previously, when searching for organizations on the Organizations page and selecting a single organization to create an invoice using the dropdown menu, the system incorrectly defaulted to a person invoice template instead of an organization invoice. When multiple organizations were selected, the correct template default was used. This has now been fixed so that even when only one organization is selected, the invoice template correctly defaults to the organization type.
Next release
The August 2025 release of Alinity is scheduled for deployment to production sites August 21st.
English 
French