| Anchor | ||||
|---|---|---|---|---|
|
...
DAP-2033 - Enhance Notification Manager - To provide ability to select recipient from fields of the formDAP-2149 - Notification Manager Changes - to include Action Items, Repeater, Text box Controls and Custom Data Sources
DAP-2065 - Enhance the Excel export list option - to include the repeater control fields
DAP-2050 - Change the approach of sharing a form when user is selecting a "Level" to share the form
Configurable
| Anchor | ||||
|---|---|---|---|---|
|
Configurable: NA
- Title: NA
- Public / Private: NA
- Default: NA
Existing System:
- The form header is occupying much of the space and because of this the usability of form builder area is affected
Currently, for notification recipients, user would be able to select only Location,User & Roles.
Purpose:
- Improve the usability of form builder screen by increasing the actionable space of the screen to 90%. To help users configure notification recipients dynamically from form fields.
Enhanced System:
- User would be able to see all the options in one screen and will be easier for building the form.configure recipients from form fields for the below controls
- Textbox with format as Email.
- Dropdown List, Single/Multi Auto Complete, Multi Choice - Where User/Employee system data source is configured.
- Any custom data source which has Email Id as lookup value.
- Any of the above fields if configured in a repeater section.
- Action item related fields (Owner, Assigned by, Verify Users and Completed By)
Impacts: None.
| Anchor |
|---|
...
|
...
|
...
2038 - Enhance the PDF Export of form details - Provide ability to configure the output in desired format
Configurable: NA
- Title: NA
- Public / Private: NA
- Default: NA
Existing System:
- Existing system provides ability to configure notification events but we cannot edit the template of notification. In existing system, user can get a PDF export of the form but he has no option to customize it.
Purpose:
- Provide an end to end notification manager so that user would be able to configure and manage different types of notifications. To help users to configure the Header, Report & Footer in desired format.
Enhanced System:
User In Enhanced System, user would be able to
...
to have static text or dynamic lables from the form fields.
- Configure header format where user can choose display fields as company logo, form title, report generated time along with other form fields.
- Configure report format where user can add grid formats to view the form data.
- Configure footer format where user can choose display fields as pagination and other form fields.
Impacts: None.
| Anchor |
|---|
...
|
...
|
...
2065 - Enhance the
...
Configurable: NA
...
Excel export list option - to include the repeater control fields
Configurable: Yes
- In form properties, a Toggle "List Drill Down Export" is introduced
- If this toggle is on, then all the drill down data would be exported.
- By default, this toggle would be off.
Existing System:
- In existing system, user would not be able to select the fields to be displayed on the list and wouldn't be able to set other preferences.
Purpose:
- Provide more user friendly interface to build the list screenexport fields inside the Repeater/ Action item/ Related document controls.
Purpose:
- Ability to export every field and also provide additional ability to import excel into Cognos.
Enhanced System:
In Enhanced System, user would be able to to export
- Define fields and set the order of display
- Define sorting rules
- Define data filtersAll fields inside Repeater control - Will be exported as a separate sheet.
- Action Item Fields - Will be exported in a separate sheet.
- Related Document Fields - will be part of same sheet but as a merged column.
Impacts: None.
...
| Anchor |
|---|
...
|
...
|
...
2050 -
...
Change the approach of sharing a form when user is selecting a "Level" to share the form
Configurable: NA
- Title: NA
- Public / Private: NA
- Default: NA
Existing System:
- In existing system, we don't have any version number associated with form definitions.
Purpose:
- Ability to track every form definition change by a versionhave only one tab "Locations" where user can share a form to either locations or Levels.
Purpose:
- To improve the usability and reduce the complexity of technical implementation.
Enhanced System:
- In Enhanced System, every change to the form definition would be tracked by a version number, we have two tabs - "Locations" and "Levels".
- In Locations tab, user would be able to select only scoped locations.
- In Levels tab, user would be able to select levels. Once a level is selected, the form gets shared to all locations under that level.
- This functionality is implemented in Share, Notification Recipients configuration.
Impacts: None.
| Anchor |
|---|
...
|
...
|
...
Configurable: NA
...
2011 User would like to configure Incident and Audit Findings as system data sources to forms in app builder
Configurable: Yes
- Title: Module Data Sources
- Public / Private:NA Private
- Default: NAHide
Existing System:
- In existing system, we don't have any differentiator to know the form status. Currently, these system data sources are not available in app builder to configure.
Purpose:
- Ability to identify form status on DAP homeTo help users associate a form's record with a incident or a finding.
Enhanced System:
...
- User would be able to see Incident and Finding as system data sources.
- The Incident data source has the following data points - Incident ID, Incident Title, Incident Date, Incident Description.
- Finding data source has the following data points - Finding ID, Finding Title, Finding Date, Finding Description.
- User would be able to configure them and build dependencies.
- Top 1000 records by created date in that location will be returned when user is associating a Incident or finding to a app builder record.
Impacts: NoneApp Builder Mobile.
