/
23.4 App Builder Release Notes
  • Ready for review

    • 23.4 App Builder Release Notes

    Owned by Vikram Vemula
    Last updated: Nov 15, 2023
    4 min read

    New and Improved Features


    New Features

    • None

    Usability

    Enhancements

    Mobile

    • None

     

    DAP-8766 - User would like to see App (Source) details in the Action Item Reference field

    Existing System: Currently, we support this feature only on mobile.

    Purpose: To improve usability and close the consistency gap between web and mobile.

    Enhanced System:

    Action Item List Screen Changes:

    • On clicking the hyperlink on the reference column, app record details screen opens up so that user can view the complete source information.

    • As this hyperlink is redirecting to app builder record, permissions would be evaluated and only if user has at least view app permission, then he would be able to see.

    • User would land back to the action item list on clicking 'Back'.

    Action Item Detail Screen Changes:

    • Currently, we only show 'Source Id' in the source details section.

    • With this enhancement, rest of the source information would be pulled from source record and will be shown in read-only mode.

    • As the source fields are not fixed, system dynamically pulls “Top 5” fields configured in summary builder as the source information.

    Impacts on existing forms: No

    Supported on Mobile: Yes, this feature was originally released in mobile. In this version, we closed the web gap.

     

    List Screen Navigation:

    Opening Record Details in the Pop-Up:

    Displaying full source information in the “Action Item Details>Source Details” section:

    Back to top

    DAP-8754 - Ability to restrict the display of access-based field data in the list and summary

    Existing System: Currently, we display the data in List as well as Summary even for the access-based fields.

    Purpose: To fix the security flaw in the system.

    Enhanced System: 

    • It has a new form property to restrict the access-based fields. By default, this property will be "No”.

    • Once an admin turns on this property as Yes, any columns configured in List and Summary will be removed.

    • Going forward, the user wouldn’t be able to configure any access-based field in List and Summary.

    • PDF export and Email me a Copy features also will not expose these access-based fields.

    Impacts on existing forms: No impact as we are turning them off by default.

    Supported on Mobile: Yes.

    Configuration in the Form Properties Screen:

    Example of an Access-Based Field:

    Back to top

    DAP-8759 - Refactoring “Form JSON” to make it lighter when we have Action Item controls

    Existing System: Currently, we have a very heavy form JSON, depending on the number of action item controls. 

    Purpose: To improve performance.  

    Enhanced System: In the enhanced system,

    • Form JSON is refactored in such a way that there will be a considerable reduction in size for any action item app.

    • This will improve the mobile performance as it has to download less data.

    Impacts on existing forms: Yes

    • As part of this refactoring, all existing action item controls display columns have been updated as given below

    • Customers can go ahead and overwrite this configuration as per their business needs.

    • This mandatory data correction for all apps was done as the structure to store action item controls within the form JSON was changed.

    Supported on Mobile: Yes. 

     

    Back to top

    DAP-8767 - Ability to set a limit to the number of controls that can be added to an app

    Configurable: Yes

    • Title: AppControlLimits

    • Public/Private: Private

    • Default: 2500

    Existing System: Users can add an unlimited number of controls to any app and this sometimes goes beyond what mobile apps can handle. 

    Purpose: To avoid performance and crash issues on mobile.  

    Enhanced System: Once a limit is set, the user will be able to

    • Add controls to an app only within the specified limits.

    • By this, we can be sure that we won’t have any performance lag on the mobile later on during the app usage.

    • If user is trying to create an app beyond the specified limit, system would allow the request but save the app as 'Draft'.

    Impacts on existing forms: None.  

    Supported on Mobile: NA. 

    Back to top

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