Upgrade Guide for Unaric Payments

this guide explains how to manage and upgrade unaric payments in a salesforce sandbox use this guide if you are refreshing your salesforce sandbox upgrading unaric payments in sandbox before a production upgrade moving across multiple unaric payments versions checking whether version specific changes apply to your org prerequisites pre upgrade checklist use this checklist before making any changes identify your current unaric payments package version and the target version you want to install review release notes for every version in the upgrade path confirm whether your sandbox has been refreshed recently decide whether to reuse your existing unaric payments sandbox customer id or create a new one check whether any version specific upgrade considerations apply to your org at minimum, you should assess permissions and permission sets record types merchant group configuration multi merchant behaviour page layouts and object fields dashboards paypage behaviour psp connection setup any customisations tied to older object or field names confirm whether you are using merchant groups (upgrading from multi merchant), certinia or outbound payments for specific upgrade steps plan time for post upgrade validation and testing best practices always perform and test upgrades in sandbox first review all release notes between your current and target versions upgrade in manageable steps where possible complete the full testing checklist before promoting to production notify unaric payments support after each sandbox upgrade with your sandbox customer id your installed package version 1\ refresh your salesforce sandbox to learn how to refresh your sandbox, see docid 1rxvefnvfhiulwt 5sxfr for details on setting up the sandbox post refreshing, see docid\ b2pxtdaj92d 8txmbidqj reuse an existing sandbox customer id when you refresh your salesforce sandbox, you can either create a new unaric payments sandbox customer id or reuse an existing one reusing the existing customer id will preserve its sandbox configuration, including customised paypages merchant groups test payment service provider (psp) connections there is a 1 1 relationship between your salesforce sandbox org id and your unaric payments customer id if your sandbox org id changes as part of the refresh, this must be considered when managing the associated unaric payments sandbox setup 2\ upgrade unaric payments in sandbox for sandbox installations, ensure your installation url domain is test salesforce com instead of login salesforce com salesforce does not support package rollbacks for that reason, all upgrades should be completed and fully tested in sandbox before production there are two supported upgrade approaches the simplest route is to install the latest supported unaric payments version from the salesforce appexchange we strongly recommend upgrading no more than 4–5 versions at a time to ensure you can review all intermediate changes and considerations upgrading in incremental versions can help you test if any contain breaking changes related to your org or any customisations you may have our support team can advise if you need additional details if you need to install a version that is not the current latest release, use the installation links provided in the relevant release notes or ask them to support at mailto\ payment support\@unaric com required after each upgrade if you are upgrading from versions prior to 2 18, notify unaric payments support with your sandbox customer id the installed package version this allows the unaric payments team to align support you with any of the older version changes requiring back office support 3\ release notes and upgrade review before upgrading, review the release notes covering the full path from your current version to your target version releases may include new features behaviour changes configuration changes permission updates object or field changes (including field names or new fields) compatibility considerations review every release in between, especially if you are moving across multiple versions if you use certinia (formerly financialforce) with unaric payments, confirm that you are using the recommended compatible package versions before upgrading to learn this, see docid\ guw7yo ycqdeqa2 k8dz0 version specific upgrade considerations the following version changes are particularly important to review when planning your upgrade path for a full list of changes, see https //docs unaric com/payments/release notes version why this matters action required affects 2 13 merchant groups introduced review merchant groups setup and usage clients using merchant segmentation 2 15 validation rule introduced affecting multi merchant record creation check whether multi merchant users can create records after upgrade multi merchant clients 2 17 data integrity token (dit) introduced review whether custom permissions need to be updated clients with custom permission models 2 18 / 2 18 1+ record type changes following outbound (supplier/vendor) payments add the correct record type to existing unaric payments users’ profiles; review outbound payment record types clients using unaric payments users, especially with outbound payments 2 19 dynamic dashboards introduced review dashboard behaviour if step upgrading through 2 19 clients step upgrading through 2 19 2 21 merchant group field changes and unaric payments object naming changes since merchant groups is now a picklist, add the new picklist field in object manager if upgrading from earlier versions; review references to object names now prefixed with “unaric payments” clients upgrading from pre 2 21 versions 2 37 all references to asperato have been replaced with unaric payments unaric payments object names are now prefixed with “unaric payments”, so any references or assumptions based on older naming should be reviewed clients upgrading to this version, certinia clients 4 testing after upgrade after the upgrade is complete, testing should include c ard payment flow testing direct debit payment flow testing psp connection testing p aypage rendering checks e rror handling and logs r econciliation of expected outcomes in salesforce records and objects for complete testing guidance, see docid\ qmppuk9rkjuswrjl ucjb do not promote to production until the sandbox upgrade has been validated end to end contact support mailto\ payment support\@unaric com support when you are unsure which upgrade path is best you are moving across multiple versions and want the key considerations highlighted you have refreshed your sandbox and need customer id guidance you have completed an upgrade and need the back office components aligned if you reach support, provide your current version your target version your sandbox customer id confirmation of the installed package version after upgrade