Start with a small request in a practice draft. Before applying a proposal, identify which steps it should change and what a correct result would be. If the feature is not available in your environment, continue editing manually; it is not required for the beginner path.
The editor can provide an AI Assistant for proposing workflow changes. Other AI surfaces include instruction generation in Import Nodes from Workflow and translation tools, when their required services are enabled.
Check availability
The AI Assistant button in the header appears when the assistant service is enabled for the environment. If it is absent, ask your administrator to confirm the configuration.
Import Nodes from Workflow can display a disabled AI-generation area when its service is unavailable. Do not assume every AI surface is enabled simply because one is visible.
The AI assistant opens beside the editor. Its input explains that questions are allowed but write tools are disabled in read-only mode. Applying a change requires an editable draft and the appropriate service availability.
Ask for a small, specific change
Select the relevant step or explain the scope in your request. For example:
Rewrite this instruction in shorter operator language.
Add a review step after the inspection.
Propose explicit Pass and Fail routes.
Translate this instruction into an enabled content language.
Provide the process facts and acceptance limits. Review the result for technical accuracy; the assistant should not be treated as the source of an engineering specification.
Review the proposal
The assistant presents proposed operations for review. You can approve or reject individual rows and use the available bulk actions.
Approving a row applies that change immediately. You do not need to wait for a separate final Apply after approving every row. Review the rest of the proposal with that in mind.
Inspect the edited workflow after approval. Use the available undo/revert controls if a change is unwanted, then confirm save status and validation.
What requires your attention
An assistant proposal is not a published release. You still need to inspect the instructions, fields, conditions, and targets; test the affected paths; and run the publish process yourself.
Step-level certifications or operation codes are different from system-wide user permissions or ERP configuration. Do not use an assistant request as a substitute for administering those external settings.
Translation and imported steps
AI-generated translations and imported instruction rows also need review. Check terminology, units, choices, fields, and connections in the resulting workflow.
For data-handling, hosting, or access questions, use the information confirmed for your organization's deployment. Availability of the button alone does not establish those details.