Skip to content Skip to main navigation Skip to footer

Package Update Release Notes

When upgrading a managed package, some components such as page layouts and picklist values are not updated automatically and instead must be updated manually by the user. To determine whether a specific component is updated automatically during a package upgrade, click on the specific component listed in the “Supported Components in Managed Packages” section of this article: Components Available in Managed Packages.

Package 3.3

Required action for existing customers who upgrade: Add “Disable Default Signature Page” and  “Email BCC” fields to the eSign Doc page.

  • Add BCC to signature preview page: The new field “Email BCC” has been added to the eSign Document object. Existing customers need to add Email BCC field to the eSign Doc page layout.
  • Added CC option for Signed Document Notification: Sends the PDF signed copy to cc’d emails specified in the Email Action Settings section of the Document Action.
  • Remove default signature page if merging signatures into generated document: Check the “Disable Default Signature Page” field on eSign Doc page to remove the default signature page that is appended to the signed document. Existing customers need to add “Disable Default Signature Page” field to the eSign Doc page layout.
  • Additional Supported Merge fields : Merge fields from the current user related to the “Email Template Preview” button, to add fields related to current user. We support Owner, CreatedBy and LastModifiedDate. See merge fields listed below:
    • {!esign__Document__c.Owner.Email}
    • {!esign__Document__c.CreatedBy.Name}
    • {!esign__Document__c.LastModifiedBy.Id}

Package 2.8

  • To use on mobile, users must first download the Salesforce  app and login to their org.
  • If using Opero Signature 2.8 with Opero Documents, user must install Opero Documents 3.7 version or greater.

Package 2.3

  • We have converted all Workflows to Flow. Existing customers who upgrade will need to deactivate the following workflows:
    • Auto Counter Sign (logic moved to Apex trigger)
    • Counter Sign Required (logic moved to Apex trigger)
    • No Counter Sign Needed (logic moved to Apex trigger)
    • Document Counter Sign Required (logic moved to flow with same name)
    • Document Signed By Recipient (logic moved to flow with same name)
  • Improve Sign Now UI. The Sign Now UI has been updated to be more responsive. Detects screen size and if mobile or a small window then it uses the mobile version. 
  • Signature button image update for “Send for Signature to Signer 2” email template. Existing customers who upgrade must update the “Click Here to Sign” button image in the “Send for eSignature to Signer 2” email template if it is being used. To do this, go to Setup>Classic Email Templates>eSign Templates>select the “Send for eSignature to Signer 2” template. Click the “Edit HTML Version” button. Replace the old image url with this new image url: https://accept.today/Images/Email-Button.png as shown in the screenshots below. Similarly, any custom email templates that use the old image need to be updated by replacing the old url with the new url.

Package 1.96

We have added support for additional languages on our signature page.

  • Existing customers should add the following values to the Language__c picklist field:
    • Italian
    • Spanish
    • Dutch
    • Polish
    • Danish
    • For new customers this Language__c field will automatically be updated. The Language__c field we use if we want to translate fields on merged document.

Package 1.91

  • We have updated Opero Signature to prepare for the retirement of Salesforce platform API versions 21.0 thru 30.0. Opero Signature customers must upgrade to package version 1.85 or greater by June 1, 2023. Customers who do not upgrade by this date will no longer be able to use the app. Please see Salesforce Documentation for details: Salesforce Platform API Versions 21.0 through 30.0 Retirement
  • All customers using Opero Documents and Opero Signature together must upgrade both apps at the same time. Specifically, customers who install Opero Signature 1.85 version or greater must also install Opero Documents version 2.150 or greater and vice versa. 
  • Standard User Permission Set. We have added a custom permission set that includes the minimum permissions that a standard user (non-system administrator) would need in order to send a Google Document for signature. For more information see the Opero Signature Basic Configuration article: https://kb.opero.com/signature/knowledge-base/basic-configuration-getting-started/#set-user-permissions
  • Sign Now feature. New eSign action that allows users to generate a document and serve for in-person signing. Note that this feature can only be used with automation. It cannot be used with preview. The following Document Action fields must be populated: Email Template, Email To. For more information see the Opero Signature Basic Configuration article: https://kb.opero.com/signature/knowledge-base/using-opero-documents-with-opero-signature-for-full-automation/
    • Existing customers upgrading their signature package will need to create a new picklist value “Sign Now” (label) “Sign_Now” (API name). 
    • New customers installing for the first time do not need to create the picklist value.

Package 1.80

  • Security update to user permissions:
    • We now check field level security for the required fields for sending an esign doc such as the Encoded ID field on the eSign Doc object. This is an update to meet Salesforce security requirements. As a result, the user who sends the esign doc now needs edit permission specifically in their profile for all fields on the eSign Doc object.
  • Fixed issue related to witness signer feature.

Package 1.78

  • Lightning version of “Send Document” page
    • The Send Document page has been converted to Lightning Experience. 
    • Customize the Send Document page by adding the lookup fields included with the app (Opportunity, Account) or your own custom lookup, text, or picklist fields. To add your own fields, first create the field on the eSign Doc object. Next, go to the eSign Doc Field Sets (Setup>Object Manager>eSign Doc>Field Sets>Send Document Custom Fields). Drag your custom field from the “Send Document Custom Fields” box down to the field set box below. The Field Set allows you to modify the Send a Document page layout by adding fields or reordering how the fields are displayed on the layout.
    • The above information can also be found in our Basic Configuration article.

Package 1.66

  • Q2 App Release.

Package 1.60

Package 1.59

  • Redirect URL
    • We have added a field called “Sign Completion URL to the eSign Doc object, under the Technical Details section. Users can set a value in the Sign Completion URL field to redirect to a custom URL once the recipient signs the document. For more information, see this article:  About the eSign Doc Object.