New and Improved Features
Product Level Level
PMP-64082 Remove unused BBS menu
Configurable
MP-5328 Report By Name to be made mandatory / non mandatory configurable
...
Configurable :NA
- Title :NA
- Public / Private :NA
- Default : Unused items would be removed
Existing System: Few unused old menu in BBS
Purpose : Unused menu
Enhanced System:
- Unused menu are removed 1. Business Rule 2. Corporate Notification 3. Site Notification
- Existing Data : NA
- Impacts : NA
...
68070 : Rename Tag for both Employee and users to Observation By
Configurable
PMP-67739 :Multiple Sub Goal for a behaviour
Anchor | ||
---|---|---|
|
...
|
...
|
...
PMP-68070 : Rename Tag for both Employee and Users to Observation By
Configurable Setting: Customer specific Product Level
- Title: "IsReportByNameMandatory" ; Value : Yes - Mandatory , No - Non MandatoryNA
- Private / Public: PrivateNA
- Default: YesNA
Existing System :
Report by Name is mandatory in the both Peer to Peer and Group Observation for mobile . In last version it was made mandatory / non mandatory configurable in web
Purpose :
- Implement consistency as per web in mobile
Enhanced System:
- Report By Name field made mandatory /non mandatory configurable for both Group and Peer to Peer Observation in mobile
- Existing Data :No Change
- Impact :NA
...
- 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:
- Its confusing to users
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
BBS Stability Item
...
Anchor | ||||
---|---|---|---|---|
|
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)