AutoBatch™ Plug-in for Adobe Acrobat.Release Notes | Adobe Acrobat, Reader

Looking for:

Adobe acrobat standard dc release notes free. Release Notes | Acrobat, Reader 

Click here to DOWNLOAD

     

- Adobe acrobat standard dc release notes free

 

Fix: The reporting code for generating the report CSV has been updated to properly capture only the data pertaining to the requesting admin. Fix: The workflow that governs navigating back to the Compose page has been updated to properly manage the Sender when their email value is masked by the Display Email value.

Fix: The email distribution process has been improved to evaluate duplicate recipient email values and will only deliver one copy of the final email for any one transaction.

This functionality was not designed functionality, and subsequent code was added that prevented this effect, creating what appeared to be a bug in the agreement message field.

Fix: A setting has been added to properly render a hyperlink in the email message. This setting is not accessible to customers and must be edited by support or the account success manager. The setting is enabled by default on enterprise and business tiers of service.

This caused agreements sent to the user to be affiliated with a user type that would prevent the agreements from being listed on their Manage page. Fix: Multiple code changes have been installed to prevent the issue from recurring, as well as to detect and warn about the conditions which can cause this type of problem. To include detecting the email address used for single-use pending users and automatically using the correct email address, preventing any new invalid users from being created when the other checks fail.

These fields were rendered as blank fields on the final PDF. Fix: An internal library has been updated to better annotate converted documents, ensuring only one digital signature field is applied and throwing the appropriate error when multiple fields are found the expected behavior. Fix: Users that were converted via the clean-up process have been returned to a Pending status.

Code has been added to prevent Pending users in claimed domains from being converted to the Created status. Fix: Validation is no longer applied to Summary: Signing a web form with only one name one contiguous string triggers a server error. Fix: Error handling has been applied to web forms that will manage the use case and supply a proper error message as appropriate. Fix: The file naming process when producing the final downloadable PDF document was updated to remove the previous file extension.

Improved Functionality. Improved reporting charts and data export - The Reports interface has been updated, allowing for: Preconfigured graphical reporting for: Agreements: Eleven reports tracking agreement activity by the sender, group, and workflow. Transaction consumption Expected in a future release : Four reports specifically tracking the volume of created agreements.

Data export reporting: Data exporting allows the user to define the output of a report CSV file by selecting the source report type, applying filters, and selecting the individual columns to be included. Improved Authoring environment available at the account and group level - The in-application authoring environment has an optional new experience with a new look and feel designed to enhance ad hoc agreement authoring up to two recipients. The new environment is currently only for the Send for Signature workflow and does not support Web forms, Send in Bulk, or library templates.

Enhancements include: Field placement that allows the author to select a field type and then click to place the field one or more times, allowing for much quicker placement of multiple fields of the same kind.

More explicit indications of the field content e. Properties for a selected field are listed in the left rail for better visibility and editing. Field height for subsequently placed fields automatically adopts the height of the last field to have modified the field size of the same field type. The font color, size, and style for subsequently placed fields automatically adopt the font properties of the last field to have the font properties modified spans field types that allow font modification.

Easier default value editing by simply clicking into the field and typing the default value. The improved authoring environment currently supports only: Placing fields when sending an agreement ad hoc authoring. Send in Bulk, Web Forms, and Template authoring are not yet supported. Up to two recipients. A limited number of fields the most common : Signature Initials Name the recipient's name imported from the signature Email the recipient's email as defined during the agreement composition Date of Signing inserted by the system when the signature is applied Text Number Date Checkbox Radio Buttons Currently unsupported elements: Agreements with more than two recipients Self Signing Web forms Send in Bulk Library templates Text tags Conditional fields Calculated fields Regular expression validation.

Define a recipient name at Send - Administrators at the account and group level can require that the recipient name be included with the recipient's email address during the agreement configuration by the sender. The included name value is imported to the signature panel when the recipient opens a signature field. The recipient may not edit the configured name value in any case. The sender of the agreement can edit the name values prior to the first signature being applied. Senders can replace the current recipient, providing a name-value for the new recipient.

Required name-values also enforced for web form counter-signers - When the feature is enabled, newly created web forms will also require a name-value for any configured counter-signers. Customize the contact information for signing password support - Customize the contact information provided to recipients when a signing password is used for signer identification.

The default experience embeds the email address of the sender. However, it may be more practical to redirect this type of support request to a centralized support team or a security contact that manages passwords. Customization can be configured at the Account and Group levels. This rebranding does not impact any features or functionality of the service e. Integration packages will update the branding with their next package update. This will not happen in the April release.

