Skip to content Skip to main navigation Skip to footer

Package 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 1.30

Transaction fee

We have added a feature that allows you to charge a transaction fee for a payment depending on the payment method selected. The transaction fee can be a percentage of the total amount and/or a flat fee. See Basic Configuration article for more detail. Updating customers will need to update the page layouts for the following objects:

  • Payment Method page layout: Transaction Fee Charged, Transaction Fee Flat , Transaction Fee Description
  • Invoice page layout: Transaction Fee Charged

New Fields on Payment Customer & Invoice objects

  • opay__Additional_Billing_Email__c (email) & opay__Additional_Billing_Email_2__c (email): Two new email fields on the Payment Customer Object.
  • opay__All_Billing_Emails__c (formula, text): New formula field on Payment Customer object that merges the Billing Contact Email as well as any additional billing emails (Additional Billing Email, Additional Billing Email 2) separated by a comma.
  • opay__Payment_Customer_All_Billing_Emails__c (formula, text): Formula field that merges the value of Payment Customer.All Billing Emails
  • Existing customers installing a new package will need to do the following:
    • Update Invoice page layout: Remove opay__Additional_Billing_Emails__c and add opay__Payment_Customer_All_Billing_Emails__c
    • Update Payment Customer page layout: Remove opay__Old_Additional_Billing_Email__c and add opay__All_Additional_Billing_Emails__c , opay__Additional_Billing_Email__c, Additional_Billing_Email_2__c

Package 1.23

Error Handling

Whenever our app has a successful transaction processed it attempts to record the Payment record to Salesforce. We have added a feature to Opero Payments that allows users to see an error log when a payment transaction is unable to record to your Salesforce org. These records serve as a detailed error log to help you ensure that all payment records in your Salesforce org are accurate and up to date. Please see this article for more detail: Error Management

Package 1.14

Package published on AppExchange.