Difference between revisions of "Maximum Word/ Character Limit - Why?"
From SmartWiki
Paul Dimerin (talk | contribs) |
|||
| Line 1: | Line 1: | ||
{{WhyHeader}} | {{WhyHeader}} | ||
| − | By displaying how many characters/words over the limit you have gone, your users know exactly how many words or characters they need to cut from content to meet field requirements without needing to constantly guess and rewrite entries. The character/word limit will still be enforced once you hit “save.” | + | By displaying [[Maximum_Length|how many characters/words]] over the limit you have gone, your users know exactly how many words or characters they need to cut from content to meet field requirements without needing to constantly guess and rewrite entries. The character/word limit will still be enforced once you hit “save.” |
This makes it much easier for users to figure out, when completing open text fields in an application or claim, exactly how much content needs to be removed in order to meet the field requirements. | This makes it much easier for users to figure out, when completing open text fields in an application or claim, exactly how much content needs to be removed in order to meet the field requirements. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | [[Category:Why]] | + | [[Category:Why]][[Category:Custom Fields]] |
Revision as of 09:45, 1 September 2016
|
This article will explain why this feature is a benefit to your organization. |
By displaying how many characters/words over the limit you have gone, your users know exactly how many words or characters they need to cut from content to meet field requirements without needing to constantly guess and rewrite entries. The character/word limit will still be enforced once you hit “save.”
This makes it much easier for users to figure out, when completing open text fields in an application or claim, exactly how much content needs to be removed in order to meet the field requirements.
