#Customer Portal Users0 diskutieren mit

Hello,

I am currently creating a customer community and looking for a way for an internal employee to update a customer on their case. I do not want to expose the case chatter feed as that could lead to more issues. I noticed there was this option called "case comments" that I can add as a related list to a case.

If one of our employees were to create a new case comment on a portal users case and sets that comment to "public." Can someone confirm it is only the portal user who's contact is on the case who can see this comment?

Basically I do not want any other portal user seeing comments on a case that does not belong to them.

Many thanks,

Naomi

#Experience Cloud #ServiceCoud #Service Cloud #Experience Site #Customer Portal #Customer Portal Users #Case Comment

In customer portal(community portal) we have two tabs one is asset map & another one is smart tracks(both are aura component). If i open asset map it is visible, if i go to smart tracks it is visible, if i again go to asset map tab the component is not visible its shows blank in portal. 

#Salesforce Developer  #Aura  #Help  #Customer Portal Users

Let's compare notes on a CTA scenario challenge: How to share published Race records to everybody? 

Context: Race a custom object that's private. But once it's published, it should be visible to everyone. 

Idea (1): Use criteria based sharing to share to an All Users group.  This does not work. (1.1) You can create an All Users public group, then you can put in "All Internal Users" and "All Portal Users" in it.  But "All Customer Portal Users" is not available to become members of another group. 

Idea (2): Use criteria based sharing to share to "All Internal Users", "All Portal Users" and "All Customer Portal Users".  But "All Customer Portal Users" contains all Customer Portal users, except for high-volume portal users. So the customer community (CC) users are not included. Advanced sharing is not available to to share to CC users. 

Idea (3): Create a Published Race custom object with OWD of public read.  Use an after save flow to copy a race to a published race once its status becomes "Published".  

Do you have a way to make (1) or (2) work? Do you have a better solution than (3)? 

Next question: I get an Invalid Page error when I click on my Cases tab (in the community logged in as a community user). I figured out that it had to do with the visibility of the default list view. If I set the defaulted list view (which is a custom list view I created) to be visible to all users, it works fine. But if I set it to be only visible to the group "All Customer Portal Users", then I get the Invalid Page error. Same thing happens when I do this on the Accounts tab and other Salesforce object tabs. 

Do I need to configure which users are in the "All Customer Portal Users" group? If so, how do I do that?

We are implementing SSO and are having trouble understanding what we need to do to include our existing customer portal users.

We are using Salesforce as both our Identity Provider and Service Provider.

On page 44 of the current 'Single Sign-On Implementation Guide' under 'Enable Single Sign-On for Portals' it says "In addition to the SAML sign-on information that must be gathered and shared with your identity provider, you must supply your information provider with the Organization ID and the Portal ID. In the SAML assertion that is sent from your identity provider, the portal_id and organization_id must be added as attributes."

Could somebody please explain how to edit the SAML assertion so the attributes for the Org ID and the Portal ID can be included.  

I'm going crazy reading documentation and I think I'm only getting more confused so any help will be very gratefully received!

Is it not possible to expose a Chatter Answer question custom field to customer portal users?

I can expose the custom field to internal users but not seeing an obvious way to add the question custom field to the standard question post form even though FLS is set correctly for the high volume customer portal users.