AnchorTopTop

Image Removed

...

Anchor
Top Top

Image Added

New and Improved Features

New Features

1. Data Source Management
2. Data Source Filters
3. Customize the System/Auto Generated ID
4. Introduce new control Control-Tree view for showing the department hierarchy

5. Introduced - Summary Builder (Mobile)

6. Enhance Mobile List-View Builder to support two-column display - With with Action item countsItem Counts
7. Color coding for Segmented control
8. Information Guide Note
9. Ability to select "Icons" for fields

Improved Features

1. Record Level Permissions (Self & and Others)
2. Ability to sort and save the forms displayed on the apps' home
3. Persist the view (Card or List) selection by the user the 's apps' home
4. Hiding a form in mobile and display only on the web (restricted access of apps)
5. Adding App roles as a data source and adding Role Id ID column to user data source
6. Inactive lookups should show as strikeout in the list screen
7. Show Record Created By and Date, Updated By and Date in the list view along with the locationLocation
8. Enhance Image control Control to support uploading attachments

Usability Changes (Mobile)

1. Show progression in an app
2. Landing Page for the app
3. Reviqo Apps Page with the record count
4. Make section separator more pronounced section separator
5. Show location name in All ScreensLocation Name in all screens
6. Calendar Icon to all pages except details
7. Dropdown control redesign
8. Toggle Button style changes
9. Show Only 5 Five Icons in Portrait and 6 Six in Landspace in a row for iPads with larger Image

...

1. Data Source Structure/Data Flattening
2. App Builder Microservices de-monolith changes.

Anchor
101 101

Data Source Management

...

• Add a multi-column data source.
• Easily access/add/manage all the data sources from "Manage Data Sources" screen.
•  Enhanced Import import data source feature. feature 
• Ability to build dependencies for custom data sources. sources 

Impacts to existing forms: 

• None.

Navigate to Manage Data Sources:

...

Add/Edit Data Source: (Note: Only Custom Data Sources can be edited/added)

Back to top

Anchor
102 102

Data Source Filters

Existing System: We currently don't have this feature. 

Purpose: Ability to filter the data source values. 

Enhanced System: User would be able to 

• Add filters to a control by selecting the values from the data source fields.
• Can apply Apply filters on both system and custom data sources.

Impacts for Existing forms: 

• No impact for existing forms as the filters would be blank. 

Back to top

Anchor
103 103

Customize the System/Auto Generated ID

Existing System: Currently, it appears as  <Formcode>-<YYYY>-<DAP>-<timestamp> - Example: "PTW-2020-DAP-0120020156499". 

Purpose: Ability to configure the system generated ID as per business needs. 

Enhanced System: 

1. User would be able to configure the format using the below options:
   • Country
   • Location Code
   • Form Code
   • Calendar Year
   • Fiscal Year
   • Timestamp
   • Sequence Number by Form
   • Sequence Number by Form by Location
   • Sequence Number by Form by Location by Calendar Year
   • Sequence Number by Form by Location by Fiscal Year
2. For new forms, the default format would be "@@Formcode-@@CalendarYear-@@Timestamp".

Impacts to existing forms: 

• The default format for existing forms would be "@@FormCode-@@CalendarYear-DAP-@@Timestamp". 
• As it is the current format, so there is no impact to existing forms data. 
• If user changes the format, it would apply to the records created going forward. 

Configuring ID Format in Builder:

Back to top

Anchor
104 104

 Introduce new

...

Control-Tree view for showing the department hierarchy

Existing System: Currently, it appears as a flat list in the drop-down. 

Purpose: To provide flexibility to user to select the right value using the hierarchy. 

Enhanced System: 

• User would be able to see the data in hierarchical view. view 
• Currently, this control would be only for single selection. selection 
• User would be able to select either the parent or child departments. departments 

Impacts to existing forms: 

• As this is a new control, user has to add this to the form to see it.
• Any other control configured with department control would behave as earlier as a earlier 

Configuring the control in the form:

...

Mobile:

Back to top

Anchor
105 105

 Introduce - Summary Builder (Mobile)

Existing System: Currently, we don't have summary screen for apps. 

Purpose: To provide a summary of the record without having to navigate to the details screen. 

Enhanced System: 

• User would be able to configure the fields which they want to see on summary. summary 
• User would also be able to see the Attachments, Action items, Repeaters and Related Data. Data 
• There would be additional options in the summary:
  • Export PDF
  • Duplicate
  • Email me a Copy. 

Impacts to existing forms: 

• All the fields configured for display in the List would come in the summary tooalso. User can change this by form. form 
• All the action buttons would be by default turned on. 
• (Attachment, Action Item...) Cards wouldn't be turned on.

Configuring the Summary in App Settings: 

...

Summary Page	Ellipse Options

Back to top

Anchor
106 106

 Enhance Mobile List-View Builder to support two-column display - With Action

...

Item Counts

Existing System: Currently, we don't have two column support for apps mobile list. 

Purpose: To improve the usability. usability 

Enhanced System: 

• User would be able to configure the fields in a two-column format. format 
• User would also be able to see the counts of Overdue and Open Action items. Items
• There would be additional icons icons:
  • Pin icon  icon - To to denote if there are attachments associated with that record. 
  • Sync icon -   To to denote if the record is not yet synced to server.  

Impacts to existing forms: 

• All the fields configured for display in the List would come in the summary tooalso. User can change this by form. form 
• All the action buttons would be by default turned on. 
• (Attachment, Action Item, etc...) Cards wouldn't be turned on. 

