This setting determines how many operations are loaded in the MFS overviews per page. Performance increases if MFS loads fewer operations per page. If you jump to a new page in the list of operations, MFS retrieves the next batch (with the same number) of operations.

Use the fields under Operation statuses to determine which Isah statuses correspond to the listed MFS statuses visible in the operations overviews. Some statuses, such as 'Planned' and 'Accepted', are compulsory. The other stauses may be left empty, and if they are, they will not be enabled in MFS.

It is not possible to assign the same Isah status to more than one MFS status.

Please note: Only operations with a status specified in one of these fields will be visible in MFS. In addition, the production order they belong to needs to have a status that is within the range specified in the field Production order statuses.

Use the range in this field to determine which production orders are eligible for display in MFS. From these production orders, only operations with a status corresponding to an MFS operation status (see the fields under Operation statuses) will be shown in the operations overview. An employee will only see the operations if they are assigned to them (field Employee in the operation line).

This setting defines the kinds of costs that the user can register in MFS (i.e. parts of the 'Cost' type). Only types of costs you have selected here will be available in the app.

This setting contains the hour codes from Isah. Hour codes define a type of activity, for instance 'Man hours', 'Production' or 'Travel'. Only hour codes you have selected here will be available for the Mobile Field Service app. If you want all hour codes to be visible in Isah MFS, leave this setting empty.

The warehouse/location specified in these fields is the standard warehouse/location from which unplanned parts are issued during production. If a service employee uses another warehouse/location, specify this in the user settings.

Isah MFS only uses the warehouse and location for unplanned parts issues. Employees can only issue these unplanned parts if:

• these parts have at least one stock line
• they are situated in the warehouse and on the location specified for the Isah MFS user. If no location has been entered, all locations within the specified warehouse are valid.

Planned parts are always issued from the warehouse and location specified in the order.

Specify which hour code Isah should use to book travel hours.

Specify which hour code Isah should use to book work in progress.

To be able to create time registration lines for an employee, Isah MFS needs a working hours table. Because Isah MFS does not work with fixed hours, this has to be a working hours table of the type 'Variable working hours'.

Specify your default variable working hours table here.

Specify to which value you want the registered hours to be rounded off. Employees register their hours in decimals and can fill in all values, such as '2.35 hours', but the value they enter will be rounded off in accordance with this setting.

When work for a service order is done, it can be signed for by the customer. Before the customer places a signature, Isah MFS shows a summary of the service order details. Standard, all parts issued for the order, all hours registered to the order and all costs registered to the order are displayed for the customer to see. If you want one or both of these items to be hidden from the summary, activate the relevant field.

A wide range of documents can be linked to service orders, such as drawings and service contracts. Standard the Use Isah document rights field is empty, so in Isah MFS all linked documents are displayed. In Isah, employees need rights to view documents. If the Use Isah document rights field is activated, the Isah document rights will be used. In that case, to be able to view documents in Isah MFS, the service engineer needs Read rights.

Activate this setting if the object of the service order is part of an as-built structure and you want to update this as-built structure with the new object data.

If the object replaces an existing object, you can specify that the as-built structure of the existing object is to be copied to the new object by selecting the check box.