Configuring FSM Automatic Project Creation for New Assets
Configure the item values and the warranty.asset collection that supply project values when FSM processes asset creation. For record relationships and background processing, see FSM Automatic Project Creation for New Assets.
Properties and Defaults
FSM supplies the standard collection. The standard outcome also requires item setup because the item fields have no supplied default values.
The following table lists the item settings and the warranty.asset property, including accepted values, defaults, units, and effects.
|
Property or Setting |
Location |
Accepted Value |
Default |
Effect |
|---|---|---|---|---|
|
Field Service Project Type ( |
Item record |
A Field Service Project Type |
No supplied value |
Supplies the type of the project. The standard lookup requires a populated value. |
|
Field Service Project Duration ( |
Item record |
Integer duration in months |
No supplied value |
Supplies the months added to the current start date, before subtracting one day. |
|
|
Root |
Object containing project values, or |
The item search and map in Default JSON |
Supplies the project values for a newly created asset. |
The supplied item fields apply to inventory, noninventory, and assembly items. Their visibility also depends on the item form. For a warranty period, configure a positive whole-month duration.
The standard collection is an object with array: true and a named item search. It is not a list of rules with conditions and outputs evaluated by Shared Rule Matching.
The following table describes the entries in the standard collection.
|
Standard Collection Entry |
Standard Value or Behavior |
|---|---|
|
|
|
|
|
|
|
|
Restricts the search to the asset's item and requires a populated Field Service Project Type. |
|
|
Reads |
|
|
Uses the current date in the asset's time zone, or the session time zone when no asset time zone is supplied. |
|
|
Adds |
Default JSON
The following fragment is the standard warranty definition. The dates resolve from the asset and item context during asset creation. The JSON does not contain stored literal dates. Other root properties remain inherited.
{
"warranty": {
"asset": {
"array": true,
"item": {
"record": "item",
"filters": [
[
"custitem_nx_project_type",
"noneof",
"@NONE@"
],
"and",
[
"formulatext:case when {internalid} in ('${ asset.item }') then 'T' else 'F' end",
"is",
"T"
]
],
"map": {
"type": "custitem_nx_project_type",
"start": "formuladate:CURRENT_TIMESTAMP at time zone ${ asset.timezoneid ? '\\'' + asset.timezoneid + '\\'' : 'SESSIONTIMEZONE' }",
"end": "formuladate:ADD_MONTHS(CURRENT_TIMESTAMP at time zone ${ asset.timezoneid ? '\\'' + asset.timezoneid + '\\'' : 'SESSIONTIMEZONE' }, {custitem_nx_project_duration}) - 1"
}
}
}
}
}
The asset relationship is supplied by the creation path after this collection resolves. It is not a missing map entry that needs to be added to the standard definition.
For collection, search, map, and template syntax, see FSM Searches and Field Mapping and FSM Expressions and Template Tags.
Changing the Project Type and Duration
On the item used by the asset, select a project type in the Field Service Project Type field. In the Field Service Project Duration field, enter the duration in months. These settings determine the standard type and date period for subsequent asset creation requests using that item.
For example, select the appropriate warranty project type and enter 12 for a twelve-month period. The standard lookup uses the selected type. It does not require every configured type to be Warranty. The duration has no supplied default, so a twelve-month period must be entered rather than assumed.
Changing Whether Projects Are Requested
To stop this collection from supplying projects for asset creation requests, use this root fragment:
{
"warranty": {
"asset": []
}
}
This supplies an empty collection. It does not remove existing projects or cancel creation work already requested with resolved project values.
For instructions to edit, merge, preview, and apply custom configuration, see FSM Configuration.
Dependencies and Customization Limits
The standard lookup depends on the asset's item mapping and the item's configured project type. Its date formulas use the item duration and the asset's time zone. If the asset does not supply a time zone, the formulas use the session time zone.
Preserve the item restriction, project type, and valid date values when modifying a collection definition. The resolved values are used to create projects through FSM Project processing, whose record validation and defaults continue to apply. Record-model mapping definitions belong in FSM Record Model Configuration.
When Changes Apply
The collection resolves during the asset-create event. Item setup and configuration changes affect later creation requests without automatically updating existing project types or dates.
Editing an existing asset does not replay this event. A request already carrying resolved project values is not cancelled by changing the item or replacing warranty.asset with [].
Related Topics
- FSM Configuration Reference
-
FSM Automatic Project Creation for New Assets
- Configuring FSM Related Service Work
- FSM Searches and Field Mapping
- FSM Expressions and Template Tags