FSM Automatic Project Creation for New Assets
FSM can automatically create a project associated with a newly created asset. The standard setup uses the asset's item to supply the project type and duration. The dated project can represent a warranty or another service context without requiring separate project entry.
After creation, the project can appear on the case form for the same asset if the project is active. Its date range must also include the case's start date. This makes the capability useful for other service contexts that fit the same model; it is not restricted to warranties.
How it Works
When FSM handles the asset's creation, it looks up the asset's item. If Field Service Project Type is set on the item, FSM uses the selected type for the linked project. FSM calculates the project dates using Field Service Project Duration. FSM then requests background creation of that project.
The standard definition sets the start to the current date in the asset's time zone. It calculates the end by adding the item's Field Service Project Duration in months and subtracting one day. If the asset does not supply a time zone, the date calculation uses the session time zone.
For example, an asset is created on 12 October 2026 in the applicable time zone. Its item specifies a Warranty Project Type and a duration of 12 months. The project period runs from 12 October 2026 through 11 October 2027. These are illustrative dates and setup values.
Prerequisites
The asset must identify the item used by the standard lookup. That item needs a Field Service Project Type and an appropriate Field Service Project Duration. The required FSM asset and project processing must be available, with access to read the item and create the resulting project.
For settings, the standard JSON definition, and the effects of setup changes, see Configuring FSM Automatic Project Creation for New Assets.
Key Behaviors
The following table describes when FSM requests project creation and how asset edits or configuration changes affect the request.
|
Condition or Scenario |
Behavior |
|---|---|
|
The asset's item has a populated Field Service Project Type |
The standard lookup supplies a project of that type for background creation. |
|
The item has no Field Service Project Type |
The standard lookup does not supply a project. |
|
The item's Field Service Project Type is set to a value other than Warranty |
The standard definition uses that configured type. It does not require a type named Warranty. |
|
An existing asset is edited |
The asset-create event is not replayed by that edit. |
|
The |
FSM requests no projects through this collection. |
FSM uses the current date when it processes asset creation, rather than an Item Fulfillment date or an installation date. The item duration controls the period calculated by the standard definition.
Record interactions
The feature reads setup from the item and creates a relationship between the new asset and its project.
|
Record |
Role in the Feature |
|---|---|
|
Item |
Supplies the Project Type and duration used by the standard definition. |
|
Asset |
Supplies its item and time zone. Asset creation triggers the lookup, and the requested project includes the asset ID. |
|
Project |
Receives the type and dates, is linked to the asset, and is created through FSM project processing. |
Project record behavior and Project Type defaults continue to apply to the created project. For relationships between assets, projects, cases, and tasks, see FSM Related Service Work.
Processing Model and Lifecycle
Sourcing and project creation are separate stages. A saved asset and a submitted creation request are distinct from a successfully created project.
|
Stage |
What Happens |
|---|---|
|
Asset creation |
FSM resolves the configured collection in the new asset's context. |
|
Project request |
Each supplied project receives the asset relationship and is submitted for background creation. |
|
Project creation |
Background processing uses the project model to create the project with the supplied asset relationship. |
The request carries the values resolved during asset creation. Later changes to item setup or the collection do not rewrite those supplied values. Editing the asset is not a retry procedure for a missing project.
Configuration
The item's Field Service Project Type and Field Service Project Duration determine the standard project type and date range. The warranty.asset collection supplies the project values. An empty collection disables creation requests through this path.
Limitations and constraints
This capability automatically creates a dated project associated with a new asset. Warranty is one use of that project. The configured project type determines the resulting service context.
Changing setup does not remove existing projects or create replacement projects for existing assets. Project creation does not define a recurrence pattern. Program behavior depends on the project's setup. For more information, see FSM Program.