Skip to main content

#OhanaSlack2 discussing

Does anyone have an updated link to the Ohana Slack channel? Every link I've found so far is not active. 

 

#Slack Community  #OhanaSlack

3 answers
0/9000
We are building our first community. We are using the Customer Service template and are keeping things pretty simple. We have a Cases record page that contains the Case Comments related list, as we plan to use Case Comments for the back-and-forth communication. 

 

The Related List is not customizable, and it looks terrible with the Comment field jammed over to the right. I found that there is a Case Comments component, but according to documentation this has been sunset and is no longer available.

 

https://help.salesforce.com/articleView?id=rss_case_comments.htm&type=5

 

Below is a screenshot of our ugly Case Comments section in the Community. What is a better approach? I suppose I could build my own component, but we would like to use out-of-the-package features when possible.

 

Display Case Comments in Community
9 answers
  1. May 16, 2019, 6:30 PM
    According to Salesforce Tech Support this is not possible with the Case Comments related list or with any existing component. We will need to build a Custom Component.

     

    Yay. I get to mark my own Best Answer.
0/9000

TLDR: The Review record I created was the 10th one I've created today, and therefore my User record should be flagged and send an email alert and a custom notification, but the flow cannot locate the other 9 reviews.

 

==============================================================

Business need:

 

Designated users want 1) to be notified in and outside of Salesforce when a user creates a large # of Review records in a single day.

 

In addition to sending out an Email Alert and Custom Notification when someone creates too many Review records, 2) the business requires that a user is also "flagged" if they create more than a certain # of Review records related to a single Movie. 3) Last, this user should be unable to create any more Review records as a result of this flag.

 

==============================================================

New Fields on User record: 

 

  • Today's_Review_Count__c         (Number field)
  • Flagged                                          (Formula checkbox field: Today_s_Review_Count__c > 9)

 

My Flow: Record-Triggered 

 

Start Element: I have a record-triggered flow for when a Review record is created and there are no condition requirements. 

 

Get Records Element: Captures these fields from the User who created the Review record:

  1. User ID
  2. Flagged__c (Formula checkbox)
  3. Today_s_Review_Count__c (Number)

Get Records Element: Captures fields from all other Review records created by User found in last Get Records Element:

  1. ID
  2. Created_Date__c
  3. CreatedById
  4. Movie__c

Assignment Element: Gets count of Review records found in last Get Records Element:

 

varNCount (number variable) Equals Count reviewsFound (record collection variablel)

 

Update Records Element: Updates User record where Id = $Record > Created By Id

 

Field: Today_s_Review_Count__c <- Value: VarNCount

 

 

Decision Element: If VarNCount > 9 and $Record > Created Date Equals TODAY(), follow "Yes" branch

 

Yes: 

 

Get Records Element: Captures all User record IDs with the System Administrator profile ID and stores them in sysAdminUsers record collection variable.

 

Assignment Element: Assign sysAdminUsers to sysAdminIds text collection variable.

 

Get Records Element: Captures Custom Notification Id of notifications with DeveloperName = (my custom notification API name)

 

Send Email Alert: {!$Record.Id}

 

Send Custom Notification Element: 

 

Custom Notification Type ID: {!Get_Custom_Notifications.Id}

Notification Body: {!textBody}

Notification Title: {!textTitle}

Recipient IDs: {!sysAdminids1}

Target ID: {!userId}

 

==============================================================

Results: 

 

The Review record I created was the 10th one I've created today, but the flow cannot locate the other 9 reviews.

 

Debug / Rollback mode

 

How the Interview Started: 

This debug run was triggered as if the review__c record was created.

Jenna Hill (0058b00000GorSi) started the flow interview.

API Version for Running the Flow: 57

Some of this flow's variables were set when the interview started.

$Record = Review__c (a018b000010fOUyAAM)

Flow start time: May 22, 2023 at 5:08 PM.

 

Entry Conditions: 

The triggering record met the condition requirements.

Entry Conditions

null

 

Get Records: Get User Record

Find one User record where

Id Equals {!$Record.CreatedById} (0058b00000GorSiAAJ)

Result

Successfully found record.

{!flagged} = false

{!userId} = 0058b00000GorSiAAJ

{!todaysReviewCount} = 0

 

***Get Records: Get Reviews***

Find all Review__c records where

CreatedById Equals {!userId} (0058b00000GorSiAAJ)

AND Created_Date__c Equals {!Today} (May 22, 2023)

Store those records in {!reviewsFound}.

Save these field values in the variable: Id, Created_Date__c, CreatedById, Movie__c

Result: Failed to find records.

 

Assignment: Get Count of Reviews

{!VarNCount} Assign Count {!reviewsFound}

 

Update Records: Update User Review Count

Find all User records where

Id Equals {!$Record.CreatedById} (0058b00000GorSiAAJ)

Update the records’ field values.

Today_s_Review_Count__c = {!VarNCount} (0)

Result

All records that meet the filter criteria are ready to be updated when the next screen, pause, or local action is executed or when the interview finishes.

 

Decision: Greater Than 9?

Skipped this outcome because its conditions weren't met: Yes_Greater_than_9

Outcome conditions

1. {!VarNCount} (0) Greater than 9

2. {!$Record.Created_Date__c} (null) Equals {!Today} (May 22, 2023)

Logic: All conditions must be true (AND)

Default outcome executed.

11 answers
0/9000

Will Classic Knowledge show in Community Components? (ex. Search Results and Article Content) @* Experience Cloud - Best Practices * 

7 comments
  1. Aug 19, 2019, 12:16 PM
    @Andrew Bixler, yes this works fine. That's what we are doing - using Classic Knowledge to surface articles in Lightning Community customer service template. One thing I discovered is that in Classic, Article Type is an object so you can set up several article types, and assign visibility to different user profiles. That's how we are leveraging this feature to let certain users see articles of certain article types.
0/9000