Expected Workflow for Creating and Linking Records Between Vision and TrafficLIVE
Projects/jobs, employees, timesheets, and some organization levels can be linked between Vision and TrafficLIVE when you run the TrafficLIVE web service.
The following table summarizes the workflow for creating and linking the records between Vision and TrafficLIVE.
Linked Record | Expected Workflow |
---|---|
Project/Job | Vision's projects are equivalent to TrafficLIVE's jobs. A project in TrafficLIVE is a group of jobs.
The expected workflow is:
You cannot send new project/jobs that you create in Vision to TrafficLIVE. Changes that you make in TrafficLIVE to linked projects/jobs cannot be updated in Vision. |
Employee |
The expected workflow is:
You cannot send new employees that you create in TrafficLIVE to Vision. Changes that you make in TrafficLIVE to linked employees cannot be updated in Vision. |
Timesheets |
The expected workflow is:
You cannot send new timesheets that you create in Vision to TrafficLIVE. The edits that you make in TrafficLIVE to existing linked timesheets cannot be sent to the timeheets in Vision. |
Organizations | Employees in TrafficLIVE must have a company location and a department specified. Before you can link Vision employees with TrafficLIVE, you must:
After Vision organization levels are sent to TrafficLIVE, the required location and department for employees will be populated in TrafficLIVE when you send new employee records from Vision to TrafficLIVE. If Vision's organization levels do not map to TrafficLIVE's location and/or department or you do not use organizations in Vision, you can set up a default location and department for the mapping in Vision to use when employees are sent from Vision to TrafficLIVE. |