New and Improved Features
Product Level
PMP-68070 : Rename Tag for both Employee and users to Observation By
Configurable
PMP-67739 :Multiple Sub Goal for a behaviour
PMP-68070 : Rename Tag for both Employee and Users to Observation By
Configurable Setting: Product Level
- Title: NA
- Private / Public: NA
- Default: NA
Existing System:
- For an observation on selecting Observer type, we get options to select the observer type by user, employee or other
- If employee is selected it populates the Employee picklist field with a tag as Employee Name
Purpose:
Enhanced System:
- Observer's field name to be changed to Observed By for both Employee, others and users
- Applicable to Peer to Peer and Group Observation
- Existing Data: No Change
- Impact: Mobile
Back to Top
PMP-67739: Multiple Sub Goal for a Behaviour
Configurable: Yes
- Title: IsMultipleSubGoalsApplicable
- Public / Private: Private
- Default: Single Subgoal
Existing System: Single subgoal for a behaviour can be defined
Purpose: unable to adress multiple subgoals on specific dates
Enhanced System:
- Multiple subgoals can be configured for a Behavior
- Subgoal fields: Sub-goal, Start Date, End Date, Status (values: active/inactive/habbit strength)
- Condition to add new sub-goal
- To existing sub-goal, user needs to enter the Sub-Goal End Date which would be mandatory, default to current date should not be less than start date
- Start date should not be greater than end date of one sub-goal
- If 2 sub-goals present, older with status inactive and newer with active. It will not allow user to edit the status for older
- New sub-goal start date to be greater or equal to old sub-goal end date
- Sub-goal status to be inactive
- Once a sub-goal status is habits strength, no additional sub-goals can be added
- Max 20 sub-goals can be configured for a behavior
- Sub-goals can be made inactive but cannot be deleted
- Existing Data: NA
- Impacts: Behavior List, BI, Frontline ADI report (would be completed by 23rd March, 2020)
Back to top