Signer authentication modernization - The signer authentication screens have been improved to no longer block recipients that have third-party cookies disabled when authenticating with password or SMS authentication methods. The experience has also been modernized to be responsive to different platforms.

Issue Description Summary: The message popup for canceling an invite and revoking access tokens is misaligned with the text. Fix: the messages have been updated to properly align the text.

The signature is visible during the signing process. The server-side date values converted from the now function aren't rendering properly, where the client-side values are. This results in an invalid date, which hides the field. Fix: The server-side evaluation has been enhanced to correctly convert and manage the numerical value of the date as passed from the now function. Fix: A setting has been added to explicitly manage the formatting of number fields authored in Acrobat.

This setting is disabled by default. Customers that have issues with number formatting when using forms created in Acrobat should contact the Support team and request to enable number field formatting for Acroforms.

Fix: The setting scope has been adjusted to the proper value. Fix: Interaction with the page after time out redirects to the login page. Fix: A new setting has been added to manage user profiles between Adobe systems. Fix: The mapping library has been updated to include the encoding type to properly render the Korean glyphs. Fix: Code has been added to strip admin rights from users that are migrated into a different account.

Fix: Additional code has been added to ensure that only "Created" users can be immediately activated. Fix: The code has been updated to properly load the task worker. Fix: Stamp signature strings are no longer tied to the user profile and update as all other fields do.

Fix: The country codes for Botswana, Bermuda, and Sudan have been added. Fix: Code has been added to handle an empty email value. However, annual limits do not apply if a transaction is Notarize managed. Fix: We now ignore the annual limit for the Notarize managed transaction type and display it on Send settings page.

Fix: Error checking has been added to capture and manage events where values are missing for migrated users. Fix: Values are now returned in lowercase characters in all cases.

Fix: Agreements containing a digital signature correctly contain a name property. For agreements created from multiple documents, the API will still return a single document for digitally signed agreements, and that document will now have the name listed as "multidoc.

Fix: A check has been added to manage a null value in a Currency field. Fix: Database scripts were updated to exclude single-use pending users from these lists. Fix: The orchestrator service was properly connected to the shard. Fix: The "Signing Reason" component has been updated to track the before and after name changes properly. This is due to a null pointer exception occurring on form creation because the second participant is not defined on form creation Fix: Added null pointer checks to resolve any exceptions in the java class.

Fix: Implicit delegation flows have been improved to act the same as an explicit delegation. Fix: The button and text have been altered to provide a 4. The indexing method finds the correct part for this stamp. But when there is a recipient group, this will give a random part from the group, which may not be the current signer. In such cases, the value is sometimes assigned as null and the signer part fails. Fix: Modified the indexing method to return the correct signer part of the participation group.

Fix: Updates to the rendering library now allow proper rendering of the glyphs, allowing the signing process to complete. Fix: Inactive users in a claimed domain no longer generate a single-use pending user. This resulted in a participation signature that was just a Hibernate proxy that if called would result in errors. This could happen during agreement event fetching since it looks at the scribble data. Fix: Added code to check if there is really a scribble before reading any values from it.

Updated the clean-up code to null out the signature content. Fix: The code for Curacao has been added to the method and is now available. Fix: The database was manually corrected. Fix: For users in UMG enabled accounts the group level setting will be selected over the user-level settings. Fix: Updated the dropdown field to read-only after filling the value Summary: If the wrong email address for a participant is used, but it is very similar to the correct one eg user email.

Fix: A more accurate method is in place to better manage user identities in these cases. Fix: The code has been updated to read the proper selected group settings for the Send in Bulk workflow. Fix: The manage page will reflect the value entered at the time of signing. Fix: The function to capture the email of a participant has been updated to take this context into account.

Fix: the managing method has been updated to include the retryAfter response. Fix: The link expiration function in conjunction with custom email templates has been modified to eliminate the error. Fix: The associated code has been updated to properly resolve the pointer issue. Since it doesn't have participation assigned this causes the agreement auto-cancellation project timeout approx.

Fix: We no longer create a document without participation. Fix: Modified the library method to ensure we don't filter the group for library documents if the user is the originator of the library template. Access to knowledge-based authentication for participant defined recipients on web forms Customers that build web forms that allow for multiple external participants can now use the knowledge-based authentication method for the additional participants.

Issue Description Summary: Agreements can not be created via custom workflows when Required recipient name is enabled. Customers can select from a wide array of authentication services and leverage the type of identity verification that best suits their demands.

