Versions Compared

Version Old Version 41 New Version 42
Changes made by

Jay Crouch (Unlicensed)

Jay Crouch (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. 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 for the Asset using the Scope CMS web interface.

  2. 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:

    Code Block
    worklink://resource?action=fetch_catalog&asset=INSERT_ASSET_ID_HERE&work_order_id=INSERT_WORK_ORDER_ID_HERE

  3. The administrator creates a custom internal application designed to receive Scope Webhooks, and configures .

  4. The administrator contacts Scope support to configure the customer’s Scope account to send Webhooks to said application.

Scope Deeplinks are highly extensible and accept any number of external data parameters, not just work_order_id.

For more information, see “Using Webhooks”, “Using Deeplinks”.For example Salesforce Deeplink configuration instructions, see , and “ServiceMax Configuration Guide”.

...