Release Notes Archive
v5.16 Release Notes
2/9/2023
Important Notes
The following items are considered breaking changes.
- PEP-5350 - Twilio Authy was Removed as an integration option as it was deprecated by Twilio. If your team utilizes Twilio Authy for Mobile Authentication, it will no longer work and will need to be updated to Twilio SMS or Verify.
- PEP-4090 - /ProntoNet/HealthCheck.aspx and /ProntoNet/ServiceHealthCheck.aspx will be removed in 2023. If your team utilizes these health checks, you will need to switch them to the new HealthCheck and ServiceHealthCheck endpoints. More information can be found in the developers guide: https://developers.alphatrust.com/getting-started/installation/health-status-monitoring.html.
New Features
- PEP-5928 - Added the ability to submit document form fields via the Bulk Launch feature. An example form field and CSV legend can be seen in the images below for more details.
- PEP-5497 - Switched all new transactions over to use the new Signing UI. The new Singing UI will automatically be used. To force the usage of the old signing UI, please reference the settings below. Note: the old signing UI will be removed in version 5.17.0.
Location of change: ProntoConfig.ini > PRONTO_MODE
Example setting: UseOldSigningUI=1 - PEP-5346 - Replaced the drop-in Analytics.htm functionality with official Google Tag Integration to support downstream Google Tag-enabled services (e.g. Google Analytics, etc.). Please see the image below for more details.
- PEP-5288 - Implemented ADFS, Azure, and Okta SSO for the new Signing UI. Please see the image below for more details.
- PEP-4977 - Created a new documentation website for developers to facilitate improved discovery and access to information. New Website: https://developers.alphatrust.com/. Note: Old website link will redirect to the new website.
- PEP-4096 - Made improvements to the HTML Document Type Signing UI to be more consistent with the pdf Signing UI.
- PEP-4090 - Added HealthCheck and ServiceHealthCheck endpoints to the new Public Signing UI. This gives administrators the ability to monitor individual service groups and receive alerts and action them independently. Please note that the /ProntoNet/HealthCheck.aspx and /ProntoNet/ServiceHealthCheck.aspx will be removed in 2023. More information can be found in the developers guide: https://developers.alphatrust.com/getting-started/installation/health-status-monitoring.html.
- PEP-3870 - Created a new modernized Signing UI to increase the overall performance of a user’s signing experience. The upgraded components will also reduce the frequency of PDF validation errors as a result.
Improvements
- PEP-5816 - Updated the documentation folder in on-prem installations. Removed documentation pdf’s and changed them to links to the developers guide. Developers Guide Website: https://developers.alphatrust.com/.
- PEP-5779 - Changed the max characters for Workflow Action URLs from 512 to 2083. Please reference the image below for more details.
- PEP-5350 - Removed Twilio Authy as an integration option as it was a form of second-factor authentication that has been deprecated by Twilio. Please reference the image below for more details.
- PEP-5297 - Added additional Search Filter options (Entity Type) in the Status Reports. Please see the image below for an example of the search filter Entity Type referenced.
- PEP-5278 - Made minor UI/UX improvements on the Trends and Completion Rates Reports. Please reference the images below for more details.
- PEP-5037 - Added LogRocket integration for the new Signing UI. Please reference the image below for more details.
- PEP-4830 - Removed Authentication Requirement for RemoteSign() API. It now supports Password, Registered, and None. Please view the Signing Remotely developers article below for more information. https://developers.alphatrust.com/documentation/tasks/signing-remotely.html.
Bug Fixes
- PEP-6012 - Fixed issue where when using the Bulk Launch feature, an email string could incorrectly have double quotations around the custom email message content. An example image of the CSV legend and issue can be seen below.
- PEP-6008 - Fixed issue where events were not being logged in the Event History for the new Signing UI. Increased logging for new Signing UI transactions.
- PEP-5944 - Fixed issue where the public launch page would not pull in custom branding or content from either the workflow or the group settings. Please see the settings referenced in the images below.
- PEP-5904 - Updated Aspose version to 22.11.0 to fix a transparency issue with Signature Chrome images.
- PEP-5815 - Fixed issue where a user would see an internal error message after uploading a Bulk Launch CSV file. The error message would appear due to the CSV file not containing the expected header row. Added validation to the Bulk Launch CSV file to ensure the file uploaded is valid file with the expected header row. Please see the image below of the Workflow setting referenced and an example CSV file header row for more details.
- PEP-5812 - Fixed issue where the Bulk Launch Status screen would hang and never update if a CSV file that only contained header row was used. Added CSV validation to ensure more than just a header row is in the CVS file used. Please see the images below of an example CSV with header row only and the Launch Status screen.
- PEP-5775 - Fixed a typo in the Notifications placeholders. Changed “Participant First Namee“ to “Participant First Name“. Please reference the image below for more details.
- PEP-5670 - Fixed issue where when using the Bulk Launch feature, the custom SendFromName and SendFromEmail would not be recognized and the system default SendFromName and SendFromEmail would be used. Please see the images below for an example of a SendFromName and SendFromEmail with Bulk Launch and the Workflow setting.
- PEP-5540 - Fixed issue where the Participant Setup and Final Email Notification toggle options such as In-Person, Final Email, and Send If Completed would not update correctly when sending a Sign & Send workflow. Please see the images below referencing to the affected Workflow type and toggles settings.
- PEP-5535 - Fixed issue where the Printed Name Block Data, relating to an Initials task, would appear as initials on the document when it should appear as a printed name. Please see the image below for more details.
- PEP-5488 - Fixed issue where another user could take ownership of a Web Form and move it to a Sub-Group by editing and saving the Web Form.
- PEP-5486 - Fixed issue where when calling GetWorkflowLaunchRules() the Sub Group API credentials could not find any shared Workflows when they belonged to the Parent Group. The call should have returned information on shared Workflows that were owned by the Parent Group or Sub Group. Please see the Workflow settings referenced in the images below.
- PEP-5483 - Fixed issue where when calling GetWorkflowLaunchRules() for a Workflow that does not exist, the API permission check would return the incorrect response. If no Workflow exists, the API call should return false with a message stating that the Workflow either doesn't exist or you don't have the correct permissions to access it.
- PEP-5442 - Fixed issue where when selecting Mobile Authentication integration for a participant the Integration Name dropdown would not populate with selectable integrations. This issue would specifically affect users that did not have permission to Integration Administration. Please see the image below for the referenced permission and more details.
- PEP-5440 - Fixed issue where some of the options buttons would not appear on the Workflows page for certain Workflows. This issue affected Workflows where the Created By user was deleted. All options will now render on the page but will be disabled if the current user is not allowed to click/use them. Please reference the image below for more details.
- PEP-5421 - Fixed issue where after reassigning a task to a new participant the Event Subscription for an Authentication Failed Event would not carry over to the reassigned participant. Please see the referenced setting in the image below.
- PEP-5240 - Fixed issue where phone number validation would not allow for + country codes. Please see the example phone number with a country code below for more details.
- PEP-4984 - Fixed issue where the Document Review workflow action on a task would show all documents in the participants workflow instead of only the document that the task was in. Please reference the example setting and image below for more details.
- PEP-4322 - Fixed issue where a user would be unable to un-check a DocForms dropdown option while in the task editor. Please see the image below for more details.
- PEP-3438 - Fixed issue where when a page in a PDF document is rotated 90 or 180 degrees, the calculation for the signature placement is off when its position is near search text. Please see the example signature image below.
- PEP-2979 - Fixed issue where the RemoteSign() API call would fail validation if the participant name wasn't set on creation. Please view the Signing Remotely developers article below for more information. https://developers.alphatrust.com/documentation/tasks/signing-remotely.html.
- PEP-2555 - Fixed issue where the User Password Change setting could be set to a negative number. Please see the image below for an example of the setting referenced.
- PEP-2554 - Fixed issue where the Document Retention setting could be set to a negative number. Please see the image below for an example of the setting referenced.
- PEP-1643 - Fixed issue where the password change field was no longer a number field when set to never. Please see the image below for an example of the setting referenced.
v5.16.8
7/12/2023
- PEP-6906 - Fixed issue where Participant metadata used to authentication via KBA wasn't properly overwriting the initial Participant metadata. Please see the images below for the settings referenced.
v5.16.7
6/1/2023
- PEP-6728 - Fixed issue where the toggle buttons within the Final Email Notifications section would not properly update for Send for Signature ad hoc Workflows. Please see the image below for additional information.
- PEP-6722 - Fixed issue where the signing UI could get hung indefinitely if it could not connect to an external resource. Added request timeout into the Control Panel and Signing UI to fix the resource issue.
- PEP-6721 - Fixed issue where the document service would report and log an error that was not an actual error. Updated the locking strategy so multiple services would not cause the error to be reported.
v5.16.6
5/18/2023
- PEP-6702 - Fixed issue where checkbox options could not be added to a Web Form. The default checkbox setting includes three options. The Add Options button would not add a new option as it should. Please see the checkbox and Web Form settings referenced below.
- PEP-6701 - Fixed issue where the CreateTransaction() API request would fail if it contained multiple actionable tasks with no placement information. The resulting error message seen stated “Can’t locate coordinates: Field ‘field_name’ not found”.
- PEP-6691 - Fixed issue where Carbon Copy and Delivery tasks would appear on the Process Explanation screen when they should not. Please see the image below for the Workflow Action settings and an example of the Process Explanation Screen.
- PEP-6685 - Fixed issue where transactions would be stuck in a pending status if a participant was assigned a Signature task followed by a Delivery task. Please see the image below for an example of the assigned tasks.
- PEP-6681 - Fixed issue where transaction emails would not load correctly within the Emails tab of the transaction details. Please see the image below for an example of the Emails tab referenced.
v5.16.5
5/4/2023
- PEP-6637 - Fixed issue where transactions could not be created when encrypted PDF/A documents were uploaded or used.
v5.16.4.1
4/24/2023
- PEP-6606 - Fixed issue where the vertical location would be shifted down by two pixels when placing the signature or signature data using the search text functionality, Offset Start Position, set to “Left” or “Right”. This fixes the specific settings referenced in addition to what was fixed in PEP-6572. Please see the image below for the settings referenced.
v5.16.4
4/20/2023
- PEP-6594 - Fixed issue in the new Signing UI which would cause performance issues on high-volume systems regarding the deletion of expired security tokens.
- PEP-6589 - Fixed issue where that can show up in Event Viewer under certain scenarios:
Document integrity check failed for DocumentID = ########### on SignatureID = ########### Document cannot be processed further - fatal error (SignDoc2-primary). - PEP-6572 - Fixed issue where the vertical location would be shifted down by two pixels when placing the signature or signature data using the search text functionality. Please see the image below for the settings referenced.
- PEP-6569 - Fixed issue where read-only form fields would be editable if the field name contained spaces. Please see an example and settings referenced in the images below.
- PEP-6567 - Removed X-Frame-Options from Sign App as it is not required.
- PEP-6560 - Fixed issue where transactions with only a delivery task, and the Document Access Windows set to any value other than zero, would show a “process cannot continue” error message instead of properly loading the exit page. Please see the images below for the referenced settings.
v5.16.3
4/6/2023
- PEP-6495 - Fixed issue where when attempting to verify an HTML document the user would receive an error message and the document was unable to be verified. Please reference the Verify Document feature in the image below.
- PEP-6481 - Fixed issue where accessing license information was causing an “Index was outside the bounds of the array” error.
- PEP-6480 - Fixed issue where if a user hit the session expiration limit, the timeout modal would not appear on screen. The timeout modal should appear on screen if the user exceeds the session expiration set. Please see the setting referenced in the image below.
- PEP-6302 - Fixed issue where phone numbers entered in Web Forms would lose their formatting when transferred onto a document. Please see the example image below of a phone number keeping it’s formatting after being entered into a Web Form.
- PEP-6056 - Fixed issue where accessing license information was causing an “An item with the same key has already been added.” error.
v5.16.2.2
4/12/2023
Note: Updates in version 5.16.2.2 are not included in version 5.16.3 but are included in version 5.16.4.
- PEP-6472 - Fixed issue where pages intermittently aren't saved to the database. Ensured that the signing process can continue if rows are missing from the Page table in the database.
v5.16.2.1
4/6/2023
- PEP-6550 - Fixed issue where a transaction would not be created successfully when the CreateTransaction() API call would reference the Document Source via the FilePath property.
v5.16.2
3/29/2023
- PEP-6424 - Fixed issue where when UseOldSigningUI was set to 1, you could not publicly launch workflows using ProntoNet. Please see the Signing UI location and public launch setting below.
Setting Location: ProntoConfig.ini > PRONTO_MODE - PEP-6382 - Fixed issue where when creating a Content or Notification set with a default language that is not English, the templates would not load correctly. Please see the example images below of a Content Set and templates using a non-English language as the default language.
- PEP-6363 - Fixed issue where server information could be identified via headers. Modified headers to remove server information.
- PEP-6353 - Fixed issue where if mobile authentication was set as the first method of authentication in a two-factor authentication workflow, the second authentication method would be ignored and or skipped as if it was not set. Please see the example image below for more information.
- PEP-6260 - Fixed issue where bulk launch was not allowing optional participants, if defined by another participant. Please see the example images below for the Participant and Workflow settings referenced.
- PEP-6249 - Fixed issue where the Offset Start Position drop-down should have a default value set to Left but was blank. Please see the image below for more details.
- PEP-6207 - Fixed issue where signatures using Registered Image Application Type would not have the Signature Chrome frame when it should. Please note the Signature Chrome setting and reference the images on a user’s Signature Image (Registered Image), signature settings, and example signature that should have the Signature Chrome below.
Setting Location: ProntoConfig.ini > PRONTO_MODE
Example setting: UseSignatureChrome=1
v5.16.1.5
3/27/2023
- PEP-6483 - Fixed issue where when utilizing the Search Text functionality the signature would not be placed in the correct location on a document. Please see the image below for the settings referenced.
v5.16.1.4
3/16/2023
- PEP-6431 - Fixed issue where some text characters weren't being found when using the search text signature placement method when creating transactions.
- PEP-6427 - Fixed issue where duplicate fields on documents were being incorrectly omitted from the DocForms page when signing.
- PEP-6419 - Fixed issue where when using FormField_InstanceOfField property for signature placement some signatures would not be placed on the document correctly.
v5.16.1.3
3/7/2023
- PEP-6413 - Fixed issue to accommodate documents containing signatures or all required text fields.
v5.16.1.2
3/3/2023
- PEP-6399 - Fixed issue where if a workflow had a no action task as the first item, the system would not properly move forward to complete the signing process and the user would get stuck on a blank screen.
- PEP-6397 - Fixed issue where a participant cancel comments would not properly save to the LastComment object in the database. Please see the cancel behavior setting referenced in the image below.
- PEP-6388 - Fixed issue where when uploading a document to a Workflow with all fields required, fields would not be imported properly. None of the fields would appear on the document during the signing process. The fields should have appeared on the document for the participants to enter information and complete the signing process.
- PEP-6383 - Fixed issue where when uploading a document to a Workflow, DigitalSignature fields were not being imported properly nor recognized when tagging the document.
v5.16.1.1
3/1/2023
- PEP-6387 - Fixed issue where upon completing a workflow with a custom Exit URL with capitals after the domain, the user would be incorrectly redirected to a lowercase URL instead. Example: "domain.com/Example" would be incorrectly changed to "domain.com/example". Please see the image below of the setting referenced.
- PEP-6381 - Fixed issue where comments were not properly rendering on Web Forms. Comments should be shown if entered. Please see the image below of examples of comments on a Web Form.
- PEP-6380 - Fixed issue where cancelling a transaction with a custom URL would not properly cancel nor redirect as expected.
v5.16.1
2/28/2023
- PEP-6347 - Fixed issue where upon cancelling users were not shown the options to choose to either cancel or suspend the transaction when the cancel behavior was set to "Prompt Participant to choose status". Please see the setting referenced in the image below.
- PEP-6329 - Fixed issue where if a participant has a custom exit URL set, any delivery task would not complete and stay in a Pending status. Please see the images below of the settings referenced.
- PEP-6303 - Fixed issue where DocForm fonts during signing were being ignored in the final Document. The font size in the DocForm will now properly match the font size as styled from the control panel. Please see the example font size setting for a textbox in the image below.
- PEP-6298 - Fixed issue where the Process Explanation screen would not display the correct tasks for each document in a transaction. Please see the referenced settings and example Process Explanation screen below.
- PEP-6286 - Fixed issue where when attempting to update Signature Block Data, changes would not save. When using the "Edit More Data Item Properties" modal to edit a Signature Block Data element the element will now properly update and save. Please see the example Printed Name Signature Block Data in the image below for more details.
- PEP-6280 - Fixed issue where the web form test pages API URLs were incorrect. Please see the image below of an example Web Form and test API URLs for more details.
- PEP-6278 - Fixed issue where if a participant cancels on an optional task, the participant is taken to the Exit page and the transaction status is changed to Pending. The Participant should be taken to the next task instead of the Exit page. Please see the optional task setting referenced in the image below.
- PEP-6277 - Fixed issue where if the cancel behavior is set to prompt for the cancellation reason, after the participant selects to cancel a task, the participant is not prompted for the cancellation reason and moves to a suspended status. The participant should be prompted for the cancellation reason if the cancel behavior is set to do so. Please see the cancel behavior setting referenced in the image below.
- PEP-6242 - Fixed issue where if the Document ID entered for document verification had one extra digit an error and success message would display simultaneously on screen. The error message should be the only message that appears on screen. Please see the example image below.
- PEP-6233 - Fixed issue where a Participant would see a blank screen with a logo after signing. The screen would go on to the correct next page, but the blank screen should not be seen. This was fixed by adding in a loading spinner and a prefetch on external exit screens to try and make the process more performant. Please see the example screen a Participant would see below.
- PEP-6215 - Fixed issue where signing sessions would not properly expire if you started another one.
- PEP-6156 - Fixed issue where outgoing email templates sometimes caused emails to be flagged as spam. Updated the email notifications to include proper HTML and a plain text alternative view in the sent emails.
- PEP-6093 - Fixed issue where when adding a PDF with a read-only DocForm field, the field would not be read-only and could be edited by the participant. Please see the example image below for more details.
v5.16.0.2
2/25/2023
- PEP-6355 - Fixed issue where the incorrect Participant IP address was being recorded and logged on the Audit Report.
v5.16.0.1
2/23/2023
- PEP-6336 - Fixed issue where when a participant defines another participants’ mobile authentication, it would not save the details correctly. Please see the setting referenced in the image below.