Please see procedure When and how are the permissions used? to determine if the object in question needs to have public access. Please FULLTEST any updates should you reduce the recommended settings.
Salesforce Alerts/Notifications
Topics on Salesforce Alerts/Notifications
Why is Object XXX showing in RED
Please see procedure When and how are the permissions used? to determine if the o ...
Can we disable the Potential Risk (RED) Permissions shown in the GUAR report associated with Payments2US Guest user profile
The Permissions that are associated with Payments2Us Guest User Profile which you ...
The Permissions that are associated with Payments2Us Guest User Profile which you can disable.
- permissionspasswordneverexpires
- permissionsenablenotifications
- permissionsactivitiesaccess
- permissionsallowuniversalsearch
- permissionscontentworkspaces
- permissionsselectfilesfromsalesforce
- permissionsadddirectmessagemembers
- permissionsenablecommunityapplauncher
- permissionsuseweblink
- permissionsemailtemplatemanagement
- permissionsemailadministration
- permissionsmanagechattermessages
- permissionsshowcompanynameasuserbadge
You can use Workbench to set these Permissions to False. Please see the instructions below.
- Open the link provided in the GUAR Report. Login to your instance of Salesforce.
- Set the Permissions which are True to False and Confirm Update.
Our organisation is moving to Hyperforce does this impact our custom domain?
Yes, there is a known issue where having a custom domain using your own certifica ...
Yes, there is a known issue where having a custom domain using your own certificate and CDN.
To check, go to setup and search for "Domains". For the domains where the certificate is entered, if these are hosted on the Salesforce Cloud, there can be an issue moving to Hyperforce. In this instance, the migration would be blocked. Furthermore, salesforce generally will not select you for migration to Hyperforce if they believe there will be an issue. This is one of the criteria they look at.
Enabling Salesforce Enhanced Domains?
Salesforce has delayed the timeframe for the deployment of enhanced domains rollo ...
Salesforce has delayed the timeframe for the deployment of enhanced domains rollout. Note, the seasons mentioned are Northern Hemisphere.
From Salesforce notifications:
To ensure customers have adequate time to prepare, test, and make necessary adjustments for enhanced domains, the deployment timeline for this feature changed. The new timeline is as follows:
- Spring ’23: Enhanced domains deployed in all orgs that don’t have enhanced domains deployed, with options to opt-out & disable the feature.
- Summer ’23: Enhanced domains deployed in all orgs that don’t have enhanced domains deployed, with an option to disable the feature.
- Winter ’24: Enhanced domains enforced in all orgs.
For additional timeline details, see Enhanced Domains Timeline in Salesforce Help.
This help article is being updated as we learn more. Contacting our support team or us directly is not going to be able to provide more information as this article is the most up to date. Please book mark and check back regularly.
We have been running enhanced domains internally since December, our test and development environments were updated months ago. We are also aware of customers using Windcave Webservice and Stripe with enhanced domains for a while. If electing to turn on, we do suggest testing your normal business as usual. Ideally testing from a Sandbox first.
Whilst we are not aware of any current issues, we need to go through and do some thorough checks. This section will be updated as progress is made.
Actions Required by you after enabling Enhanced Domains:
- NOTE: These are actions known to date. We are still reviewing an more may be required.
- The Base Site URL on all Merchant Facilities will need to be updated.
- You should update your website where forms are iframed in to to have the updated Base Site URL.
- For Experience Cloud/Communities, you will need to add a new CSP Trusted Site.
Known Issues
- Create Samples does not assign the correct Base Site URL on DEMO FACILITY. This is addressed in 9.2 (release now available for install from the AppExchange)
- Failure to update Base Site URL will cause PayPal to stop functioning. Symptons of this issue is when pressing the PayPal payment method button, the PayPal login screen flashes up, then disappears.
Might show the redirection with "CORS Error Access-Control-Allow-Origin" - If using custom CSS and with your specific Fonts then the static resource CSS will need to be updated to use the new force.com - Sites Base URL.
- Create Remote Site settings component in the Payments2Us Settings Tab/App sub tab will always show, even after successfully creating the remote site. This is addressed in the current version 9.3.
Recommended Updates
Webhook setup again if you are using:
- PayPal - How to setup PayPal
- Stripe - How to setup Stripe
- Shopify - How to setup Shopify
- Payments2Us Webhooks - Payment Complete
1. Enhanced Domains FAQ
Q: What will happen to links for membership renewals that have already been sent out?
A: Salesforce has implemented redirects. These renewal links will be redirected and should continue to work. For more info, see Salesforce Help Article Redirect Site URLs After you enable Enhanced Domains.
2. Disabling Enhanced Domains
Should you wish to disable Enhanced Domains after Salesforce has completed the Spring 23 release update an automatically turned on Enhanced Domains, then:
- Click on setup cog (top right)
- Quick find "My Domain"
- Click on "My Domain" menu
- Click "Edit" button
- Untick "Use enhanced domains"
End of life Workflow notification / Migration from Workflow/Process Builder to Flow
Salesforce have announced the retirement of Workflows and Process Builder. Organi ...
Salesforce have announced the retirement of Workflows and Process Builder.
Organisations with Workflows/Process Builders will still be able to use and edit these for a little while, but cannot add new ones.
Payments2Us will migrate Workflows to Flows over the coming releases. Keep an eye out on this FAQ for updates.
NOTE: You cannot use the migration wizard to migrate the standard Payments2Us Managed Package Items. We need to do this as part of a release update.
JDK Locale Format Retirement
Salesforce is migrating from JDK to ICU Locales. You can see more details in thei ...
Salesforce is migrating from JDK to ICU Locales. You can see more details in their online help: JDK Locale Format Retirement
Our checks have not located any issues with this announcement.
Should we subsequently discover anything, then we will post updates in this FAQ.
The latest and most up-to-date information is in the FAQ - Contacting us directly or via support will not have any additional information that we can provide.
Update Unsupported Legacy API Version - Upto Version 30.0
You may receive an email from Salesforce along the lines of "You are receiving th ...
You may receive an email from Salesforce along the lines of "You are receiving this email because you’re an admin of an org that is actively using the legacy API endpoints. Versions 21.0 through 30.0 of the Salesforce Platform SOAP, Bulk, and REST APIs are currently unsupported and you need to take action before May 2023. "
This does not impact Payments2Us.
We have received an email that our Salesforce Org is due to be migrated to a new server/instance
Question: I've seen that our Salesforce Org is due to be migrated this weekend, a ...
Question:
I've seen that our Salesforce Org is due to be migrated this weekend, and I wanted to check in to see if I need to update anything with Payments2Us? (e.g. hard-coding in anything)?
Answer:
From the Payments2Us Perspective, there is nothing that will be impacted.
Customer orgs are migrated to new instances of Salesforce all the time.
You may need to check for any of your own customisations that your Admin or Consulting partners has done. Those sort of checks are outside of our support as they are general Salesforce Admin related.
Enforce RFC 7230 Validation for Apex RestResponse Headers
Salesforce is alerting customers with the following message for Spring 24 Enforce ...
Salesforce is alerting customers with the following message for Spring 24
Enforce RFC 7230 Validation for Apex RestResponse Headers
- Apex that invokes the RestResource.addHeader(name, value) method, with a header name that isn’t RFC 7230-compliant results in a runtime exception of type InvalidHeaderException.
- Before activating this update in production, check with your package providers to make sure that all your installed packages are compatible.
- There is no use of RestResponse.addHeader(name, value) in the instance, just need to confirm with the Package providers.
We have run code scans and checks and are currently not aware of any issues. Nor, have we had any customers report any issues.
Please book mark this FAQ and check back. We will update this FAQ if we learn of any new updates.