Skip to main content

#Case Comment1 personne en discute

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

4 réponses
  1. Forum Ambassador Michael Brown (Salesforce)
    20 oct. 2023, 18:50

    Hi Naomi, that is correct. When a case comment is made public, that comment is visible in the portal, whereas unchecking that box only makes it internal for internal users. Case Comment security is inherited from Cases, so as long as your portal users can't see each others' case, they won't see each other's case comments. You can use a private sharing model, or sharing sets to lock down cases, though so that you can only see the cases that you own, or only those affiliated with your account/contact record. 

0/9000

Hi everyone,

 

I am currently building a LWR experience cloud website and I am having issue while viewing and creating case comments from my website with experience cloud Guest User profile. How can I give access to CaseComment object to a experience cloud website's guest user?

 

Thank You.

 

#Case Comment

1 réponse
  1. Forum Ambassador Sushil Kumar (UKG)
    25 févr. 2024, 16:22
    I believe casecomment access is determined by parent object(which is case in this case). But be careful when giving this kind of access to guest.
0/9000

Hi

I have created a workflow rule on the Case Comment object with the following criteria (please see attached screen shot) but when I test it (in a Sandbox) it doesn't trigger the field update on the Case Object. Any help will be appreciated. Thanks. 

1 commentaire
0/9000

Hi, There are two users in my organization not able to see the 'New" button on the case comment related list on the case record. When I am logging as them I can see the "New" button but it is not showing up for them. Please suggest how to troubleshoot the issue?

 

Thanks & Regards,

Megha

1 commentaire
  1. 12 avr. 2021, 13:09
    Hi Megha, try having the user view the page under the same browser you are using (ie chrome, firefox, etc). Let me know if that makes any difference....
0/9000

We need HELP!  

 

I know someone out there has to be doing what we are trying to accomplish and can give us some advice.

 

Use Case:

We have events that happen in our support department that require large number of ticket to be opened from our partners.  All of the cases surround the same problem. We could have 10 tickets we could have 1000 tickets open for the same problem. 

Solution:

Create a parent Case and add all of the related cases as children to the parent case through the partentID field in Salesforce on the Case object.  When a parent is updated all the children are updated accordingly.  This could be a field update and or a case comment being made. 

Issues:

Salesforce doesn't do this inherently.  Why I have no idea.  So many other system handle this type of solution but this one does not.  So we have a developer working on code to implement this but we are running into roadblocks left and right with previously written code causing recursion and other things that were written to fire in code for updates on cases for our Milestones and Entitlements. We are currently trying to call a flow from the APEX code because when a public case comment is made we need to send an email to the contact on the case to let them know the case has been updated.  This causes and error because when we test out 800 children cases its hitting governor limits.  We have an email template setup that sends out these emails on a case by case basis now, but seems we cannot figure out how to get this to bulk send properly from the template when it loops through and creates the collection of children cases. I think that we have many more issues trying to get this to work but the bottom line here is that it's cumbersome, has taken way too much time and just simply isn't effective way to manage cases at this point. 

 

If anyone has a solution to this I am all open to anything at this point.  We have done our research and everything points to the only way to make parent replicate to children is through code and we are trying but it just seems to put up roadblock after roadblock.  I keep thinking someone has to be doing this and using parent/child in some capacity that is easier.  Any help, insight or advice would be greatly appreciated.  We are going on like 4 weeks time now trying to make this work...

1 commentaire
  1. 26 mars 2021, 13:54

    I can't think of anything simple to do this because of all our configuration complexity. My advice would be to make a list of every automation that touches cases. Then draw out a really complex flow chart that shows how they all work together. I'm assuming you probably have workflows, process builder flows, flows, and apex code which is all clashing together. If you draw it out, you may see you have duplication or places where you can combine automations (turn workflows into PB or Flows, combine PBs, turn all workflows and PBs into Flows, etc.)

    If you're able to reduce the complexity, it may become an easier problem. Because without any other automations, this is a very simple record-triggered flow. When a case is changed, get all children cases, change the status of all these child records to match the status of the record that started the flow.

    Good luck!

0/9000

Hi Team,

 

I have a process builder on Case comment and it is sending a bell notification(not email) to user if any comment is added with merged, but while clicking on notification it is giving error like :

 

Looks like there's a problem.

INVALID_TYPE: sObject type 'CaseComment' is not supported in describeCompactLayouts.

 

Can somebody help? how to get bell notification for Case merged ?

0/9000

Hello master admins , Is there a way to display the queue name when a Case comment is entered rather than the member of the queue. ex, Our cases get assigned to a queue , but when different members of the queue comment on that case , we want it to show as the Queue name instead of the individual user who commented there. There is nothing wrong in showing the user name who commented , but  we are trying to display these notifications on a Student community and want them to see a uniform id like a queue rather than individual names.

@ admin trailblazers 

Thanks!

0/9000

A case of Circuit Breaker Double IPA to help my complete brain freeze here please!  Can't fiddle through Friday fog to fix this formula (alliteration anyone?). Missing parentheses?

 

Case comment workflow:

 

IF( OR( AND( ISNEW(), CreatedBy.UserRole.Name = " Choice Community Users Partner User"), AND( ISCHANGED (LastModifiedBy.UserRole.Name)( LastModifiedBy.UserRole.Name = " Choice Community Users Partner User")), True, False)

5 commentaires
0/9000

I have a flow that creates a Case Comment; the flow itself works fine (since it's modeled after another one I have).

 

In the template that contains the text of the comment, I pull in several fields off the Case. (the case is getting routed to another queue and RT that doesn't have access to all of the same fields). The lookup fields are displaying the record ID instead of the text name of the record - how do I get .Name to show up instead?

 

Thanks!

2 commentaires
  1. 1 déc. 2017, 21:21
    @Darrell DeVeaux

    Yes, I'm using a text Template.

    I'm not using formulas for my other fields on my Record Lookup first step, I assigned variables to reference in my flow and inserted those variables into the template. If I can use a regular formula instead, I think you've solved my problem.

0/9000

Hi Lightning Now group, 

 

Seeking to get some assistance with an issue with Case Comment in Lightning. 

 

In the classic Service Cloud Console - we had the 'internal comments' standard field available, and used with an custom 'update case' quick action. This allows the support agent to add a comment when updating the case altogether. See screenshot here: 

https://www.screencast.com/t/IO6nMhAw

 

In Summer 17' - the 'internal comments' field is missing for some reason. See screenshot here: 

https://www.screencast.com/t/jRxPhNqkGv

 

There is a new quick action - 'Case Comments' (https://releasenotes.docs.salesforce.com/en-us/summer17/release-notes/rn_cases_case_comments.htm) though, but this doesn't allow us to customize the Comments as add them within other Quick Actions, such as 'Update Case'. 

 

Am I missing anything here? 

 

Thank you. 

 

@Service Cloud Users

2 commentaires
  1. 16 mai 2017, 19:00

    Thanks for the answer and workaround.

    We are still debating around making a switch to Lightning console once Summer 17' goes into production.

    Except this minor 'case comments' issue, we are mainly concerned with the lack of the Default Email Template support, as we rely heavily on that to distinct different scenarios according the case type (Enterprise, Consumers, etc.).

    To add to that the partial classic Email Templates support, along with missing Macros and Quick Text (and also visual notifications in the console), and also lack of VF Email Templates, takes us further rather then closer to making a switch.

    I guess we'll have to sit patient waiting for Spring 18'.

    Thanks again for your time here.

0/9000