Salesforce Communities replacement by AEM || ??Mulesoft ?? Rest ?? Anthing else | Community
Skip to main content
M
mk_aem21
Level 2
February 23, 2024
Solved

Salesforce Communities replacement by AEM || ??Mulesoft ?? Rest ?? Anthing else

  • February 23, 2024
  • 1 reply
  • 1717 views

Hello All,

 

I am totally new to AEM from experience point of view and thus looking forward to suggestions from experts.

We have Salesforce communities(it is basically a normal website used for self-service for users) for support and self-service work portal.

 

Now, we want to Just replace the frontend of this Salesforce community portal(not the Salesforce itself) with organization AEM standard look and feel website so that the support and self-service portal also become part of main website of organization.

 

Here, what is the best approach for this replacement?

  • Do we need salesforce and AEM integration. If yes, how ? and does it work for AEMaCS ?
  • The salesforce community code is kind of coupled as flows comprising of UI logic as well as Salesforce backend logic. Do we have to move both logics to ui.frontend and core respectively ? Or there is any other way?
  • Are there any documentation or 3rd party integrators that can be leveraged?
  • Can we simply go ahead with AEM(frontend) - Integration(custom middleware/Mulesoft/Any thing else) - Salesforce(Backend) architecture and use API calls?

 

Any valuable suggestions will be really helpful.

Thanks!

 

#aem #salesforce #community

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Saravanan_Dharmaraj

@mahesh_gunaje Some of the major issues we faced during our implementation

1. Content moderation - very difficult in extending it to show more facets to filter and approve/deny

2. User sync - we faced many issues in terms of new users signing into community and that user node is created in one publish instance and that needs to be published to other publish instances through SCD(Sling Content Distribution) set up. It was so buggy, the sync was not happening and we have only 2 pub instances, if you have many more issues. Created multiple p1 request with daycare. 

3. There was no OOTB rate filter and spam filtering there to prevent spam messages in blogs/forum/ideas section. We tried to do block with Akamai. Lot of time went into clearing messages from communities.

4. Development - we need to learn one more language Handlebars for all the components. 

5. Adobe stopped adding new features and enhancements in community

 

many more.. issues and then we finally moved to Salesforce. 🙂 . I wish it would have worked out better

1 reply

Saravanan_Dharmaraj
Community Advisor
Saravanan_DharmarajCommunity Advisor
Community Advisor
February 23, 2024

@mk_aem21 When you said customer communities , i assume all User Generated Contents? You need to have the new set up in AEM(Extra license) to AEM communities which includes the data stores(MSRP or ASRP) for storing UGC. If you are looking to bring some UGC contents from the salesforce(headless) into AEM and displaying it , then its a REST call from the AEM side. We have done that.  We also moved the communities from AEM(AMS set up) to SF (not the other way around) because of so many issue with AEM communities.

Also AEM communities is not supported in AEMaCS. 

    M
    Mahesh_Gunaje
    Level 7
    February 24, 2024

    Hi @saravanan_dharmaraj 

    Curious to know about, what you said: "because of so many issue with AEM communities"

    Usually, for the web CMS, company will compare Drupal with AEM.  For example, to migrate drupal application to AEM. Since, in Drupal, blogs/community are the nicest feature. Whereas in AEM, its not the case. So, if possible, could you please elaborate about "AEM communities" from your experience.

     

    - Thanks

      Saravanan_Dharmaraj
      Community Advisor
      Saravanan_DharmarajCommunity AdvisorAccepted solution
      Community Advisor
      March 5, 2024

      @mahesh_gunaje Some of the major issues we faced during our implementation

      1. Content moderation - very difficult in extending it to show more facets to filter and approve/deny

      2. User sync - we faced many issues in terms of new users signing into community and that user node is created in one publish instance and that needs to be published to other publish instances through SCD(Sling Content Distribution) set up. It was so buggy, the sync was not happening and we have only 2 pub instances, if you have many more issues. Created multiple p1 request with daycare. 

      3. There was no OOTB rate filter and spam filtering there to prevent spam messages in blogs/forum/ideas section. We tried to do block with Akamai. Lot of time went into clearing messages from communities.

      4. Development - we need to learn one more language Handlebars for all the components. 

      5. Adobe stopped adding new features and enhancements in community

       

      many more.. issues and then we finally moved to Salesforce. 🙂 . I wish it would have worked out better

        Terms & ConditionsAccessibility statement

        Loading footer...