Upvise Integration

Overview:

For detailed information about Upvise as a service, see the https://webwbdoc.atlassian.net/wiki/spaces/UPVISE/pages/1222148099 space.

Below you will find information about the integration settings between Workbench and Upvise.

image-20240105-022915.png

Screen Guide:

Upvise Synchronisation with Workbench

Initial Configuration:

Please note that Data Entry and Job Costing and Finance licences or higher have full access to the screen. People with permission "Allow Upvise Integration” have access to the Last Update field, the "Export / Import" button, Save button, and the Fin Co Code combo.

image-20240108-220545.png
Data Entry & Job Costing View

 

 

Your Workbench Consultant will assist you with the initial integration configuration below:

  1. The Upvise Login and Password will be entered for each financial company.

  2. Once this is Saved the Status shows "Connected to Upvise"

  3. Leave Job: The job that any leave transactions should be recorded against.

  4. Invoice Sales Code: Default Sales Code that any Invoices being imported from Upvise will use.

  5. Allowance Activity: Default time type activity that allowance transactions will use when syncing from Upvise to Workbench. This may need to be created if it does not exist. This can be a standard time activity but to distinguish these allowances, it may be easier for reporting purposes to have an activity titled ‘ALLOW’ as the code or something similar.

  6. Plant Person:

    1. IMPORTANT this user is used to identify plant transactions that are to be imported as plant issues rather than time and plant transactions.

    2. Please setup a person called Plant(Firstname) Person(Last Name). This person does not need a licence but needs to be set up to ensure the plant issues are created without a user. The person can be set up as per below under people set up.

 

 

 

Your Workbench Consultant will assist you in defining what we are exporting to Upvise and importing back from Upvise on an hourly basis, details below.

 

Exports

  • Upvise Exports data every hour

  • This synchronisation can also be performed manually by clicking Export/Import.

Use setting 'Upvise Additional Fin Co Export Filtering' to limit data export to Upvise to only include data linked to the Finco indicated in the Integration screen. This will be applied to Companies, People, Plant tems/groups/locations, Stock Locations.

Exports

Controls & Settings

Exports

Controls & Settings

Companies

  • Tick ‘Other’ in company maintenance to enable a company to sync

  • Use setting Upvise Companies Sync Basis to control whether exporting Clients, Suppliers or All

  • Default if no value is populated is All.

Read More: https://webwbdoc.atlassian.net/wiki/spaces/UPVISE/pages/1222377486

People

  • Use setting Upvise People Sync Basis to control whether exporting Employees, Contacts or All

  • Default if no value is populated is All

  • If contacts and/or employee are to be exported, all of them are exported as they get updated in Workbench.

  • No specific flag needs to be ticked for these two entities to be included in the export.

  • Employees will sync with their timesheet group and default stock location.

  • These employees cannot login unless they have an Upvise licence associated with them

Read More: https://webwbdoc.atlassian.net/wiki/spaces/UPVISE/pages/1222377486 &

Jobs

  • tick ‘Requires Scheduling’ in job maintenance

  • The Project (Job) in Upvise will store work centers, stock locations, docket schedules, output schedules and any header jobs that the project is associated with

Read More:

Plant

  • Tick ‘Requires Scheduling’ in plant maintenance, required for any plant transactions to be generated from Daily Diary.

  • Plant Rate codes sync with the plant item.

Read More:

