https://verint14-pre-02.socialedgeconsulting.io/product-fieldpulse/FieldPulse is a cloud-based operations platform designed for organizations that manage technicians, inspectors, installers, and other field-based workers. It enables teams to manage work orders, schedules, inventory, safety checklists, customer communicatien-US14.0.0.622 14https://verint14-pre-02.socialedgeconsulting.io/product-fieldpulse/f/user-q-a/248/confirmed-working-offline-status-update-sync-resolved/1401Thu, 23 Apr 2026 09:17:00 GMTforumreply:1401Hi Sam, happy to help confirm this! What you're describing is exactly how offline status updates are designed to work. Here's what's happening under the hood: Status changes made offline are stored in a local queue On reconnect, the app syncs automatically (you'll see the spinner Sam mentioned) Conflicts are resolved server-side with timestamps Important: Do not force-close the app while offline, as Art and Josh noted — this clears the queue. Backgrounding the app is fine. We've also seen improved reliability with this flow in app version 3.2.1 and later. If anyone is still experiencing issues after following these steps, feel free to tag me and I can dig into your specific account.https://verint14-pre-02.socialedgeconsulting.io/product-fieldpulse/f/developer-integration-help/180/using-make-integromat-instead-of-zapier-gotchas/1014Thu, 25 Sep 2025 18:20:00 GMTforumreply:1014Perfect — the v1 vs v2 thing is exactly the kind of detail I needed. Already running into the "run it once to see data" pain, good to know that's expected behavior and not me missing something. Will likely go HTTP module route for the newer endpoints. Appreciate the confirmation on OAuth refresh too.https://verint14-pre-02.socialedgeconsulting.io/product-fieldpulse/f/developer-integration-help/180/using-make-integromat-instead-of-zapier-gotchas/1013Thu, 25 Sep 2025 16:45:00 GMTforumreply:1013Devon — yeah this one tripped me up too when I first looked at it. Leo's right on the custom fields thing, that's a platform limitation on our end not a Zapier/Make thing. The OAuth refresh is actually smoother in Make in my experience. Their "Connection" model handles token refresh automatically without the extra "Refresh Token" step you need in Zapier. Heads up though: if you're using a custom OAuth app (not the default FieldPulse one in Make's app directory), you'll need to manually configure the token endpoint. That's auth.fieldpulse.io/.../token with grant_type refresh_token . One gotcha that got me: Make's "FieldPulse" app in the directory is on v1 of our API. If you need v2 features (like the new checklist endpoints), use the generic HTTP module and hit the endpoints directly. The v1 app works fine for work orders and customers, just not the newer stuff. Also worth noting — Make doesn't have the same "Test Trigger" behavior as Zapier. You often need to run the scenario once to see sample data, which can be annoying when you're building against production. I usually set up a filter early in the scenario to catch only test records while I'm building. Documentation link for the direct API approach: Using the FieldPulse APIhttps://verint14-pre-02.socialedgeconsulting.io/product-fieldpulse/f/developer-integration-help/180/using-make-integromat-instead-of-zapier-gotchas/1012Thu, 25 Sep 2025 14:12:00 GMTforumreply:1012Two things: Webhook payloads are identical — same JSON structure. The difference is Make parses nested objects differently in the trigger data mapper. Check the "Data structure" settings on your webhook module. Custom fields: same limitation as Zapier. The custom_fields array is not expanded in trigger payloads. You need a second API call to /work_orders/{id} with include=custom_fields . See Setting Up Webhooks — the payload examples there apply to both platforms.https://verint14-pre-02.socialedgeconsulting.io/product-fieldpulse/f/user-q-a/199/limiting-technician-view-edit-permissions-how-granular/1121Tue, 26 Aug 2025 12:10:00 GMTforumreply:1121Anita — thank you for that detailed follow-up. I have reproduced the search behavior you described and confirmed this is unintended. Customer records from unassigned jobs should not surface in mobile search when the restriction is enabled. I am escalating this to our engineering team as a bug. You should receive a ticket reference within 30 minutes. The workaround until resolved: disable search for technician role users (toggle under Mobile Permissions ), though I recognize this impacts usability. Your documentation of this as a control deficiency is appropriate. I will update here when the fix is scheduled.https://verint14-pre-02.socialedgeconsulting.io/product-fieldpulse/f/user-q-a/199/limiting-technician-view-edit-permissions-how-granular/1120Tue, 26 Aug 2025 09:47:00 GMTforumreply:1120Thank you for the responses. I have implemented the "Restrict to assigned work orders only" setting as described. I can confirm that technicians with this restriction enabled are unable to view unassigned jobs in both the web interface and mobile application. This satisfies requirement #1. However, I have identified an inconsistency: when a technician uses the search function in the mobile app, customer records from unassigned jobs appear in search results with partial address information. This occurs despite the restriction setting. I have documented this behavior with screenshots and will submit a support ticket unless this is a known configuration issue. Regarding the pricing visibility gap: I have logged this as a control deficiency per Fatima's recommendation. We will proceed with the $0.00 template approach as an interim compensating control, with manual dispatcher review of all closed work orders. Please confirm whether the search visibility behavior is expected or requires escalation.https://verint14-pre-02.socialedgeconsulting.io/product-fieldpulse/f/user-q-a/199/limiting-technician-view-edit-permissions-how-granular/1119Tue, 26 Aug 2025 08:15:00 GMTforumreply:1119It is worth noting that the pricing visibility limitation Priya identified may have compliance implications depending on your jurisdiction and contractual obligations. From a governance perspective, I would recommend documenting this as a known control gap in your internal risk register. Anita, you may wish to reference Managing User Roles and Permissions for the current permission matrix, though I have confirmed the documentation does not address field-level granularity beyond what Priya outlined. Additionally, it is worth noting that API access (if provisioned for your account) inherits the requesting user's role permissions. If you are considering custom integrations to enforce pricing restrictions at the data layer, ensure your API keys are scoped appropriately and audit access quarterly.https://verint14-pre-02.socialedgeconsulting.io/product-fieldpulse/f/developer-integration-help/185/build-custom-mobile-interface-using-fieldpulse-api/1040Sun, 27 Jul 2025 09:15:00 GMTforumreply:1040Can you share the actual error on session handling? Specific flow and IdP would help. Also — what does your /work_orders response payload look like for a record with checklist data? Want to confirm you're expanding the right nested fields.