Release Notes: 12.7.0
- Peter Fasano
- Seth Petry-Johnson
Description | This release contains a number of performance and stability improvements, some new PDF functionality, and contains a very-early-alpha-preview of an upcoming “Criteria-Added Activities” feature. |
|---|---|
Release Date | Apr 4, 2025 |
Marketing |
12.7.0
Category | Description | Internal documentation | |
|---|---|---|---|
| 1 | |||
| 2 | Configuration Enhancement | Large File Uploads are enabled by default for all clients We have been able to support Large File Uploads (E.G. “S3 Upload attribute) since release 11.0.35. Previously, this required manual infrastructure setup, but in 12.7 a default S3 Bucket and S3-backed File Library are automatically created. | |
| 3 | Usability Enhancement | Merge Account feature supports files in a User's S3 File Library We closed a feature gap with our merge account feature which did not previously support files in a member’s S3 library. Files in the S3 library will now be merged as well. | |
| 4 | Usability Enhancement | Word documents uploaded to an S3 Upload Attribute can be converted to PDF Microsoft Word documents uploaded to an S3 Upload Attribute can be viewed as a PDF. This closes a feature gap with the legacy File Upload Attribute and allows the document to be viewed directly in the browser, without needing to download it and open it in a desktop application. | |
| 5 | |||
| 6 | Usability Enhancement | New "Generate PDF" Behavior A Workflow Behavior can render a template, convert it to a PDF, and store it in a user’s S3-backed File Library. The main benefit of this feature is that it can generate a PDF of a point in time snapshot of the Workflow details, for instance to render a certificate when a credential is obtained. Other mechanisms for rendering Templates into PDFs use the current values of the Workflow’s Attributes which make them unsuitable for use as historical records. | |
| 7 | Security updates for self-hosted clients | ||
| 8 | Self Hosted Reporting | Izenda 7 has been upgraded to version 2024.4.3 and is available for self-hosted clients. (This is notable for security reasons as it removes a dependency on .NET 6, which is no longer supported by Microsoft) This version will be rolled out to Heuristics-hosted clients in the future. | |
| 9 | FIPS Mode support | The Address Verification feature will now work correctly when FIPS-compliant mode is enabled in Windows. |
|
| 10 | Other Improvements | ||
| 11 | Usability Enhancement | Organization accounts are not considered to be assignee candidates when identified by email This addresses an edge case information disclosure defect. In this edge case, an Organization exists in LearningBuilder and has as its Primary Email the personal email address of its Executive Director. That Organization record is configured with Alternate Emails so that emails sent to the Organization account are forwarded to multiple key personnel. A user enters the Executive Director’s email address into a Workflow Assignee attribute, intending to assign a Workflow to them in their personal capacity. An email is sent to this address containing a privileged link to act on the Workflow. If the Executive Director’s email address is ALSO linked to a Person account, then everything works fine; they get the email as expected. But if the Executive Director’s email address is NOT linked to a Person account, and ONLY exists for that Organization account, then the privileged link gets sent to that email address AND the Alternate Emails on the Org account. In this configuration, the privileged link could potentially be sent to people that are not intended to (and should not) receive it. In 12.7, we changed the notification system so that if an email address is entered into the assignee system, it will ONLY match to a Person account. (The purpose of the assignee system is to assign a task to an individual; there are no use cases where we would expect an Organization account to be the assignee) | |
| 12 | Usability Enhancement | Email Templates validate that helper methods refer to valid Attribute names We improved the Email Template validation to validate that all | |
| 13 | Usability Improvement | Increased the size of the “tag” element in the Behavior configuration screen This field is often used to pass complex JSON-formatted text to a custom procedure. The form field has been increased in size to make that easier to do. | |
| 14 | Stability Improvement | Improved stability of background queue processing services Numerous “under the hood” improvements were made to improve the stability of the External Queue Processor system which powers numerous systems including the Workflow Import Queue. These changes make the services more resilient to edge case issues that temporarily interrupt connection between the service and the queue. These changes are intended to reduce the scenarios in which a queue processing job can get “stuck” and require manual intervention. | |
| 15 | System Insights | Numerous “Insights” views have been added and linked to the configuration UI These views are designed to support System Administrators in understanding how a piece of configuration is used or has changed over time. |
|
| 16 | System Insights | System Search searches the “Client Default” App Config scope if a PROD environment value is not set System Search is an internal tool for finding configuration elements by a text search. This change allows it to target the “Client Default” App Config scope when no PROD environment setting is defined, making the search more effective and accurate. | |
| 17 | Defect | “Read Only” Attributes no longer an option for Update Workflow Instance Attribute behavior. | |
| 18 | Defect | Email Tracking time stamp causes emails to appear not delivered Email tracking does not consider a communication as “delivered” if the “sent” timestamp is greater than (more in the future) than the delivered timestamp. This makes the communication look like it never got to the recipient even though it did. We should not rely on the dates when transitioning from sent to delivered. We made a change in the message queue event service record events function to properly track the transitions. | |
| 19 | Defect | Delete LPI leaves orphaned archived task instances When a LPI is deleted we leave behind archived task instances in random instances, which were preventing future deletions for users and throwing an error. We resolved this issue so we do not impact future deletion attempts. | |