Release V9.2.6.8
New Terminal Support
Enhanced terminal management capabilities with new hardware options:
FEATURE
[UP-879]Added Support for Sunmi P3, P2 Lite SE and P3 Mix Terminals
Context: The system previously lacked support for the newest Sunmi terminal models (P3, P2 Lite SE, and P3 Mix), limiting available POS hardware options for merchants.
Solution: Implemented comprehensive support for Sunmi P3, P2 Lite SE, and P3 Mix terminal models by adding them to system classifiers and updating all relevant UI components.
Impact: Merchants and administrators can now order, configure, and manage the newest Sunmi terminal models through the UniPay Gateway, expanding the range of available POS solutions.
- Implementation Details
- Testing & Validation
- Database Changes
System Changes Overview
- Database Changes: Added new values to the terminal_data table's MODEL_CL column classifier (TerminalModelClassifier) for P3, P2 Lite SE, and P3 Mix terminal models
- Configuration Changes: Updated terminal model compatibility masks to include new models and reorganized model display order
- Code Changes: Modified UI components to display and support the new terminal models with proper alignment
- Filesystem Changes: None
- Data Migration: None
Implementation Actions
- Added three new terminal models to the TerminalModelClassifier system component
- Updated UI components to display the new models in proper order
- Enhanced UI layout with improved vertical alignment of model selection checkboxes
- Removed fixed height constraints from terminal model panel for better flexibility
Configuration and Access Steps
- Log in to the system as an administrator with access to terminal management
- Navigate to terminal configuration and management screens to verify new models
- Ensure all relevant user roles have proper access to new terminal models
- Navigation: Merchant Perspective > Terminals > New Terminal (Extended)
Test Scenarios
-
Terminal Model Selection Verification
- Steps: Navigate through all UI interfaces where terminal models can be selected and verify the new models appear in the correct order
- Expected result: P3, P2 Lite SE, and P3 Mix models appear in all dropdown lists and checkbox panels in the specified order
-
Terminal Creation and Initialization
- Steps: Create a new terminal with each of the new models (P3, P2 Lite SE, P3 Mix) and initialize them
- Expected result: Terminals are created successfully with correct model information and initialization completes without errors
-
Terminal Configuration Application
- Steps: Create terminal configuration targeting the new models and apply to corresponding terminals
- Expected result: Configuration parameters are correctly applied to terminals of the new models
Common Issues
- Model names may appear truncated in some UI panels if space is limited
- Vertical alignment issues might occur in terminal model selection panels
- Terminal model value might revert to incorrect value after initialization if terminal firmware isn't fully compatible
Potential Impact Areas
- Terminal Management: All terminal creation and configuration processes now include support for new models
- Order Processing: Equipment ordering flows now support selection of new terminal models
- Reporting: Terminal inventory and status reports will include new model types
Schema Updates
- No schema structure changes were made
- Added new values to the existing TerminalModelClassifier
- No database tables were modified structurally
Example SQL
-- Note: Actual implementation is through Java code in TerminalModelClassifier
-- This is a representation of the equivalent SQL operation
-- Adding new terminal models to classifier
INSERT INTO classifier_values (classifier_name, value_id, display_name)
VALUES
('MODEL_CL', 'p3', 'P3'),
('MODEL_CL', 'p2_lite_se', 'P2_Lite_SE'),
('MODEL_CL', 'p3_mix', 'P3_Mix');
Rollback Information
Rollback is possible with minimal impact as changes are additive rather than destructive.
- Remove any terminals configured with the new models before rollback
- Revert code changes in the TerminalModelClassifier to remove the new model values
- No database scripts are needed for rollback as changes were made through application code