...
| Anchor | ||||
|---|---|---|---|---|
|
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
| Anchor | ||||
|---|---|---|---|---|
|
Existing System: Currently, we can’t mask field datadon’t have this feature.
Purpose: To comply with the regulatory requirements.
Enhanced System: With this feature, user would be able to:
...
Share an app with a group of users.
...
Will be able to configure control-level access on a particular field/section to a group.
...
Will be able to send a notification to a group.
...
When a group is selected in all the above scenarios, location scope is always considered.
...
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:
...
| Anchor |
|---|
...
|
...
|
...
4332 -
...
Introduce the ability to 'Encrypt' data
Existing System: Currently, we don’t have a feature to upload images to the notification templatethis feature.
Purpose: To improve the usability of the notification template. comply with the regulatory requirements.
Enhanced System: The user would be able to
Turn on the encryption for any existing form and the encryption of data will be done moving forward.
If the encryption property is allowed to be set as true, then we need to
...
Upload a static image to the notification template.
Users can use this feature to make the template look more visual than printing plain text.
Supported Image types are: Jpeg, Jpg, Jpe, Jfif, Png, Gif, Bmp
Maximum Image Size allowed: 1 MBalert user that he can't undo this change - 'Encryption configuration can't be turned off later'.
The encryption property field would be disabled if the user turns it on.
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'.
The default value of the Encryption property is by default "No".
Encryption support will be maximum for '5' controls per app. There would be a configuration in case if this number has to be increased.
Encrypted fields are not supported in Cognos reports.
Impacts on existing forms: No impact.
Supported on Mobile: NA.
| Anchor | ||||
|---|---|---|---|---|
|
...