Configure the Field Execution module | NextGen Geo

Audience: Administrators

Understand how to configure the module_field_execution module in NextGen Geo, set up data import constraints, and define optional initial display filters for work orders (WOs).

Prerequisites

Before you start:

Verify that your organization has purchased and activated the Field Execution module.
- See Configure modules.
Create a module_workorder instance in NextGen Geo.
- See Users and permissions.
Ensure you have access to the target module's zone.
- See Configure zones and areas.

Understand Field Execution configuration

Configuring the Field Execution module establishes a map-based workflow tailored to specific operation centers (OCs) and work order parameters.

Key behaviors:

Data caching: The import process does not clone the entire NextGen FSM database. Instead, it creates a cache of relevant fields based on your configuration.
Automatic zone mapping: If a zone or structure does not exist for a selected OC, the system creates the structure, maps it to a new zone, and links it to the OC.
Exclusive OC assignment: Each operation center can be assigned to only one module at a time. Administrators can assign one or more OCs to a single module.

Configure module parameters

On the main page, click Open configuration window.
In the header, click Module.
In the Modules window:
- To create a module, click New module.
- To edit an existing module, click Edit next to a module with the module_field_execution xtype.
On the Properties tab, enter general module properties (see Configure modules).
Click the Configuration tab.
Configure the data import settings (see Configuration reference).
Optional: Configure initial user filters (see Configure initial filters).
Click Save.
When prompted to import data from NextGen FSM:
- Click Yes to import the initial data cache.
- Click No to skip the import. You can initiate the import later by saving the configuration again.

Configuration reference

The fields on the Configuration tab control which work orders are imported from NextGen FSM into NextGen Geo:

Field	Input type	Description
Operation center	Multi-field	Restricts displayed WOs to specific organizational or geographical scopes available in NextGen FSM via API.
Work order status	Multi-select	Restricts imported WOs to specific operational statuses (for example, Open, Planned, Schedulable, In charge, To reschedule).
Work order type	Multi-select	Restricts imported WOs to selected type classifications. If left empty, the module relies on other configured criteria.
Work orders created in the last:	Numeric	Sets the maximum creation date interval (in days) for imported WOs. Delimited by system property `fsm.maxWorkorderTTL`.
Language to use for the import	Drop-down	Translates and formats imported data strings into the selected interface language.

Note: In multi-select fields, if selections exceed field width, the interface displays the first items followed by a +N counter indicating additional selected values.

Configure initial filters

Initial filters define the default subset of work orders a user sees when opening the module. Configuring initial filters is optional; if left unconfigured, the module displays all imported data. Initial filters do not lock the filter panel—users can modify or clear them at any time.

Complete all mandatory fields on the Configuration tab. The Filter button enables automatically once the form is valid.
In the upper-right corner of the configuration card, click Filter (funnel icon).
Configure default user display parameters.
Click Apply, then click Save to save both the main configuration and the initial filters together.

Filter	Input type	Mandatory	Description
Work Orders started in the last:	Drop-down	No	Number of days to look back, counted from the day the module is opened. Bounded by the period selected in Work Orders created in the last:.
Work Order Status	Multi-select	No	Default active statuses shown when the module opens. The list offers only the statuses selected for the import.

Note: To return to the main configuration settings from the filter view, click Back. Modifying the main import constraints automatically clears the applied initial filters.

Understand the relative date filter

The look-back period is stored as a number of days, not as a pair of dates. It is resolved every time the module is opened, so a module configured with a look-back of 30 days always shows the last 30 days, and the configuration never goes stale.

The period is applied to the start date of the work orders, and it is truncated to whole days: the window starts at the beginning of the first day and ends at the end of the current one. Because the bounds do not move during the day, the same query is served from the cache instead of being recomputed at every request.

Note: The look-back is applied through the start date filter of the module. If Work Order Start Date is not among the configured filter fields, the period cannot be applied and the module opens unfiltered.

Consistency rules

Initial filters must align with the main import configuration:

Status consistency: You cannot select initial status filters that are excluded from the main import settings. Changing the statuses of the import clears the initial filters.
Period consistency: The look-back period cannot exceed the period selected in Work Orders created in the last:. Changing that period clears the initial filters.

Configure the fields of the module

The search filters, the columns of the list, and the detail view of the module are composed from a configuration instead of being fixed. Standard work order fields and customer-specific fields imported from NextGen FSM (EDM) are declared the same way, so a deployment can present the terminology and the information set of the customer.

The configuration is edited in the EDM configuration area at the bottom of the Configuration tab, which holds three collapsible sections:

Section	Drives
Filter fields	The fields of the search mask above the work order list.
Grid columns	The columns of the work order list.
Detail fields	The read-only fields of the work order detail panel.

To configure a section:

On the Configuration tab of the module, scroll to EDM configuration.
Click the section you want to edit. The other sections collapse.
Set the layout setting of the section:
- For Filter fields and Detail fields, set Layout columns — the number of columns the fields are arranged over, from 1 to 4.
- For Grid columns, set Default flex — the relative width given to a column that does not declare one, from 0.1 to 10.
Click Add field. A new row is added at the end of the list.
In the Field column, select the field. The list offers the standard work order fields and the imported extension fields, each marked with a badge: STD for a standard field of the work order data model, EDM for a customer-specific field imported from NextGen FSM.
Optional: In the Label column, type the label to display. Leave it empty to use the label the platform dictionaries define for the field.
Set the third column, which differs per section.
Optional: Reorder the rows by dragging them by the handle on the left. The order of the rows is the order the fields appear in.
Optional: To remove a row, click the bin icon at the end of it.
Click Save.

Section	Column	Description
Filter fields	Mandatory	The user cannot leave the filter empty.
Grid columns	Hidden	The column is configured but not displayed. Users can show it from the column menu of the grid.
Detail fields	—	The detail section has no third column.

Note: A section left empty falls back to the standard behaviour of the widget, which displays the fields of the data model in their natural order.

Optional: A field pointing at another entity — for example Technical object — can be added either as a whole, which expands into all of its sub-fields, or one sub-field at a time. The sub-fields are listed right below the parent field and qualified with its name, so that the same sub-field name under different parents stays recognisable.

Note: The list of selectable fields is built from the entity metadata. A field that is imported but not declared is not offered. See Manage entity metadata. If the metadata service is unreachable, the drop-down offers the standard fields only, and the extension fields already saved stay visible.

What's next

To establish spatial boundaries for operations, see Configure zones and areas.
To locate work orders on the map, see View work orders and technical objects on the map.
To create work orders from map features, see Create a work order from the map.
To maintain synchronization between systems, see Real-Time Updates and data cleanup.
To declare the customer-specific fields the module can use, see Manage entity metadata.