New and Improved Features
...
- DAP-3811 - Enable New Persistence Feature
- DAP-3804 - Performance Improvement - Home Page, Details, List Screens, PDF and Excel Exports.
Enhancements
- DAP-3711/ DAP-3896/ DAP-3821 - Action Item Changes - Enable Action Item Id, Asset and Department fields for app builder module
- DAP-3755 Configure a system default summary with top 5 fields
- DAP-3788 Enhance the System Id format to include Location Name
- DAP-3928 Changes to the department data source in app builder to show only departments type with "BU"
- DAP-3693 Ability to populate the default status as "Open" for an action item created in App Builder
- DAP-3691 In Apps List Screen, the column header should freeze when scrolling down through the record list
- DAP-3827 Correct the auto search engine flaw to exclude the value Id's
...
Configurable: Yes from backend.
- Title: NA
- Public/Private: NA
- Default: NA
Existing System: Currently, we don't have this feature.
Purpose: To provide the ability to conduct by employee audit and by asset audit.
Enhanced System: Changes include:
- Introduce a new field - "Audit Sub-Type" with values - Asset, Employee and Department.
- This new field would be available for Basic Audits, Advanced Audit and Audit Templates.
- It would be available only for Site Audits and it would be a non-mandatory field.
- On selecting the audit subtype, the user would see a picklist for him to select Department or Asset or Employee based on the subtype selected.
- Currently, we have a field "Audit By Department - Yes/No". This field would be deprecated.
- Users, would be able to fill the questionnaire by asset or employee.
Impacts: Mobile, Reports and BI.
Creating Audit:
Questionnaire Screen:
...
Configurable: Yes
- Title: DynamicIAuditInternalIDFormat
- Public/Private: Private
- Default: Country Code - Location Code - Audit Create Year(YY) - Audit Type( C or S ) - Sequence by Location and Year
Existing System: Doesn't have any system generated Id
Purpose: To uniquely identify an Audit
Enhanced System:
- Audit ID would be generated for every Audit by Location.
- The default format would be - Country Code - Location Code - Audit Create Year(YY) - Audit Type( C or S ) - Sequence by Location and Year
- System would support ID format configurations like Location Name/Code, Calendar/Fiscal Year, Delimiter Configuration and Audit Type Code.
- Audit ID would be displayed across the module in all relevant screens and Audit Header as shown in the screen shot below.
Impacts: Mobile, Reports, BI.
Display in List Screen:
Display in Audit Top Header:
...
Configurable: No
- Title: NA
- Public/Private: NA
- Default: NA
Existing System: There is no provision to configure alerts and reminders.
Purpose: To give more flexibility in notifications.
Enhanced System: User would be able to create
- Audit Alerts and Reminders configurations would have below fields to setup
- Audit Start Date, Audit End Date, Audit Program Status configured.
- Finding Alerts and Reminders.
Impacts: No Impact
Notifications List Screen:
Existing Event Notifications Configuration:
Audit Reminders:
Audit Alerts:
Finding Reminder:
Finding Alerts:
...
Configurable: Yes from backend.
- Title: NA
- Public/Private: NA
- Default: NA
Existing System: Currently, we don't have this feature.
Purpose: To provide the ability to conduct by employee audit and by asset audit.
Enhanced System: Changes include:
- Introduce a new field - "Audit Sub-Type" with values - Asset, Employee and Department.
- This new field would be available for Basic Audits, Advanced Audit and Audit Templates.
- It would be available only for Site Audits and it would be a non-mandatory field.
- On selecting the audit subtype, the user would see a picklist for him to select Department or Asset or Employee based on the subtype selected.
- Currently, we have a field "Audit By Department - Yes/No". This field would be deprecated.
- Users, would be able to fill the questionnaire by asset or employee.
Impacts: Mobile, Reports and BI.
...
Configurable: Yes from backend.
- Title: NA
- Public/Private: NA
- Default: NA
Existing System: Currently, we don't have this feature.
Purpose: To provide the ability to conduct by employee audit and by asset audit.
Enhanced System: Changes include:
- Introduce a new field - "Audit Sub-Type" with values - Asset, Employee and Department.
- This new field would be available for Basic Audits, Advanced Audit and Audit Templates.
- It would be available only for Site Audits and it would be a non-mandatory field.
- On selecting the audit subtype, the user would see a picklist for him to select Department or Asset or Employee based on the subtype selected.
- Currently, we have a field "Audit By Department - Yes/No". This field would be deprecated.
- Users, would be able to fill the questionnaire by asset or employee.
Impacts: Mobile, Reports and BI.
...
Configurable: Yes from backend.
- Title: NA
- Public/Private: NA
- Default: NA
Existing System: Currently, we don't have this feature.
Purpose: To provide the ability to conduct by employee audit and by asset audit.
Enhanced System: Changes include:
- Introduce a new field - "Audit Sub-Type" with values - Asset, Employee and Department.
- This new field would be available for Basic Audits, Advanced Audit and Audit Templates.
- It would be available only for Site Audits and it would be a non-mandatory field.
- On selecting the audit subtype, the user would see a picklist for him to select Department or Asset or Employee based on the subtype selected.
- Currently, we have a field "Audit By Department - Yes/No". This field would be deprecated.
- Users, would be able to fill the questionnaire by asset or employee.
Impacts: Mobile, Reports and BI.
...
Configurable: Yes from backend.
- Title: NA
- Public/Private: NA
- Default: NA
Existing System: Currently, we don't have this feature.
Purpose: To provide the ability to conduct by employee audit and by asset audit.
Enhanced System: Changes include:
- Introduce a new field - "Audit Sub-Type" with values - Asset, Employee and Department.
- This new field would be available for Basic Audits, Advanced Audit and Audit Templates.
- It would be available only for Site Audits and it would be a non-mandatory field.
- On selecting the audit subtype, the user would see a picklist for him to select Department or Asset or Employee based on the subtype selected.
- Currently, we have a field "Audit By Department - Yes/No". This field would be deprecated.
- Users, would be able to fill the questionnaire by asset or employee.
Impacts: Mobile, Reports and BI.
...
Configurable: Yes from backend.
- Title: NA
- Public/Private: NA
- Default: NA
Existing System: Currently, we don't have this feature.
Purpose: To provide the ability to conduct by employee audit and by asset audit.
Enhanced System: Changes include:
- Introduce a new field - "Audit Sub-Type" with values - Asset, Employee and Department.
- This new field would be available for Basic Audits, Advanced Audit and Audit Templates.
- It would be available only for Site Audits and it would be a non-mandatory field.
- On selecting the audit subtype, the user would see a picklist for him to select Department or Asset or Employee based on the subtype selected.
- Currently, we have a field "Audit By Department - Yes/No". This field would be deprecated.
- Users, would be able to fill the questionnaire by asset or employee.
Impacts: Mobile, Reports and BI.
...
Configurable: Yes from backend.
- Title: NA
- Public/Private: NA
- Default: NA
Existing System: Currently, we don't have this feature.
Purpose: To provide the ability to conduct by employee audit and by asset audit.
Enhanced System: Changes include:
- Introduce a new field - "Audit Sub-Type" with values - Asset, Employee and Department.
- This new field would be available for Basic Audits, Advanced Audit and Audit Templates.
- It would be available only for Site Audits and it would be a non-mandatory field.
- On selecting the audit subtype, the user would see a picklist for him to select Department or Asset or Employee based on the subtype selected.
- Currently, we have a field "Audit By Department - Yes/No". This field would be deprecated.
- Users, would be able to fill the questionnaire by asset or employee.
Impacts: Mobile, Reports and BI.
...