Configuration Restrictions

•

Empty protocols cannot be added to a workflow. The protocol must include steps.

•

Empty workflows cannot be activated. However, empty workflows can be saved in the pending state.

•

Modify a workflow only while it remains in the pending state. You cannot rename a protocol included in an active or archived workflow.

•

Delete a workflow only while the workflow remains in the pending state. You cannot delete active or archived workflows.

•

A protocol cannot be removed from an active or archived workflow.

•

A protocol cannot be deleted from an active or archived workflow.

•

A protocol cannot be added to an active or archived workflow.

•

Protocols cannot be reordered within an active or archived workflow.

•

Steps in a protocol cannot be added, reordered, or deleted in an active or archived workflow.

•

Settings saved as part of the master step configuration cannot be configured at step level. On the step configuration form, these settings display with a Locked icon.

•

The master step can be changed, providing the new master step is of the same step type. The list of master steps is filtered to show valid options.

•

If you remove configured settings from a master step, the settings on the derived steps revert to their default values unless doing so would leave the step in an unworkable state. For example, the last container from a step cannot be removed. Exceptions to this 'revert to default' rule are noted where applicable.

•

A master step cannot be deleted if it is used to generate a step that is in an active or archived workflow.

•

A master step cannot be deleted if it has already been used to create one or more steps. First, delete the step, and then delete the master step. In this case, the Delete button is disabled.

•

After a step type has been chosen and saved as part of a master step configuration, it cannot be change.

•

A master step field cannot be deleted if it has been assigned a value, or is in use in a step. If a step derived from the master step with which the field is associated has been started.

•

A custom field no longer displays if deleted in the LIMS interface; however, its information is retained in the database for historical purposes.

•

If the field name specified is the same as a field that has been deleted, the new field is created and the conflicting field name is renamed in the database.

•

A custom field cannot be deleted on a global field object or master step with the same name as an existing field on that object/master step. For example, if a global field is created called 'Description' on the Account object, another global field cannot be created called 'Description' on the Account object. However, a 'Description' field on the Project object can be created.

•

Multiple automations with the same name cannot be enabled on a master step, even if the automations are configured differently.

•

Two automations can have the same name as long as they are unique in some other way. For example:

–

channel name is unique, or

–

command line is unique, or

–

run-program-per-eventvalues (available in the API only) are unique