Bugs Resolved
|
Redmine Ticket # |
Zendesk Ticket # |
Detail
|
|
18100 |
2071 |
We have changed the error message in the Personal Details section when the driving licence number does not match the data in one or more of the fields against which it is validated: Last Name, First Name, Middle Name, DOB and Gender. This will now display as, "DL number is inconsistent with personal details." We have found this to be a necessary change because a number of applicants have correctly entered their DL number but were unable to proceed because of a mistake in their personal details. |
|
17971 |
2042 |
One client experienced a problem after "Rebuild Views" was initiated whereby m_target_person_candidates view was missing in their Analytics database. We have created a fix so that this will not occur again. |
|
17959 |
2025 |
We have done some work to improve the way ALX monitors and notifies when emails have not been successfully sent. We have added a new history item to record ALX default notification backend failures. |
|
17776 |
None |
We have corrected the misspelling of "Driving License" in the Criminal Records Check criteria. It is now using the UK spelling and will display as "Driving Licence". |
|
17445 |
1920 |
We have fixed an issue where the Role Permission "Hide Sequencer Notes" was failing to hide the criteria sequencer notes. In future when this permission is enabled both criteria and level sequencer notes will be hidden. |
|
17176 |
1843 |
We have fixed an issue whereby the patron merge fields were not populating in a document generated in a sequence and attached to a send message actor. We have also fixed the <<patron.signature>> merge field which was failing to merge in any area of the system. These merge fields will now correctly populate from the appropriate system user account details. |
|
17175 |
1843 |
We have fixed an issue whereby the patron merge fields were not populating in criteria "Notes to Display to Target". These merge fields will now correctly populate from the appropriate system user account details. |
|
17174 |
1843 |
We have fixed an issue whereby patron merge fields were failing to populate in a Send Message actor when the feature "Copy to Patron" was enabled. Patron merge fields will now populate from the appropriate system user account whether this feature is used or not. |
|
17173 |
1843 |
Fix to ensure that patron merge fields successfully populate data in all message templates. |
|
15784 |
1541 |
Fix to prevent target fields being duplicated when a dynamic form is copied. In addition, this ticket has fixed an issue where a copied dynamic form could not be downloaded. In future target fields will not be duplicated when a form is copied and a copied create only form will be able to be downloaded a expected. |
|
15780 |
2057 |
We have fixed an issue where new target fields where added to a dynamic form but these fields where not available for selection on the form. Fields added to a target group will now be immediately available for selection on a dynamic form for that target group. |
|
11824 |
1768 |
The ability to create a zip file from selected files in the Document Store was broken. We have fixed this so that a zip file can now be created when two or more document store files are selected. |
Features Introduced
|
Redmine Ticket # |
Zendesk Ticket # |
Detail |
|
17911 |
n/a |
We are introducing a new field type, JSON. It will be available for all target types. JSON objects can be saved to this field type which originate from an API call, dynamic form submission or from a variable. Keys from the JSON object will be able to be merged into a send message actor, document template and other system generated templates. |
|
17888 |
None |
We have made a change to the Criminal Records Check criteria set up to allow client dev environments to connect to GB Group's UAT environment and live systems to to connect to their live environment at https://gbg.onlinedisclosures.co.uk. The new setting can be found in the "Configure Provider" section in the store. You do not need to know the url but simply select the correct radio button, UAT or LIVE. |
|
17822 |
None |
We have increased the number of areas within an API call which will support the use of merge fields. These comprise Authentication = Basic Auth Login and Pass; Authentication = OAuth2 Client ID and Client Secret and for Authentication = HMAC Client Api Key and Client Api Secret. In future, the user can either provide a static value in the field or use a merge field such as a variable merge <<variable.test>>. |
|
17785 |
n/a |
We are removing the feature called "Allow Saving Target Records Without Mandatory Fields Completed But Don't Process" on the create/edit target group pages. It has not been found useful so is deemed redundant. |
|
17757 |
We are hiding the "Allow Overwriting" feature within the DRAAv2 criteria response type. This means that it will not be available as an option when new criteria of this type are created. However, for existing criteria where this option has been selected it will continue to work as before. |
|
|
17718 |
We are removing the "POP3" protocol option from the target import set-up. |
Comments
0 comments
Please sign in to leave a comment.