Release date: 1 December 2018
Bugs Resolved
| Redmine # | Kayako # | Detail | Related KB |
| 12456 | n/a | The welcome email was not being sent to the first nominated user when a new instance of ALX was created because there were no backend email settings. This has been fixed so that the notification will be sent using ALX's email relay. | n/a |
| 12630 | n/a |
The patron field was not updating on the dashboard following |
n/a |
| 12670 | n/a |
Fix for problem where the "Due Within" filter on the dashboard was obscured. |
n/a |
| 12688 | n/a | From the dashboard you can view messages sent by the target via the "Contact the Admin Team" in specific criteria. Clicking View will take you to the criteria and the message will display. However, this was only working if you were on the correct target group tab. If you clicked View when on another target group tab the target group would change but the target, level and criteria did not expand to display the message. This has been fixed so that a message will be displayed correctly irrespective of the target group tab currently selected. |
n/a |
| 12696 | 2820 | The ability to move notes on sequence triggers has been re-instated. These are notes created by adding text to the label field in Properties on a trigger. The note can now be moved right off the trigger and placed anyway on the blue background. | n/a |
| 12750 | n/a | Fix for 500 error when clicking the rotate icon on a file uploaded to a criteria via the carousel. The file will now rotate as expected. | n/a |
| 12755 | 3216 |
Uploading a PowerPoint file into a document field via a dynamic form was causing an error, "API Key is Null". This has been fixed so that PowerPoint files can be successfully uploaded via a dynamic form. In addition, we have changed this misleading error message to the following: "Oops something went wrong. Please try again later." |
n/a |
| 12812 | n/a |
Fix to ensure that newly created builds have missing database table loginurl_key. |
n/a |
| 12840 | n/a |
We recently improved the system message displayed when a |
n/a |
| 12871 | n/a | We have fixed an issue whereby fields that had been created and added on Target Groups in a dev instance and subsequently migrated across to the live environment were not appearing in any view of the data analytics. | n/a |
| 12915 | 3224 | We have fixed an issue whereby image files uploaded to the signature field of a system user account were not remaining when the account was saved. |
n/a |
| 12926 | 3234 | Fix for an issue with the Target Import settings in Step 2. When clicking 'Next Step' from the Step 2 there was a 500 error displayed and a user was not able to continue with the Target Import settings. | n/a |
Features Introduced
| Redmine # |
Kayako # | Detail | Related KB |
| 12733 | n/a | We have added further optimisation to the Dashboard to increase its loading speed. | n/a |
| 12769 | n/a | We have improved security through limiting access to data by adding extra options within the "Configure Fields" area of a dynamic form. The user is now able to set which roles are allowed full lookup access per lookup field and restrictions can be applied per lookup field. In order to achieve this we are moving this config from the "Edit form settings" page to the "Configure fields" page. Please check your dynamic form "Configure fields" pages following the release to ensure that all settings are correct. |
Click Here |
| 12783 | n/a |
We have created the following new criteria response types to allow strong typing of data: |
Hotfixes rolled out
| Redmine # | Kayako # | Detail | Related KB |
| 12843 | 3186 | 'On demand' document packs weren't being generated correctly when there were levels without any attachments to include - this caused issues with the sorting of levels and criteria which had been introduced in release-3.50.0. This has been fixed. |
n/a |
| 12685 | 3217, 3218, 3221, 3222 | This release will fix two issues: 1. Two requests were being sent for criteria completion when using the “process level” feature. One of these caused a 500 error. Now only one request will be sent. 2. The error message which is shown when a criteria response type is changed while using “process level” has been changed to the following: “An error has occurred. One of these criteria’s response types might have changed. Please try again in a while.” The error is valid but we hope this description is more informative for the user. |
n/a |
Comments
0 comments
Please sign in to leave a comment.