Deployment Controls and Risks

Use the supplied baseline to identify changes. A setting being editable in NetSuite does not establish that FSM supports changing it.

The following table describes deployment controls, supplied baselines, and the boundaries of each change.

Control	Baseline or Behavior	Effect and Boundary
Deployed and deployment status	Deployments are enabled. The hourly dispatcher is Scheduled. Dedicated background jobs are Not Scheduled. User Event, Client, and service deployments are Released.	Disabling or changing a deployment can prevent requests, form behavior, or services from running. Scheduling an on-demand job changes its submission rules.
Deployment ID, script association, and record type	The verified identities in this reference.	FSM resolves fixed jobs and services by ID. Renaming or repointing an ID, or changing its record type, can disconnect the behavior.
Audience	Record deployments include all internal roles and supplied external center roles. Setup has a narrower audience.	Narrowing an audience can make FSM behavior unavailable to affected roles. Scheduled scripts have no Audience subtab. See the distinction after this table.
Execute as Role	Field Service System for supplied User Event and Suitelet deployments.	Script maintenance manages roles for `customscript_nx_userevent` and `customscript_nx_suitelet`. See Script Configuration Properties for the limits of the role map.
Available Without Login and Field Service URL (`custscript_nx_url`)	Values in Suitelet and RESTlet Deployments.	These settings participate in FSM entry points and request routing. Changes can interrupt access or route a request differently.
Log Level	Audit, except for the Work Order dedicated deployment at Debug.	More restrictive logging can hide assessment, skip, and continuation messages. Changing Log Level does not correct pending or failed business work.
Schedule, priority, and execution settings	Hourly recurrence for the dispatcher. Feature-triggered submission for other fixed jobs.	These govern submission and processor allocation. This reference does not establish support for arbitrary FSM deployment changes.
Field Service Module (`custscript_nx_module`)	Instructions for generated callbacks.	Changing the parameter can change the operation and its inputs. It does not replace customer feature configuration.

Control

Baseline or Behavior

Effect and Boundary

Deployed and deployment status

Deployments are enabled. The hourly dispatcher is Scheduled. Dedicated background jobs are Not Scheduled. User Event, Client, and service deployments are Released.

Disabling or changing a deployment can prevent requests, form behavior, or services from running. Scheduling an on-demand job changes its submission rules.

Deployment ID, script association, and record type

The verified identities in this reference.

FSM resolves fixed jobs and services by ID. Renaming or repointing an ID, or changing its record type, can disconnect the behavior.

Audience

Record deployments include all internal roles and supplied external center roles. Setup has a narrower audience.

Narrowing an audience can make FSM behavior unavailable to affected roles. Scheduled scripts have no Audience subtab. See the distinction after this table.

Execute as Role

Field Service System for supplied User Event and Suitelet deployments.

Script maintenance manages roles for customscript_nx_userevent and customscript_nx_suitelet. See Script Configuration Properties for the limits of the role map.

Available Without Login and Field Service URL (custscript_nx_url)

Values in Suitelet and RESTlet Deployments.

These settings participate in FSM entry points and request routing. Changes can interrupt access or route a request differently.

Log Level

Audit, except for the Work Order dedicated deployment at Debug.

More restrictive logging can hide assessment, skip, and continuation messages. Changing Log Level does not correct pending or failed business work.

Schedule, priority, and execution settings

Hourly recurrence for the dispatcher. Feature-triggered submission for other fixed jobs.

These govern submission and processor allocation. This reference does not establish support for arbitrary FSM deployment changes.

Field Service Module (custscript_nx_module)

Instructions for generated callbacks.

Changing the parameter can change the operation and its inputs. It does not replace customer feature configuration.

Record-deployment audience and background record selection are separate controls. See Defining Script Audience.

Deployment controls in NetSuite are described in Scheduled Script Deployment Record. FSM support for audience, priority, and other deployment changes requires confirmation for the particular deployment.

Script Configuration Properties

The following table lists properties in the top-level script configuration object. These properties affect shared background execution or deployment maintenance rather than a single feature's data rules.

Property	Supported Values	Default	Effect
`timelimit`	Integer, in seconds	`60`	Budget checked before an action in the dedicated assessment and action loop. It does not apply per record or define the callback queue's budget.
`subsidiarydeployments`	Boolean	`false`	With NetSuite Subsidiaries enabled, maintains separate Program deployments for subsidiaries and changes Program deployment selection. It does not provide general concurrency for every job.
`deploymentroles`	Object keyed by deployment ID, with role internal ID values	`{}`	Specifies roles used by Script maintenance for the main Suitelet and User Event deployments. Role selection and maintenance behavior are described after this table.

Property

Supported Values

Default

Effect

timelimit

Integer, in seconds

60

Budget checked before an action in the dedicated assessment and action loop. It does not apply per record or define the callback queue's budget.

subsidiarydeployments

Boolean

false

With NetSuite Subsidiaries enabled, maintains separate Program deployments for subsidiaries and changes Program deployment selection. It does not provide general concurrency for every job.

deploymentroles

Object keyed by deployment ID, with role internal ID values

{}

Specifies roles used by Script maintenance for the main Suitelet and User Event deployments. Role selection and maintenance behavior are described after this table.

The deploymentroles map is not a universal override for all script types. Unspecified deployments use the role named Field Service System where found. Maintenance can replace manual role changes on these managed deployments. The timelimit property does not define the budget for the callback queue described in Generated Deployments.

The schema baseline is:

            {
  "script": {
    "timelimit": 60,
    "subsidiarydeployments": false,
    "deploymentroles": {}
  }
}

See FSM Configuration for shared configuration merging and updates. Feature-specific selection, maps, and rules remain in their configuration topics. Extending a deployment's time budget does not resolve records excluded by errors. It also does not establish that the relevant searches and actions perform well.

General Notices