I want to add a merge button to an experience cloud page . A merge button on community page is not working

We are excited that you are interested in using Apsona's merge buttons on an Experience Cloud page. Our sales and support team need to work directly with you to get the experience cloud merge button up and running as it involves some technical steps on our end. We will reach out to you with more details. In the meantime, here is a checklist of questions and user permissions that need to be in place for this to work.

Questions and Next Steps:

  • If you have not installed our Button Lightning component yet, you can install here for production or a sandbox.
  • Are you working with an Implementation or Managed Services Partner on this project?
  • Approximately how many experience Cloud Users will need to use this merge button?
    • Will these be a set number of logged in community users or a variable number of community 'guest users' visiting a public facing page?
  • Are you testing this button on an experience cloud page in your production environment or sandbox environment?
    • There is a one time effort that our Engineering Team must take to 'whitelist' a particular web subdomain for every environment that you want to use the button in.
  • Please reply to us with the Org ID  of your Salesforce org so we can find your licenses in our system
  • There is a one time setup fee for this enablement. Our Sales team will reach out with further details.
  • Here are some helpful support resources for creating your merge button:

Requirements:

  • Please assign an Apsona license to the Experience Cloud User (aka: Community User). This can take the form of a full "Apsona for Salesforce License", ensuring that the "Doc Gen" checkbox is checked for this user (see this video for instructions); or this can be our specialized "merge button only" license if your org meets the license threshold to qualify (see this video for instructions).
  • Experience Cloud User Profile/Permission Set Requirements:
    • The profile or permission set assigned to the Experience Cloud User (aka: Community User) must have "view all fields" access on the relevant objects used in the merge action
    • The user profile or permission set must be set up to access Apsona as any standard user would be:
      • The user profile or permission set must have the System Permission: "API Enabled" box checked
      • The user profile or permission set must have access to the "ApsonaForSalesforce" Visualforce page
      • The user profile or permission set must have create, read, edit, delete access to "Apsona Items" and all fields within the object must be checked as editable
    • Check access provided in Org-Wide Defaults and Sharing Settings to the relevant objects used in the merge action:
      • If org-wide defaults are set to private, make sure there are sharing rules to open up records that the user needs to see
      • If org-wide defaults are set to “controlled by parent” ensure that parents are public, or that there are sharing rules on the parent objects to open up records that the user needs to see
  • Please ensure that the merge button is on a record page that will give the right access to the objects that the merge is based on.
    • Buttons placed on non-record pages will function as if it were being run from the Apsona data source, ie: without any record level filtering to a particular record associated with that Community User
  • Experience Cloud pages can be built using different frameworks that are available through Salesforce. One being the AURA framework and the other being the Lightning Web Runtime (LWR) framework. At this time Apsona's merge button custom component (install link for production / install link for sandbox) will only be visible for pages built on the AURA framework. Consider this as you choose the framework on which to build your pages. When building your page, you will see the component show up at the bottom of the component section in the experience cloud builder:
    • image.png
  • Once added to the page you will see a pop up on the right where you can enter the parameters for the button:
    • image.png

Other helpful notes as you build:

  • Note that the filter options you have for components on an internal Salesforce record page are not available on an Experience Cloud page built on the AURA framework, only pages built on the newer LWR framework. So if you intend to conditionally hide a button on an Experience Cloud page, this is currently not possible through basic filtering.
    • But as an alternative: Experience Cloud has a feature called Audiences which allows you to configure components based on domain, location, permission, profile, or user; and in the context of an Experience Cloud record pages, by record criteria as well. To find these settings within the Site Builder go to Pages > Object > Object Detail > Page Actions (the three horizontal dots) > Page Settings > Page Variations > dropdown at the end of the Page Variant row > Edit Assignment.
  • For more information about deduping contacts when they are also Community Users, see this article.