Anchor | ||||
---|---|---|---|---|
|
...
- MP-3548 Auto Upgrade of the app with every version release
- MP-2779 User would like to see the user log-in statistics for mobile
- MP-2768 BBS Mobile Pro Gap with BBS Web
- DAP-1747 Ability 1747 Ability to set values and support variables based on other control actions
- MP-3666 BBS 3666 BBS Mobile - Technical Gaps
- MP-3655 Work 3655 Work Area filter added for BBS for added for BBS Module
- MP-3497 Custom Settings Implementation for Behaviour Comments field to be in Sync with web for BBS Module
- DAP-1261 Forms and Records deleted in web should be synchronized in mobile by sync button
- MP-3656 Combination of filters in DAP
...
Anchor | ||||
---|---|---|---|---|
|
Default: Common change
Existing App
- There is no option to know if an updated app is available in stores
Purpose: To allow users to know if any new App has been published after 18.2.1 released on Aug 13th 2018
Enhanced App
- Users can download a new App from stores if any new app published after 18.2.1
- When new version is available in stores it will show an alert for Auto Upgrade of the app.
- On clicking on update users will be redirected to the Store page to update the App.
Anchor | ||||
---|---|---|---|---|
|
Configurable setting: Permission driven
Default: Common change
Existing App
- There is no option for user to get the customer log in statistics
Purpose: To allow users to get the customer log in statistics
Enhanced App
- Users to get the customer log in statistics
Anchor | ||||
---|---|---|---|---|
|
Configurable Setting: NA ,Product Level Change
Default :Department field to appear in observation details for both peer to peer and group
Existing System :
- Department field currently exist in Web but not in Mobile
Purpose :
•Gap
Enhanced System:
Department field would appear while creating observation for both group and peer to peer
- Department field would appear in observation filter
- Department would appear in observation list
Existing Data :Department field in observation detail would show blank
Impact :Mobile
Observation Detail
Observation List
Observation Filter
Anchor | ||||
---|---|---|---|---|
|
DAP-1747 Ability to set values and support variables based on other control actions
Configurable: NA
- Title: NA
- Public / Private: NA
- Default: NA
Existing System:
- We doesn't have the option to set a default value to a field when user is trying to add a new record to the form.
Purpose:
- Reduce the time to complete a form by auto populating logged-in user's data.
Enhanced System:
- User would be able to set a default based on logged in user's profile - (List of controls and options mentioned below).
- User would be able to set a default value based on the condition configured in actions - for Text box, Numeric and toggle controls.
Impacts: Mobile.
Anchor | ||
---|---|---|
|
...
|
...
|
...
Configurable setting: Permission driven
Default: Common change
Existing App
- There is no option to add and manage attachments to a Injury/Illness Incident Claims
Purpose: To allow users to add and manage attachments to a Injury/Illness Incident Claims
Enhanced App
- Users can add new attachments to a Injury/Illness Incident Claims
- Users can manage existing attachments of a Injury/Illness Incident Claims
-3666 BBS Mobile - Technical Gaps
1) Created Date and Updated Date Consideration missed
When Observation Created in Offline we are not considering the date when the user has exactly created, we are inserting when the request has arrived to DB. We need to consider date passed from UI
2) Inactive look ups not considered
For ex: After creation of Observation the made shift mapped to that observation as inactive from setup them when we open this observation from mobile the shift drop-down will come empty. Generally for created ones even the lookup was in active we need to display
3) Source Identification
Need to plan to know from which source the observation created (Web/iOS/Android/Windows)
Anchor | ||||
---|---|---|---|---|
|
...
Configurable setting: Permission driven
Default: Common change
Existing App
- There is no option to convert an existing Near Miss Incident to different Incident Type
Purpose: To allow users to convert an existing Near Miss Incident to different Incident Type
Enhanced App
- Users can convert an existing Near Miss Incident to different Incident Type
...