The November 2022 release of Alinity was deployed to Test environments on November 10th and Production environments on November 17th. A summary of the changes included in this release appear below.<\/p>\n
If you have been following our monthly blog posts, you will have seen our announcements about migrating Alinity to a new hosting platform. The new platform is Microsoft Azure\u00a9 and we have been working with it in our development environment for all of 2022.\u00a0 We are excited about how well it is performing and the new features it will allow us to create in Alinity.\u00a0 We have decided to postpone our move to Azure until 2023 in order to allow renewal periods that are currently in progress, to be completed without interruption.\u00a0 Migration to Azure will begin on Test environments in the first quarter of 2023 and then for production systems starting in the second quarter.\u00a0We will continue to upgrade Alinity with bug fixes and new features each month while the transition is moving forward.<\/p>\n
\nVerification 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 Member 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 member and public-facing features on your system before each upgrade. Please see our\u00a0Verification Introduction<\/a>\u00a0article for further details and guides for testing.<\/p>\nChange List<\/h2>\n
\nThis list is incomplete, please check back shortly.<\/p>\n
Change<\/strong><\/td>\n| Type<\/strong><\/td>\n | Applies To<\/strong><\/td>\n<\/tr>\n | ***************New Feature***************<\/td>\n | <\/td>\n | <\/td>\n<\/tr>\n | Form Correction Button<\/td>\n | New Feature<\/td>\n | Admin<\/td>\n<\/tr>\n | Forms such as renewal, audit and profile update have a new button next to Unlock called Correction. This button will unlock the form as the other button does but will also put the form in edit mode for you to make changes right away.<\/em><\/td>\n<\/tr>\n | Task Queue Subscriber Emails<\/td>\n | New Feature<\/td>\n | Email Triggers<\/td>\n<\/tr>\n | Two new email triggers have been added to the system, “Daily Task Summary” and “New Task Assigned”. Activating these triggers will allow Task Queue Subscribers to receive new task emails and\/or the daily summary emails. New tasks are sent to administrators to inform them that a new task has been assigned. The daily summary provides a summary of all open tasks and tasks that have been assigned (Open or closed) within the last 24 hours. Administrators may individually choose to receive the emails trough the Task Queue Subscriber setup.<\/em><\/td>\n<\/tr>\n | ***************End of New Feature***************<\/td>\n | <\/td>\n | <\/td>\n<\/tr>\n | ***************Feature Update***************<\/td>\n | <\/td>\n | <\/td>\n<\/tr>\n | Corporate Renewal Dashboard Order<\/td>\n | Feature Update<\/td>\n | Member Portal<\/td>\n<\/tr>\n | The corporate renewal portion of the member portal has been reordered so that it sits closer to the top of the items to help prevent it from showing up scrolled off the bottom of smaller screens.<\/em><\/td>\n<\/tr>\n | Question Explanations on Exams<\/td>\n | Feature Update<\/td>\n | Jurisprudence<\/td>\n<\/tr>\n | The explanations that can optionally be provided to members when a question is finalized have been updated to provide more options. The correct and incorrect explanation have been removed and replaced with a default explanation on the question and a specific explanation on the choice that will be used instead of the default if it is filled in; these fields are optional and your exams have been upgraded so that if you use the existing feature, it will operate the same way as before. You can also set whether or not the explanations should show up immediately, the default is that they show up only when the member has no more attempts for a question to match the original behavior. This new setting will better allow you to create learning exams where the member can be directed to new information as they make choices on questions.<\/em><\/td>\n<\/tr>\n | Reactivate User as Registration Admin<\/td>\n | Feature Update<\/td>\n | Admin<\/td>\n<\/tr>\n | The reactivate option for users can now be used if you have the registration admin permission whereas before you needed to be a full system administrator. A note is now created on the person who was reactivated recording this action for audit purposes.<\/em><\/td>\n<\/tr>\n | Admin Emails on Org Summary<\/td>\n | Feature Update<\/td>\n | Admin<\/td>\n<\/tr>\n | The email list shown on the summary for an org will now display the business email address if it is available in place of the personal email address.<\/em><\/td>\n<\/tr>\n | Termination of Specializations<\/td>\n | Feature Update<\/td>\n | Registration<\/td>\n<\/tr>\n | Whether a member’s specializations should be cancelled, after a change in registration occurs, can now be controlled at the granularity of individual register change mappings. The default behaviour is to cancel specializations when the member is moving to a non-practicing register. If you wish to change this for a specific process please contact the Alinity helpdesk.<\/em><\/td>\n<\/tr>\n | ***************End of Feature Update***************<\/td>\n | <\/td>\n | <\/td>\n<\/tr>\n | ***************Bug Fix***************<\/td>\n | <\/td>\n | <\/td>\n<\/tr>\n | Partial Refunds in a Locked Period<\/td>\n | Feature Update<\/td>\n | Accounting<\/td>\n<\/tr>\n | The restriction preventing use of Partial Refunds against payments in a locked accounting period has been removed.\u00a0 Now when a partial refund is created for a payment in a locked period, the system creates the reversing transactions required in the current period. The state of the GL transactions in the locked period is not modified (prior reporting is stable) and the adjustments will be passed to your GL in the current period.\u00a0 FYI – another update to this feature is being planned that will allow a portion of the refund to be re-classed as an administrative fee in the same operation (thank you to Melanie at CLPNA for this excellent suggestion.)<\/em><\/td>\n<\/tr>\n | Dynamic Selection of Organization Names versus Organization Labels<\/td>\n | Feature Update<\/td>\n | General<\/td>\n<\/tr>\n | Alinity supports both a full-sized “Organization Name” field and a shorter “Organization Label” field.\u00a0 The full organization name can be quite long, and these long fields don’t display nicely on small screens like smart phones.\u00a0 On full sized Mac and PC screens, however, showing the full name makes it easier to distinguish similar organization names from each other. In this release we have implemented a new technique to display the shorter “label” field on smaller screens, and the full sized “name” field on larger screens dynamically.\u00a0 We are using it only for the display of Employment information for now, but if the method is successful, we will look to use it in other areas of Alinity where “name” and “label” fields exist.<\/em><\/td>\n<\/tr>\n | My Forms Saving Multiple Tabs<\/td>\n | Bug Fix<\/td>\n | Admin<\/td>\n<\/tr>\n | When editing the first tab of a form customized by the help desk to have additional tabs it now correctly preserves the customized content on the additional tabs.<\/em><\/td>\n<\/tr>\n | Problem Payment Report<\/td>\n | Bug Fix<\/td>\n | Accounting<\/td>\n<\/tr>\n | For some large databases the Problem Payment report was timing out.\u00a0 This problem is now corrected by having the report work in one-month windows according to a cut-off date you specify. The report is accessed from the Accounting->Payment page from the menu at top right.\u00a0 Resolving problem payments appearing should be your first step in reconciling your Alinity system with your bank and your General Ledger. Problem payments include credit card payments where no result was returned by the processor.\u00a0 These are referred to as “pending payments” and their status must be resolved to proceed with balancing. See this article to see how to Resolve Pending Payments<\/a>.<\/td>\n<\/tr>\n | GL Account Detail<\/td>\n | Bug Fix<\/td>\n | Accounting<\/td>\n<\/tr>\n | A bug in the GL Account Detail report was corrected that caused some refunds from not appearing. The missing refunds were included in the total of the report, but not in the content displayed and this problem is now corrected.<\/td>\n<\/tr>\n | Payment Status Popover<\/td>\n | Bug Fix<\/td>\n | Accounting<\/td>\n<\/tr>\n | The popover next to the payment status on the payment detail screen will show properly when clicked now.<\/em><\/td>\n<\/tr>\n | Payment Details Invoice List<\/td>\n | Bug Fix<\/td>\n | Accounting<\/td>\n<\/tr>\n | In rare scenarios such as when a payment is applied and unapplied from the same invoice more than once you would see multiple entries in the invoice summary. This could lead to confusion since the lines would look the same. Now when more than one entry occurs like this only the most relevant one will be shown to ensure that each invoice is only shown once in the list.<\/em><\/td>\n<\/tr>\n | Browser Verification Resend Code<\/td>\n | Bug Fix<\/td>\n | All<\/td>\n<\/tr>\n | Email messages can take several minutes to arrive depending on the destination and overall system congestion. Many users were clicking the resend button multiple times if they did not receive the email immediately which would then have multiple emails arrive at the same time causing confusion. Now a resend can only happen if the latest email is at least five minutes old otherwise the user is presented with a warning asking them to wait a few minutes longer.<\/em><\/td>\n<\/tr>\n | Email Trigger Sender Override<\/td>\n | Bug Fix<\/td>\n | All<\/td>\n<\/tr>\n | If a specific email sender is specified for an email trigger, that email address will now be respected. The sender specified at the level of the trigger takes priority, but if no override is set there it will check if the linked email template has a specific email sender chosen.<\/em><\/td>\n<\/tr>\n | New Lines in Forms<\/td>\n | Bug Fix<\/td>\n | All<\/td>\n<\/tr>\n | Many forms supported paragraph sized text boxes for entry and allow new lines to be entered. These new lines wouldn’t appear in all read only displays due to the way browsers display whitespace. An update has been made to ensure that these new lines now are shown in browsers.<\/em><\/td>\n<\/tr>\n | ***************End of Bug Fix***************<\/td>\n | <\/td>\n | <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n |
Next release<\/h2>\nThe December 2022 release of Alinity is scheduled for deployment to production sites December 15th<\/span>.<\/p>\n","protected":false},"excerpt":{"rendered":" The November 2022 release of Alinity was deployed to Test environments on November 10th and Production environments on November 17th. A summary of the changes included in this release appear below. Alinity is Moving to Microsoft Azure \u2013 Almost There! If you have been following our monthly blog posts, you will have seen our announcements […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-467","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.alinity.ca\/fr\/wp-json\/wp\/v2\/posts\/467","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.alinity.ca\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.alinity.ca\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.alinity.ca\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.alinity.ca\/fr\/wp-json\/wp\/v2\/comments?post=467"}],"version-history":[{"count":0,"href":"https:\/\/www.alinity.ca\/fr\/wp-json\/wp\/v2\/posts\/467\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.alinity.ca\/fr\/wp-json\/wp\/v2\/media?parent=467"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.alinity.ca\/fr\/wp-json\/wp\/v2\/categories?post=467"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.alinity.ca\/fr\/wp-json\/wp\/v2\/tags?post=467"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}} |