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
Existing System: Currently, we don’t have this feature.
Purpose: To 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 alert 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.
DAP-1694 - Move ‘Form Properties' to 'App Settings’ to improve usability
Existing System: Currently, we have form settings tab on the 'Form Builder' page next to field properties.
Purpose: To improve usability.
Enhanced System: In the enhanced system,
The form properties are moved to 'App Settings' page.
Form properties is the first tab where user can actually see all the controls.
There is no functional change and this story only intends to move the controls for better usability.
Impacts on existing forms: None.
Supported on Mobile: NA.
DAP-8466 - Option to remove icon for a control so that it doesn't render on mobile
Existing System: Currently, we don’t have the option to remove an icon.
Purpose: To improve usability.
Enhanced System: User would be able to
remove an icon in the app studio by clicking on 'x' on Icon property dropdown in field properties.
Once the app is re-saved, 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 available.
Impacts on existing forms: None.
Supported on Mobile: Yes.
DAP-8315 - Ability to configure super admins for apps
Configurable: Yes
Title: SuperAdmins
Public/Private: Private
Default: 1000 (ProcessMap Admin)
Existing System: Currently, we don't have a configuration to set a user as super admin.
Purpose: To be able to configure super admin for apps, who can access all apps.
Enhanced System: Super admin 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“.
Impacts on existing forms: None.
Supported on Mobile: NA.
DAP-6902 - Introduce Min/Max limits for Time Control
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.
DAP-8196 - (Phase 2) Ability to sync data sources before rendering the details screen on mobile
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.
DAP-8051 - Introduce configuration to turn off outbound API by app
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.