Common Use Case Orchestration

Learn about recommended orchestration techniques for several common use cases.

In This Article

Glossary

There are a number of key services and objects relevant the use cases described in this document.

Key Term	Description
GraphQL API	Method of retrieving a customer’s data via a single endpoint. For more information, please see “Introduction to the Scope GraphQL API”.
DeepLinks	Method of launching the Scope Worklink app via a structure URL. For more information, please see “Using Deeplinks”.
Webhooks	Method of notifying a customer’s internal systems about key events that take place in the Scope platform. For more information, please see “Using Webhooks”.
Scenarios	Sets of work instructions pertaining to a specific physical device, to completed by a user while using the Scope Worklink app. For more information, please “Scenario” in the reference docs.
Scenario Sessions	Recordings of Scenarios performed and completed by a user while using the Scope Worklink app. For more information, please “ScenarioSession” in the reference docs.
Scenario Catalogs	Method of mapping a customer’s internal system objects (like assets or training modules) to Scenario Sessions. For more information, please “ScenarioCatalog” in the reference docs.
SSO Integration	Method of syncing Scope users with a customer’s directory. Coming in 2021

system-of-record Integration

Use Case #1: Real-Time Synchronization

Problem

As an administrator, I want to associate Scope Scenario Session data with work orders in my system-of-record (e.g. Salesforce), in real-time, as my users interact with the Scope platform.

Solution

I will use a custom internal application, Deeplinks, Scenario Catalogs, Webhooks, and the Scope GraphL API to retrieve Scenario Session data and associate said data with work orders, as the data becomes available.

Orchestration Summary

I will provide a work order identifier to Scope whenever a user leaves my system-of-record (to interact with the Scope platform).
The Scope platform will then attach said work order identifier to the Scenario Session data that it creates and manages.
The Scope platform will then notify me, in real time, whenever the user creates or updates Scenario Session data.
I will then retrieve the data, filter by work order id, and associate with work orders in my platform.

Configuration

For each physical device (aka the “Asset”) that work orders might pertain to in the system-of-record (.e.g. “Generator Model #1234”):
1. The administrator creates at least one Scenario for the Asset using the Scope Create 2 application.
2. The administrator creates a Scenario Catalog using the Scope CMS web interface.
The administrator configures the system-of-record to present a dynamically generated link whenever system-of-record users view work orders (aka the “Deeplink”). The link passes both the asset identifier and work order identifier as parameters:
```
worklink://resource?action=fetch_catalog&asset=INSERT_ASSET_ID_HERE&work_order_id=INSERT_WORK_ORDER_ID_HERE
```
The administrator creates a custom internal application designed to receive Scope Webhooks, and configures the customer’s Scope account to send Webhooks to said application.

To view sample configuration instructions for Salesforce, please see “ServiceMax Configuration Sample”.

Procedure

The user visits the Deeplink preconfigured in the system-of-record.
The WorkLink app launches and loads the Scenario Catalog identified by the Deeplink asset_id query param.
The user selects a Scenario and begins a Scenario Session (causing all query parameters passed by the Deeplink to be stored as a JSON hash in the externalData attribute, including and especially the work_order_id).
The customer’s custom application receives Webhook event notifications pertaining to the creation (and later update) of the Scenario Session.
The customer’s custom application queries the Scope GraphQL API and retrieves the data identified by the Webhook resource_id and resource_type (see Sample Queries).
The customer’s custom application inspects the data retrieved decides whether to act based on the value of ScenarioSession.externalData.work_order_id
The customer’s custom application then associates the retrieved Scenario Session data with the work order in the customer’s system-of-record (using the system-of-record APIs).

Use Case #1b: Multiple Sessions

Summary

As an administrator, I want aggregate data for Work Instruction Sessions so that I can merge it with data from my system-of-record to calculate KPI and ROI metrics.

Application

For Learning Management Systems (LMS), get a report of everyone that has completed a particular work instruction scenario so that they get credit for the associated learning module in the LMS.

Orchestration

Customer system is configured to automatically query the GraphQL endpoint to receive the data fields necessary to perform any internal analysis.
Customers can transform JSON format into CSV to merge with system-of-record data.

Use Case #2: Data Analytics

Summary

As an analyst, I want to merge data from the Worklink system with my internal BI tools to visualize the data.

Application

Advanced visualization of WorkLink data, merged with customer system-of-record data.
Pull WorkLink system data to integrate with Security Information and Event Management systems. (Coming soon)

Orchestration

Customer system is configured to automatically query the GraphQL endpoint to receive the data fields necessary to perform any internal analysis.
Customers can transform JSON format into CSV to merge with system-of-record data.

Use Case #3: Call Integration (Coming Soon)

As a field service technician, I want an easy way to launch a call from our service desk application so that it’s associated with the active job id.

As an analyst, I want to measure time-to-resolution metrics for jobs that had AR Remote Assistance calls to measure ROI.

Application

Simplified calling
Closed loop service desk SLA metrics.

Orchestration

Users are assigned call IDs that can be integrated with a system-of-record (like a service desk tool’s contact list)
Experts can click on a Deeplink to launch application and call a specific contact from the system or record.