...
| Anchor | ||||
|---|---|---|---|---|
|
New and Improved Features
New Features
Enhancements
- Populate System
- Fix
Fix the design flaw with duplicate calendar categories for a single app
DAP-5315 -
EnhanceEnhance Formula Builder to include aggregate functions like Minimum, Maximum, Sum and Average
Mobile
DAP-3846 -
ProvideProvide Sub-label support in Andriod
DAP-1705 -
RelatedRelated Data Control Changes - Implement online search approach
DAP-7025 -
iOSiOS : Segmented Control Changes - Display complete text label without truncation
DAP-7306 -
AndroidAndroid : 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)
| Anchor | ||||
|---|---|---|---|---|
|
Existing System: Currently, we have a static action item screen that doesn't have configuration support.
...
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 calendaron calendar action
item permissionsitem 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 |
|---|
 |
 |
| Anchor | ||||
|---|---|---|---|---|
|
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 
...
| Anchor | ||||
|---|---|---|---|---|
|
Existing System: We currently populate 'Source Id' as 0 for all action items created from app builder.
...
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 where the action item was created.
Impacts on existing forms: For all existing records, the source Id would auto-populate.
Available in Mobile: Yes. 
...
| Anchor | ||||
|---|---|---|---|---|
|
Existing System: Currently, we have only "Users By Group" data source.
...
Enhanced System: Users would be able to:
Configure this data source to any single/multi-selection control.
Add a data source filter on a particular role so that they don't see the full user list.
While entering the data, only users belonging to a selected role will show up in the details screen.
Impacts on existing forms: No
Available in Mobile: Yes. 
...
...
| Anchor | ||||
|---|---|---|---|---|
|
Existing System: User would be able to change the data type of a column using field settings. Currently, this shows up as a button and on clicking opens up a po-up. 
...
Purpose: To improve the usage of the feature and help users configure the right data type for each column.
Enhanced System: The user would be able to:
Configure the data type of the column right in the grid without any additional click.
Users can expand/collapse the settings for usability.
Data type selection is mandatory and currently, it is defaulted to "String" for any new column.
Note: The data type selection option is only available while creating the data source, it cannot be modified for the existing data sources.
Note: If the proper data type is not selected it may not work in the formulas and when auto-populating the data into desired fields.
Impacts on existing forms: No impact
Available in Mobile: NA.
...
| Anchor | ||||
|---|---|---|---|---|
|
Existing System: Currently, the system displays data from a single data source column.
...
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. 
...
...
| Anchor | ||||
|---|---|---|---|---|
|
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. 
...
.png?version=1&modificationDate=1666358853694&cacheVersion=1&api=v2&width=1000)
...
| Anchor | ||||
|---|---|---|---|---|
|
Existing System: Currently, we have few usability gaps.
...
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 |
|---|
 |
 |
 |