Production deployment: July 19, 2023

GovCloud deployment:  July 25, 2023

• Transaction consumption reports - Transaction consumption reports provide administrators with the visibility to better understand transaction consumption patterns for their organization. Admins can create dedicated reports to track transaction consumption with four different charts:
  
  • Transaction volume trend
  • Transaction by sender
  • Transaction by group
  • Transaction by workflow 

• New Setting Activity Audit to review the activities of administrators - A new report type that provides an audit log that helps to ensure continued compliance, safeguarding against any inappropriate changes, and auditing suspicious behavior within your organization.
  As an administrator, you have complete visibility into the setting changes made to the settings to the users, groups, or account (Depending on the user authority level). You can filter the audit log based on the setting name, the actor that made the change, or the target of the change (name, user, or group). Then, view and export these reports for further analysis. Account admins can view logs across all groups. Group admins can only view the audit logs for the groups in which they have authority.

• Improved details in data exports to properly reflect recipient replacement events - New data export columns have been added to better represent when recipients are changed during a transaction's signature process. The new columns are:
  • Recipient Status
  • Recipient Signed
  • Recipient Change Reason
  • Recipient Change Date

• Audit report logging of enforced authentication challenges - Customers using the Enforce identity authentication feature (on the Bio-Pharma Settings tab) with Phone based authentication will have each authentication event explicitly logged in the audit report. The new audit report events include the stage at which the authentication was captured (opening the agreement, applying a signature, and selecting the Click to Sign button) and the type of authentication used. (Phone authentication is the only method supported in this release. Acrobat Sign authentication is scheduled to be included in the August 2023 release.)
  The activity list also reflects each authentication (albeit in a shorter format).

• Web form support for enforced identity authentication - Web forms now respect the Enforce identity authentication settings, allowing for signature compliance with regulations such as CFR 21 part 11, and completely logging the signature events in the audit log (as described below).
  Additionally, Acrobat Sign authentication has been added as an authentication method, providing web forms with the detailed signature logging that supports many compliance requirements.
  

• Organizational address book integrated with LDAP or Active Directory -  Customers that manage their users in the Adobe Admin Console can link their LDAP or Active Directory to import an organizational address book for all users in the account. This allows users to type in the name or email of any person in their company LDAP/AD and have that party sorted into the auto-generated list of contacts. Organizational contacts (derived from the organization LDAP/AD) are listed separately from personal contacts (derived from any email address to which the user has sent an agreement).

• Reusable recipient groups for the Custom Workflow Designer - Persistent recipient groups can be created at the user, group, and account levels for use when building Custom Send Workflows.

• New user provisioning report to help resolve user creation issues -  Accounts that manage their users in the Adobe Admin Console have a new user provisioning report available on a new Pending page under the Users tab. This is particularly useful for accounts that move users from multiple existing Adobe Admin Console organizations (perhaps in different environments) to one enterprise organization. To filter active users from users that have not yet completed their activation in the new organization, the Users tab has been divided into two sections:
  • Entitled - Users that are appropriately provisioned and able to use Acrobat Sign. This page is identical to the previous Users page with all of the same functionality.
    
  • Pending - Users who are not fully entitled yet require some action or assistance.  

• Improved granularity for permissions to edit group-level settings - Account-level administrators now have tab-level granularity for allowing the editing of group-level permissions. Group-level administrators are provided a clear message of their restricted access at the top of their group pages when the authority to edit is disabled.

• New Trust Service Provider (TSP) - New providers are being added to expand the international availability of the digital signature solution. New in this release:
  
  • Certinomis

