Note: All Due Dates are the Build Date. Those stories will be released to production when respective build is released. All user stories which has due date as 16th Aug will be available in Production on the date.
...
21.2 Apps HotFix Items
Product Level Change
- DAP-5693 Apply default list settings when user clicks "Save As" AppBuilder
- DAP-5563 Web - Tree View Control changes for Inactive parent nodes
DAP-5693 Apply default list settings when user clicks "Save As" AppBuilder
Configurable: NA
- Title: NA
- Public/Private: NA
- Default: NA
Existing System: Currently, when user creates a copy of default view, option Share with Global Users is defaulted to "Yes.
Purpose: To ensure that user unknowingly shouldn't share his view to all global users.
Enhanced System: When user clicks on "Save As" from a default view,
...
Impacts: No impact to existing forms.
DAP-5563 Web - Tree View Control changes for Inactive parent nodes
Configurable: NA
- Title: NA
- Public/Private: NA
- Default: NA
Existing System: Currently, when parent is inactive, we don't show the value.
Purpose: To ensure that user should be able to see the complete tree irrespective of status.
Enhanced System: User would be able to
...
Anchor | ||||
---|---|---|---|---|
|
Configurable: No
- Title: NA
- Public/Private: NA
- Default: NA
Existing System:
- The current reference & citation field doesn't allow to put a hyperlink
Purpose:
- To provide options to put hyperlinks for another reference website
...
Anchor | ||||
---|---|---|---|---|
|
Configurable: No
- Title: NA
- Public/Private: NA
- Default: NA
Existing System:
- As of now the Body Part widget does not have any navigation.
Purpose:
- Ability to drill down to see list of Incidents
...
Anchor | ||||
---|---|---|---|---|
|
Configurable: No
- Title: NA
- Public/Private: NA
- Default:
Existing System:
- As of now few Incident Severity fields were not added as columns in Manage Incident List screen
Purpose:
- Provide option to create view based on Severity
...
Anchor | ||||
---|---|---|---|---|
|
Configurable: No
- Title: NA
- Public/Private: NA
- Default:
Existing System:
- As of now "Is this Case Recordable According to Local Recordkeeping Requirements?" field is dependent on an OSHA recordable case classification
Purpose:
- Enable Non US locations to mark an Incident as recordable as per Local recordkeeping
...
Anchor | ||||
---|---|---|---|---|
|
Configurable: No
- Title: NA
- Public/Private: NA
- Default:
Existing System:
- As of now system does not enforce users to provide reason for classifying the Incident as "Not Recordable"
Purpose:
- Enforce users to provide reason
...
Anchor | ||||
---|---|---|---|---|
|
Configurable: Yes
- Title: FROI Claim Read-Only
- Public/Private: Public
- Default: No
Existing System:
- As of now the field can be made read only by defaulting the response to Yes for field "Would you like to submit a workers compensation claim?"
Purpose:
- Show claim sections by default so that users provide claim related information as well while filling the Incident Detail Report
...
Anchor | ||||
---|---|---|---|---|
|
Configurable: Yes
- Title: Display Root Cause Completion Date
- Public/Private: Public
- Default: No
Existing System:
- As of now system does not have an option to capture actual Root Cause Analysis completion date
Purpose:
- There are cases when Root Cause Analysis was completed on an earlier date was entry in the system was made later. In this case users need the ability to record actual RCA completion date
...
Anchor | ||||
---|---|---|---|---|
|
Configurable: Yes
- Title: Display Date Determined as Recordable
- Public/Private: Public
- Default: No
Existing System:
- Does not have a field that clearly indicates a date when 1st recordable case was created for an Incident
- All reports and data points in the system are driven by Most Severe Case or Current Case dates
Purpose:
- There is a need to track the date when the 1st recordable case was created in the system
- This may be different than actual case start date in case it was entered at a later time in the system
...
- Has an optional read-only field "Date Determined as Recordable" in Classification of Case screen
- The field is placed after "Is This a Company defined Recordable Case?"
- The field will be visible if "Is This a Company defined Recordable Case?" is answered as Yes
- System will automatically populate it with the date when first recordable case was created in the system for an Incident
- This is not the case date but the case created date
Impact: Cognos
Anchor | ||||
---|---|---|---|---|
|
Configurable: Yes
- Title: Display Activity involved when outside premises
- Public/Private: Public
- Default: No
- Title: Make employer premises address fields optional
- Public/Private: Public
- Default: No
Existing System:
- As of now there is no way to capture information if the employee was on duty out side the employer premises when the incident occurred
- Also there is need to make Address related field optional because in some cases exact address is not known
Purpose:
- Align it with Web and provide ability to capture if incident occurred on duty or after work from Mobile Pro
...
Anchor | ||||
---|---|---|---|---|
|
Configurable: NA
- Title: NA
- Public/Private: NA
- Default: Show Supervisor column in Session list
Existing System:
- Does not show Employee Supervisor in Session List
Purpose:
- Incomplete information
Enhanced System:
...
Anchor | ||||
---|---|---|---|---|
|
Configurable: Yes
- Title: EnableTrainingEffectiveness , Values = Yes / No .Yes = Field will be visible , No = Field will be hidden
- Public/Private: NA
- Default: No
Existing System:
- In 21.1 Training Effectiveness field was added in Session Details , Reports and Mobile
- But was not implemented in SOA and Import Template
Purpose:
- Gap
Enhanced System:
- Training Effectiveness will now appear in SOA and Import Template
...
Anchor | ||||
---|---|---|---|---|
|
Configurable: Yes
- Title: ProductTypeMandatory , Value = Yes / No , Yes = Mandatory / No = Non Mandatory
- Public/Private: NA
- Default: No
Existing System:
- Product Type Field in Chemical Request is non mandatory
Purpose:
- Customer specific usage
Enhanced System:
...