Release date: EMEA - 18th December 2019
America - 19th December 2019
Bugs Resolved
| Redmine# | Kayako/Zendesk# | Detail | Related KB |
| 14075 | 1092, 1090, 1139, 1169, 1191, 1503 |
Previously when the email backend was not able to send a message because for instance it was too big, ALX would send constant backend failure messages. We have changed this so that the sending will be tried only 3 times every 15 minutes where there is a connection error and not at all for an authorisation error or when incorrect content is detected. System event history will be updated with the error details in the notes field and the failed email message will have a status of "Cancelled" in the Outgoing Messages list. |
n/a |
| 14200 | n/a | Fix to document pack content so that only approved documents included. | n/a |
| 14383 | n/a | Fix to ensure that the correct New Action or Reject/Ask Again notifications are sent to a person target type whether in a relationship or not when a criteria is reassigned or rejected/asked against respectively. | n/a |
| 14853 | 1275 | Fix for intermittent issue in ID Document criteria response type where a target experienced errors when clicking the complete button. | n/a |
| 15206 | n/a | Change to API call format for Previous Middle Name fields in Criminal Record Check criteria in order to avoid processing errors. | n/a |
| 15329 | 1406 | Investigation into issue reported by one client whereby it was thought that the manual reference chase reminder in DRAAv2 was going to the target instead of the patron. It was found that the confusion had occurred as a result of the same message template being used for both auto and manual requests. | n/a |
| 15492 | 1517 |
Fix to prevent target from seeing file uploaded to Unassigned by system user. We have removed the carousel from the target portal to ensure that his cannot occur again. |
n/a |
| 15591 |
n/a |
Fix for an issue where a system user had added an additional reference/referee in a DRAv2 criteria and the details were not showing on the dashboard until the process button had been clicked. | n/a |
| 15616 |
n/a |
Fix for issue using the online form in DRAAv2 response type where a user was not able to complete the criteria when the detail in one of the references was not agreed by the referee. | n/a |
| 15643 |
n/a |
Fix for issue where summary header in the email collector was not able to process emails when the From contained only the email address. Most servers use the full form for sender mailbox identification e.g. First Name, Last Name, Email Address. | n/a |
| 15674 |
1502 |
Fix for an issue where a system user was not able to view targets on the dashboard despite having the appropriate role permissions. | n/a |
| 15684 |
n/a |
Fix for issue where a DRAAv2 criteria activity type was set up with target supplied documents as required. When edited to be Not Required the target could not complete the criteria because the document was still required but there was no place to upload it, | n/a |
| 15686 | n/a | Fix for an issue in the DRAAv2 criteria where a target had entered information but not completed their data entry, effectively saving the response. When revisited the display had become distorted. | n/a |
| 15698 | 1516 | Fix for an issue where the watermark and document stamp where not added to a document pack despite the set-up having these features enabled in the store. | n/a |
| 15753 | n/a | Fix for an issue where the email collector assigned messages and attachments to the wrong targets. This was an isolated incidence experienced by one client. We have changed the way emails are processed by the collector to prevent this from re-occurring. | n/a |
| 15765 | n/a | Fix for an issue where a system user was able to complete a Target Field Completion criteria response type without fulfilling the mandatory field requirements. | n/a |
| 15799 | 1554 | Fix for an issue where there was inconsistency between the criteria completion date and the document stamp/watermark in a document pack. | n/a |
| 15803 | n/a | Related to 15643 above, this dix is to prevent the email collector failure notice from being sent on a loop when an email message cannot be processed. | n/a |
| 15833 | n/a | Date/time stamp alteration to take into account end of British Summer Time. | n/a |
Features Introduced
| Redmine# | Kayako/Zendesk# | Detail | Related KB |
| 14893 | n/a |
We have increased the speed of API v2 Get Requests in order that records can be fetched at a much faster rate. |
n/a |
| 15159 | n/a | Following our successful audit by GB Group of the Criminal Record Check implementation, we have added two new trigger options: CRC State which allows you to use Clear, Non Clear and Withdrawn options CRC Approved with Yes and No options which allows you to reference whether a Non Clear disclosure has been accepted We have also added Merge fields specific to the Criminal Record Checks response type. Main details like First/Last Name, Gender, Date of Birth, CRC State and Notes saved during accepting or declining Disclosure. New merge fields can be found here: Target -? Person -? <name of Target Group> -> Criteria -> <name of CRC Criteria> -> Response -> Most Recent -> CRC Application. We have also added two new trigger options for a sequence trigger directly connected from a criteria: When Criteria State Changed When Response State Changed These will be particularly useful for referencing when for instance a webcheck has been processed. |
Knowledgebase will be updated shortly |
| 15263 | n/a | We have made changes to the approval and sign-off process once a disclosure has been processed and returned a result. A clear disclosure has been processed and returned a result. A clear disclosure will automatically approve and complete. A non-clear disclosure can be accepted or declined resulting in a final status of Pass (Non-clear, accepted) or Pass (Non-clear, declined). | Knowledgebase will be updated shortly |
| 15278 | n/a | There are two document routes in the Standard and Enhanced DBS which require ID verification by an external validation service. We have added an upload button to allow the system user to upload the result from this service. | Knowledgebase will be updated shortly |
| 15284 | n/a | We have changed the hint on Mother's Maiden Name in the Disclosure Scotland check to read, "Your Mother's Maiden Name (enter your earliest known surname if you are unsure)". | n/a |
| 15429 | n/a | If a system user creates a gap in the Date Range and Activity v2 criteria response type by editing date from/to and the gap is above the gap tolerance, we have added functionality which ensures that a new line is created. | Knowledgebase will be updated shortly |
| 15517 | n/a |
We have added the ability for a client to enter their office address in the Store set-up which will auto-populate the fields used for where the DBS paper certificate is to be sent. The applicant (target) will have the ability to change this if they wish. |
Knowledgebase will be updated shortly |
| 15727 |
n/a |
In the Date Range and Activity v2 criteria response type we have added the ability to specify text per activity type which will appear as a sub-mask in the Detail field where a target enters their occupational history or other data. | Knowledgebase will be updated shortly |
| 15793 |
n/a |
For both Standard and Enhanced DBS we have extended the validation for Phone number available in the Personal Details section in order to avoid unnecessary processing errors. | n/a |
| 15802 |
n/a |
We have changed the email header in the email collector so that the From will show First Name, Last Name and Email address. | n/a |
Hotfixes rolled out
3.63.1
| Redmine# | Kayako/Zendesk# | Detail | Related KB |
| 15494 | n/a |
In the DRAAv2 criteria response type we have added the ability for a system user to save supporting evidence documents supplied by the target either together with a reference or in place of a reference when one cannot be obtained. When this action is taken the supporting evidence document will already be marked as "CHECKED" and the user can complete the criteria without looking at the document again. These documents will be present in the document pack if one is generated which includes the criteria. |
Article will be updated |
| 14589 | n/a | We have changed the functionality which asks a target to provide supporting evidence documents in the DRAAv2 criteria. It is now clearer when these documents are required or optional. | Article will be updated |
| 15653 | n/a | We have amended the instructions in the information box on a DRAAv2 criteria which describes the number or period of time for expected entries and gap allowances. This is intended to make the requirements clearer to the target. | Article will be updated |
| 15647 | n/a | We have done a lot of development on our DRAAv2 criteria response type. This bug was found and fixed by our QA team immediately following the 3.63.0 release. It is a fix for a broken page when DRAAv2 criteria entry was rejected/asked again. | n/a |
Comments
0 comments
Please sign in to leave a comment.