New and Improved Features
New Features
DAP-1946 - Integrate "Configurable Action Item" screen in app builder
DAP-5205 - Ability to set up app level default alerts and reminders for action items
Enhancements
DAP-7113 - Populate 'System generated Id' as 'Source Id' in Calendar list Screen
DAP-6920 - Fix the design flaw with duplicate calendar categories for a single app
Mobile
DAP-3846 - Provide Sub-label support in Andriod
DAP-1705 - Related Data Control Changes - Implement online search approach
DAP-7025 - iOS : Segmented Control Changes - Display complete text label without truncation
DAP-7306 - Android : Ability to concatenate another data source field in a dropdown
Technical
DAP-7454 - File Scanning while uploading attachments
PMP-87592 - .NET Core Upgrade from 3.1 to v6.0 (DAPI & MAPI)
DAP-1946 - Integrate "Configurable Action Item" screen in app builder
Existing System: Currently, we have a static action item screen that doesn't have configuration support.
Purpose: To upgrade app builder action item to a configurable action item framework.
Enhanced System: With this upgrade, user would be able to:
Turn on/off fields and features of action item screen.
Make fields mandatory and optional using the configuration.
Able to access latest CAPA features like - Due date extension, Verification, Asset Picklist integration etc.. .
Action item would now be access-driven - user would be able to create/ update action item only based on calendar action item permissions.
Impacts on existing forms: No
Available in Mobile: Yes.
Web Details screen:
Mobile Details Screen | Clicking 'View action item' will navigate to List Screen |
---|---|
DAP-5205 - Ability to set up app-level default alerts and reminders for action items
Existing System: Currently, we have alerts and reminders for each action item.
Purpose: To be able to set default alerts and reminders as well as default owners for all action items created for an app.
Enhanced System:
Users would be able to set a default alert and reminder for every action item created for a particular app.
We can even set a default owner for the action items created for that app.
This setup is available in the Location setup → Administration Setup → Module Defaults.
Impacts on existing forms: No impact.
Available in Mobile: NA
DAP-7113 - Populate 'System generated Id' as 'Source Id' in Calendar list Screen
Existing System: We currently populate 'Source Id' as 0 for all action items created from app builder.
Purpose: To be consistent with all modules and populate the system-generated id of the record as source id.
Enhanced System:
User would be able to see the actual record Id as source Id in action item list screen.
This would help users to identify the actual source record where the action item was created.
Impacts on existing forms: For all existing records, the source Id would auto-populate.
Available in Mobile: Yes.
DAP-6920 - Fix the design flaw with duplicate calendar categories for a single app
Existing System: Currently, duplicate calendar categories are getting created if an app is renamed.
Purpose: To always have a unique calendar category even if the form name is updated.
Enhanced System:
Calendar category creation logic has been enhanced so that its always unique for an app.
There wouldn’t be any duplicate calendar categories even though there are modifications done to app.
All existing action items are also remapped to one single category (which is the latest in use).
There will be no data loss because of this consolidation.
Impacts on existing forms: Yes, all action items are moved under latest category.
Available in Mobile: NA.
DAP-5315 - Enhance Formula Builder to include aggregate functions like Minimum, Maximum, Sum and Average
Existing System: Currently, there is no support for aggregate functions in the formula builder.
Purpose: To be able to support risk score calculations that are based on Minimum and Maximum.
Enhanced System: The user would be able to:
Configure a formula that involves calculating a Minimum/ Maximum (Num1, Num2, … Num n).
Even other aggregate functions - sum and average will be supported to improve usability.
The outcome of these functions will be a numeric value and the values configured inside an aggregate function should also be all numeric controls.
The functions should have all controls configured as comma-separated values.
These functions are be supported in:
Default Value
Set maximum and minimum limits to numeric control
In Action Conditions
Set Actions
Both Repeater and Sections.
Impacts on existing forms: No impact.
Available in Mobile: Yes.
DAP-7306 - Android : Ability to concatenate another data source field in a dropdown
Existing System: Currently, the system displays data from a single data source column.
Purpose: To improve usability of a dropdown control to display additional information.
Enhanced System: Changes include:
'Addtional Display Field' property added to every single/multi-auto complete control.
User would be able to configure an additional column of the same data source.
This column would be displayed along with the primary display column with a hyphen (Ex: 'Name' - 'ID').
Impacts on existing forms: This additional property will be blank for all the existing forms.
Available in Mobile: Not available. Feature implemented only on web.
DAP-6822 - Introduce a configuration to Include QR Code in the System Generated Report
Existing System: Currently, we don't have an option to print QR code in the report header.
Purpose: To improve the usability of PDF report.
Enhanced System:
Users have to switch to “System Defined Header (With QR Code)” for the existing forms.
PDF's generated going forward will have the QR Code printed on the header portion.
If any app doesn't need to have this feature, we can let the PDF remain as is with the default option - "System Defined Header".
Impacts to Existing Forms: No Impact.
Available in Mobile: Yes.
DAP-5944 - Andriod usability enhancements
Existing System: Currently, we have few usability gaps.
Purpose: To improve the usability of the android app.
Enhanced System: Changes include
The user would be able to now see the 'Static icons' configured for the fields now in android as well. (Already available in iOS)
Improve the usability of the 'Tree View Control' by displaying the parent nodes even though they are inactivated so that the tree structure is visible. However, they will not be available for selection. (Already available in iOS)
Improve the usability of the 'Segmented Control' - Values with long text will no longer truncate. The size of the control will be increased to accommodate the entire value. (This is not yet implemented in iOS)
Impacts on existing forms: No.
Available in Mobile: Yes.
Static Icons support for every field | Segmented Control | Tree View Control |
---|---|---|