How Inbound App‑to‑App Calls Work

The TrueContext Mobile App can receive a “request” or “call” from another app on the same device. This topic describes how calls and callbacks enable offline communication between apps on a device.

Available on all tiers:

Essentials
Advanced
Enterprise

Inbound requests

The TrueContext Mobile App can receive a “request” or “call” from another app on the same device (the source app). An inbound App‑to‑App request directs the TrueContext Mobile App to launch in the foreground and complete an action. For example, the source app can direct the TrueContext Mobile App to

  • open a new form and prepopulate it with data from the source app

  • open a list of forms in the user’s Inbox, or

  • search for previously submitted forms.

x-callback parameters

The source app can also specify “x‑callback” parameters. These parameters tell the TrueContext Mobile App what to do when a user submits or discards a form, or when there’s an error. For example, after a user sends a form, TrueContext can bring the source (calling) app back to the foreground and send the submitted form data to the source app. The combination of requests and callbacks enables offline communication between the source and TrueContext Mobile App, which is critical for managing step-by-step workflows such as checklists.
Note:

  • Different source apps vary in their ability to use the data that the TrueContext Mobile App provides in a callback.

  • Your source app must be configured to handle the callbacks and any data returned. You might need to check with your own experts to set this up for your specific app.

  • We recommend that you configure a custom App‑to‑App allow list to manage the apps that can receive data from the TrueContext Mobile App.

  • App‑to‑App callbacks are supported on the Advanced and Enterprise tiers only.

If you want the mobile device user to stay in the TrueContext Mobile App, you don’t need to specify a callback parameter.

The combination of requests and callbacks enables offline communication between the source and TrueContext Mobile App, which is critical for managing step-by-step workflows such as checklists.

Tip:Organizations that use a work order management system can combine the offline functionality of App‑to‑App communication with the online functionality of a TrueContext cloud-based Data Destination. A Data DestinationClosed A Data Destination specifies where to send data from a submitted form. You can use Data Destinations to automate data sharing and storage, routing data to a specific service (such as email or cloud storage) in several different formats. is typically used to send detailed data to the back-office system of the source app. Data DestinationsClosed A Data Destination specifies where to send data from a submitted form. You can use Data Destinations to automate data sharing and storage, routing data to a specific service (such as email or cloud storage) in several different formats. enable full access to the data submitted from the TrueContext Mobile App, including photos.