Config Slicer Version Updates

•

The entity summary is now shown after the individual differences have written to the log file, as opposed to before these differences.

•

Support was dropped for the following process type attributes, which are no longer used:

–

SupportsExternalProgram

–

ShowInExplorer

–

ShowInButtonBar

–

OpenPostProcess

–

IconConstant

•

Support was dropped for the show-in-tables property on Custom Fields (UDFs) because it is no longer used.

•

There is now support for the new Clarity LIMS v5.x distinction between Protocol Step names and Master Step (ProcessType) names.

•

It is now possible to slice in and out all the new Master Step settings added in Clarity LIMS v5.0:

–

Default Process Template

–

Instrument Types

–

Container Types

–

Reagent Kits

–

Reagent Types

–

Control Types

–

Sample Fields

–

Queue Fields

–

Ice Bucket Fields

–

Step Fields

–

Step Properties

•

When importing/validating a slice from 4.x into 5.x, if the package contains any Master Steps (process types) or Protocols, it is upgraded to be compatible with the new configuration available in 5.x. This process is automatic, and the updated package is written out to the directory containing the package being imported or the directory that log file is being written to. If errors occur while importing, this updated package can be manipulated directly and imported to fix them.

The following changes were added to support slicing between Clarity LIMS v4.x and v 5.x. All changes are saved into a new configuration package that is written to the same location as the package being sliced:

•

Backwards compatibility for Protocol Step setup configuration.

•

Support for updates of parent entities after both the parent and child entities have been imported.

–

This change is required for updating the defaultProcessTemplate and step-fields step properties on Master Steps. Both require that the Master Step (ProcessType), ProcessTemplate, and Master Step Custom Fields (ProcessType UDFs) exist before they can be set on the Master Step.

•

Support for setting the qcProtocolStep flag on Master Steps, allowing the correct Master Step type to be displayed in the Lab Work Configuration UI. The setting is propagated up from the Protocol Step to the Master Step.

•

Support for setting the default container on Steps and Master Steps in such a way that all behavior is maintained from 4.2.

–

If every child step of a Master Step has the default container that was defined as a permitted container on the master (through the OutputContainerType process-type-attribute), then the default is added as a permitted container on the master step.

–

If any child does not have the default container from the Master Step, then the default is removed from the Master and each child that had the container is updated so that the default is the first permitted container (and hence default).

•

Extra containers and any step properties that are no longer valid on a step are migrated to new properties or removed.

•

Step-setup file configuration has been moved to the Master Step and it not possible to have a different set of step-setup files on a step than are specified on the Master. The master step owns the list of files. Both the search-result-file-index attribute on each file element and the message element for each file are defined by the Master and must be duplicated on every step. When moving a 4.x configuration with step-setup files to a 5.x configuration, the following events will occur:

–

The set of all the step-setup files found on all the child steps in the slice are added to the Master Step and each child step.

–

If more than one step in the slice defines step-setup files for the same search-result-file-index, then all the messages for that search-result-file-index are concatenated by newlines.

–

The enabled attribute is set to true for the step-setup on all child steps.

–

The locked attribute is set to false for the step-setup on all child steps.

–

In the case of importAndOverwrite, the step-setup of any existing child steps for an overwritten master step is included.

•

Upon validation after import, the following differences have been reconciled:

–

UDFs that differ by style only

–

missing defaultProcessTemplate

–

missing attemptAutoPlacement

–

missing autoAttachFiles

–

missing qcWithPlacement