Nick Sauer adds Smart Word Processing Features to Rich Text Input
Input Rich Text has been around for a while. It sports a nice toolbar and allow rich text creation. Nick Sauer has enhanced it with a number of killer new features that add business productivity, including Find and Replace, Autoreplace, and Blocklists. As you can see below, these new features are available via a swanky bottom toolbar, and can be turned on or off as a group.
You can pass in a map of terms that you want to automatically replace.
How it Works:
Use Case Example: Business has the need to enter customer-facing details that:
- Blocks users from entering certain sensitive words/symbols
- Automatically applies Trademarks (™) or other company-specific terminology.
- Allows for Find & Replace tool to correct mistakes
Component Setup:
| Parameter | I | O | Information |
| enableAdvancedTools | X | Boolean. Set to true if you want to use these enhanced rich text features. Default is false (regular input component) | |
| autoReplaceMap | X | JSON formatted key:value map. (example => {“Test”: “GreatTest™”} ) | |
| disallowedSymbols | X | Comma-separated list of words to block. Example: /,@,* | |
| disallowedWords | X | Comma-separated list of words to block. Example: bad,worse,worst | |
| warnOnly | X | Boolean. Set to True if you want to allow Next even where disallowed Symbol or Word remains. Default is false. | |
| value | X | X | Input and output Rich Text that you’ll be editing |
| label | X | X | Input to provide field-level label if desired (label not read only on v1, so left as-is to prevent breaking existing implementations). |
| characterCount | 1) Character count is off by default. Set characterLimit to an integer value to show character count and limit. 2) If warnOnly is not set when characterLimit is on, then the Flow Next/Finish cannot be used until resolved |
Component Input Example:
Installation:
Resources:
Old Versions
This look amazing, thank you Nick!
[…] UPDATE: We recommend you use this more powerful, more recent version of rich text input […]
[…] SF has posted my first contribution to their incredible collection of components! I only have 99 to go to get ‘even’ for […]
This only works if there is existing text in the value’s variable. If the variable starts as blank, then any text entry is not saved.
Is there any fix for this? We don’t want to display any existing or placeholder text for the user.
Thanks David – fixing that now.
Pull request is pending for it — careless mistake in testing on my end, and thanks for finding it!
In the interim, you can put a ‘ ‘ in the input value, and it will then work.
Hello, I was using the previous version but for some reason, from time to time it suddenly stopped working without a cause and it didn’t capture any output value. Now I have updated this component to the newest version and it turns out… it never works!! Doesn’t matter whether there is a value or not in the input value, the output value is always what there was in the input value. So if the input value was defaulted to “Text” then the output value will always be “Text”. I have tried different alternatives for the input value: plain text, formulas,… Read more »
Hi Jaime – assuming you’re using the legacy function (no enhanced function). I’ve found the issue there and resolved. Pull request is in for it. Sorry about that and thanks for pointing it out!
Hi Nick, thanks for the fix! 😀
Should I have to reinstall the component? Is the fixed version available now?
Hi Jaime – it’s pending review currently, so not available quite yet.
Thank you Nick,
just to be clear about how this process works (sorry but I’m not quite used to this), will the date at the top of the page be updated when the new version is released?
I assume I’ll have to download the component again in order to implement the fix.
Thanks again!
I mean this date
Hi Jaime – I am not sure on that. In the interim, I can help with couple options to get around the issue.
1) You can turn the Advanced Features on by changing that field to True.
2) If you’re passing in an empty value to that field you can add a ‘ ‘.
This will get you around both bugs fixed in the pending pull request. Feel free to email me if you want to put in the new version, and then you can overwrite it as needed once the new package is released. archwise.nick@gmail.com
Nick, I have tried this workaround you’ve mentioned and with that I have managed to make it work again. Thanks!!
This is good enough while the fixed version is released.
Thanks Jaime – sorry for the hassle. The new version fixes that, and adds character count enhancement too, so maybe that’ll be useful too.
New version 1.3 available above with all of Nick’s fixes.
Hello! I am very excited for these changes. It seems the character counts starts at 8 instead of 1 though. I assume I can just bump the limit by 7 and “get around” it. Just thought I would mention it.
oh i see, that won’t work because it is counting <p> and </p> in the characters. Let me see if i can take those out somehow
Hi Kate – correct. Rich Text will always have <p> </p> so the starting count will be 8.