How to Use Identifiers in an App‑to‑App Call

Info:Keep in mind that:

Different form identifiers apply at different stages in a workflow. When you build an App‑to‑App request, you must use valid combinations of identifier and location (Forms, Inbox, Drafts, or Search).
A dispatched record might also be located in the Group Inbox (Intelligent and Elite tiers).
Resources Resources are materials that field technicians can access while they work on records in the Mobile App. A resource might be a Resource Document, like a manual or a floor plan, or a Resource Image, like a schematic or a diagram. Resources are uploaded to a FormSpace and can be referenced in forms or made available in the Resource Library. are always located in the resourcelibrary, regardless of the workflow.

This topic describes the form identifiers that you can use in an App‑to‑App call. It also explains how to find a resource identifier.

Available on all tiers:

Digital

Intelligent

Elite

Form identifiers

As a form progresses through a workflow, it moves from one location (“list” or “tab”) on the TrueContext Mobile App to another. For example, a user can open a form from the Forms list, add information, and then save it to Drafts.

The following table describes the location-identifier combinations at various stages in a form’s workflow.

Form stage	Location on the TrueContext Mobile App	Identifiers to use in an App‑to‑App request	Description
Saved and deployed by a form designer	Forms	formID	Identifies the form. In an App‑to‑App request, this is the most recently deployed version of the form.
Saved and deployed by a form designer	Forms	formIterationID	Identifies the form and version of the form.
Dispatched	Inbox	dataRecordID	Identifies the form based on the ID assigned by the TrueContext server.
Dispatched, opened, and saved
Sent for edit
Sent for edit, opened, and saved
Opened for edit from the Sent box, and saved
Opened from the Forms box and saved as a draft	Drafts	clientDataRecordID	Identifies the saved form by the ID assigned by the TrueContext Mobile App. Tip:The only way to get the clientDataRecordID is to send an App‑to‑App request that includes an `x-success` callback parameter.
Sent (complete)	Search	N/A	The search action searches the text of the form submission name only. Note:“Incomplete” applies only to teams with TrueContext Teamwork TrueContext Teamwork is a feature that enables mobile users to transfer incomplete forms for other users to complete as part of a multi-user workflow. This can be useful for jobs that require someone else's expertise or that span multiple shifts.-enabled forms.
Sent (incomplete)	Search	N/A

Resource identifiers

Info:The Resource Library The Resource Library enables you to build a digital, multilingual, and searchable knowledge base that contains your organization’s essential content. Available to your mobile users in the Mobile App, the Resource Library simplifies the distribution, discovery, and use of critical information—such as manuals and schematics—to support your field technicians in their work. The Resource Library serves as a mobile reference library for your field teams. must be set up for your team, and individual resources must be set to Visible in Resource Library. The topic Set Up the Resource Library describes the process in more detail.

You can find a resource identifier in the TrueContext Web Portal The TrueContext Web Portal is a web application used to manage security settings, forms, FormSpaces, other users, Data Sources, and Data Destinations..

Go to Forms & Integrations > Resources.
Select the resource that you want to identify in your App‑to‑App call.

Result: The browser URL includes the resource identifier, as shown in the following example.
Copy the resource identifier to use with the open action. The following example shows the resource identifier syntax in bold.
```
truecontext://x-callback-url/open?type=resourcelibrary&resourceID=1234567891
```