Timeline for Pre-populate rich text field in the case creation page
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 9 at 1:07 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 6 at 19:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 7 at 12:07 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 1, 2023 at 7:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Sep 13, 2022 at 14:53 | answer | added | Richard Clarken | timeline score: 0 | |
| Jul 20, 2021 at 20:51 | answer | added | SFDC FORR | timeline score: 0 | |
| Jul 15, 2021 at 19:34 | comment | added | Kris Goncalves | Any reason each of your bolded pieces couldn't just be its own custom field with its own help text? No doubt, I'm sure the request is as you laid it out, but I'd fight for simplifying it versus sticking everything in one big rich text field and having to go down the road of overriding the default create screen. Easier reporting, filtering, can add validation rules to require certain parts, etc. | |
| Jul 15, 2021 at 19:25 | history | edited | Kris Goncalves | CC BY-SA 4.0 |
added 34 characters in body; edited tags
|
| Jul 15, 2021 at 18:17 | comment | added | cropredy | did you try a before save Flow? | |
| Jul 15, 2021 at 16:28 | review | First posts | |||
| Jul 15, 2021 at 16:53 | |||||
| Jul 15, 2021 at 16:20 | history | asked | SFDC FORR | CC BY-SA 4.0 |