Configuring FSM Enhanced Technician Notes

Configure the inherited Clean Up action for FSM Mobile text areas, its default prompt, and any element-specific prompt choices. For details about editing behavior, language selection, errors, and when revised text is saved, see Enhanced Technician Notes.

The shared settings belong inside the root form object in Field Service Configuration. An element override belongs inside its existing resource under the literal "routes/mobile" key. For editing, activation, and merge rules, see FSM Configuration.

Properties and Defaults

The following table lists the configuration settings, accepted values, defaults, and effects.

Property or Setting	Location	Accepted Value	Default	Effect
textenhance	form	Boolean	false	When true, supplies the configured cleanup prompt as the inherited prompt for eligible text areas. When false, supplies an empty inherited prompt.
cleanupprompt	form	Prompt internal ID or saved Script ID as a string	"-27"	Selects the shared prompt. The cleanup service also uses it when no prompt is supplied with a request.
textenhance	routes/mobile.<resource ID>.element.<element name>	Prompt internal ID or saved Script ID as a string; "" to remove the action	Inherits the shared prompt when enabled; otherwise an empty inherited prompt	Overrides the prompt for this text area. An explicit empty string removes its Clean Up action.
Field Service Language	Employee record	Available FSM language	Effective user language when Multi-Language is enabled; otherwise account default language	Participates in selection of a related language prompt.

An element's prompt must be a string identifying a prompt, not the Boolean value true. The outer form.textenhance flag and the element's textenhance value have different types and purposes. For the shared input definition, see FSM Mobile Element (Block) Reference.

Default JSON

These are the explicit standard defaults:

            {
  "form": {
    "textenhance": false,
    "cleanupprompt": "-27"
  }
} 

          

The element prompt is supplied when resources are rendered, rather than being a fixed "-27" property on every standard element. With the shared flag enabled and no element override, the inherited prompt is the configured form.cleanupprompt. With the flag disabled, the inherited prompt is empty.

Prerequisites

Use a supported editable textarea element mapped to an appropriate NetSuite text field. Existing long-text field definitions can normalize to this FSM Mobile type. To choose a prompt, you don't need to replace existing mappings or copy the resource.

The account must provide the NetSuite generative AI service used by prompt evaluation. Current platform availability is described in Generative AI Feature Availability in NetSuite. Administrators configuring custom prompts need access to Prompt Studio; an Administrator role or Setup Prompts (ADMI_PROMPTS) permission provides that access. Technicians do not need to manage prompts to use a configured FSM Mobile action.

Using Enhanced Technician Notes consumes NetSuite AI Units. See NetSuite AI Units and NetSuite Features and AI Units FAQ for allowances and usage monitoring.

Changing Inherited Availability

To make the generic cleanup prompt available to eligible text areas, enable the shared flag:

            {
  "form": {
    "textenhance": true
  }
} 

          

The omitted cleanupprompt remains inherited, with the standard value "-27" unless the account has another override. These examples are fragments to merge into the account configuration.

Setting form.textenhance to false removes the inherited prompt. If a text area has its own explicit prompt, also set that element's textenhance to "" when its action must be removed. The shared flag controls the inherited prompt; it is not a substitute for service-access permissions.

Changing the Prompt

Use an available whole-text prompt. A saved custom prompt's Script ID includes the custprompt prefix added by NetSuite. For example, a prompt created with Script ID suffix _fsm_textenhance is referenced using its saved ID:

            {
  "form": {
    "textenhance": true,
    "cleanupprompt": "custprompt_fsm_textenhance"
  }
} 

          

The Script ID is illustrative: it must identify the actual saved prompt in the account. Alternatively, use that prompt's internal ID as a string.

Choose a Prompt for Actions Taken

The following fragment changes the prompt for the existing Details resource's Actions Taken text area. It retains the element's inherited field type, mapping, and edit restrictions:

              {
  "form": {
    "textenhance": true
  },
  "routes/mobile": {
    "details": {
      "element": {
        "actions": {
          "textenhance": "custprompt_fsm_textenhance"
        }
      }
    }
  }
} 

            

Use the actual prompt identifier. The standard actions element is a long-text definition mapped to custevent_nx_actions_taken; it is read-only for a team user where its existing rule applies. Assigning a prompt does not make that field editable.

To remove Clean Up from that text area and keep inherited enhancement available elsewhere:

              {
  "routes/mobile": {
    "details": {
      "element": {
        "actions": {
          "textenhance": ""
        }
      }
    }
  }
} 

            

Omitting an element override lets it inherit again; an explicit empty string disables that element's action.

Prepare a Custom Prompt and Language Variants

Prepare a Custom Prompt and Language Variants

1. Go to Setup > Company > AI > Prompt Studio. Click Create Prompt, or copy an appropriate existing whole-text prompt.

2. Enter a unique prompt name and Script ID suffix, such as _fsm_textenhance. Select the Language, select a Language Variant if needed, and complete the other required settings.

3. Configure the prompt to consume the input variable text and return the complete revised text. FSM supplies that text variable; it does not supply arbitrary Task, Case, Asset, or form-field values. For full prompt settings and template syntax, see Manage Prompts.

4. If you need related language prompts, create separate prompts with the same base Script ID and an appropriate locale suffix. For example, use _fsm_textenhance_es. Set each prompt's Language and Language Variant to the intended values.

5. Click Save for each prompt. Use the saved base prompt's full Script ID or internal ID in form.cleanupprompt or the element's textenhance setting.

FSM searches for a related prompt matching the effective user's language and matching or unspecified variant. If no related prompt is found, it evaluates the configured prompt. The prompt instructions determine the output language; setting a language alone does not establish a translation workflow. See Configuring FSM Localization and Translation for the shared language settings.

Dependencies and Customization Limits

Important:

Use whole-text prompts. Partial enhancement is not supported by the FSM Mobile action.

Preserve the existing resource and article map. The cleanup response updates an input; normal saving and synchronization write its value to the mapped record field. Prompt configuration does not add field permissions or remove required-field rules. It also does not guarantee that generated text meets the record's length requirements.

Read-only and disabled text areas do not expose Clean Up. The online action is disabled when FSM Mobile is offline or the input is empty. An unavailable prompt or failed service request does not turn the cleanup action into a successful record save.

When Changes Apply

Inherited and element prompt choices are included when the affected FSM Mobile resource is rendered and loaded. Reload the affected configuration through the guidance in FSM Mobile Resource Selection and Shared Data. A loaded element can retain its previous prompt until refreshed.

Changes affect subsequent cleanup requests and do not rewrite saved notes or reverse text already accepted and synchronized.

Related Topics

• Enhanced Technician Notes
• FSM Mobile Element (Block) Reference
• FSM Mobile Resource Properties Reference

General Notices