...
I will use a custom internal application, Deeplinks, Scenario Catalogs, Webhooks, and the Scope GraphL API to retrieve Scenario Session data, as the data becomes available, and associate said data with work orders in my system-of-record.
To view a live demo “custom internal application”, complete with source code, see https://api-demo-ruby.scopear.com.
Orchestration Summary
The system-of-record provides a work order identifier to the Scope platform whenever a user leaves the system-of-record to interact with the Scope platform.
The Scope platform then attaches said work order identifier to the Scenario Session data that it creates and manages.
The Scope platform then notifies a custom application (aka “Webhook Listener”), in real time, as the user creates and updates Scenario Session data.
The Webhook Listener then retrieves Scenario Session data and stores in the system-of-record using the previously provided work order identifier to locate the relevant work order.
...