New and Improved Features
New Features
DAP-4300 - Introduce the ability to ‘Mask’ a field
DAP-4332 - Introduce the ability to 'Encrypt' data
Mobile
DAP-8518 - Android - When a field is disabled then show the background as grey to indicate that it is non-editable
DAP-8519 - iOS - Show loader when user clicks on create a new record
DAP-8563 - Provide Sub-label support for remaining Segmented, Toggle, and signature controls
Technical
DAP-7711 - .NET Core Upgrade from 3.1 to v6.0 (API)
DAP-7753 - App. Security-Checkmarx
Usability
None
Enhancements
None
DAP-4300 - Introduce the ability to ‘Mask’ a field
Existing System: Currently, we don’t have this feature.
Purpose: To comply with the regulatory requirements.
Enhanced System:
Once masking is turned on for a particular field, then data will be masked and control will be displayed as '**********'.
This applies to all existing data already entered for that app.
There is an additional security configuration for ‘Unmask’ access. Any user who has this access can see the actual data.
User wouldn’t be able to configure masked controls in all the below areas:
List & Summary Views
Action Conditions, Notification Conditions & Set Actions
Formula Builder and Default Values
Admins would be able to turn on Masking=Yes for any existing app.
However, if it's used in the above-mentioned screens, then the system will not allow to turn on masking unless the field is removed.
Masked fields are not supported in Cognos reports.
Impacts on existing forms: No
Supported on Mobile: Yes.
Field Properties:
Access Configuration:
Details Screen:
DAP-4332 - Introduce the ability to 'Encrypt' data
Configurable: Yes
Title: EnableEncryption
Public/Private: Private
Default: False
Existing System: Currently, we don’t have this feature.
Purpose: To comply with the regulatory requirements.
Enhanced System:
The default value of the Encryption property for all controls will be by default "No".
User would be able to turn on the encryption for control in the existing app and the data encryption support will be moving forward.
Once the encryption property is set as Yes, then there will be an alert to the user that he can't undo this change and the property will be disabled.
Also, if data was already reported for the control then there will be an alert - 'Data is already reported for this control. Please raise a technical assistance ticket to encrypt the existing data'.
Encryption support will be maximum for '5' controls per app. There would be a configuration in case this number has to be increased.
Encrypted fields are not supported in Cognos reports.
Encrypt property is applicable only to controls below:
Textbox
Textarea
Numeric
Date
Time
System Generated Id
Signature
QR Code
Toggle
Impacts on existing forms: No impact.
Supported on Mobile: NA.
DAP-8518 - Android - When a field is disabled then show the background as grey to indicate that it is non-editable
Existing System: Currently, there is no style difference between a enabled control and a disabled control.
Purpose: To improve usability.
Enhanced System: In the enhanced system,
Enabled control will be shown with a grey background indicating that it is not editable.
Android is now consistent with iOS and Web platforms on this representation.
There is no functional change and only the usability is improved.
Impacts on existing forms: None.
Supported on Mobile: Yes.
DAP-8519 - iOS - Show loader when user clicks on create a new record
Existing System: Currently, when user is trying to open a heavy app, there is some delay after clicking ‘Create New Record’ option.
Purpose: To improve the usability and indicate to the user that the system is trying to load something for him.
Enhanced System: The user would be able to
See a loader symbol once he clicks on the 'Create New Record' or Plus Icon seen on the list screen.
Once the loader ends, the user will be able to see the form that is ready for data input.
There is no functional change and a loader is introduced to indicate that form is being rendered.
Impacts on existing forms: None.
Supported on Mobile: Yes.
DAP-8563 - Provide Sub-label support for Segmented, Toggle, and signature controls
Existing System: Currently, we don't have sub-label support for a few controls.
Purpose: To improve usability and extend sub-label support for all the controls.
Enhanced System: User would be able to
See sub-labels for fields configured with Segmented, toggle, and signature controls.
This feature is now supported on both iOS and Andriod.
Impacts on existing forms: None.
Supported on Mobile: Yes.