Skip to end of banner
Go to start of banner

22.3 App Builder Release Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 15 Current »

New and Improved Features


New Features

Enhancements

Mobile

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


Back to top

 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 

Back to top

 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. 


Back to top

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. 

Back to top

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: 

    1. Default Value

    2. Set maximum and minimum limits to numeric control

    3. In Action Conditions

    4. Set Actions

    5. Both Repeater and Sections.

Impacts on existing forms: No impact.

Available in Mobile: Yes.

Back to top

DAP-3846 - Provide Sub-label display support in Andriod

Existing System: Currently, we don’t have sub-label display support in andriod. 

Purpose: To improve usability.  

Enhanced System: Changes include:  

  • Sub-lables added in the form were previously not getting displayed on the android app. 

  • Now, user can see the sub-lables on app with this release. 

  • There is no additional configuration required for this enhancement. 

Impacts on existing forms: None.  

Available in Mobile: Yes. 

Back to top

DAP-1705 - Related Data Control Changes - Implement online search approach

Existing System: Currently, when user is searching for a specific record of related app, it only shows up if its already loaded on mobile device. 

Purpose: To improve usability of related data search.  

Enhanced System: 

  • If user is online, then he would be able to search across full list of records created for that app in that location.

  • Based on the search criteria of the related data control, mobile would make a database call to get the relevant records.

  • This way user doesn’t need to rely only on the device data but can link the record which he is looking for even though it is not present on the device.  

Impacts on existing forms: None.  

Available in Mobile: Yes. 

Back to top

DAP-7025 - iOS : Segmented Control Changes - Display complete text label without truncation

Existing System: Currently, We have this feature only on andriod and web. 

Purpose: To improve usability of a segmented control.  

Enhanced System: Changes include:  

  • Values with long text will no longer truncate.

  • The size of the control will be increased to accommodate the entire value.

  • This is already available in iOS and now will be available on andriod too.

Impacts on existing forms: None.  

Available in Mobile: Yes. 

Back to top

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: Available on Andriod. 

Supervisor Selection

Ability to see additional display value (Emp Id in the below example)

Back to top

  • No labels

© 2018 ProcessMAP Corporation, All Rights Reserved Confidential, may not be disclosed without the express permission of ProcessMAP Corporation