Release 3.58.0 - 05 Jun - 06 Jun 2019

Fix for issue where some targets whose email notifications had been disabled still received criteria related messages.

Fix for issue where system user is not able to delete unwanted multi-select options when editing a criteria.

Fix for issue where a grouped level which included several
Document Generation criteria response types was processing too slowly. Several system delays have been removed in order to considerably speed up processing.

Amendment to the message which is displayed when a dynamic form is used to create an incomplete target ie one which does not have all mandatory fields completed. This message pop up will now say, “We noticed that you haven't completed some mandatory fields. That's OK, we can save your data and you can return to complete this later, but we can't process anything until this is completed.”

Fix for issue where Patron and Creation Date target fields should not be enabled for selection of Required or Unique values.

In our last release (3.57.0) we introduced two new criteria response types - Document Generation v2 and Document Signature. We have changed some of the logic to fix the following when a document is signed by several users using several Document Signature Criteria:

- consecutive signatories do not see previous signatures when
signing documents - there is no place where a System User or Target can view or download a copy of the document with all signatures applied

- System Users can view document copies via "View Response" action in the Dashboard. However each criteria shows a copy of the document with a signature from that Criteria

- Targets also have multiple copies of the document, each with a single signature The correct behaviour which has now been applied, for example, when 3 individuals are required to sign a document is as follows:

1. System User will see 3 Document Signature Criteria for the given Target in the Dashboard. When viewing the response for any of them he will see the document (pdf) with all the signatures applied up to this point in chronological order. ie Criteria 1 shows signature 1; Criteria 2 shows signatures 1 and 2; Criteria 3 shows signatures 1, 2, and 3, etc.

2. Target will see (in Portal Document List) only those copies that were checked in the Document Signature Criteria as "visible to target".

3. The second signatory will see the first signature when signing the document. The third one will see two previous signatures, etc.

Fix for isolated issue reported by one client where New Criteria
Action Required and Criteria Completed notifications were not sent. 

We have improved the Document Pack feature so that it will include screenshots taken as part of the Webcheck criteria response type.
Please note: as you will be aware a screenshot returned in a
webcheck is watermarked with the date/time stamp of when it was taken. If your document pack setup includes "Watermark - Yes" the webcheck screenshot will have a second watermark applied showing when the document pack was generated.

We have added a feature whereby system users can define the
name to be used for their signature for online signing. For instance, if in their user account their first and last names are Robert Smith the system previously would expect them to sign documents as "Robert Smith". They can now choose to sign, for example, as Bob Smith or B M Smith. A new field has been added to the user account for this purpose.

We have added a Message Dashboard link to the main Dashboard under each person type target. In this first phase this will handle outgoing messages (sent from the dashboard) and any replies. Emails to targets which originate from Send Message Actors in a sequence or from Message response type criteria will not be shown in the message dashboard. Please see our Knowledgebase article for more information.

We have enhanced a recently released feature which allows
targets to be saved despite their record not having all mandatory fields completed. The enhancement takes into account the fact that a number of incomplete targets may become complete if the target group is edited with the removal of the mandatory requirement on some fields. If target records are updated to completed and there are sequences which commence on the update of targets these sequences will run. This could place a heavy load on the system which may affect performance. When a target group is edited in this way, the system user will now see a warning message which shows
the number of targets affected so that a judgement can be made to either process now or abort this update until a more convenient time.

We have identified a single instance in which an ALX customer
had misconfigured a message notification template (they had
copied and pasted the content from the single message field to
the grouped message field in their expiry notification template).
This removed the repeat mechanism which allows several
expiries to be notified daily or weekly as set in Reminders & Notifications. As a result, the messages were scheduled but
could not be sent preventing subsequent notifications from
being actioned. To avoid a misconfiguration related problem of
this kind in future we have put in place a new feature to ensure
unaffected messages can still be processed. For a future
release we will also add an error warning in the event that the
repeat mechanism is removed from a grouped message field.