• Select how the attached files are named when added to emails - Administrators at the account and group levels can now dictate how the files attached to email notifications are named. File names are influenced by the setting Merge multiple documents into one document after signing, which delivers either one attachment with all files merged or separately attached files with their individual names. The options are:
  • Agreement Name:
    •  When all files are merged - One file that is named per the agreement name. e.g., Service Contract 2023
      
    • When files are separated - One file is attached per uploaded file. Each file uses the agreement name with an appended enumerator. e.g., Service Contract 2023 (part 1), Service Contract 2023 (part 2), Service Contract 2023 (part 3)
  • File Name
    
    • When all files are merged - One file with the name derived from the first uploaded file.
      
    • When files are separated - One file is attached per uploaded file. Each attachment retains the original file name regardless of the source (template, uploaded agreement document, transient document, recipient attachment).
  • Hybrid 
    • When all files are merged - One file that is named per the agreement name.
      
    • When files are separated - One file is attached per uploaded file, with each attachment retaining the original file name.

To access the controls, navigate to Account Settings > Global Settings > Files attached to email will be named as:

• Unshare agreements - Shared agreements can be unshared by the originator of the agreement or any participant that may have created a share to some other party. Unsharing with any party automatically unshares the agreement with all downstream parties, pruning the entire sharing branch.

• Custom Send Workflow interface will be enabled for all users - All accounts that have enabled Custom Send Workflows for their administrators have been enabled with workflow designer access for all users. Users can access the workflow designer through the Workflows tab in the top navigation bar and the Create reusable workflows tile on the Home page. Users only have the authority to create workflows for their personal use until an administrator explicitly enables the option to share workflows in the admin menu.
  Administrators that would like to suppress access to the workflow designer for users can do so in the Global Settings under the Custom Send Workflow section:

• The User tab has split into two tables for Admin Console users - Accounts that manage their users in the Adobe Admin Console have their Users tab split into two pages:
  • Enabled - This page holds a table of all users that have been successfully created in the Acrobat Sign environment and who should be able to use the service without issue. This page is equivalent to the previous Users tab with all of the same functionality.
  • Pending - This page holds the users that have been added to the user profile in the Admin Console but haven't successfully converted into a functional user in the Acrobat Sign system. 

• Improved Acrobat Sign Authentication flow - The Acrobat Sign Authentication method has been improved to reduce the complexity and number of steps for signers. The recipient's email is imported into the Adobe authentication system to determine if the user is a known entity, eliminating multiple screens/clicks and providing a cleaner path to authentication. The recipient is prompted to provide a password if the email already exists. The user is automatically directed to create an account if the email does not exist.

• Support for up to 10 digital signatures per recipient - The limitation of one digital signature per recipient has been improved for cloud-based signatures to allow for up to 10 digital signature fields to be placed per recipient. (Aadhaar and Singpass are not supported)
  

• The new Reports environment loads by default when opening the page - The default version of the Reports page has been changed to load the new reporting environment when users first open the interface. Users retain the option to switch back to the classic environment as needed.

• Before the July 2023 release, an agreement sent using a custom send workflow would not honor the authentication methods set at the account and group level. A sender could change the default authentication method for the signer even though the account/group settings disallowed it. The July release corrected this behavior and made it consistent with the Send page, which requires the sender to use the default authentication method if the account/group setting does not allow changing the default authentication method. 

For example, if the default authentication method for internal signers is Email, and the option Allow senders to change the default authentication method isn't enabled, senders will be prevented from sending the agreement with any authentication methods other than Email. This is the correct behavior and aligns with the experience on the Send page.

Mobile application updates

• Option for push notifications on the iOS platform - Accounts that manage their users in the Adobe Admin Console can enable push notifications for users with the Acrobat Sign for iOS app installed on their mobile devices. Active push notifications update recipients that new agreements await their attention, and senders are notified of signed and completed agreements. Individual users can opt to disable push notifications in their device settings.
  This feature will be available to users on iOS v15+ in the 3.29 release on the Apple App Store in early August.
  

Integrations

Acrobat Sign for Veeva Vault is being upgraded with the following:

• Updated branding - The Adobe Sign branding has been updated to Adobe Acrobat Sign to align with the current branding of the service. As part of this brand change, all objects in the Veeva Vault integration have been updated to Adobe Acrobat Sign. 
•  Current document version assurance - Given that Veeva Vault allows multiple versions of a document to persist, the updated Acrobat Sign for Veeva Vault installation will restrict users to attach only the most current version.