Identity verification services include: Video Identity Verification services ID document identification Knowledge-based authentication services Identity information is optionally stored on the Signer Identity Report. Identity verification is priced separately and consumed per the vendor policy.

Authentication transactions are procured and billed directly from the IDP. Name values can be prepopulated through the API or through the Require recipient name when sending feature. Updates to the custom workflow designer - Updates to the custom workflow designer include: Users in Multiple Group awareness. Accounts that have UMG enabled allow: Group administrators can assign workflows to any group that they are an administrator of not only their primary group.

Group administrators can edit any workflow assigned to any group they are an administrator of. An update to the workflow scope control interface that defines which users can access the workflow. The array of radio buttons used to select an individual group has been changed to a single-select drop-down menu with the text label Selected Group. Improvements to the new authoring environment - The new authoring environment introduced in April has been updated to include: Support for up to 25 recipients.

New fields: Dropdown single-select Hyperlinks New Acrobat web accounts and free Acrobat users enable these features automatically. Option to disable the email tracking pixel - Enterprise tier accounts can request the support team to disable the tracking pixel embedded in the recipient "Review and Sign" email templates. Disabling the email pixel changes the trigger for the "Viewed" event: When the pixel is enabled , the "Viewed" event triggers when the email is opened.

When the pixel is disabled , the "Viewed" event triggers when the agreement is opened via the signing link. New accounts of all service levels created after the June date will have the pixel disabled by default. Disable hyperlinks embedded in signatures and initials - Enterprise tier accounts can request the support team to disable the embedded hyperlinks in signature and initial field objects which open the transaction verification page.

All accounts created after the June release have this linking disabled automatically. Accounts that exist before the June release will continue to see the legacy functionality. Disabling the hyperlinks is not retroactive to agreements completed before adjusting the setting. Once disabled, the embedded links can not be reenabled. Expanded the Audit Report events - The audit report has been improved to include several events that were previously only reflected on the activity log or embedded in report files.

Improvements include:. User settings override group settings. Group settings override account settings. Internal users are defined as users within the same Acrobat Sign account as the sender of the agreement. External users are defined as all users that are not members of the same Acrobat Sign account as the agreement sender. Access to knowledge-based authentication for participant-defined recipients on web forms - Customers that build web forms that allow for multiple external participants can now use the knowledge-based authentication method for the additional participants.

Web Forms no longer require third-party cookies to be enabled for signers - Accounts that use web forms no longer need to be concerned if their signers have third-party cookies enabled before applying their signature. Web forms now support cookieless signature activity. Expired signing links are limited to ten requests per hour - When a signing URL expires, the recipient can request a new URL up to ten times in a minute time window. A new URL will not be sent after the tenth request in the same minute window.

The ten signature requests exist in a rolling time window, meaning that each request has a minute timer. Updated External Archive interface - The external archive interface has been updated to challenge the administrator to enter the email address twice to ensure the correct email is configured and store the email as a clickable address object instead of a text string.

Updates to the Notarize integration - Improvements continue for the Notarize integration: The agreement expiration time is being shared with Notarize and will be honored by Notarize as part of their scheduling feature. The Notarize API key is now validated before the agreement is sent for notarization.

Update to the expiration date label in emails - The text identifying the expiration date in recipient emails has been updated to clarify that agreements can be signed until the expiration date.

Improved automatic form field detection limited deployment - Automatic form field detection has been improved to more accurately identify the type, size, number, and location of form fields to be placed. Only deployed on the NA4 environment after the June release. To be deployed on other environments in future releases. Trial accounts available to all markets - The Adobe Acrobat Sign Solutions trial is now available globally. Register for a day free business tier trial.

No credit card is needed. Issue Description Summary: PDF forms created in InDesign specify a value of "Off" for unchecked checkbox fields, which caused issues when the fields are editable by recipients.

Fix: The GovernmentID package has been updated with improved code to address this error. Fix: Database updated to correct the settings mismatch. Fix: Updates to the API to provide the correct reply to the signer when invoked from the Manage page. Fix: Updated the field parameters to allow the space for the full signature stamp.

Fix: Code has been added to bridge the gap between the legacy object and the modern functionality. Fix: Code has been added to properly manage a default value containing a single quote. Fix: Code has been updated to not check for prefill fields when modifying an active web form. Fix: Corrected the code to retrieve the correct value and publish that as the expiration date. Users must consent each time they authenticate Fix: Cookie consent selections and updates are being saved for the user.

Fix: The code has been updated to use the original title string instead of creating a new one during the conversion Summary: Some of the Group level Email Settings do not save when updated to override the account-level settings due to a failure to check the override value for those parameters.

