VWorks records of interest
About this topic
This topic describes the VWorks Plus records of interest (ROI).
Types of records of interest
VWorks has two categories for records of interest:
1 Records that transition through state changes: In Development, In Validation, and Released
2 Records that are exempt from state changes
VWorks records that transition through state changes
Records in this category transition through the following states. The following table lists the types of records in this category.
• In Development. By default, the software does not create an audit trail log for records in development. However, the software includes an option to log the audit trail entries for In Development records. For details, see Setting audit trail options. If an audit trail is being logged, the Audit Comment dialog appears any time you modify and save a record in this state.
A VWorks technician or administrator can edit records that are In Development. Only a VWorks administrator can delete records that are In Development. For a list of the types of records that can be deleted, see the following table.
• In Validation. The software automatically logs an audit trail for In Validation records. The Audit Comment dialog appears any time you modify and save a record in this state.
Figure Example of Audit Comment dialog box
 |
A VWorks technician or administrator can edit records that are In Validation. These records cannot be deleted within the VWorks interface.
• Released. The software prevents any changes to records that are in the Released state. If you attempt to save a change for a released record, a message appears stating that the record cannot be changed. These records cannot be deleted within the VWorks interface.
Note: A VWorks administrator can delete records of interest in the Content Browser regardless of record state. For details, see the VWorks Plus Configuration and Administration Guide.
• Pending. If e-signatures are enabled, the software prevents any changes to records that are pending signatures. Pending records may still be used, but they may not be modified or transitioned until all e-signatures are completed.
 |
Table Types of records that transition through state changes
Record of interest (file extension) | Description |
|---|---|
Device file (.dev)* | A file that contains: • The list of devices the software will communicate with and control • Configuration information of each device • Communication settings (profile) |
Device profile (.xml) | A file that contains a collection of settings that the VWorks software uses to communicate with a specific device, for example, the Bravo Platform.  Although profiles can transition from the In Development state to the In Validation state, these records cannot transition to the Released state. This exception is necessary because adjustments to the teachpoints for a given device may be required if the instrument is moved to another location or if a hardware collision occurs. A teachpoint adjustment would result in an update to the device profile. |
Error library (.elb)* | A file that contains a collection of automated error responses. |
Form file (.VWform)* | A file that provides a simplified user interface for running a protocol. |
Hit pick format (.xml) | A file that is used by hit picking protocols to specify the destination well pattern and a few other items. |
Labware entry (.xml) | A file that contains a collection of labware properties that the VWorks software uses to handle a given labware type in the automation system. Note: Each labware entry is assigned to a labware class or classes. Labware classes are exempt from record state changes, but labware entries in the released state cannot be removed from a labware class. |
Liquid class (.xml) | A file that specifies pipetting settings, set up for different liquid types. |
Macro library (.mlb)* | A file that contains a collection of macros. A macro is a collection of protocol tasks in an abbreviated form that you can insert at various places within the same protocol or throughout other protocols where the same task sequence is required. |
Pipette technique (.xml) | A file that specifies the x- and y-axis offset when pipetting. |
Protocol file (.pro)* | A file that contains instructions for performing a run. |
Runset file (.rst)* | A file that specifies a collection of protocol runs that can be scheduled in advance to be performed without operator intervention. |
*These records cannot be deleted within VWorks even when In Development because the VWorks interface does not provide a mechanism for deleting them. | |
Records exempt from state changes
VWorks logs all the audit trail entries for an exempt record of interest starting from the creation of the file. The Audit Comment dialog appears any time you modify and save a record of interest that is exempt from record state changes.
Figure Example of Audit Comment dialog box for exempt record
 |
The following table lists the records of interest that are exempt from record state changes.
Table Types of records exempt from state changes
Record of interest (file extension) | Description |
|---|---|
VWorksOptions (.xml) | A global options file that specifies parameter settings that apply to all the protocols on the computer running VWorks Plus. Note: To view these options in the VWorks window, click Tools > Options. For details, see Setting general and view options. The software logs an audit trail for this record, starting with the creation of the record and tracks any subsequent changes. |
Labware class (.xml) | A file that lists a collection of labware entries that can be used with a given device, for example, Uses Standard Platepad or Uses Filter Platepad. |
Teachpoint file (.xml) | A device-dependent file that contains your teachpoint settings, for example, a BenchCel teachpoint file. |
Miscellaneous files that are imported into the Secure Storaget Repository. The software logs an audit trail for the following records after they are imported into the Repository. | |
Barcode files (.bar, .csv, or .txt) | An input file for specifying the barcodes to apply to a microplate. |
Excel files (.xlsx, .xls, or .xlsm) | A utility file for calculating volume requirements or for creating a method used by the AssayMAP Protein Sample Prep Workbench. |
Gantt chart files (.gnt) | A file that contains a Gantt chart for one or more protocols while they are running, or for one or more open protocols that have been run in the current VWorks session. Note: You must import these files to view them in the VWorks window. |
Hitpick input files (.csv) | An input file used by the Hit Pick Replication task. The file contains information about the source microplate and specifies the dispense pattern in destination microplates. |
Image files (.jpg, .png, .bmp, or .ico) | An image file referenced by a labware definition or a form file. |
Inventory database files (.sql) | A labware inventory database file. |
Experiments database files (.expTags) | Archived files and exported files that contain experiment data in XML format. The software saves these files to the local file system, not Shared Services storage. Ensure that you move these files to a secure location. |
JavaScript (.js) | A text file that contains JavaScript code that is used to execute instructions, for example, in a protocol task. The JS Wrapper task uses a JavaScript task file (.js). |
Related information
For information about... | See... |
|---|---|
Compliance features | |
Audit trails | |
Record states | |
Global options | |
Miscellaneous files | |
Tamper detection | |
Labware inventory | |
Experiment IDs and Experiments database |