Skip to end of banner
Go to start of banner

22.2 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 10 Next »

New and Improved Features


New Features

Enhancements

Usability

Technical

  • DAP-6769 - .NET Core version 3.1 to 6.0 Upgrade (DAPI & MAPI)
  • DAP-6831 - xUNIT - .NET UNIT Testing Framework Implementation in AppBuilder Microservices
  • DAP-6830 - Jest - React UNIT Testing Framework Implementation in AppBuilder

DAP-6758 - Enhanced Related Data Control - Ability to create a record and link it

Existing System: Currently, we would only be able to search a record and link. 

Purpose: User should be able to add a record and link with smoother navigation.

Enhanced System: The user would be able to: 

  • Create a record from the parent form without any hassel.
  • On save, the record not only gets saved but also is linked to the parent record where it is referenced.
  • This feature is configurable. All existing apps would be defaulted to "Search" only option.
  • Users can modify the app and select "Both - Search & Add", or only "Add". 

Impacts on existing forms: No

Available in Mobile: Yes.

Details screen changes: 

MobileWeb


Configuration: 


Back to top

 DAP-7051 - Flexibility to download attachments from notification

Existing System: Currently, we don't have an option to download an attachment from notification. 

Purpose: To access attachments from notification. 

Enhanced System: 

  • Users would be able to download the attachments from notification.
  • If an upload control is configured in a notification, then a hyperlink is made available. 
  • On clicking the hyperlink of the attachment, it would redirect user to our processmap application and ask for authorization. 
  • Once authorized, the attachment automatically downloads. 

Impacts on existing forms: No impact. 

Available in Mobile: NA 


Back to top

 DAP-6793 - Physical Demand Analysis(PDA) App Integration with Occ. Health

Existing System: We currently don't have a solution for capturing PDA metrics.  

Purpose: To provide the ability to capture and compare the PDA metrics against the employee job requirements. 

Enhanced System:

  • User would be able to enter physical, environmental, and cognitive metrics for every job classification. 

  • Medical staff would be able to associate the PDA records with the employee restriction summary record. 
  • Once the association is done, the system would generate the comparison report between the restrictions identified and the PDA. 
  • This report would help the supervisor to decide whether the employee is fit for the job role. 
  • Users would also be able to navigate to the associated PDA record from occ. health module with a single click. 

Impacts on existing forms: No impact 

Available in Mobile: NA 


Back to top

DAP-7007 - Introduced "Users By Role" Datasource 

Existing System: Currently, we have only "Users By Group" data source. 

Purpose: To be able to select the users with the help of role filter. 

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. 


Back to top

DAP-7127 - Usability changes to "Field Settings" option in manage data sources

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. 

Impacts on existing forms: No impact 

Available in Mobile: NA.


Back to top

DAP-7008 - Ability to concatenate (or show as a sub-label) 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. 




Back to top

 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. 



Back to top

DAP-5944 - Andriod - iOS usability gaps 

Existing System: Currently, we have few usability gaps. 

Purpose: To improve the usability of 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. 
  • DAP-4893 - Andriod - Segmented Control Changes - Values with long text are getting truncated
  • DAP-5786 - Andriod - Tree View Control changes for Inactive parent nodes

Impacts on existing forms: No. 

Available in Mobile: Yes, supported now in both iOS and Android. 



Back to top

DAP- 6342 - Ability to add "Empty/Not Empty" conditions on system-generated Id field

Existing System: Currently, user would not be able to configure actions for system-generated Id control. 

Purpose: To provide flexibility to configure actions that are "Save-Dependant". 

Enhanced System: User would be able to: 

  • Configure 'Empty' or 'Not Empty' based conditions for a System Generated Id.
  • If a user wants to have the application behave differently after record save, then this configuration will be much helpful as a system-generated Id gets generated when users hits save.
  • So, any condition like "Id is Empty" is configured means the behavior is applicable for record create scenarios. 
  • Similarly, any condition like "Id is Non-Empty" is configured means the behavior is applicable to all existing records which are already created and user wants to update it.

Impacts on existing forms: No

Available in Mobile: Yes on both iOS and Andriod.



Back to top


DAP- 6341 - Introduced a configuration for "Public/ Anonymous Document Link"

Configurable: Yes

  • Title 1:EnablePublicLink
  • Public/Private: Yes
  • Default: No

  • Title 2:AppBuilderUser

  • Public/Private: Yes
  • Default: Blank

Existing System: Currently, we have this functionality available without configuration abilities. 

Purpose: To provide configuration. 

Enhanced System: The user would be able to: 

  • Show/Hide the public notification link in the notification builder using "EnablePublicLink" custom setting. If value is set to "Yes" then public link would be shown. 
  • "App Builder User" custom setting will be used to set a particular user as the public user. We need to provide the User Id as the value to the custom setting. 

Impacts on existing forms: No

Available in Mobile: NA. 


Back to top

DAP- 5629 - Save only edited fields data (Parallel Users Case)

Existing System: Currently, when two users are updating the same record, data is getting overwritten. 

Purpose: To prevent data loss. 

Enhanced System: Changes include 

  • System would save only edited fields data and this will help users to prevent data loss if they edit fields of different sections. 
  • Apps that have Multi-approval workflow or Multi-Access configuration on different sections can take advantage of this feature. 

Impacts on existing forms: No

Available in Mobile: Yes, supported on both iOS and Android. 

Back to top

DAP- 6444 - Ability to record the source (iOS/Andriod) when a record is created/updated from mobile

Existing System: Currently, in the backend we save only whether the record is created/updated from web/mobile. 

Purpose: To uniquely identify the source (iOS / Andriod) for analytics or issue investigation. 

Enhanced System: Changes include

  • Differentiate the record which is created/updated from the android app and iOS app.
  • In the backend, the system would capture the source information. 

Impacts on existing forms: No

Available in Mobile: Yes, supported on both iOS and Android. 

Back to top

  • No labels

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