The November 2021 release of Alinity was deployed to Test environments on November 11th and Production environments on November 18th. A summary of the changes included in this release appear below.
We’re moving platforms in 2022
If you have been following our monthly release blog posts closely, you will notice the number of new and improved features in this release is lower than we usually provide. This is because our development team is working on migrating Alinity to a new hosting platform for early 2022. The new platform uses the latest versions of cloud and database technologies and Alinity is being upgraded to take advantage of them. This work will continue through the end of 2021. We will continue to upgrade Alinity with bug fixes and new features each month but at a lower volume.
The new platform will provide better performance, better security, and will make new technologies available for further improvements to the product. One of the new features we can take advantage of immediately after moving to the new hosting platform will allow us to automatically add computing resources to your system during peak periods like renewal, and automatically return to normal resource levels when demand drops. There are new options for document storage that will allow us to reduce storage charges going forward. The software will look the same as it does on our current platform so no special planning or retraining is required for this move. We are excited about starting this next chapter of Alinity’s progression. Please let us know if you have any questions.
Change List
| Change | Type | Applies To |
| Custom Rules for Showing “Other” Forms to Members | Feature Update | Other Forms |
| Other forms, custom forms that don’t belong to a standard module such as applications or renewal, can now be set up to enforce custom rules for when to make these forms available to members. | ||
| Copy Supervisors to Next Year’s Employment Option | Feature Update | Employment |
| Unexpired supervisors can now be automatically copied to the next year’s employment record when a member, or admin, adds an employment record for the same organization for the next year. This option is off by default and can be enabled via the “Automatically copy supervision forward” option. | ||
| Export Performance Improved | Feature Update | General |
| The underlying method used to retrieve data for export has been revamped for improved speed and reliability. The overall speed will still be limited by the base speed of the datasource chosen however larger exports should complete more quickly in general. Additionally the chances of an export timing out have been greatly reduced. | ||
| Education Level Code Length Increased | Feature Update | General |
| The length of the internal code used for Education Levels has been increased to allow for more flexibility. | ||
| Org Document Upload Validation | Bug Fix | General |
| In rare cases it was possible to add longer text to fields depending on the length of the file name of the file that was chosen for upload. These are now validated ahead of time and return a legible warning. | ||
| “Top” Employment Selection | Bug Fix | General |
| In cases where the member’s latest employment was expired, but they had employment with the same employer the previous year which had no expiry date, it was possible for “top” employment to pick up on that previous employment record. This has been addressed. | ||
| Phone Number not Recorded on Initial Corporation Insert | Bug Fix | Corporations |
| When a member initially applies for a new corporation registration from the member portal the phone field was not being saved. The phone number is now properly saved to the record. | ||
| Deposit/GL Reports Fail When Non-Numeric Characters are Included in the GL Account Code | Bug Fix | Accounting |
| Certain accounting reports would fail when a GL account with a non-numeric character, such as a dash, were part of the code. These reports have been updated to support these characters properly. | ||
| Business Rule Clarity for Data Where Effective Time AFTER Expiry Time During Approval | Bug Fix | General |
| When approving a form any errors where an effective date is AFTER an expiry date now properly indicate the part of the form the error is associated with. This will make locating and correcting the error much easier. | ||
Next release
The December 2021 release of Alinity is scheduled for deployment to production sites December 16th.
English 
French