Following a successful update to Fonteva 20Spring, you need to perform the following actions to ensure the update’s success in your org:
Payment Method Field Update on Scheduled Payment Object (IMPORTANT!)
It is of the utmost importance you perform this step. Failure to do so will result in your org unable to function properly.
Delete the deprecated Payment Method field and add the new Payment Method field on the Scheduled Payment object.
Run Access Manager
Run Access Manager on Fonteva items for your Community and Guest Profiles.
Conditionally Required: Backend Custom Payment Types Update
Perform the Backend Custom Payment Types Update if you utilize a custom payment type component and a custom Lightning Component to use on checkout pages.
We’ll guide you through each of these actions step by step in the following sections:
Payment Method Field Update on Scheduled Payment Object (IMPORTANT!):
After updating, the Payment Method field (OrderApi__Payment_Method__c) on the Scheduled Payment object will become deprecated. You will need to delete this field and add the new Payment Method field (OrderApi_Saved_Payment_Method__c) to your Scheduled Payment page layout.
Follow the directions below to successfully delete the deprecated field and add the new Payment Method field.
Do not skip this step. If you do not delete the deprecated field and add the new Payment Method field, your new update will not work properly.
After upgrading, log in to your org and navigate to Setup > Installed Packages. Locate and select the Spark package. The Spark package details page will open.
On the Spark package details page, determine the version name is Fonteva 20Spring. This means the update was successful. If the version name is not Fonteva 20Spring, your update was unsuccessful. Contact Fonteva Customer Support for further steps if your update was unsuccessful.
Type Objects into the Quick Find search bar and select Object Manager from the results generated. The Object Manager will open.
Enter Scheduled Payment in the Object Manager search bar. Select the Scheduled Payment object from the results generated.
On the Scheduled Payment object page, select the Fields and Relationships tab.
Type Payment Method in the Search bar and ensure the Payment Method field with a field name of OrderApi_Saved_Payment_Method__c displays. This confirms your update is complete.
Type deprecated in the Search bar and locate a deprecated field with a field name of OrderApi__Payment_Method__c from the results generated. Click the dropdown menu at the end of the row and select Delete.
A message will open to inform you that you are deleting a custom field. Click Delete on this message. The field will successfully delete. If you are prevented from deleting the field, please read the Potential Issues Deleting a Field section below to troubleshoot.
After successfully deleting the field, click the Page Layouts tab and select the 20Spring layout.
On the 20Spring page layout, add the Payment Method field (OrderApi_Saved_Payment_Method__c) to the page layout and click Save.
Potential Issues Deleting a Field:
There are a couple of scenarios where you may be prevented from deleting a custom field.
Issue - Cannot Delete Managed Component: If this field is part of a managed package, you will not be able to delete the field and will receive the below message. This is a sign that your update is still in progress or failed.
Solution: Check your version following steps 1 and 2 above to ensure you are on Fonteva 20Spring and contact Fonteva Customer Support if you are not on the correct version. Also check to ensure you are deleting the correct field.
Issue - Custom Field Referenced Elsewhere: If the field is referenced elsewhere, you will also be prevented from deleting the field. You will receive a table listing all the areas where the field is being referenced as seen in the screenshot below.
Solution: Remove the referenced field from the sections listed (see screenshot below) and replace it with the new Payment Method field.
Steps to Run Field Level Security (FLS):
You must be logged in as an Administrator to perform these steps. Reach out to your System Administrator if you do not have Admin permissions.
If your org does not grant FLS to profiles, refer to the Minimum Object Access Permissions page for setting up the correct permission set for the Guest User Profile.
You’ll first want to locate the profile name of your Guest User Profile so you know it for later.
Navigate to Setup and [Enter] All Communities in the Quick Find search bar.
[Select] Workspaces for your Community. Community Workspace will open in a new tab.
[Select] Administration to access your Administration settings.
[Select] Pages. Under Advanced Customizations, [Click] Go to Force.com. The Site Details page for your Community will open in a new tab in Salesforce Classic.
Locate and [Select] the Public Access Settings button. The profile name will display as the header for the page that opens.
Now that you know your Guest User Profile name, it’s time to run Access Manager.
Navigate to the Fonteva Framework tab.
[Select] Access Manager. You may be requested to log in. [Select] Production or Development and [Enter] your Salesforce credentials.
The Choose Packages and Profiles page will open. [Check] the following Fonteva packages under Packages:
Engage - Member Community
Fonteva Lightning Bolt Template
Rapid Order Entry
Under Unpackaged at the bottom of the page, [Check] Standard.
Under Profiles, [Check] the Guest User Profile you identified before opening Access Manager. You should also check other profiles you would like granted access to the update. You can check up to 15. We recommend selecting any Partner profile, any profile that includes "Fonteva" in the title, any Guest profile, the Standard Platform User profile, the Standard User profile, the System Admin profile, and any other relevant profile that is used in your org.
[Click] Fetch Profiles at the bottom of the page. The Set Up Profiles page will open.
[Click] the orange menu to open it. Ensure the Object Permissions option is enabled (the other two menu items should be enabled by default.)
[Click] Update Profiles at the bottom of the page. The Guest User Profile you selected will be updated. You can return to the Fonteva Framework page.
Conditionally Required: Backend Custom Payment Types Update:
The new Apply Payment page in the backend introduces a new payment window and Pay button. Customers can now directly override where users will be redirected or use the default behaviors. Because of this, customers that have developed their own custom payment component and utilize custom Lightning Components on checkout pages will need to perform the below steps.
These steps are NOT necessary if you do not use a custom payment type and a custom Lightning Component to use on checkout pages. Do not follow these steps if you do not meet that criteria.
Remove the component Pay button. The system now automatically generates a Payment window and Pay button. If this component is used for both the backend and the Community, the Pay button must now be removed from the backend.
Every component will now need to have the “prePaymentTask” and “paymentTask” methods added.
This allows the component to do field validation
Shows Receipt id if returned
Will redirect the user after the payment
The system automatically calls these methods and executes the correct logic.