For operations and business teams
A structured starting point for IFS Mobile Work Orders
Teams evaluating an adjacent IFS workflow can start with three required details: a work order reference, the site, and a description of the work. Spindlewick brings them together in one focused request surface for active subscribers.
Request details
Three inputs, clearly defined
The supported request surface is organized around three inputs. Capturing them clearly helps a team evaluate the adjacent workflow without implying an external IFS action.
01
Work order reference
Required. Keep the request tied to the work order reference used by the operations team.
Up to 100 characters
02
Site
Required. Record the site where the work will take place.
Up to 200 characters
03
Work description
Required. Describe the work and include relevant constraints or operating context.
Up to 5,000 characters
Reference mapping
Input-to-IFS mapping
This table is a reference to the completed MVP specification only. It does not indicate a live IFS integration, synchronization, work-order creation, or work-order update.
| First-job input | Specification-supported IFS entity or parameter | Detail |
|---|---|---|
| Work order reference | Unknown | Required; up to 100 characters. The exact IFS target is not present in this checkout. |
| Site | Unknown | Required; up to 200 characters; the existing workflow treats this as a site label, not a URL. |
| Work description | Unknown | Required; up to 5,000 characters. The exact IFS target is not present in this checkout. |
Documentation boundary
Setup caveats for a future IFS adapter
The points below summarize general IFS product and documentation requirements. They are not evidence that Spindlewick has configured, activated, or connected an external IFS account; this page makes no external IFS request.
Mandatory integration
In IFS Workflow Configuration, administrators define mandatory integrations that must be completed before a task can be completed.
Expected return
Each mandatory integration needs an expected return parameter name and value. IFS uses Status / Submitted as an example; that is a documentation example, not a Spindlewick configuration.
Validation mode
Allow User to Skip Integration Validation can permit a technician to confirm the required action manually. When disabled, task completion remains blocked until the mandatory integrations are complete.
Administrator setup
Defining Mobile Integrations requires administrator access in IFS. This page does not establish that an administrator has configured or activated anything for Spindlewick.
Environment-specific REST settings
IFS REST task configurations are environment-specific. Imported workflow configurations can be incomplete when required environment values are not imported; the target environment must supply them before use. URL and method are required task fields, while the required values and credentials for this app are not supplied.
What is still unknown here
The exact mandatory integration name, expected parameter pair, endpoint, HTTP method and payload, authentication mode and credentials or configuration keys, target environment, administrator activation state, and any external IFS account connection to Spindlewick are not established.
Documentation sources
These official IFS pages describe general product requirements and configuration concepts; they do not confirm a Spindlewick integration:
FAQ
Clear answers about the adjacent IFS Mobile Work Order request workflow, its boundaries, and who can evaluate it.
Recovery context: IFS documents that a stale metadata cache can return HTTP 503 with MI_MODIFIED_ERROR. After the cache refreshes, the same request can be retried. That source-backed condition informs the subscriber guide; it does not mean this page has a connected IFS adapter. Read the IFS metadata cache documentation.
Subscriber workflow
Ready to use the workflow?
An authenticated account with an active subscription can open the submission experience. The request validates all three fields, but it is currently blocked before saving because the IFS execution specification is unavailable. Review subscription options if you need access; pricing terms are still being finalized.