Form Builder Configuration: 

Mobile List Display: 

Back to top

Anchor
107 107

 Color

...

Coding for Segmented

...

Control

Existing System: Currently, we don't have color display for options in segmented color . 

Purpose: To improve usability. 

Enhanced System: 

• User would be able to configure colors for each of the individual values. values 
• On selecting a value, user would be able to see the color configured. 
• Default color would be "Standard Blue".
• This color configuration would be possible only in case of single selection. selection 

Impacts to existing forms: 

• All the existing forms segmented control colors would be defaulted to "Blue".

Back to top

Anchor
108 108

 Information Guide Note

Existing System: Currently, we don't have option to configure guide note for any field. 

Purpose: To improve usability. usability 

Enhanced System: 

• User would be able to configure guide note for the controls. Except Section, Repeater, Attachment controls, guide controls 
• Guide note can be configured for all the other controls. controls except Section, Repeater and Attachment controls 
• We have an option either to select "Custom Text" as a guide note or "URL". 
• Guide notes would display only in Mobile and not on web forms. 

Impacts to existing forms: 

• No impact.

Back to top

Anchor
109 109

 Ability to select Icons for fields

Existing System: Currently, default icons are assigned to each control. 

Purpose: To improve usability. usability 

Enhanced System: 

• User would be able to configure icons for the controls. controls 
• A library of icons is available for user to choose the icons. icons 

Impacts to existing forms: 

• All default icons are assigned to existing controls.

Back to top

Anchor
110 110

 Record Level Permissions (Self

...

and Others)

Existing System: Currently, there is no record level security applied to apps. 

Purpose: To enhance the security of apps. apps 

Enhanced System: 

• Admin user would now be able to further split permissions into "Self" and "Others" to view apps data. app's data 
• The same would be applied for form share as well.
• When "Others" permission is selected, the respective permission from "Self" would also get applied. 

Impacts to existing forms: 

• Both Self and Others would be selected for all the apps.

Security → Roles: 

Form Share:

Back to top

Anchor
111 111

  Ability to sort and save the forms displayed on the

...

app's home

Existing System: Currently, all apps are sorted by created by date. 

Purpose: To improve usability. usability 

Enhanced System: 

• Admin user would now be able to sort the forms as per his preference.
• Once saved, the apps would be displayed to all users in the same order.  order  
• Any new form created would be appearing appear on the top of the list.

Impacts to existing forms: 

• Existing apps would still be sorted by created date.

Back to top

Anchor
112 112

  Persist the view(Card or List) selection by user on the apps home

Existing System: Currently, card view is the default view for web and icon view for mobile.  

Purpose: To improve usability. 

Enhanced System: 

• User's last viewed option would now persist - If he selects the list view then every time the apps always shows the list view.
• Even on the web, the last viewed option would persist.  

Impacts to existing forms: 

• The default settings would apply and there is no impact to existing forms.

Back to top

Anchor
113 113

  Hiding a form in mobile and display only on the web (restricted access of apps)

Existing System: Currently, any would be displayed both on web and mobile. 

Purpose: To provide flexibility. 

Enhanced System: 

• Now, there is a new configuration (backend) to support show/hide of apps.
• Using this configuration an app can be hidden on mobile and can be available only on web.  

Impacts to existing forms: 

• All the existing forms would be available on both web and mobile as per the current configuration.

Back to top

Anchor
114 114

  Adding App roles as a data source and adding Role Id column to user data source

Existing System: Currently, we don't have roles as a data source. 

Purpose: To provide flexibility to filter users based on their roles. 

Enhanced System: 

• Admin user would now be able to configure "App Roles" data source to a control.
• Based on this control, he can configure an other control with "Users" data source
• User would be able to build dependency between both using the Role Id column. 

Impacts to existing forms: 

• None.

Back to top

Anchor
115 115

  Inactive lookups should show as strikeout in the list screen

Existing System: Currently, this implementation is only there for system lookups. 

Purpose: To improve usability. 

Enhanced System: 

• User would now be able to view all the inactive values in strikeout.
• This implementation is applicable both for web and mobile.  

Impacts to existing forms: 

• Data of the existing apps also would be shown in the striked-out format if the value is inactive.

Back to top

Anchor
116 116

  Show Record Created By and Date, Updated By and Date in the list view along with the location

Existing System: Currently, we don't have these as options in list to pull data. 

Purpose: To improve usability. 

Enhanced System: 

• User would now see additional options like Location Name, Created By, Created Date, Updated By and Updated Date.
• Once saved options to the view, the list would show these for each record available for that app.  

Impacts to existing forms: 

• These fields would be available for the existing apps as well.

Back to top

Anchor
117 117

  Enhance Image control to support uploading attachments

Existing System: Currently, image control has option to support URL. 

Purpose: To improve usability. 

Enhanced System: 

• Admin user would now be able to upload an image.
• This image would be rendered both on web and mobile.  

Impacts to existing forms: 

• No impact.

Back to top

Anchor
118 118

  Usability Changes to mobile App

Existing System: Currently, there are few usability gaps. 

Purpose: To improve usability. 

...

• Dropdown control redesign
• Toggle Button style changes

Landing Page: 

• Show the quick links for creating a new record, view records and manage action items. 
• Have "My ToDo" section with count of all action items. 

...

Impacts to existing forms: 

• No Impacts.

Back to top