An Introduction to Oneserve to Oneserve

This guide is an introduction to Oneserve to Oneserve, outlining the events that can be passed between systems and the configuration required from each system.

For more information, please reach out to your CSM or Account Manager.

O2O (Oneserve 2 Oneserve) allows updates to be passed between systems in real time, no delays, no phone calls or emails. These updates include the following:

1. Events passed from Primary to Secondary system:

Job Activity assignment to Contractor - Creates job in Secondary system
Mapped Job Statuses - Adds a Job Event in Secondary system
Job Document uploaded (with mapped Document Category) - uploads document in Secondary system
COMING SOON: Version Approved - Approves version in Secondary system
COMING SOON: Version Rejected - rejects version in Secondary system
COMING SOON: Version Cancelled - Cancels version in Secondary system

2. Events passed from Secondary to Primary system:

Appointment Scheduled: Adds a Job Event in Primary system
Appointment Rescheduled: Adds a Job Event in Primary system
Appointment Cancelled: Adds a Job Event in Primary system
Appointment Completed: Adds a Job Event in Primary system
Mapped Job Statuses: Adds a Job Event in Primary system
Job Document uploaded (with mapped document category): Uploads document in Primary system
COMING SOON: Version created - Creates a version in Primary system with updated Activities

How to manage Versions (Variations)?

Whilst we are working away behind the scenes, variations must be still be managed separately in each system. For. more information on how to create variations, please see the guide linked here.

3. Configuration:

O2O forms a link between two systems, Primary and Secondary. The Primary system is where a job originates from, and the Secondary is where the work has been assigned to.

3.1. Required from the Primary system:

Name of the team representing the Secondary system

3.2 Required from the Secondary system:

Name of the Work Log Type of the work being sent over
Name of the Work Type
Name of the Workflow
Name of the Priority
Name of the Client
Name of the Service
Name of Job Status to send 'Accepted' notification back to the Primary system

3.3 Data required in both systems:

Activity (SOR) Codes
Sites
Contact Ref's need to align