Generating Cases from a Project Program
Use configured Project Program rules to create service cases from an existing project. The project supplies the service context and schedule boundaries. Each generated case is a separate standard NetSuite case record linked to the project through Company.
This procedure supports one planned service occurrence or repeated service work. The configured rules and complete calculated plan determine the number of occurrences.
For field definitions and record relationships, see FSM Project Record and FSM Case Record.
Before You Begin
The project must have a Field Service Project Type, Start Date, and either End Date or a usable Program Create Until value. Applicable Project Program rules must already be configured. The standard configuration supplies no predefined Program schedule.
For the generation stages and rule requirements, see FSM Program.
Use a project classified as active for Program. A project request assesses both case additions and removals. Inactive-project and removable-case classifications can permit removal of existing work.
For one occurrence, the complete matching plan must contain one occurrence. An occurrence count on one rule does not limit other matching rules.
To generate cases from a Project Program:
-
Go to Field Service > Projects > Projects.
Open the intended project for editing.
-
Review its Field Service Project Type, customer, asset, Start Date, End Date, and Time Zone.
The supplied FSM form labels Field Service Project Type as Type. This FSM classification is separate from the native Project Type.
-
Review Program Start Date and Program Create Until when used. Program Start Date establishes the pattern's starting point. If it is blank, Program uses the project Start Date. The project Start Date provides the lower calculation boundary. Program Create Until is a horizon in days, not a stored end date.
-
On Field Service, open Program and review the calculated rows and matching cases. For one occurrence, confirm that the complete plan contains only the intended occurrence.
A planned row is not a saved case. Matching uses chronological order and case type, rather than exact dates. Existing manual or recurring cases can affect the matches.
For column meanings and a case-matching example, see FSM Program Planned Rows and Case Matching.
-
Check Field Service Update Program. Some forms shorten this label to Update Program.
-
Click Save.
After Saving the Project
The project save stores the request. Background processing creates eligible missing case records and can assess qualifying removals. The request itself does not create a case immediately.
After processing, open the matching saved cases. Confirm their case types, customer, asset, service dates, time zones, and Company links to the project.
Applicable Case Program rules can separately request child CRM tasks. Confirm those saved tasks before requesting further work. If required tasks are missing, use Generating CRM Tasks for a Case with Program. If the intended path uses manual visits, use Adding CRM Tasks to a Case in NetSuite.
Next-only, advance, and all-planned creation are timing variations of this procedure. In a next-only plan, closing a case without the required Field Service completion values can leave the next occurrence ineligible.
For request handling, completion-date requirements, and processing results, see FSM Program Processing and Case Closure.
For one-occurrence work, completing the case and closing the project are separate outcomes. A rolling Program Create Until value prevents automatic project closing, even when the plan contains one occurrence.