Copilot for Checklist Template Generation

The Checklist Template Copilot helps you create and iteratively refine a checklist structure from natural language prompts. It is available on both the Checklist Template and Checklist Version pages. The generated draft can include section headlines, questions, boolean answer groups, hierarchy, criterion or inspection intent, input types, variable codes, numeric limits for decimal or integer inputs, the More Answers Possible setting on question lines, and variable options for single-selection questions.

After an initial prompt creates a draft, you can send follow-up instructions to add, change, or remove lines; the draft is kept between rounds instead of being discarded. The generated content is not written to the checklist template or version until you choose the Confirm button.

Setup

Ensure that the Azure OpenAI settings are defined in the Configure to Order Setup page and the Checklist Copilot is registered in the Copilot & agent capabilities page either manually or via the Register Checklist Copilot Capability function.

Usage

Open the Checklist Template page, or the Checklist Version page for a specific version.
Choose the Copilot Template button on the top right of the page.
In the Copilot - Generate Checklist Template page, you can optionally use the Base on Master BOM (optional) section to select a Master BOM Code whose variables should be considered when generating the checklist. If the Master BOM references item components that themselves have a Master BOM, you can also select a BOM Type so those component Master BOMs are resolved and analyzed as well. For more information, see Basing the Draft on a Master BOM.
Enter a natural language description of the product or machine for which the checklist template should be created, or choose the Attach a file button to add a text or JSON file with specifications.
NOTE: If a Master BOM Code is selected without entering a description, a default prompt is used to generate the checklist from the Master BOM structure.
Choose the Send Prompt button to create the initial draft.
Review the generated draft.
- Existing variable codes and options are shown in green; newly proposed variable codes and options are shown in orange.
- Edit generated lines directly if needed.
- Delete lines that should not be created.
- Choose the value in the Variable Options field to review and edit the generated options before confirmation. The option count on the line is updated if you add or remove options.
To refine the draft, enter an instruction in the Follow-up Instruction field (for example, to add, change, or remove specific lines) and choose the Send Follow-up button. Repeat as needed; the current draft is used as the basis for each follow-up.
After reviewing the draft, choose one of the following:
- Choose the Confirm button to create the new checklist template or version lines. If the template or version already contains lines, you are asked whether to apply the reviewed draft as the new structure.
- Choose the Discard button to close without making any changes.

After confirmation, the following are created:

New checklist template or version lines in the Checklist Template or Checklist Version page.
New variables in the Variable/Attribute Types page if a generated variable code does not already exist; existing variable codes are reused instead of duplicated.
New variable options for generated single-selection questions in the Variable Options page; existing options, including options inherited from another variable through an option reference, are reused instead of duplicated.
A run log entry that records how many lines, variables, and options were created, and how many existing variables and options were reused.

Note

If the draft adds new options to existing variables that are shared master data, you are asked to confirm the change before the options are added, because other checklists or Master BOMs may rely on these variables. If a variable inherits its options from another variable through an option reference, its proposed new options are not added; a message lists the affected variable codes instead.

The generated draft can also include:

Criterion or inspection intent values
Lower and upper numeric limits for decimal or integer inputs
The More Answers Possible setting on question lines

Note

The Criterion / Inspection Intent field is hidden by default in the Checklist Template lines but can be shown via personalization.

Basing the Draft on a Master BOM

When a Master BOM Code is selected, its variables are analyzed recursively so the generated checklist can drive the Master BOM's existing formulas:

Variable codes referenced in description placeholders (for example, #VARIABLE#), formula fields, and attribute formula values are collected from the Master BOM lines.
Master BOM lines of type Master BOM are analyzed recursively.
If a BOM Type is selected, item component lines are resolved to the Master BOM assigned for that BOM Type and analyzed recursively as well.
Unless your prompt explicitly requests otherwise, only variable codes actually used by the Master BOM are generated; the Copilot does not invent unrelated variables and does not add options beyond those that already exist for a reused variable.

Copilot Run Log

Each confirmed template generation run is recorded in the Copilot Run Log page, accessible via Tell Me. The log shows when the run was executed, which user started it, which checklist template and version were affected, and how many lines, variables, and variable options were created or reused.

Use the drill-downs in the log page to review the records created by a specific run.

Current Scope

This feature creates or updates a checklist structure through an iterative draft process; nothing is written to the checklist template or version until you confirm. After review and confirmation, the generated content creates lines, variables, variable options, criterion values, hierarchy, input types, multiple-answer settings, and numeric limits.

This feature does not populate dynamic formulas, messages, translations, price calculation fields, or write-back settings.

Although the description field is not pre-populated with the existing checklist content and is cleared after each Send Prompt or Send Follow-up, the current draft (or, for the first prompt, the existing checklist template or version lines) is automatically provided to the Copilot as context, together with existing variable and option master data. If the checklist template or version already contains lines when you choose Confirm, you are asked whether to apply the reviewed draft as the new structure; confirming replaces the existing lines with the draft.

Table of Contents

Copilot for Checklist Template Generation

Setup

Usage

Note

Note

Basing the Draft on a Master BOM

Copilot Run Log

Current Scope

See Also