Skip to content Skip to main navigation Skip to footer

Package Update Release Notes

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.