Example of App‑to‑App Communication

This topic provides an example that describes an inbound App‑to‑App call that launches the TrueContext Mobile App, prepopulates some of the form data, and then returns data to the source app.

Info:We're now TrueContext.

To support both new and existing integrations, the TrueContext App‑to‑App URL scheme will remain prontoforms:// with alternative https://prontofor.ms/.

For more detailed information about what’s changing, visit https://support.truecontext.com/hc/en-us/articles/19516168513556

Available on all tiers:

Essentials
Advanced
Enterprise

Info:Teams on the Advanced and Enterprise tiers can set up a callback request to send data back to the source app. The topics App‑to‑App Actions and App‑to‑App x-callback parameters provide more details about how to format an App‑to‑App request, including callbacks.

  1. The technician launches a work order in your “source” app.

  2. Your source app launches the TrueContext Mobile App (the “target” app) and prepopulates questions, such as the service type.

  3. The TrueContext Mobile App sends data from the form back to the source app.

In this example, the App‑to‑App request might look like this:

prontoforms://x-callback-url/open?name=Inspection&ServiceType=Warranty&x-success=sourceapp://callback

where

  • open is the action that launches the TrueContext Mobile App

    Note:The mobile device user must be signed in to the TrueContext Mobile App.

  • Inspection is the form name

  • ServiceType=Warranty is a question unique ID and answer, and

  • x-success=sourceapp://callback is the x‑callback parameter to open and send data to the source app.

The following illustration shows an example of how App‑to‑App requests and callbacks work.

  • 1 shows an inbound request to open and prepopulate a form.

  • 2 shows an inbound request that includes a callback to the source app.

  • 3 shows the default information sent to the source app.