Challenge Overview
We love the functionality of quick text - it's a great way to standardize our communication across a variety of channels. Reps who use quick text can respond more quickly and more accurately, allowing them to solve a larger number of customer issues every day.
There are a couple things we don't love that much about quick text, though, and this group of challenges will help us bridge the gaps to get the most possible value out of this great functionality:
1) Interactive quick text picker - custom console component for interactive picking of quick text.
2) Multi-language quick text - ability to create translated versions of quick text records and link them to a master, English-language quick text record.
3) Rich text quick text (this challenge!) - replicate standard quick text functionality but leverage a rich text field to populate case emails.
Salesforce Get rich quick text!
With the case feed, our support reps are writing rich, lovely HTML emails to our customers. We're also using quick text, but quick text out of the box doesn't allow us to use rich text. This challenge is to allow users to write quick text in rich text using a standard rich text type field, and then substitute the rich text for the plain text when a user selects a quick text record.
Challenge Requirements:
1) Users write rich text using the standard Salesforce rich text field type.
2) If a rich text value exists for a quick text record, then when a user selects that quick text record the rich text value is substituted for the plain text value.
3) If no rich text value exists for a quick text record, then when a user selects that quick text record no substitution is performed.
4) BONUS REQUIREMENT (not required for your submission to be considered, but scores extra points): The rich text quick text can include merge fields in exactly the same way that the plain text quick text does.
Final Submission Guidelines
Submission Requirements
1) Include your source and package.xml. In addition, we recommend you also provide an unmanaged package to facilitate installation of your solution.
2) Include a video showing your solution in action. If English is your second language feel free to annotate your video rather than narrate it. A video walk-through of your code is nice but not required.
3) Provide detailed documentation of your solution. Include installation and setup instructions.
4) Also you may choose to provide the login and password to your dev org. This is not required but will only help you in the judging if you omit something in your package the and judges have difficulty installing. If you do this you should also install Ray Dehler’s “Enable All Trusted IP ranges” so we don’t have to ask your for the activation code.
5) All your fields, classes and page should have your handle as a prefix so we can install them in the same org.
6) Create a custom app for your solution and include all the tabs the judges will need to test and review it.