• State Verified Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 2 subscribers
  • Views 7 views
  • Users 0 members are here
Options
Related

Deep-link into specific work order from external app

Carlos Vega

Need to deep-link from our internal dashboard directly into a specific work order in FieldPulse mobile app. URL scheme documentation is sparse.

Tried fieldpulse://work_orders/{id} — no response. Also fieldpulse://app/work_orders/{id}.

What's the actual URL scheme? Need this working for iOS and Android.

Parents
  • 0

    Hey Carlos — yeah, we don't document this as well as we should. The scheme you're looking for is:

    fieldpulse://workorder?id={work_order_id}

    Not work_orders plural, and it's a query param, not a path segment. This trips up a lot of people.

    For universal links (HTTPS), you can also use:

    app.fieldpulse.com/workorder

    If the app is installed, it'll open directly; if not, it falls back to web. The web view will prompt to open in app on mobile.

    Edge case worth noting: if the work order is assigned to a technician who isn't logged in on that device, it'll land on the auth screen and redirect after login. We don't currently preserve the deep link through a full auth flow on iOS — there's a ticket open for that (FP-4421).

    Docs reference: Mobile App Deep Linking — though honestly the examples there need updating. I'll flag it.

Reply
  • 0

    Hey Carlos — yeah, we don't document this as well as we should. The scheme you're looking for is:

    fieldpulse://workorder?id={work_order_id}

    Not work_orders plural, and it's a query param, not a path segment. This trips up a lot of people.

    For universal links (HTTPS), you can also use:

    app.fieldpulse.com/workorder

    If the app is installed, it'll open directly; if not, it falls back to web. The web view will prompt to open in app on mobile.

    Edge case worth noting: if the work order is assigned to a technician who isn't logged in on that device, it'll land on the auth screen and redirect after login. We don't currently preserve the deep link through a full auth flow on iOS — there's a ticket open for that (FP-4421).

    Docs reference: Mobile App Deep Linking — though honestly the examples there need updating. I'll flag it.

Children
No Data