...
| Anchor | ||||
|---|---|---|---|---|
|
New Features
Mobile
DAP-8519 - iOS - Show loader when user clicks on create a new record
DAP-8563 - Provide Expand Sub-label support option for remaining Segmented, Toggle, and signature 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 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 |
|---|---|
 | .png?version=1&modificationDate=1695041699829&cacheVersion=1&api=v2) |
| Anchor | ||||
|---|---|---|---|---|
|
Purpose: To comply with data privacy regulations.
Existing System: Currently, we don’t have this feature. Purpose: To comply with the regulatory requirements.
Configurable: Yes
Title: EnableEncryption
Public/Private: Private
Default: False
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:
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.
Impacts on existing forms: No impact.
Supported on Mobile: NA.
...
| Anchor |
|---|
...
|
...
|
...
8518 - Android - When a field is disabled then show the background as grey to indicate that it is non-editable
Existing System: Currently, we have form settings tab on the 'Form Builder' page next to field propertiesthere is no style difference between a enabled control and a disabled control.
Purpose: To improve usability.
Enhanced System: In theenhanced system,
The form properties are moved to 'App Settings' page.
Form properties is the first tab where user can actually see all the controlsEnabled 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 this story only intends to move the controls for better usability is improved.
Impacts on existing forms: None.
Supported on Mobile: NA Yes.
Android (New Enhancement) | Web (Implementation Already Exists) |
|---|---|
.png?version=1&modificationDate=1695042316447&cacheVersion=1&api=v2) |  |
| Anchor |
|---|
...
|
...
|
...
8519 - iOS - Show loader when user clicks on create a new record
Existing System: Currently, we don’t have the option to remove an iconWhen the user is trying to open a heavy app, there is some delay after clicking the ‘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: User The user would be able to
remove an icon in the app studio by clicking on 'x' on Icon property dropdown in field propertiesSee a loader symbol once he clicks on the 'Create New Record' or Plus Icon seen on the list screen.
Once the app is re-savedloader ends, the icon wouldn’t be visible on iOS/Andriod devices.Device auto-adjusts the extra space and renders the form using the wide space now availableuser 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.
...
| Anchor |
|---|
...
|
...
|
...
Configurable: Yes
...
Title: SuperAdmins
...
Public/Private: Private
...
Expand Sub-label option for Segmented, Toggle, and Signature controls
Existing System: Currently, we don't have a configuration to set a user as super adminsub-label support for a few controls.
Purpose: To be able to configure super admin for apps, who can access all appsimprove usability and extend sub-label support for all the controls.
Enhanced System: Super admin User would be able to
Access all apps irrespective of whether an app is shared with him.
He would be able to Modify/ Delete an app that is not shared with him.
Super admin will also be able to access module-integrated apps as well on the home page and will be able to Modify/Delete.
Module-integrated apps will be displayed under a reserved category - “System Apps“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: NA.
...
Existing System: Currently, we cannot set minimum and maximum limits to time control.
Purpose: To enhance time control.
Enhanced System: The user would be able to:
Configure minimum and maximum limits which would be validated while entering data.
The limits could be a formula as well.
This will be optional property.
Impacts on existing forms: None.
Supported on Mobile: No.
...
Existing System: Recently, in v22.3 we have refactored the way data sources are downloaded on mobile. Click Here to go over the (Phase-1) release notes.
Purpose: To handle all the remaining scenarios where the user can directly land on the details screen.
Enhanced System: The improved system would handle the below-mentioned scenarios:
Navigation from email notification live link.
Navigate to the details screen by scanning QR Code.
Navigation from a parent form to a child form by using related data control.
Navigation from (Action Item Summary → Source Card) to source record details.
In all the above-mentioned scenarios, data sources download would be triggered only when user clicks on a particular app to eliminate the blank dropdown issue before landing on to the details screen.
Also, as we are downloading app-specific data only after clicking it, it is important to access a particular app in online mode at least once to be able to use it offline later.
Impacts on existing forms: None.
Supported on Mobile: Yes.
...
Existing System: Currently, there is no configuration to turn off data transfer from an outbound API.
Purpose: To be able to have better control on data export.
Enhanced System:
The system would provide a configuration to turn off outbound API data transfer by app.
For now, there is no UI for this configuration for an admin to change, but the technical team would be able to assist.
Impacts on existing forms: None. Default would be 'Yes'.
Supported on Mobile: NA. Yes.
Mobile (New Enhancement) | Web (Implementation Already Exists) |
|---|---|
 |  |