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 5.9

Action required for existing customers: The updated deadline to upgrade Opero Documents and re-authorize is July 15, 2024. Google has made new requirements for using their API. Opero Documents uses Google Drive to manage templates and generate documents. You must update Opero Documents app to the latest version in order to utilize the updated integration with Google. The deadline to update is July 15, 2024. Steps to update are listed below. In order to avoid any downtime, we recommend first testing in a sandbox before installing in production. If any questions, please reach out to support@opero.com.

Important note: With the Google API update, Drawings are no longer supported by Google and will result in a 500 error. If you have any templates that use Drawings, you will need to remove them from your template. As a workaround, take a screenshot of the Drawing, remove the Drawing from the template, and replace it with the screenshot/image. For more information, see our Error 500 article.

  • Install latest version of Opero Documents from the AppExchange: https://appexchange.salesforce.com/appxListingDetail?listingId=a0N3000000B5O5UEAV.
  • Customers using Opero Documents with Opero Signature will also need to install the latest version of Opero Signature from the AppExchange: https://appexchange.salesforce.com/appxListingDetail?listingId=a0N30000000q4LeEAI&channel=recommended
  • The authorizing user(s) will need to re-authorize their Google Drive by following the steps below. Specifically, if each user has authorized their individual Google Drive, they must re-authorize their Google Drive. If using the feature that allows the Administrator to authorize one Google Drive for all users, the Administrator will need to re-authorize their Google Drive.
  • Open the DocGen Configuration tab.
  • Verify that in the browser you’re logged into the Google Account that you intend to authorize and that it is the only Google account that you are logged into.
  • Click Grant Access to re-authorize the Google account you would like to use with Opero Documents.
  • You will be prompted to select an existing Google Drive account to use.
  • After installing the latest package and re-authorizing the app, no further action is required.

Other features included in this package:

  • Folder Id is now dynamic: Under Google Doc settings, the Folder Id field can now be either hardcoded or a merge field.

Package 5.4

  • Support for Lightning email Templates: Users can now use a Lightning Email Template when generating and emailing a document. First, create the Lightning email template (link). The on the document action, set the value of the Email Template field with the “use Id” or “use field” option. See Basic Configuration article for more detail.
  • Support for conditional section merge within a table. See Template Configuration Article for more information.
  • Support for formula fields with the Document Action Email BCC setting. See Basic Configuration article for more detail.

Package 4.9

Customers using Opero Documents with Opero Signature will also need to upgrade Opero Signature to package 2.9 or greater.

  • Added support for users to delete a document after merge where the Document Action is set to preview.
  • Added Email BCC to Signature Preview Page
    • Customers using Opero Documents with Opero Signature: The Email BCC URL param will not work if the customer does not have both Opero Documents 4.9 version and Opero Signature 3.3 installed.

Package 4.1

  • Action required for existing customers using Merge Additional Documents Feature: After upgrading, manually activate the OperoDocumentsAzureService remote site setting (Setup>Remote Site Settings>OperoDocumentsAzureService>select the “Active” checkbox). For security reasons, Salesforce automatically deactivates the remote site setting when upgrading a package. This action is required only once and will not be necessary for future upgrades.
  • Update to the Preview Document Enabled Feature: Page layout update for more space. 
  • Update to Merge URL Feature: The label of a merged URL can now be either hardcoded text or a merge field. Previously the Merge URL feature only supported a hardcoded text label. See Template Configuration article for more detail.

Package 3.1

  • Convert Edit Template Document Page to LWC.
    • We have converted the Edit Template Document Page to Lightning Web Component (LWC) for more modern styling and responsive design. 
  • Opero Documents Permission Sets. We have created the following permission sets to make it easier to manage permissions for Opero Documents users:
    • Opero Documents User Permissions: This permission set is appropriate for users who need to generate documents. 
    • Opero Documents Administrator Permissions: This permission set is appropriate for users who need to authorize the app and generate documents. 
    • See Basic Configuration article for more detail, including a list of the individual permissions included with each permission set.

Package 2.162

  • Option to to Remove Template only Document with PDF Merge Feature. When the “Delete Extra Generated Attachment” checkbox is selected, Opero Documents will automatically delete the initial generated document and only attach the pdf that contains both the merged document and additional documents. For more information, see PDF Merge Feature.

Package 2.160

  • Support Rich Text merge into table with filter for base and child. Note that the filter must be between the merge field and the “[HTML]” statement, e.g., {!Opportunity.r.OpportunityLineItems.rsdoc__Rich_Text_2__c[ProductCode=”GC1020″][HTML]}. For more detail, please see the following articles:

