About Mobile Integrations

Mobile Integrations provide a workflow‑driven integration framework within the IFS Mobile Work Order (MWO) application. This capability enables seamless interaction between MWO and external mobile applications, allowing technicians to launch third‑party apps with contextual data, perform required actions, and return validated results directly into the workflow.

Integrations can be displayed on Task Actions or the Home Screen and support linking to external applications and web pages.

Passing Contextual Data

To open an integration from a Task (Work Assignment), the Screen Type must be set to Work Task.
Attributes from the following entities can be passed as parameters:

• JtExecutionInstance
• JtTaskAddress
• EquipmentObject
• MobileIntegration
• RequestTask
• RequestBundleTask
• JtTask
• JtBundleTask
• TaskMapPostion

Attribute names must be specified together with the entity name in the URL definition. Names can be provided in uppercase or lowercase.

Example:

https://www.google.co.uk/search?q={RequestTask.Description}+{EquipmentObject.MCH_CODE}+{JtTaskAddress.LocationId}

This example starts a Google search using the Task Description, Object ID, and Task Location as query parameters.

Custom fields on supported entities can also be used by prefixing the field name with CF_.

Example:

https://www.google.co.uk/search?q={JtTask.CF_GAS_SAFETY_ID}

URL Usage Considerations

Different browsers, operating systems, servers, and mobile applications apply their own internal limits to how long or complex a URL can be. These limits vary widely and may affect deep linking, parameter handling, and mobile workflows.

Recommendation:

Keep URLs as concise as possible, avoid embedding large or structured data, and validate any URL‑based integration across all target platforms to ensure reliable behavior.

Mandatory Integrations

The Mandatory Integrations tab within Workflow Configuration allows administrators to define integrations that must be completed before a task can be completed.

For each mandatory Integration , the expected return parameter name and value must be specified.

Example:

When working with Advanced Forms , the mandatory parameter configuration requires the following:

• The Mandatory Parameter Name must be Status.
• The Mandatory Parameter Value must be Submitted.

 

The Allow User to Skip Integration Validation toggle controls whether validations act as hard or soft requirements:

• When enabled, the technician can manually confirm that the required actions have been completed.
• When disabled, task completion is blocked until all mandatory integrations are completed.

An Integration Log securely records integration completion states and supports offline execution. The Clean Up Mobile Integration Logs scheduled task is available to clean up Mobile Integration Logs regularly.

Defining Mobile Integrations

Administrator access is required to define Mobile Integrations. Once configured, these integrations allow the mobile application to communicate effectively with external systems through links displayed on Task Actions and the Home Screen.