Fix: Code has been updated to properly check the override value when group level settings are updated. Fix: Code has been added to ensure the field location is calculated properly with corrected coordinates. Fix: the code has been updated to properly suppress the Decline to sign options in the UI when recipients first load the agreement page. Fix: The tenantIDs are now properly updated in the executor threads when they are inherited from the scheduler.

Fix: Calculated expressions are cleaned before saving to document data XML. Fix: Group filtering has been updated to ensure that filters update when the user admin changes group authority. Fix: The combined lists are now sorted alphabetically numbers before alpha characters and case insensitive.

Fix: Field properties for automatically detected fields are not stored if they are not placed. Fix: The package for the Government ID function has been updated to resolve the root cause.

Fix: Newly created agreements commit the ID to the DB with the initial save of the agreement removing the need to update the ID at any time. Fix: The Save button is immediatly disabled upon saving a workflow, preventing the duplicate entry. Fix: Translation as been corrected. Fix: Improved the code to allow for deleting with the delete key. Fix: Code for the field value tables has been improved to better include the properties of prefill fields.

Fix: The roles have been added to the roles options. Fix: The code has been improved to manage this situation. Fix: Conditional visibility code has been tightened to ensure accurate display when conditions are met. Fix: Code has been added to manage a migration in progress when a new migration is executed.

Fix: Reporting scopes have been improved to account for disabled and hidden workflows. Fix: Added new authoring to the filter for shared access. Require recipient name at delegation - The feature to require the recipient name when sending a new agreement released in April has been improved to allow entering a recipient name at the time of delegation as well. Users can enter the recipient name when they click Delegate signing to another option on the signing page or using the delegate link in the email.

Form field tooltips support up to characters - The customizable tooltip option for all form fields has increased the number of characters allowed from to The upgraded search feature is scheduled to be deployed by tier of service over the second half of The documentation for the improved search functionality is available in the online help documentation. A link to the documentation is provided in the application by clicking the information icon next to the search field:.

Legal notices consolidated into one menu item on the e-sign page - The legal notifications on the recipient e-signing page have been collected into one Legal Notices menu item in the Options menu. Clickable message links on the e-sign and Manage page - Enterprise tier accounts that enable clickable links in their email templates will now see those links as clickable on the recipient's e-sign page as well as in the Manage page view of the agreement. Signature fields have updated their tooltips for better accessibility - Each of the signature field types has improved the tooltip to better identify the signature content required by the recipient.

Quarterly update Q : A scheduled update that includes functional improvements, new security updates, and previously released out-of-cycle patch updates. For Reader, these updates are sometimes available as full installers. Out-of-cycle patch OOC : An update targeted at security fixes. These noncumulative patch files may contain few functional updates with the intention to limit impact. Optional Update : An update targeted at a narrow set of functional fixes with limited impact. Adobe recommends that you apply these patches if you are seeing an impact by one of more of the functional fixes being delivered.

Note: Continuous releases, quarterly updates, out-of-cycle patches and optional updates can provide security enhancements. Adobe recommends that all updates and patches be applied when available. Legal Notices Online Privacy Policy. Release Notes Acrobat, Reader Search. Common questions about updates. Why should I update? Are updates free? Only new, major versions of Acrobat must be purchased. How long is the installation time?

Updates take only a few minutes to install. How do I change the update frequency or disable updates? How do admins and enterprise IT get more information? Acrobat and Acrobat Reader Continuous Track release notes. Jul 12, DC Jul Jun 14, DC Jun Apr 12, DC Apr Mar 07, DC Mar Jan 11, DC Jan Oct 12, DC Oct Sep 29, DC Sep Sep 14, DC Sep Jul 28, DC Jul Jul 13, DC Jul Jun 08, DC Jun May 11, DC May Apr 16, DC Apr Mar 10, DC Feb Feb 25, DC Feb Feb 22, DC Feb Feb 15, DC Feb Feb 09, DC Feb Dec 09, DC Dec Nov 23, DC Nov Nov 03, DC Nov Sep 24, DC Sep Aug 19, DC Aug Aug 11, DC Aug July 06, DC May Jun 02, DC May May 21, DC May May 12, DC May Mar 17, DC Mar Feb 11, DC Feb Acrobat and Acrobat Reader Classic Track release notes.

Jul 12, Apr 12, Mar 09, Jan 11, Oct 12, Sep 14, Jul 13, Jun 08, May 11, Feb 09, Dec 09, Nov 3, Aug 11, Mar 10, Nov 03, May 12, Mar 17,