Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Anchor
233
233
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

Anchor
4300
4300
DAP-4300 - Introduce the ability to ‘Mask’ a field

Existing System: Currently, we don’t have this feature.

Purpose: To comply with the regulatory requirementsdata privacy regulations.

Enhanced System:

  • 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 '**********'.

  • 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 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

  • 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 removedExisting 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.

...

Access Configuration:

...

Details Screen:

Web Screen

Mobile Screen

Image Modified

Image Modified

Back to top

Anchor
4332
4332
 DAP-4332 - Introduce the ability to 'Encrypt' data

Purpose: To comply with data privacy regulations.

Existing System: Currently, we don’t have this feature. 

Configurable: Yes

  • Title: EnableEncryption

  • Public/Private: Private

  • Default: False

Existing Enhanced System: Currently, we don’t have this feature. 

Purpose: To comply with the regulatory requirements.

Enhanced System: 

  • Has a new field property to encrypt data in an App. The default value of the Encryption ‘Encrypt’ 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 a maximum for of '5' controls per app. There would be a configuration in case this number has to be increased. Encrypted fields are not supported in Cognos reportsA configuration option is available to increase the limit.

  • Encrypt property is applicable only to controls below: 

    1. Textbox

    2. Textarea

    3. Numeric

    4. Date

    5. Time

    6. System Generated Id

    7. Signature

    8. QR Code

    9. 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.

Impacts on existing forms: No impact. 

...

Supported on Mobile: Yes. 

Android (New Enhancement)

Web (Implementation Already Exists)

Image Modified

Image Modified

Back to top

Anchor
8519
8519
DAP-8519 - iOS - Show loader when user clicks on create a new record

...

Supported on Mobile: Yes. 

Mobile (New Enhancement)

Web (Implementation Already Exists)

Image Modified

Image Modified

Back to top