Skip to main content

Configure the device selection options in Protocols

Learn how to expose the execution mode(s) in your protocols

Updated over 3 weeks ago

This documentation will teach you how to enable device selection within protocol workflows, allowing users to switch devices for different stages of their processes. It covers the configuration of device selection steps, execution modes, tip types, and input-plate types.

Configuring Device Selection Steps: Device selection can be configured in two ways:

  • Create a dedicated step for users to select devices (recommended for ease of use).

  • Include device selection options at any point in the protocol.

Enabling Device Selection for Stages:

  1. Navigate to the “Devices” tab on the Define Protocol page.

  2. Use the panel on the right-hand side to toggle on the device you wish to link to the selected step device selection.

  3. Once you have toggled the desired devices, click “Next”.

Providing Context and Reordering Steps:

  1. Once toggled on, the selected devices, stage names, and input plate selection fields will appear in the Personalize Protocol stage of the protocol creation interface.

  2. As with parameter steps, each device selection step in the protocol can include descriptions and context for clarity.

  3. Users can reorder steps as needed.

Important parameters include:

  • Execution mode for each configured stage

  • Input plate type, which may need to change when switching devices.

Publishing and Launching the Protocol:

After configuring the protocol, publish it with a relevant name and tags. Upon launching the protocol, users will see information about each device for every stage. From here, you can change devices, deck configurations (where appropriate), and input plate types directly from the protocol interface.

Benefits of Device Selection:

Device selection provides flexibility in lab workflows. Labs are busy places; device availability and last-minute changes can mean you have to adapt your protocol. With device selection in protocols, this has never been easier!

Did this answer your question?