Documentation of differences in app implementation from web
- Thomas Speekenbrink
| Sl.No | Mobile app | Web app |
|---|---|---|
| 1 | Week starts from Monday to Sunday | Week starts from Sunday to Saturday |
| 2 | No custom week configuration available | Custom week configuration available. https://finance.visma.net/0815071046/(W(1))/Main?CompanyID=InfoBridge+Dev&ScreenId=EP101000 |
| 3 | Item added in summary tab for multiple days and edited in mobile app for any one of the day — it makes changes to all the days and not just to the day where it was edited | Item added in summary tab for multiple days and edited in details tab for any one of the day — It splits the item to effect the changes made to particular day |
| 4 | ADD new time Card: Default Project and project task not populated for earning type set in preferences. | ADD new time Card: When earning type selected in time card, populates default project and project task based on settings in preferences |
| 5 | Billing type not being enabled by default | Billing type will be enabled by default when Earning type and project has setting for time card to be billable |
| 6 | Mobile app restricts billable option for earning type if preference setting has it disabled | Web app still allows user to select billable option even if Earning type in preferences is disabled for billable |
| 7 | Disabling Advance financials from "Ënable Disable Features"– Time card still accessible | Time card is not accessible if Advanced Financials is disabled from "Ënable Disable Features" |
| 8 | Time activity added from "Employee Time Activities" for any date on web — Total not getting updated in mobile, nor is the record added visible. https://finance.visma.net/0815071046/(W(9))/Main?CompanyID=InfoBridge+Dev&ScreenId=EP307000 | Time activity added from "Employee Time Activities" for any date on web ---- Total getting updated. Record getting displayed in details tab. Record sometimes displayed with numerous duplicates, sometimes not in summary tab. Also when Activity is added from Time card on web from details tab, mobile app seems to work fine. But with existing duplicate issue, it is acting weird at times |
| 9 | User is not able to search for Suspended project in time card, and this is according to Functional design document which states projects only with active status will be displayed. (Note: But if the suspended project appears in recent searches, user can save the time card as in the web) | User is able to fetch suspended projects and add time card to it if the project has a active task under it. |
| 10 | Edit existing time Card: If default project and earning type is set for earning type preferences, on edit of any time record, changing the earning type changes the project value and task automatically on save in mobile app. But user is not shown the changed values in edit mode, on save the changes are saved in background. | Edit existing time Card: If default project and earning type is set for earning type preferences, on edit of any time record, changing the earning type changes the project value and user is highlight to project value. User can change the value and save the time entry. |
| 11 | It is possible to have different email address for employee and user. User is linked with an employee on web. The mobile app uses email address from employee page, whereas user logs in with email address set for user. This way the app does not know if the user has the appropriate access to time card and thus restricts user. So we need to ensure email address is same at both places |
Sl.No 3, 4, 5, & 6 ---- As per the design discussed with Cu.
Sl.No 1 & 2 — This is according to standards. Mobile app has its restrictions when implementing.
Impact of difference in 1 & 2:
The web application differs from mobile app while representing the dates in the week.
The dates in the week in web app starts from Sunday to Saturday or can be customized.
The dates in the week for mobile app starts from Monday to Sunday
This above approach has a drawback.
When user enters time for Sundays in mobile app for any week (for example: on 30/06/2019), it stores value in 23/06/2019 in web app.
Total hours in week displayed is same, but consideration of week length is different. It will also confuse the user when they refer from mobile app to web app, or when they enter values for Sunday's.
Expected:
To document and let the Cu knows about the mismatch.
As our app follows the standards, and we will be following this approach, it should not create problem in future. If concern is raised and has to be fixed either in web app or mobile app, it becomes tedious and troublesome to understand which dates the hours were logged.