...
| Anchor | ||||
|---|---|---|---|---|
|
New Features
None
Usability
DAP-4300 - Introduce the ability to ‘Mask’ a field
Mobile
DAP-8519 - iOS - Show loader when user clicks on create a new record
DAP-8563 - Expand Sub-label option for 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
...
8766 - The user would like to see App (Source) details in the Action Item Reference field
Enhancements
DAP-8754 - Restrict access-based fields to be configured as list columns
DAP-8759 - Refactoring form definition to make it lighter especially Action Item control
DAP-8767 - Ability to set limits in app builder features to avoid performance issues
Mobile
MP-10008 - Ability to replace a sub-label with a validation message to improve usability
Technical
DAP-8761 - Execution - Mongo DB Driver Upgrade to 2.22
| Anchor | ||||
|---|---|---|---|---|
|
Existing System: Currently, we don’t have this feature.
...
Has a new field-level property to mask data and it can be applied to all the controls except for Label, Video, Action item, Related Data, and Embedded Image.
Once masking is turned on for a particular field, then data will be masked and control will be displayed as '**********'.
Unmask Access: A new access configuration, 'Unmask,' has been added. Users with 'Unmask' access privilege can view the actual data behind the masked control(s).
Configuration Restrictions: Masked fields cannot be configured in the following areas:
List & Summary Views
Action Conditions, Notification Conditions & Set Actions
Formula Builder and Default Values
Existing App Data Masking: Data masking can also be enabled for fields in an existing App, once enabled data masking will be applied to all existing records within the app for the respective fields. Data masking cannot be enabled for fields in an existing App if the fields are already used in any of the areas mentioned in the above configuration restrictions.
Masked fields are not supported in Cognos reports.
Impacts on existing forms: No
Supported on Mobile: Yes.
Field Properties:
Access Configuration:
Details Screen:
| Anchor |
|---|
...
|
...
|
...
DAP-
...
8754 - Restrict access-based fields to be configured as list columns
Purpose: To comply with data privacy regulations.
...
Has a new field property to encrypt data in an App. The default value of the ‘Encrypt’ property will be "No".
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.
Encryption support will be a maximum of '5' controls per app. A configuration option is available to increase the limit.
Encrypt property is applicable only to controls below:
Textbox
Textarea
Numeric
Date
Time
System Generated Id
Signature
QR Code
Toggle
Existing App Data Encryption:
o Data encryption can be enabled for fields in an existing App, and it is applied to newly created records.
o Once enabled encryption property cannot be disabled.
o Technical assistance can be used to encrypt data in existing records for an existing App.
Encrypted fields are not supported in Cognos reports.
En
Impacts on existing forms: No impact.
Supported on Mobile: NA.
| Anchor |
|---|
...
|
...
|
...
8759 - Refactoring form definition to make it lighter especially Action Item control
Existing System: Currently, there is no style difference between a enabled control and a disabled control.
...
Supported on Mobile: Yes.
| Anchor |
|---|
...
|
...
|
...
8767 - Ability to set limits in app builder features to avoid performance issues
Existing System: When the user is trying to open a heavy app, there is some delay after clicking the ‘Create New Record’ option.
...
Supported on Mobile: Yes.
| Anchor |
|---|
...
|
...
|
...
MP-
...
10008 - Ability to replace a sub-label with a validation message to improve usability
Existing System: Currently, we don't have sub-label support for a few controls.
...