Turn a business requirement into form questions, configuration and reviewed automatic actions.
Product location: /qms/{standardCode}/chat (fallback: /qms/standards)
Use the QMS assistant to help define what a form should collect and then maintain its fields and sections. Begin with the purpose of the record and the decisions it supports. Identify the existing template by its name and standard so the assistant can inspect the right definition.
For example: “Help improve our Supplier Evaluation Form for an annual supplier review. We need a consistent recommendation, supporting observations and follow-up for significant findings. Read the existing form first, then ask me about the criteria before making changes.”
Open the standard's chat and use the mode appropriate to authoring, such as Producing. Keep this work in its own conversation and provide relevant approved procedures or knowledge sources.
Product location: /qms/{standardCode}/chat (fallback: /qms/standards)
Ask for a proposed structure with sections, field labels, answer types, required status and the reason for each question. Include the people answering it, terminology, units and any evidence they must collect.
A useful follow-up is: “Show me the proposed questions as a table. Separate the supplier's identity, performance observations and final recommendation. Reuse our existing field codes and point out any ambiguity.”
Review the proposal and answer the assistant's questions. When you want only a discussion, state that explicitly. When you want the agreed definition saved, identify those changes precisely. Field, section, repeating-group and form-settings changes save the template directly; inspect the form editor afterwards.
Product location: /qms/{standardCode}/chat (fallback: /qms/standards)
Describe the choices and their business meaning. For example: “Use outcomes Accept, Accept with actions and Do not approve. Require an explanation for the last two. Keep the stored values stable for our output rules.”
Give the actual allowed numeric ranges, reference formats and useful defaults. Ask the assistant to explain the validation and the correction message respondents will see. An example is: “For sample quantity, allow zero through one hundred and explain the unit. Keep a blank answer different from zero.”
Review field settings and display conditions in the saved definition. A hidden answer is retained for later editing and excluded from submission and outputs while hidden.
Product location: /qms/{standardCode}/chat (fallback: /qms/standards)
State what the result should mean, the units and a small worked example. Ask for the formula and expected results before using it operationally.
For example: “For each inspected sample collect quantity and findings. Calculate the total quantity across entries. Show what the result should be for quantities two, three and five, and explain how incomplete entries are handled.”
For a repeated set of questions, describe what one entry is called, in singular and plural, and the minimum and maximum number of entries. A minimum of 0 lets the group be left empty, for example findings on a clean inspection. Review the group and member identities in the form, then test the result using the calculation reference.
Product location: /qms/{standardCode}/chat (fallback: /qms/standards)
Ask for layout changes in terms of how people work: “Present identification, observations and recommendation as three sequential steps. Allow drafts because the evidence may need to be gathered over several days.”
Specify validation timing, progress and the final submit message when these matter. After a saved change, open Form Settings and Preview to review the configuration and the respondent's path.
Use targeted follow-ups such as “Keep the existing field codes and options; only improve the instructions” when the change should be limited. Ask the assistant to read back what it saved and retain any remaining questions for review.
Product location: /qms/{standardCode}/chat (fallback: /qms/standards). Ask the assistant to inspect existing form actions and propose supported integrations; review each configuration before accepting it.
Ask which useful output actions are available for the actual form and enabled modules. For example: “Review the actions already configured on this form. Suggest how a significant supplier finding could create a CAPA and, where appropriate, a risk for assessment. Show each proposal and the required mappings before applying it.”
Review the proposed destination, conditions, record names, owners and values. Refine or reject proposals that do not fit the process. Accept an integration only when its configuration expresses the intended behavior; the assistant can apply an accepted integration as a saved output rule and action.
Open Manage Actions afterwards and inspect the saved configuration. Use output rules for action order and approval gates. Test the rule with an actual controlled example submission.
Product location: /qms/{standardCode}/forms/{templateId}/edit (fallback: /qms/standards)
After authoring, inspect the template in Edit Form. Check the fields, sections, choices, formulas, conditions, defaults and settings. Use the preview to exercise the choices and the saved response to verify the outcome.
A useful final request is: “Summarise the saved changes, identify any unresolved decisions and give me test inputs for every conditional branch.” Review those examples yourself and inspect the resulting records.
Use the record's own approval workflow when appropriate. Approval of an integration configuration, submission of a response and approval of a resulting document are different decisions.
Product location: /qms/{standardCode}/chat (fallback: /qms/standards)
Ask the assistant to inspect the existing definition and outputs before recommending changes. Give an example of the problem: ambiguous answers, repeated manual copying, missing evidence or unnecessary questions.
For example: “Review this form and its output rules. Suggest how to avoid entering the same supplier reference twice and make the required follow-up clearer. Preserve historical meaning and list dependencies before changing codes or types.”
Review small groups of changes and test them together. Use connected workflow examples for ideas combining forms with processes, controls, Vault documents and other modules.
