App‑to‑App communication is a way to exchange data between apps on a device, even if the device is offline. App‑to‑App communication includes both inbound requests (“calls”) to the TrueContext Mobile App and, on the Advanced and Enterprise tiers, outbound “callbacks” to an allowed domain or app.
To support both new and existing integrations, the TrueContext App‑to‑App URL scheme will remain
prontoforms:// with alternative
For more detailed information about what’s changing, visit https://support.truecontext.com/hc/en-us/articles/19516168513556
Learn from an expert! This video shows you how to build and use an App‑to‑App request.
Get “recipes” for frequently used App‑to‑App requests and callbacks.
App‑to‑App communication is a way to exchange information between a mobile app on your device—such as a work order management system—and the TrueContext Mobile App.
An inbound App‑to‑App request directs the TrueContext Mobile App to launch in the foreground and complete an action. On the Advanced and Enterprise tiers, “callbacks” define the data that the TrueContext Mobile App returns to the source app.
If you share data from forms in App‑to‑App callbacks, we recommend that you define an allow list. This limits the URLs and apps that can receive the data and guards against unintended sharing of information.
With your allow list configured, you can specify form data and metadata to send back to your source app in the form of custom callback parameters.
An App‑to‑App request uses the x-callback-url specification and follows this structure, with UTF-8 percent encoding for some special characters:
You can use any of the following callback actions:
On the Advanced and Enterprise tiers, you can also define x-callback parameters As part of an App‑to‑App call to the TrueContext app, x-callback parameters provide a way to launch and send data to the calling app. These include x-success, x-cancel, and x-error parameters. to return the form status, metadata, and submitted data.