Resolves Validation for Encrypted Numeric and Alpha Custom Fields

[spencerrlongg]

Description

This adds two validation rules: NumericEncrypted and AlphaEncrypted - the rules are written in the new object syntax. They do the same validation as the basic Laravel rules, but add a step to decrypt the value. The value is decrypted only in the context of the Rule class, and remains encrypted when saving to the db.

Screen.Recording.2024-11-14.at.11.46.15.mov

Fixes SC-27213

Type of change

• Bug fix (non-breaking change which fixes an issue)

[what-the-diff]

PR Summary

• Enhancement to the CustomFieldset Model
  The code has been updated to standardize custom 'alpha' (alphabetical) and 'numeric' (numerical) validation rules. This is particularly important when the fields are dealing with encrypted or secret data, thus improving the security margin.

• Introduction of AlphaEncrypted Rule
  A new validation rule has been created that will specifically verify whether a decrypted value contains only alphabetical characters, enhancing our data checking procedures.

• Introduction of NumericEncrypted Rule
  Another new validation rule has been introduced, this time concentrating on numeric data, which checks whether the decrypted value is made up of numerical characters. This step further makes our data validation more robust.

• Improvement in Validating Language File
  Changes have been made to add new error messages related to the alpha and numeric encrypted validation rules. This will help us in better issue handling and prompt resolution by giving us clearer error feedback.

[marcusmoore]

Tested and works 👍🏾

We talked about it while pairing and you already know about the translation strings 😉