Skip to main content
Eptura Knowledge Center

Set up the Workflow Tab

The Workflow tab contains these options:

Option Parameter Name Description
Work Completion Options
Require technicians to log their hours before completing requests. HourLoggingRequired

Since tracking labor hours is important for tracking costs, you might wish to enforce that OnSite users complete the hours worked on a job before they can complete the work request.

When this option is set to Required, OnSite users cannot complete the work request until they enter their hours on the Add Work Log form.

Require technicians to enter comments as part of completing a request

CommentsRequiredForCompleteWR

Comments about how a job was completed can add valuable information to the request.

When this option is set to Required, OnSite users cannot complete the work request until they enter comments; the Save button will not be enabled until a comment is entered.

Require technicians to enter data before completing requests InputFieldsRequiredForCompleteWR

If you set OnSite to display the Other Costs or Diagnostics buttons (which present a set of optional fields the technician can enter while working on the job) you can use this parameter to specify which of these fields are required fields; that is, the technician must complete these fields when completing a work request. Click here to see OnSite's Diagnostic and Other Costs commands, and their resulting forms.

You can set the following fields as required for completing a work order: Cause Type, Repair Type, Craftspersons Notes, Equipment Down Hours, Current Equipment Reading, Other Costs.

For each field that you check, OnSite will present with a red asterisk, indicating it is a required field. The "Next" button on OnSite's "Complete Work Order" form will not be activated until the technician enters values for these required fields.

Note that Labor Hours might also be a required field, based on the AbOnSiteMobile-HourLoggingRequired application parameter.

In order to use this parameter, you must also specify that OnSite should display the corresponding fields. To do so, set OnSite to show the fields by completing the "Show or hide the Other Costs section" and "Show or Hide the Display Options section" parameters; these parameters are located on the Display Options tab (described below)

For example, if as part of this parameter, you set Repair Type as a required field, you must display Repair Type as part of the"Show or Hide the Display Options section" parameter, located on the Display Options tab. This gives the technician the chance to enter the field while the job is in progress; if they do not complete the field then, they can do so as part of completing the work order.

Other Options
Require technicians to enter comments as part of changing the request status to a value other than Completed. CommentsRequiredForWRStatusChange

When an OnSite user changes a work request status, it is good practice to document the reason for the change. For example, if they change a status to On Hold, you will want to know the reason for this status. To ensure that technician-made status changes are documented, you can have OnSite to require that a comment be entered when the OnSite user changes the status.

When this option is set to Required, the technician will not be able to save the status change until they enter a comment; the Save button will not be enabled until a comment is entered.

Require the Problem Type field in the Create Request form. CreateWrProbTypeRequired

While OnSite users are in the field addressing an issue, they might see other problems and create requests to address them.

Since the Problem Type determines the SLA that governs the work request, it is important that new requests have a defined Problem Type; otherwise, the work request cannot be processed and a manager will have to enter a Problem Type.

When this option is set to Required, the OnSite user must complete Problem Type on the Create Request form; the Save button will not be enabled until this field is entered.

Give the technician the option to self-assign the request after they create it ShowCreateWrAllowSelfAssignOption

When OnSite users create new requests in the field, they might be able to quickly address the item while at the location. If they create a work request to report a problem they see, they can immediately assign it to themselves for processing.

When this option is set to Enabled, the Create Work Request (additional options) page includes the “Would you like to assign this request to yourself?” option.

When this option is set to Disabled, the self-assign option does not appear. This is handy for sites that wish to enforce that all work requests created in OnSite are routed according to SLAs.

Note that when technicians work offline, the self-assign option is always available because OnSite cannot check the matched SLA for this work to see if Auto-Create Work Order is active. When the user is online again and syncs, the work request will be appropriately routed according to the SLA.