Package 2.157

  • Support for merging rich text fields from child object. We have added support for merging rich text fields from a child object into the body of the document.
    • If a field is rich text, the merge field should have “[HTML]” suffix. E.g. {!Opportunity.Rich_Text_Field__c[HTML]}. If you are using the Template Builder to merge Rich Text fields into your template, the [HTML] suffix will be added dynamically. Supports basic HTML: List, bold, italic, color, underline, font size. Does not support rich text images or two rich text merge fields in a single line. Instead, place each Rich Text merge field on its own line.
    • To merge rich text fields from child object, place the merge field into a table. After the field is merged, the table will be removed. Merged text will appear in the body of the generated document without a table.
    • See our Template Configuration article for more detail.

Package 2.153

  • A new Opero Documents package update is available on the AppExchange. Please note that 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. This requirement is due to a recent Opero Signature update that prepares for the retirement of Salesforce platform API versions 21.0 thru 30.0. Please see Opero Signature release notes for more information about the API update.
  • New custom button parameter. We have created the FolderId parameter that allows users to override the folder Id specified in the Document Action when using a custom button. For more details, please see the Opero Documents Basic Configuration article for more details.

Package 2.145

  • Update to ensure that the Salesforce update “Enable JsonAccess Annotation Validation” does not break document generation. Salesforce made this update available in Winter ’23 release and will enforce Winter ’24. After updating the package, no additional steps will be necessary. Existing customers with package versions older than 2.143 who enable JsonAccess Annotation Validation will no longer be able to generate documents.
  • New Template Builder Features
    • Support for HTML or Rich Text fields – Opero Documents now supports HTML or rich text fields for document generation. If a field is rich text, the merge field should have “[HTML]” suffix. E.g. {!Opportunity.Rich_Text_Field__c[HTML]}. If you are using the Template Builder to merge Rich Text fields into your template, the [HTML] suffix will be added dynamically. Supports basic HTML: List, bold, italic, color, underline, font size. Does not support rich text images or two rich text merge fields in a single line. Instead, place each Rich Text merge field on its own line. Support is for merging rich text fields directly into the body of the document.
    • TODAY() merge field – To merge the current date into a document, select the checkbox “Today Date” in the Template Builder. Copy/Paste the merge field code into your document. The merge field should look like this: {!{TODAY}}.
    • Merge URL Link with label into document – Select the field in the Template Builder that contains the link. Select checkbox, “Link”. Enter the label of the link in text field to the right of the checkbox. Copy/Paste merge field code into the template.
    • See Opero Documents Template Configuration article for details.
  • Email Additional To field on the Document Action now supports formula (text) fields in addition to text and email fields.

Package 2.141

  • Updates to enable Visualforce Javascript Remoting Enforcement. See Salesforce Documentation for more details. Existing customers with older package versions will not have issues if they choose not to upgrade. 

Package 2.131

  • Q2 App Release.
  • Opero Documents, Signature, Forms and Payments Integration – Our apps work together seamlessly to fully support your business processes.
    • Please note that you will need to install Opero Documents package 2.127 or later and Opero Signature 1.65 or later.
  • Updates to the Document Action Page – We have converted the Document Action page to a Lightning Web Component in order to make the UI experience of creating a Document Action easier and update to the modern Lightning Experience user interface. See below for a list of fields that have changed as part of this update.
    • Field To Update, Save File Id Field => Picklist which contains editable fields of the base object.
    • Email Template => Picklist which contains all email templates.
    • Email From Org Wide Address => Picklist which contains all org-wide email addresses.
    • Additional eSignature Field => Picklist which contains editable fields of the base object.
    • Parent Lookup Field Name => Picklist which contains editable fields of the base object.
    • Countersigned By => Picklist which contains editable fields of the base object.
    • Signer 2 Email Template => Picklist which contains all email templates.
  • Document Action Variables Updates – Users no longer need to update custom button code each time changes are made to the Document Action.
    • We have added a formula field on the Document Action called “Simple Button/Link Code” that creates the button code with just the Field Id and Document Action Id. When using this feature, users no longer need to update their custom button code. The app references the Document Action Id in the button code and then gets all the params from the Document Action record.
    • We have renamed the “Button/Link Code” formula field to “Customizable Button/Link Code”. This button code still contains all params. Buttons created with this code need to be updated each time changes are made to the Document Action.
    • Existing customer button codes will still be supported when updating the app and functionality will not be affected.

Package 2.127

  • The Document Action “Email From Org Wide Email Address” field now accepts a merged formula field in addition to a hardcoded Salesforce Id. See Basic Configuration article for more information.

