19.2.1 App Builder Release Notes
- Vikram Vemula
New and Improved Features
New Features
- Form Versioning with roll back support
- Mobile - Picture Annotations
- Mobile - On-device PDF report generation and sending
- Mobile - Geo Tagging
New Controls
Improved Features
Introduce Sub label for repeater section to reflect in reports and details screen
Change in Data Saving/Notification Processing to be asynchronous
On Demand Load of System Data Sources like Employee, Users and Locations
Technical Enhancements
Port ReST services to micro services
New persistence structure for forms data
Mobile - App-level usage statistics
Mobile - Incremental data updates
Facelift Changes
- Apply New UI Styles Changes for App. Builder Screens
- Change the App Builder Home page card design to introduce buttons to navigate to List/Modify
- User would like to have an additional view of App Builder home page to see forms as List view
- Move "Actions" and "Share" sections under form properties to "App Settings" screen
- Move Form Access from form properties to field properties
- Introduce Preview button when user is in "App Settings" screen
- Consistency in Naming Convention for "Related Documents" control
- Mobile - Introduce Mobile landing page for ease of navigation to modules/apps
- Mobile - Changes in design for controls - Attachments/Repeater/ Related Links and Action items
- Mobile - Apply new UI styles for App Builder Screens
- Mobile - Show Form/App Icon in Home Page
Known Issues
- Restrict adding an action item twice in a section
- If a field label is updated, it would now reflect in "Notification templates" and "Report Builder template"
- Enhanced the Export PDF formatting issues related to Action Item/Related Documents
- Enhanced the formatting issues related to Excel Export - Related Links Inside a repeater
- Fixed all the downstream impacts related to deleting a section / Repeater section
Form versioning with roll back support
Existing System:
- Has basic form versioning support.
Purpose: To support dynamic form definition update with data security.
Enhanced System:
- Introduced a toggle to Turn on/off form versioning - By default it would be off.
- Once the form version toggle is on - user cannot turn it off.
- For the apps where form version is turned on, he would see any additional option "Show Earlier Version Controls".
- Show Earlier Version Controls - This option would help user to see old data associated with previous version controls.
- Handled all the down stream impacts to Actions, Access, Notifications, Reports, List Screen and field dependencies.
Impacts:
- All apps currently in production would default to - "Version 1".
- All apps will have the versioning toggle as "Off". User can turn on versioning for the necessary apps.
Form Properties:
Version list with "Roll back" option:
After Roll back:
Android Web View Support
Existing System:
- Has no Andriod support.
Purpose: To support apps on Android platform.
Enhanced System:
- User would be able to view all the apps on the android app home page.
- On clicking an app, user would navigate app List screen in Web View.
- User would be able to open an existing record or create a new record from the list.
- On landing to details screen, user would be able to modify/add the data.
Impacts: None
| Android App - Home | Details Screen |
|---|---|
|
|
Form Import and Export
Existing System:
- Currently, form import and export is done from backend.
Purpose: To reduce the support by providing an UI.
Enhanced System:
- User would be able to export an existing app.
- The app would get downloaded as a file with extension ".json".
- This file can be imported to any other site which is in the same product version.
- On import, form definition(not form data) would get imported.
- As a best practice, its good to have the below validations post import
- Data sources - Custom and System.
- Form Sharing.
- Actions.
- Access.
- Controls with related apps.
- Notifications Recipients.
- This option to Import/Export form definitions would be available only to process map administrator.
Impacts: None
Mobile List Builder
Existing System:
- Currently, the first four fields configured in the web are displayed in mobile.
Purpose: To provide flexibility to configure mobile list.
Enhanced System:
- User would be able to configure mobile list view with ability to set filter and sort criteria
- There is a configuration available to allow user to select the number of columns to be displayed in mobile.
- By default the number of columns is 4. User would be able to select maximum of 10 columns to be displayed on list.
Impacts: None
Form Properties:
Picture Annotations
Existing System:
- Currently, we don't have support to annotate pictures.
Purpose: To improve the usability.
Enhanced System:
- Once user attaches the picture, he would be able to edit it on mobile device.
- In edit mode, user would be able to annotate on the picture and add text as well.
- Post attaching the image, he can also add additional notes about the image.
Impacts: None
| Web | Mobile | Annotations |
|---|---|---|
|
|
|
On-device PDF report generation and sending
Existing System:
- Currently, we have this feature available only on web.
Purpose: To improve the usability in mobile.
Enhanced System:
- User would be able to download a PDF report in mobile (which is configured for the form in the report builder)
- User would be able to send the PDF report to via default mail engine configured in the device.
Impacts: None
Geo-Tagging
Existing System:
- Currently, we don't have this feature.
Purpose: To identify the location from which the record is created.
Enhanced System:
System captures the location coordinates(Longitude and Latitude) when the record is either added or edited from Mobile Device.
This feature will help to know from which regions most records are being added.
- This would be done only based on user preference. If user doesn't allow location capture, then the coordinates wouldn't be captured for that device.
Impacts: None
New Controls:
Video Control
Existing System:
- Currently, we don't have this control.
Purpose: To provide flexibility to configure videos in a form.
Enhanced System:
- User would be able to configure video URL's to a form.
- User would be able to view them in the details screen while filling the form.
Impacts: None
Image Control
Existing System:
- Currently, we don't have this control.
Purpose: To provide flexibility to configure static images in a form.
Enhanced System:
- User would be able to configure image URL's to a form.
- User would be able to view them in the details screen while filling the form.
Impacts: None
Signature Capture Control
Existing System:
- Currently, we don't have this control.
Purpose: To provide flexibility to capture signature from mobile device.
Enhanced System:
- User would be able to capture his signature using mobile device by finger or a stylus
- On clicking the sign button, the signature capture screen would open up.
Impacts: None
QR Code Control
Existing System:
- Currently, we don't have this control.
Purpose: To provide flexibility to scan QR code.
Enhanced System:
- On clicking the scan button, the QR Code capture screen would open up.
- Post scanning, the data would be stored as a string and shown against the record.
Impacts: None
Segmented Control
Existing System:
Currently, we don't have this control.
Purpose: To provide flexibility to configure sticky buttons for ease of use.
Enhanced System:
- User would be able to configure segmented control by selecting the data source.
- User would be able to select values for minimum selections and maximum selections for segments.
Impacts: None
Configuration:
Introduce Sub label for repeater section to reflect in reports and details screen
Existing System:
Currently, we have a default sub label for the repeater.
Purpose: To provide flexibility to configure sub label name.
Enhanced System:
- User would be able to configure sub label name for a repeater section.
- This sub label would appear in details screen and reports.
Impacts: None
Change in Data Saving/Notification Processing to be Asynchronous
Existing System:
Currently, while saving the data, we send the notification which increases the wait time to save.
Purpose: To reduce the save time and improve usability.
Enhanced System:
- With new data saving mechanism, user wouldn't see a reduced wait time.
- All the downstream actions like notifications and action items would be done asynchronously.
Impacts: None
On Demand Load of System Data Sources like Employee, Users and Locations
Existing System:
Currently, while loading every form, we load all the system and custom data sources.
Purpose: To improve the performance of the apps.
Enhanced System:
- System would load only those data sources which are required for the form.
- Because of this there would be a significant improvement in performance.
Impacts: None
© 2018 ProcessMAP Corporation, All Rights Reserved Confidential, may not be disclosed without the express permission of ProcessMAP Corporation