From discussions with product, we've decided to limit the strMaxLength parameter to 60 characters for a substringPreview-indexed encrypted field. For this change, we also must:

• add a serverParameter that would allow users to bypass the soft limits on substringPreview fields.
• improve the error message for when users have enough encrypted fields in their schema such that the worst case tag count exceeds what can fit in a BSON document. Include suggestion to reduce the number of encrypted fields, or tune the parameters.