360Facility and Serraview Data Flow Matrix
- Last updated
- Save as PDF
Parent Work Order
Legend
- Black = Integration Information
- Blue = Initial Data
- Purple = Updated Data
| Field Name | 360Facility | Data Flow | Serraview |
|---|---|---|---|
|
360: Multiple fields concatenated Serraview: Description |
Source 360Facility sends a concatenation of Date, Time, Request SubType, Requester Name, Requester Phone, and Building Name. No updates issued or received. |
-> |
Destination Serraview receives the concatenated data fields and puts it in the Description field. No updates issued or received. |
|
360: Assigned To Serraview: Assignee |
Source Configuration Option 1 – Assigned to the Integration User. Configuration Option 2 -Assigned to a specific person. Config 1 & 2 - no updates issued or received. |
-> |
Destination Configuration Option 1 - Defaults to “Unassigned”. Configuration Option 2 – Updates to the Assigned provided if there was a match. If there is no match on Assignee, it defaults to “Unassigned” Config 1 & 2 – no updates issued or received. |
|
360: Request SubType Serraview: Service Request Type |
Source The selected 360 Request SubType is pushed to Serraview No updates issued or received. |
-> |
Destination Serraview receives the 360 Request SubType and matches it to a Serraview Service Request Type. No updates issued or received. |
|
360 & Serraview: Status |
Source No initial status sent. No updates issued to Serraview except “Canceled” or “Entered in Error”. Receives 360 receives updates from Serraview based on the status mapping configured in Serraview. |
NA <- |
Destination Regardless of the current 360Facility status, Serraview will default the Status to “Unassigned” Source Serraview issues updates based on the Status Mapping configured in Serraview. |
|
360 & Serraview: Status (Cancelled or Entered in Error) |
Source Parent Work Order updated to “Canceled” or “Entered in Error”. |
-> |
Destination Serraview receives updates for “Cancelled” or “Entered in Error” only. |
|
360: Complete By Serraview: Due |
Source The selected or auto-calculated date is pushed to Serraview. No updates issued or received. |
-> |
Destination Serraview populates the Due date as provided. No updates issued or received. |
|
360: Building Serraview: Location |
Source 360 sends the Building selected. No updates issued or received. |
-> |
Destination Serraview populates the Location as the scratchpad of the Building. No updates issued or received. |
|
360: Priority Serraview: Priority |
Source None - Priority was not designed to pass via the integration. No updates issued or received. |
NA |
Destination Serraview defaults all inbound Parent Work Orders to “Normal”. If the Work Order is a priority other than “Normal”, the Serraview User is to manually change to the correct priority. No updates issued or received. |
Child Work Order
The Work Orders created within the Serraview System are actually 360Facility (Child) Work Orders. Once created, the following grid is displayed in the Serraview UI. All fields shown are populated and refreshed via the API. No updates are made in Serraview.
- Ticket # - Does not change in 360Facility
- Type –Updated by 360Facility
- SubType - Updated by 360Facility
- Description - Updated by 360Facility
- Last Comment – Updated by 360Facility
- Status – Updated by 360Facility
- Assignee – Updated by 360Facility
- Cost – Updated by 360Facility
- Scheduled For - Updated by 360Facility