Schedules ( &

  • this will sync docket and output schedules associated with jobs, required for Daily Diary docket issues and output issues.

Stock

  • This will sync Stock locations and associated products. Please note Stock locations on the Job and Stock Locations on the users will be synced to the corresponding record. Required for Daily Diary Stock issues.

Frequent Job Sync

  • This synchronises Jobs every 5 minutes, helpful when many workbench jobs are being created on the fly.

Service Logs

  • Service logs will be exported to Upvise if they fit the following criteria:

    • Service log is created from email

    • Status is Allocated

    • Company field is populated

    • job code is populated

    • Service log is allocated

  • Service Logs export option will be available on the upvise integration control page when the control parameter 'Export Logs to Upvise' is set to Yes.

Read More:

 

 

Imports

  • Upvise imports every hour

  • This sync can also be performed manually by clicking Export/Import.

Imports

Controls & Settings

Imports

Controls & Settings

Datasheets

  • Syncs header datasheet data to records in Workbench – useful if users are not logging into Upvise and need to review header form information.

  • This will be visible on the linked record e.g. Job, Plant etc that the datasheet has been associated with.

  • Uses the Last Updated date in Upvise and only retrieves the latest 100 to avoid disconnected scenarios where thousands are synced at once

  • Allows Punch Item Imports into Punch item datatable

Timesheets

  • Syncs timesheets in Upvise entered via the timesheet module as well as those generated from Daily Diary or Time and Attendance forms.

  • Upvise Timesheet Syncing Basis determines the basis upon which timesheets will be imported

    • Daily: For use with crew timesheets, will sync any timesheet entry that is created (or modified?) after the Upvise Last Update Date

    • Submit: For use with weekly timesheets or other systems where staff will Submit their timesheet on Upvise when satisfied with it. Will sync timesheets where the submitted date is after the Upvise Last Update Date

  • Attendance data can be populated into the timesheet attendance table in workbench using the “Daily Scan” forms in upvise.

AR Invoices

  • Syncs AR Invoices generated in Upvise

Plant Items

  • Allows Plant Meter readings to be imported

  • Allows plant Driver to be imported via Driver Change form

  • Allows Plant Location to be updated via Plant Movement forms

  • Allows Plant Project to be imported, defined via the allocate to project function in Upvise

Read More:

  • Dockets are supported for import into Workbench Via the Daily Diary form set.

    • Forms must be at an end state to be imported

  • Dockets can be generated via a Job linked diary or a project linked diary in upvise.

  • Plant Outputs are importable via the Plant Return form. see

  • Outputs are supported for import into Workbench Via the Daily Diary form set.

    • Forms must be at an end state to be imported

  • Outputs can be generated via a Job linked diary or a project linked diary in upvise.

Stock

  • Stock issues, Stock Adjustments and Stock Transfers are supported for import into Workbench Via the Daily Diary form set.

    • Forms must be at an end state to be imported

    • Support using Sub Project field on all transactions

Leave

  • Allows Leave Applications to be imported via the Leave Application form in Upvise.

  • Form must be submitted and date after last update date 

Service Logs

  • Upvise Job Integration Scenarios to Workbench Logs:

    • Job only has Equipment Attached, this will create a Plant Log in Workbench

    • Job has Project and Equipment Attached, this will create a Job log in Workbench

    • Job has Project Attached, this will create a Job log in Workbench

    • Job has a Site Attached, and the Site is linked to a Project in Upvise, this will create a Job log in Workbench

  • Attachments sync and attach as a PDF to the log in workbench.

 

Read More:

Purchase Orders

  • Only imports forms that have been submitted/reached the final stage of their workflow.

  • Support using Sub Project field

  • Upvise PO attachments import to Workbench PO header attachments

  • Purchase Order Types supported:

    • Project Purchase Order: Po’s linked to Projects in Upvise, will sync as a Job Purchase order in workbench

    • Job Purchase Order: PO’s attached to an Upvise Job, will sync as a Service log PO in workbench

    • Equipment Purchase order: PO’s attached to Equipment in upvise, will sync as a plant porchase order in workbench

Plant Asignments

  • Allows Plant Assignment, Plant Assignment End, Plant return lines to imported

Expense Claims

  • Personal Expense Claims and Credit Card expense claim can be im[ported into workbench.

  • Expense claims will only sync once approved in Upvise

  • Setting “Upvise Sync Expense Claims Approved” Determines if Upvise Expense Claims import as Approved. Only for Standard Approval.

Plant Issues

  • Plant Issues are supported for import into Workbench Via the Daily Diary form set.

    • Forms must be at an end state to be imported

  • Plant Issues can be generated via a Job linked diary or a project linked diary in upvise.

  • Plant issues from upvise are always auto-batched in workbench



Consultant note: For a detailed specs related to imports and exports see https://webwbdoc.atlassian.net/wiki/spaces/SPEC/pages/382403294/Upvise+Integration



 

Next Steps:

Check the import/export history on this screen by using the Previous, History, and Next links. Resolve any errors by checking the Message text.



Related Pages:

Upvise Documentation

Process Flow: