How to capture a form against a specific job using the Job Override field

Overview

Not every form gets filled in while the job it relates to is still running. A quality check gets written up after the changeover. A rework note is raised at the end of shift, about a run that finished two hours ago. By the time the operator opens the form, the line has moved on.

The Job Override field solves that. It puts a mandatory job picker at the top of your form, so the operator has to nominate exactly which job the form is about before they fill anything in — and that choice is captured with the form.

Job Override is one of two job fields in the OFS-Flow form builder. Its companion, the Job Context Selector, is covered in How to reference a previous job in validation using the Job Context Selector.

Before you start

Job Override needs to be switched on for your environment before it appears in the form builder. If you can't see it, that's almost always why — contact your OFS Sales Contact and we'll get it enabled for you.

Step 1 — Add a Job Override field to your form

Open your alert in Fusion Manager → Alerts & Flow, select it, and go to the Form tab.

The field toolbox runs down the left-hand side. Job Override is the briefcase icon at the very bottom. Click the briefcase icon once to add the field to your form layout.

Step 2 — Put Job Override first

Job Override must be the first field in the form. If it isn't, the form builder shows this error and won't let you save:

You can drag the field to the top of the layout to fix this. If the drag doesn't take, the quickest fix is to delete the job fields, add Job Override onto an empty canvas first, then add your other fields underneath it.

You'll also see this message if you try to add a second one:

Step 3 — Configure the field properties

Select the Job Override field to open its Field Properties panel.

Property	What it does
Unique Field Name	Required. The name you'll use to reference this field in validation rules and in exported data.
Recent Jobs to Show	How many recent jobs appear in the operator's picker. Three is a sensible starting point.
Form Field Label	Optional. The wording the operator sees above the picker. Leave it blank and the operator sees the Unique Field Name instead — worth filling in.
Help Text	Optional. A line of guidance shown with the field.

There is deliberately no Required toggle. Job Override is always mandatory — that's the point of the field.

Save the alert when you're done. Use the alert-level Save button at the top right, and save before you move to another module — navigating away from Alerts & Flow discards unsaved changes on the tab without warning.

Step 4 — What the operator sees

On the console and in the OFS Flow Form, Job Override renders as a Select a job picker at the top of the form.

Opening it lists the most recent jobs for that line — the number you set in Recent Jobs to Show. Each entry shows the line, the job's start and finish times, and the SKU with its description. The job currently running is marked ACTIVE.

The operator picks the job the form is about, then completes the rest of the form as normal.

Nothing is saved until the operator submits the form to a workstate. Choosing a job, typing answers and attaching photos all stay on the device until the form is submitted. Closing the form loses everything entered.

Using Job Override alongside the Job Context Selector

You can put both job fields on the same form: Job Override first, then one or more Job Context Selectors.

When you do, the Job Context Selector fields stay greyed out until the operator has chosen a job in Job Override. They become editable the moment a job is selected.

One design consequence worth knowing

A form card in the Flow feed normally shows the job's SKU and description in its header, alongside the line, operator and crew.

Adding job fields removes that header line. The job identity moves entirely into the picker, so a form with a Job Override doesn't give the operator the same at-a-glance job context from the header.

It's not a fault, but it does change what the operator sees at a glance. If your form is one where the running job matters for context, consider adding a Form Field Label that makes the choice obvious — something like "Which job is this check for?"

Need a hand?

If the Job Override icon isn't appearing, or you're not sure whether Job Override or the Job Context Selector is the right field for what you're building, get in touch through the OFS Customer Portal — we're happy to talk it through.