Use this guide when the process already has an appropriate production-entity setup. Before editing, agree which entity the operator should select and where it comes from. If this is new to you, complete the first-workflow exercise first; a production entity is not needed to learn to write and connect two instructions.
Use production-entity settings when a step needs the platform's configured machine/equipment behavior. This is different from attaching an informational tool or a Location to a regular instruction.
The relevant production entities and their types must already be configured.
Read-only example. These controls are disabled in the capture; use an editable practice draft to configure them.
Select the step's mode
Add or select a step.
Open Process.
Find Production Entity Mode.
Choose None, Production Entity Type, or Production Entity.
Select the intended types or specific entities for the chosen mode.
None leaves the step without production-entity mode. Type selection defines an eligible category of entities; specific-entity selection identifies the individual entities.
Multiple selections can be configured. Review the complete selection rather than assuming the first item is the only eligible one.
Keep the instruction clear
In Basic Info, explain what the operator must do with the equipment and what identifies the correct item or machine.
Connect the step into the workflow and check its incoming and outgoing paths. Choosing an entity does not replace the surrounding route design.
What this does not configure
The step selector does not establish a new OPC UA/SQL connection, define all machine parameters, or configure every production-entity trigger.
Maintain those settings in the entity's own configuration. Entity triggers and workflow step triggers are separate surfaces and have different purposes.
Test with the intended context
Preview can help inspect the instruction, but production-entity execution can depend on Work Order, Stock, serial, and entity state.
Use a controlled real test session with suitable test data. Verify:
The intended entities are eligible/available.
The operator can identify the correct entity.
The expected check-in/check-out actions and state changes are available.
The required records and parameter values appear where the process expects them.
Step completion and later navigation behave correctly.
Do not treat a successful preview as proof that a physical-device operation or entity transaction occurred.
If something is missing
Check the selected mode, the type/entity selection, deleted or unavailable catalog records, permissions, and the execution context. Capture the workflow/version and entity involved when reporting a problem.