Email notification for blocked corporation renewals
A new email trigger can be set to automatically send an email notification to the registrant when a corporation’s renewal is blocked, and it comes with a ready-to-use template.
Alinity ships monthly. Each release lands in Test environments first, then Production roughly nine days later, and every client gets it, included in the subscription.
A new email trigger can be set to automatically send an email notification to the registrant when a corporation’s renewal is blocked, and it comes with a ready-to-use template.
Complaints with custom fields which use the “text” data type can now be searched by the content of that text using the “By custom field” query, making specific complaints easier to find.
Previously, when instructions were attached as the first step of a form, clicking the button to view those instructions would also automatically generate the form. This created situations where a member or applicant might review the instructions, realize the form wasn’t what they needed, and then have to withdraw their submission. Alternatively, regulator staff would eventually need to withdraw the form on their behalf. This has been updated so that the form is not generated until the member or applicant chooses to proceed to the next page after reviewing the instructions.
Previously, large or complex member forms required considerable time for the system to load the initial version when starting a new form. This has been updated so the initial version of a form loads as quick as an in-progress form does.
Previously, viewing the registrations tab of a Registrant and Corporation with a large registration history would take several seconds to load the page. The performance of these pages has been improved to load almost instantaneously.
Previously, if a form with several reviewers was sent back for changes, the system would erroneously mark the form as “Review(s) Complete” as soon as the first reviewer resubmitted. This has been corrected to wait until every reviewer has resubmitted before the system changes the status to “Review(s) Complete”.
Previously, “On Paid” form status triggers were being reset to their defaults each time a new version of the form was published. This has been corrected so that all form status triggers are now kept, and no longer need to be set up again, when a new form version is published.
Previously, a misconfiguration with multi-designation Corporation workflows could silently prevent a new set of organization forms from being started, despite a registrant meeting all required criteria. This has been corrected in all organization and corporation registration forms.
Previously, a profile update which was approved automatically could result in a mismatch summary being displayed to admin when reviewing the final form. This has been corrected to ensure the summary always maps to the correct form page when a profile update was approved automatically
Previously, college’s with both the legacy “organization profile update” form and the new “Org Form” profile update would encounter an error when attempting to view a form using the chevron button in the history pop-up from the organization profile update page. This has been corrected to ensure the organization profile update page always opens the correct form for each college’s configuration.
Previously, if an invoice was changed to $0, the form status trigger actions that normally run after payment did not run. This has been resolved so that these invoices are now treated as paid and the form status triggers actions run as expected.
Previously, when an administrator edited an older invoice whose registration was already created, the system would erroneously send email notifications confirming the registration was approved. This has been resolved so that follow-up emails are no longer sent when an invoice is edited that is attached to an approved registration.
Previously, term permit end dates were being calculated one day later than they should have been. This has been corrected so that term permits now end on the correct date.
Previously, the system calculated the end date of practice restrictions and conditions to the start of the day, instead of the end of the day. This has been corrected so that restrictions and conditions now stay in effect until the end of their expiry date, the same as other dated records.
Previously, when merging an organization which was an insurance provider, the system was not correctly handling the attached records, specifically the business email addresses of contacts and the insurance records. This prevented the organization from being deleted post-merge. This has been resolved so that when two organizations are merged, the insurance records of members and corporations and business email address of contacts now move to the target organization.
Previously, if a candidate’s internet connection repeatedly dropped and reconnected during an exam, their selected answers could stop matching what was saved, and in rare cases an answer could be counted twice. This has been resolved so that answers now stay in sync, and the system displays an error message, preventing submission, if there are any answers which failed to save.
The configuration setting that allows searching the public directory by registration number now works as intended.
Previously, if a user’s session expired partway through an action, parts of the page could break without explaining why. This has been resolved to ensure the system now handles session expiration more gracefully.
If an employment record is added with a blank email, the email is now saved as empty and matches the existing logic for when a record is edited.
Resolved an issue that prevented some data from being included in cloud exports.
Resolved an error that occurred when converting a person’s other names. It was caused by a mismatch with the current database structure.
Resolved an error that was causing duplicated elements to display on entries in the other configuration details pages.
Resolved an issue where the system blocked manually recording of a payment refunded through the Elavon portal if the amount being refunded exceeded the total Elavon expected.
Previously, the requirements checklist feature was only available on forms directly associated with registration changes. This has been updated to support other person-form types as well, improving visibility into outstanding requirements for both members and administrators.
We have updated our offline page to match the design of our new UI and be more mobile friendly.
There was an issue affecting page load speeds when selecting certain data sources for exports. We have revised the underlying query used to generate exports, which has significantly improved loading times.
Previously, when a member paid by debit card, the confirmation message displayed “Your credit card transaction was processed successfully,” as the same message was used for all online payment types. This has been updated to “Your payment was processed successfully” to ensure the confirmation accurately reflects all payment methods and avoids potential confusion.
Previously, the “Searching” gear icon did not display on some pages after a query was run. This has been corrected to ensure the icon displays properly during searches.
Previously, Alinity’s phone number validation only supported international country codes with two digits. This has been updated to support country codes with up to three digits, allowing a broader range of international phone numbers to be entered successfully.
With this release, we have improved the accessibility of documents uploaded to forms as part of case events. Previously, if a document was attached to a form within a case event, you would need to navigate through the case event and the associated form to access the document. With this improvement, documents attached to forms within case events will now also appear in the general Documents tab for the case. This makes it easier to see and access all documents associated with a case in one place, without having to navigate through multiple layers of the case.
CIHI previously required “Sex at birth” to be collected as part of its Minimum Data Set. Alinity was updated at that time to include this field. CIHI later removed this requirement; however, the field remained in the Alinity user interface and continued to appear as a mandatory field for administrators to populate, even though it was no longer required. We have now removed the field from the Alinity user interface to align with the current CIHI requirements and eliminate the unnecessary data entry requirement.
Previously, when a member submitted a profile update form that required administrative review rather than automatic approval, the form was not visible on the member’s dashboard. The member would only see the form if an administrator subsequently returned it to them for updates. This has now been corrected. When a profile update form is submitted and requires administrative review, such as when it includes a name change request, the form will now appear on the member’s dashboard with the appropriate status clearly indicated.
The Alinity system provides a character count for text boxes on forms, which is designed to update as a user enters or edits text. Previously, if a user entered text, saved the form, and later returned to it, the text would remain visible but the character counter would incorrectly display 0 (for example, 0/200). The counter would only update to the correct number once the user began typing or made another edit. This issue has now been corrected. The character counter will correctly display the number of characters already entered when a saved form is reopened.
Custom fields in Alinity have supported sequencing for a long time, allowing you to control the order in which fields are displayed. Previously, however, the sequence number was only accessible to Alinity developers. We have now updated the UI to expose this setting, allowing administrators to view, set, and adjust the sequence of custom fields themselves.
Previously, if a member changed their browser settings to an unsupported language, translated the page using their browser, and then saved the form, Alinity would inadvertently save the translated text. As a result, when an administrator later reviewed the form, the content would appear in the member’s translated language rather than in English or French. We have now corrected this behaviour. Forms will retain their original English/French content regardless of any browser-based translation applied by the member.
In Alinity, administrators can create and manage note types, including activating and deactivating them. When a note type is deactivated, it is no longer available for selection, while all historical records associated with it are retained. As with other deactivated items in Alinity, deactivated note types should appear with a strikethrough when viewing the full list in Setup. This visual indicator was previously missing for note types. This has now been corrected, and deactivated note types will display with a strikethrough as expected.
Alinity allows administrators to manually apply payments, such as e-transfers, cheques, cash, and other payment types. When applying a payment, administrators can select a payment date other than the current date. For example, if a payment was received on Friday but is not entered into Alinity until the following Tuesday, the administrator can record Friday as the payment date. Previously, if an administrator selected a different payment date and then changed the payment type, the payment date would incorrectly reset to the current date. This has now been corrected, and the selected payment date will be retained when changing the payment type.
On search pages, Alinity allows administrators to pin specific records from search results or queries for easy access later. Once records are pinned, administrators can select the primary pin icon to view the complete list of pinned records and take the appropriate actions. This functionality was not working as expected for Profile Update Forms using the newer Person Form type. This has now been corrected, and these forms can be pinned and managed as expected.
Alinity has offered online multiple choice exams for many years. This release expands that to multi-select questions, allowing members to choose more than one answer, for example, “Choose all correct answers that apply.” When configuring a question you will now see a Multi-select option, along with the ability to identify multiple answer options as correct.
Answer choices can now be randomized, so each exam taker may see the options for a question in a different order. A “Random answer order” option is available at the exam section level; when enabled, answer choices for questions in that section are presented in a randomized order.
A new level above exam sections has been added, called Exam Topics. By default an exam contains a single topic, but the topic level also introduces the ability to randomize which sections each exam taker receives: five sections in a topic, of which Alinity presents a random two. This builds on the existing randomized question bank within each section.
Tags can now be assigned to exam questions, giving administrators additional data to categorize questions and supporting more detailed reporting and analysis.
Risk assessment style exams can now be configured, where each question carries a positive or negative weight contributing to the member's overall score. Members can view their final result, a summary report can be saved automatically to their documents, and System Admins can access individual results through the administrative portal.
Previously, creating an export from the Consultations page and then navigating back using the Alinity back button displayed an error. This has been resolved and users can return to the Consultations page successfully.
Batch withdrawals allow a reason and an optional comment. Previously, a comment containing an apostrophe would cause the withdrawal to fail. This has been corrected and comments containing apostrophes now save successfully.
Where a system was configured to support multiple designations for corporations, new registration forms were not always associated with the designation selected during registration. Forms are now properly attached to the applicable designation.
Administrators can manually initiate a renewal form for a member from the Registration tab of the member profile. The option was not displaying in the interface, preventing access to the functionality. It is now available as expected.
The June 2026 release of Alinity was deployed to Test environments on June 10th and to Production environments on June 18th. Full feature and fix detail for this release is published on the Alinity blog.
The May 2026 release of Alinity was deployed to Test environments on May 13th and to Production environments on May 21st. Full feature and fix detail for this release is published on the Alinity blog.
The April 2026 release of Alinity was deployed to Test environments on April 7th and to Production environments on April 16th. Full feature and fix detail for this release is published on the Alinity blog.
The March 2026 release of Alinity was deployed to Test environments on March 10th and to Production environments on March 19th. Full feature and fix detail for this release is published on the Alinity blog.
The February 2026 release of Alinity was deployed to Test environments on February 10th and to Production environments on February 19th. Full feature and fix detail for this release is published on the Alinity blog.
The January 2026 release of Alinity was deployed to Test environments on January 14th and to Production environments on January 22nd. Full feature and fix detail for this release is published on the Alinity blog.
The December 2025 release of Alinity was deployed to Test environments on December 9th and to Production environments on December 18th. Full feature and fix detail for this release is published on the Alinity blog.
The November 2025 release of Alinity was deployed to Test environments on November 10th and to Production environments on November 20th. Full feature and fix detail for this release is published on the Alinity blog.
The October 2025 release of Alinity was deployed to Test environments on October 7th and to Production environments on October 16th. Full feature and fix detail for this release is published on the Alinity blog.
The September 2025 release of Alinity was deployed to Test environments on September 9th and to Production environments on September 18th. Full feature and fix detail for this release is published on the Alinity blog.
The August 2025 release of Alinity was deployed to Test environments on August 12th and to Production environments on August 21st. Full feature and fix detail for this release is published on the Alinity blog.
The July 2025 release of Alinity was deployed to Test environments on July 8th and to Production environments on July 17th. Full feature and fix detail for this release is published on the Alinity blog.
The June 2025 release of Alinity was deployed to Test environments on June 10th and to Production environments on June 19th. Full feature and fix detail for this release is published on the Alinity blog.
The May 2025 release of Alinity was deployed to Test environments on May 6th and to Production environments on May 15th. Full feature and fix detail for this release is published on the Alinity blog.
The April 2025 release of Alinity was deployed to Test environments on April 8th and to Production environments on April 17th. Full feature and fix detail for this release is published on the Alinity blog.
The March 2025 release of Alinity was deployed to Test environments on March 11th and to Production environments on March 20th. Full feature and fix detail for this release is published on the Alinity blog.
The February 2025 release of Alinity was deployed to Test environments on February 11th and to Production environments on February 20th. Full feature and fix detail for this release is published on the Alinity blog.
The January 2025 release of Alinity was deployed to Test environments on January 14th and to Production environments on January 23rd. Full feature and fix detail for this release is published on the Alinity blog.
Looking for an older release? Notes from 2024 and earlier live in the Alinity release archive.
Every client gets every release, included in the subscription. We can walk you through what has shipped and what your team could turn on.