Feature/masked input field #3841
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Implement MaskedTextBox field type with configurable input masking - Add 6 custom properties: minLength, maskingCharacter, maskingStartIndex, maskingFromStartLength, maskingFromEndLength, isMaskedInDB - Support client-side masking with configurable characters (*, #, @, $, %, &, !, ?, alphanumeric) - Implement flexible masking positioning (start index, length from start/end) - Add comprehensive validation rules and error handling - Include complete i18n support with proper field labels - Add side-by-side layout for masking indices This provides a reusable masked input field component for jBPM forms.
…ities * Add new MaskedTextBox field definition extending AbstractMaskedTextBoxFieldDefinition - Support for start index masking with configurable length - Support for end masking with configurable length - Support for database-level masking with isMaskedInDB flag - Configurable masking character (default: *) - Min/max length validation support * Implement MaskedTextBoxFieldProvider with String type support - Set priority to 5 to avoid TreeSet collision with TextBoxFieldProvider - Register with BackendFieldManagerImpl and ClientFieldManagerImpl - Enable automatic CDI discovery * Add MaskedTextBox to form editor field type providers - Include in EditorFieldTypesProviderImpl for palette and properties - Support field type dropdown functionality in form modeler * Implement comprehensive test coverage - MaskedTextBoxFieldDefinitionTest: 6 tests for field properties, equals/hashCode, serialization - Fix equals/hashCode implementation with proper ID and name handling - All tests passing with 100% success rate Resolves: MaskedTextBox field type implementation for Business Central forms
- Add MaskedTextBoxFieldDefinition with masking properties (maskingCharacter, maskingStartIndex, maskingFromStartLength, maskingFromEndLength, isMaskedInDB) - Implement MaskedTextBoxFieldProvider for field registration and management - Add MaskedTextBoxFieldType with proper @portable annotation for serialization - Create service provider file for FieldProvider discovery - Ensure proper CDI bean registration in BackendFieldManagerImpl - Support minLength validation and placeholder functionality - Enable MaskedTextBox fields to appear in Form Controls Palette and work in Business Central UI This enables data privacy protection through configurable text masking in jBPM forms.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds comprehensive support for custom MaskedTextBox form fields in KIE Server REST API responses, enabling full feature parity with Business Central UI.
New Functionality Added
1. JSON API Support for MaskedTextBox Fields
minLength,maxLength,maskingCharacter,maskingStartIndex,maskingFromStartLength,maskingFromEndLength,isMaskedInDB2. HTML API Support for MaskedTextBox Fields
3. Complete Property Support
Technical Implementation
Backend Enhancements
Frontend Enhancements
Benefits
How to backport a pull request to a different branch?
In order to automatically create a backporting pull request please add one or more labels having the following format
backport-<branch-name>, where<branch-name>is the name of the branch where the pull request must be backported to (e.g.,backport-7.74.1.Finalto backport the original PR to the7.74.1.Finalbranch).Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.