Package 2.126

  • We have rebranded from A5 Apps to Opero and our suite of apps reflects this exciting new look.
  • The  default format of generated files is now Files. To use Documents, manually enable by going to Setup>Custom Settings>Opero Documents Settings>Manage>Select “Use Documents”.
  • Edit Google Document in Preview – We have updated our Preview feature to allow users to edit the Google Document in the document preview, then generate the document. The generated document will reflect any changes made in the document preview.

Package 2.121

  • Email Preview Option in Lightning Experience – We have created an email preview option in Lightning Experience that uses Lightning Email Composer to preview an email. Detailed information: Create Email Preview with Lightning Email Composer
  • Bulk Merge Images feature – This feature speeds up image merging for customers merging 3 or more images into their template. Detailed information: Template Configuration

Package 2.116

  • Record Id and Attachment Id saved on Document Request record – We have added the following fields on the Document Request object that are populated when a document is generated – regardless of whether it is generated manually or automatically. These fields allow customers to configure a Process Builder, Flow, or Apex on the Document Request object to copy the Attachment Id value when the status of the Document Record is “Complete”  to the base object if this value is needed anywhere else. Detailed information: Automate Document Generation.
    • Record Id – Id of the record that has initiated Document Request (e.g. Opportunity Id)
    • Attachment Id – After Document is created this will contain Id of the generated Attachment/File
    • Google Doc URL – After Document is created, this will contain URL of the generated Google Doc

Package 2.114

  • Download File and Delete Google Doc After Merge – Users can now set a Document Action to both download a file and delete a Google Doc after merge.
  • Update to DocGen Authorization Page – After installing the app, when users click the DocGen Configuration tab, only the Grant Access button will be enabled. This is to make it clear that the user is not authorized yet. Similarly, after clicking on the Grant Access button, the user will be redirected to the Google Drive authorization page and immediately after allowing access to the Google Drive, the Grant Access button will be disabled while the Revoke Access button will be enabled. This is to make it clear that the user authorization was successful.
  • Batch Mode – The Batch mode section on the Administrator VisualForce page has been reinstated in order to allow customers to manually enable Batch Mode in order to resolve Document Requests stuck in “New” status due to problems with guest site user permissions. Once enabled, the Batch Job will be scheduled and it will execute after every x minutes (number of minutes must be set in Document Settings>Batch Timeout field). For all other customers that don’t have problems with a Document Request stuck in “New” status, Batch mode on the Administrator VisualForce page must be disabled because their Batches are executed through the Document Request trigger.
  • eSign Preview Validation Rules
    • Validation rule on Document Action created to prevent saving a value to both the Signer 2 Required and Witness Required fields at the same time.
    • Validation rule on document Action created to prevent saving a record when a value is saved to the Witness Required or Signer 2 Required fields and Email template is blank.
  • Signer 2 Checkbox Field – New checkbox field (Signer 2 Required) has been added to the Document Action layout. If Signer2Required equals true, after creating the new document and redirecting to the Email preview page, Require Signer 2 dropdown will be set to “Yes” and Signer 2 NameSigner 2 Email, and Signer 2 Email Template will be merged to the on the preview page. 
  • Searchable Picklist – When selecting a Document Action from within the Generate Any Document Action button, you will see that we have replaced the combobox picklist from the Aura component with the searchable picklist Lightning Web Component.
  • Auto Email with Email Additional To – You can now auto send a document using the Email Additional To field instead of the Email To field. This feature allows you to auto email a document to an email address that is stored in a field. 

Package 2.109

  • Execute Any Document Action – You can now assign certain document action templates to a group and configure a default group within the custom button code to only show templates from a certain group when generating document. More details defined in this article.
  • Batch Mode – Batch Mode Automation improvements and changes to automation article. With this package update users no longer need to manually enable batch mode as it enabled already. The standard automation method is utilizing the Document Request custom object and more details defined in this automation article.
  • Related List in Related List – You can now merge an additional related list from a child object using this new feature.
  • Monthly Document Generation Limits – Update to monthly document generation limits. Limitation of 10,000 documents for 1-10 user licenses. Can see this article for more detail on limitations and pricing. In coordination with feature above, you will not be able to delete document request records used for automation as the document needs to exist in order for the app to know the monthly document count. You will be able to delete the Document Requests after the current month period is over.
  • App Authorization Fix – Fix of DocGen Configuration to save authorization token if you received bad request error when authorizing the app.

Package 2.101

  • Salesforce Security Regulations – Latest Salesforce security regulations with app users requires users to have at least read access to fields and objects in use with document generation. If users do not have proper access to fields in use, they may see an error message referring to inaccessible field.
  • Merge Additional PDFs – Package update also includes new feature to merge additional PDF documents into document generation per this article.
  • Conditional Section Merge Fix – Fixed feature issue with Google Apps Script for conditions when all the filtered records have the condition false.