...
Expand | ||
---|---|---|
| ||
Answer: The first thing to check is, in Workbench, are there duplicate contact records for the same person? If so, the time usually is going into Workbench however it's syncing against the non-employee personId (Same Name but inactive or supplier contact). This means that the costs on the Job will appear and show $0 (no employee class on non-employee person record). Prevention:
Remediation:
Integration Enhancements: We have made some updates recently to improve the integration to more accurately match the data for employee timesheets. We now validate:
This should address most of these issues where you may have an employee who works part time and is listed as a supplier contact, as well as duplication of contact records (multiple contact records for the same employee, inactive and active). See release notes: 4.5.40 - 24 Oct 2022 If you have this issue, please check the above and escalate to support if you need assistance. |
Expand | ||
---|---|---|
| ||
In the first instance you should backdate the Upvise Integration sync to ensure that any missing transactions are in workbench. Follow these steps below:
If the transactions still are not showing, further investigation should be completed to identify the root cause of the issue. Timesheets for people or plant entered via the daily diary, generate native transactions in the form of timelog in the timesheet module of Upvise.
2. If you cannot see timeslots here, you may need to check your daily diary form and ensure that its at an end state. This should either be “submitted” where there is no workflow on your form, or the last workflow state. 3. If you still cannot identify the cause of the issue, you should engage Workbench Support support@wbi.freshdesk.com |
User configuration
Expand | ||
---|---|---|
| ||
Removing an application on an individual user not only hides the app from showing in their menu, it also removes their ability to access the functions of that app. Example: if you turn off "Forms" in individual user application rights in Upvise, this means the user won't be able to create any forms across the entire database. The user will be presented with an error that looks like this when they try to ('ReferenceError: Can’t find variable: Forms CODE:' A solution to this is:
You can use the same logic across all apps. |
...