LIMS Thermo Phisher

SQL*LIMS
SQL*LIMS® v5 Software
User Guide
© Copyright 2004, Applied Biosystems. All rights reserved.
Information in this document is subject to change without notice. Applied Biosystems assumes no responsibility for any errors that
may appear in this document. This document is believed to be complete and accurate at the time of publication. In no event shall
Applied Biosystems be liable for incidental, special, multiple, or consequential damages in connection with or arising from the use
of this document.
Software and firmware programs are protected by copyright. It is unlawful to duplicate these programs in any manner other than for
the user’s personal use. Specifically, it is unlawful to use or duplicate these programs other than for use with the purchaser’s
computer.
APPLERA CORPORATION MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABLILITY AND FITNESS FOR A
PARTICULAR PURPOSE. Applera Corporation shall not be liable for errors contained herein or for incidental or consequential
damages in connection with the furnishing, performance, or use of this material.
NOTICE TO PURCHASER: LICENSE DISCLAIMER
Purchase of this software product alone does not imply any license under any process, instrument or other apparatus, system
composition, reagent or kit rights under patent claims owned or otherwise controlled by Applera corporation, either expressly or by
estoppel.
TRADEMARKS:
Applied Biosystems and SQL*LIMS are registered trademarks and AB (Design), Applera, SQL*QA, SQL*Stability,
SQL*Schedule, and SL Solution are trademarks of Applera Corporation or its subsidiaries in the U.S. and/or certain other
countries.
Microsoft, Windows, Windows NT, and Windows 2000 are registered trademarks of Microsoft Corporation.
Oracle, SQL*Net, and SQL*Plus are registered trademarks, and Oracle 9i and PL/SQL are trademarks of Oracle Corporation.
All other trademarks are the sole property of their respective owners.
Part Number 4347767 Rev. B

09/2004
DRAFT
September 11, 2004 6:43 pm, 00_UG_Title_Copyright.fm
Contents
Preface
How to Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
How to Obtain More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
How to Obtain Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Safety Information
Safety Conventions Used in This Document . . . . . . . . . . . . . . . . . . . . xvi
Workstation Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Chapter 1 Basics
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Instance Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Jobtype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Datagroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Workgroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Status and Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Starting the Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Exiting the SQL*LIMS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Changing Your Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Accessing Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Instance Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Displaying All Text in a Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Entering Information into the Database . . . . . . . . . . . . . . . . . . . . . . . 1-21
SQL*LIMS User Guide iii

DRAFT
September 13, 2004 1:12 pm, UGTOC.fm
Retrieving Information from the Database . . . . . . . . . . . . . . . . . . . . . 1-21
How to Execute a Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Additional Query Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
Types of Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28
Attribute Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35
Viewing Retrieved Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-37
Status Bar Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-38
Displaying More Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-39
Viewing More from a Retrieved Record . . . . . . . . . . . . . . . . . . . . 1-39
Viewing the Instance Hierarchy: Zoom . . . . . . . . . . . . . . . . . . . . 1-43
List of Valid Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-45
Using a List of Valid Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-46
Copying Multiple Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-49
List of Values for Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-49
Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-50
Attachments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-53
Using the Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-59
Saving Your Work Using Commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-60
When to Commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-61
Discarding Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-61
Chapter 2 Logging
Expediting a Log Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Logging a Planned Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Logging an Unplanned Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Logging a Planned Submission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Logging a Batch of Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Logging Samples by Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Receiving Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Adding a Sample to an Existing Submission . . . . . . . . . . . . . . . . . . . 2-19
Adding Tasks by Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Adding Methods to Logged Samples . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Assigning Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Worklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Worklist Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Creating a Worklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
iv SQL*LIMS User Guide

DRAFT
Manipulating a Worklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32
Saving a Worklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
Reassigning Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
Logging Many Samples Simultaneously . . . . . . . . . . . . . . . . . . . . . . . 2-36
Editing Multiple Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
Adding Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Adding Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
Editing Task Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41
Editing Submission Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
Chapter 3 Entering Results

Results Data Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Jobtype, Datagroup, Status, and Condition Considerations . . . . . 3-2
Electronic Signature Considerations . . . . . . . . . . . . . . . . . . . . . . . 3-3
Exploring Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Result Value Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Result Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Significant Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Result Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Primary and Secondary Specifications . . . . . . . . . . . . . . . . . . . . . 3-8
Multiple Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Limit Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Column Headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Displaying More Result Information . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Entering Results by Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Entering Results by Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Entering Results by Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Entering Results by Worklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Entering Results for Many Samples . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Entering Results by Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Editing Multiple Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Displaying Earlier Result Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
SQL*LIMS User Guide v

DRAFT
Chapter 4 Viewing Data
Viewing Instance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Viewing Submissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Viewing Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Viewing Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Viewing Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Viewing Worklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Viewing Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Customer Viewing of Instance Records . . . . . . . . . . . . . . . . . . . . . . . 4-20
Viewing Customer Samples by Submission . . . . . . . . . . . . . . . . 4-20
Viewing Customer Tasks by Sample . . . . . . . . . . . . . . . . . . . . . . 4-22
Viewing Customer Results by Task . . . . . . . . . . . . . . . . . . . . . . . 4-23
Viewing Customer Samples by Result . . . . . . . . . . . . . . . . . . . . . 4-24
Viewing Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Viewing Current Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Viewing Sample Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Viewing Location History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Viewing Sample Location History . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Viewing Log Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
Viewing Status Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Viewing Status and Condition Changes . . . . . . . . . . . . . . . . . . . . . . . 4-34
Viewing the Audit Log of Instance Records . . . . . . . . . . . . . . . . . . . . 4-36
Viewing Electronic Signature History . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
Verifying Electronic Signatures in an Instance Tree . . . . . . . . . . . . . . 4-38
Chapter 5 Approving Records

Exploring Retrieved Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Bulk Approval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Approving a Submission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Approving a Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Approving a Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Approving a Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Approving a Worklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
vi SQL*LIMS User Guide

DRAFT
Chapter 6 Editing
Editing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Editing Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Editing the Condition of a Submission . . . . . . . . . . . . . . . . . . . . . . 6-4
Editing the Condition of a Sample . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Editing the Condition of a Task . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Editing Instance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Editing a Submission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Editing a Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Editing a Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Editing a Worklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Editing Attributes and/or Parameters Simultaneously . . . . . . . . . . . . 6-14
Assigning Sample Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Assigning Sample Disposal Location . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
Chapter 7 Application Options

Choosing an Application Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Add Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Add QC Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Add Replicates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Add Sample Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Add Unknowns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Add Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Assign New Analyst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Browse Limit Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Change Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Clear Analyst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Copy Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Create Child Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Create TPL File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Define Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Define Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
Define Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
SQL*LIMS User Guide vii

DRAFT
Define Sample Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Define Studies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Edit Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
ESig Verify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
Instrument / Part Check Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
Instrument / Part Qualification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
Location History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
Log Request Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
Make Status Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
Override Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
Recalculate Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
Resequence Worklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
Sample Pooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Sample Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
Sample Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
Send Status Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
Set Analyst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
Set Log Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
Set To Requested . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30
Show Status Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30
Status Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31
Submission Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33
Suspend/Unsuspend Instrument or Part . . . . . . . . . . . . . . . . . . . . . . 7-33
Task Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
View All Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
View CMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35
View Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
View Signature Event History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37
View History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
View Result Specs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
Worklist Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40
viii SQL*LIMS User Guide

DRAFT
Chapter 8 Events and Utilities
Running an Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Sending and Reading Memos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Changing Your Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Setting Your User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Activating and Deactivating Your Datagroups . . . . . . . . . . . . . . . . . . 8-10
Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Optional Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Index
SQL*LIMS User Guide ix

DRAFT
x SQL*LIMS User Guide
DRAFT
Preface
How to Use This Guide

Purpose of This The SQL*LIMS User Guide is a step-by-step guide for using the
Guide SQL*LIMS® software.
Audience Intended for end users, the SQL*LIMS User Guide describes the user
interface and procedures for performing routine laboratory
operations.
Assumptions This guide assumes that you have a working knowledge of your
laboratory operations and functions.
Text Conventions This guide uses the following conventions:

• Bold indicates user action. For example:
Type 0, then press Enter for each of the remaining fields.
• Italic text indicates new or important words and is also used for
emphasis. For example:
Before analyzing, always prepare fresh matrix.
• A right arrow bracket (>) separates successive commands you
select from a drop-down or shortcut menu. For example:
From the System menu, select Security > System Commands.
Right-click the sample row, then select View Filter > View All
Runs.
User Attention Two user attention words appear in Applied Biosystems user
Words documentation. Each word implies a particular level of observation
or action as described below:
Note: Provides information that may be of interest or help but is not
critical to the use of the product.
IMPORTANT! Provides information that is necessary for proper
instrument operation, accurate chemistry kit use, or safe use of a
chemical.
SQL*LIMS User Guide xi

DRAFT
September 13, 2004 1:19 pm, 02_UG_Preface.fm
Preface
Examples of the user attention words appear below:

Note: The size of the column affects the run time.
Note: The Calibrate function is also available in the Control Console.
IMPORTANT! To verify your client connection to the database, you
need a valid Oracle® database user ID and password.
IMPORTANT! You must create a separate Sample Entry Spreadsheet
for each 96-well plate.
Safety Alert Safety alert words also appear in user documentation. For more
Words information, see “Safety Alert Words” on page xvi.
How to Obtain More Information

Related The following related documents are shipped with the system:
Documentation • SQL*LIMS Tables Reference Guide – Describes the
SQL*LIMS database tables and their format and content; also
includes views and synonyms. Descriptions of tables that are
specific to optional products like SQL*Stability™ and
SQL*QA™ are in the appendix of the user guides for those
products.
• SQL*LIMS Template Design User Guide – Explains how to
create SQL*LIMS analysis templates.
• SQL*LIMS Administration Guide – Explains how to set up and
configure the SQL*LIMS application.
• SQL*LIMS Online Help – Describes the SQL*LIMS software
and provides procedures for common tasks. The online help
contains the same information that is in this manual. To access
online help, press F1 from any place in the application.
Portable document format (PDF) versions of this guide are also
available on the SQL*LIMS software installation CD.
Note: For additional documentation, see “How to Obtain Support”
on page xiii.
Send Us Your Applied Biosystems welcomes your comments and suggestions for
Comments improving its user documents. You can e-mail your comments to:
techpubs@appliedbiosystems.com
xii SQL*LIMS User Guide

DRAFT
How to Obtain Support
How to Obtain Support

For the latest services and support information for all locations, go to
http://www.appliedbiosystems.com, then click the link for
Support.
At the Support page, you can:
• Download PDF documents
• Obtain information about customer training
• Download software updates and patches
In addition, the Support page provides access to worldwide telephone
and fax numbers to contact Applied Biosystems Technical Support
and Sales facilities.
SQL*LIMS User Guide xiii

DRAFT
Preface
xiv SQL*LIMS User Guide

DRAFT
Safety Information
This chapter covers:

Safety Conventions Used in This Document. . . . . . . . . . . . . . . . . .xvi
Workstation Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
SQL*LIMS User Guide xv

DRAFT
September 13, 2004 12:49 pm, 03_UG_Safety_SW.fm
Safety Information
Safety Conventions Used in This Document

Safety Alert Four safety alert words appear in Applied Biosystems user
Words documentation at points in the document where you need to be aware
of relevant hazards. Each alert word–IMPORTANT, CAUTION,
WARNING, DANGER–implies a particular level of observation or
action, as defined below:
Definitions
IMPORTANT! – Indicates information that is necessary for proper
instrument operation, accurate chemistry kit use, or safe use of a
chemical.
– Indicates a potentially hazardous situation that,

if not avoided, may result in minor or moderate injury. It may also be
used to alert against unsafe practices.
– Indicates a potentially hazardous situation that,

if not avoided, could result in death or serious injury.
– Indicates an imminently hazardous situation

that, if not avoided, will result in death or serious injury. This signal
word is to be limited to the most extreme situations.
Examples
The following examples show the use of safety alert words:
IMPORTANT! The sample name, run folder name, and path name,
combined, can contain no more than 250 characters.
– MUSCULOSKELETAL AND
REPETITIVE MOTION HAZARD. These hazards are caused by
potential risk factors that include but are not limited to repetitive
motion, awkward posture, forceful exertion, holding static unhealthy
positions, contact pressure, and other workstation environmental
factors.
– Do not attempt to lift or move the computer or

the monitor without the assistance of others. Depending on the
weight of the computer and/or the monitor, moving them may require
two or more people.
xvi SQL*LIMS User Guide

DRAFT
Workstation Safety
Workstation Safety
Correct ergonomic configuration of your workstation can reduce or
prevent effects such as fatigue, pain, and strain. Minimize or
eliminate these effects by configuring your workstation to promote
neutral or relaxed working positions.
– MUSCULOSKELETAL AND
REPETITIVE MOTION HAZARD. These hazards are caused by
potential risk factors that include but are not limited to repetitive
motion, awkward posture, forceful exertion, holding static unhealthy
positions, contact pressure, and other workstation environmental
factors.
To minimize musculoskeletal and repetitive motion risks:
• Use equipment that comfortably supports you in neutral working
positions and allows adequate accessibility to the keyboard,
monitor, and mouse.
• Position the keyboard, mouse, and monitor to promote relaxed
body and head postures.
SQL*LIMS User Guide xvii

DRAFT
Safety Information
xviii SQL*LIMS User Guide

DRAFT
Basics 1 1
This chapter describes basic concepts and techniques that you need to
know in order to work with the SQL*LIMS® software.
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2
Instance Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4
Jobtype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5
Datagroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5
Workgroup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5
Status and Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6
Starting the Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7
Exiting the SQL*LIMS Software . . . . . . . . . . . . . . . . . . . . . . . . . .1-9
Changing Your Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9
Accessing Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-20
Displaying All Text in a Field . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-20
Entering Information into the Database . . . . . . . . . . . . . . . . . . . .1-21
Retrieving Information from the Database . . . . . . . . . . . . . . . . . .1-21
Viewing Retrieved Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-37
List of Valid Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-45
Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-50
Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-53
Using the Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-59
Saving Your Work Using Commit . . . . . . . . . . . . . . . . . . . . . . . . .1-60
SQL*LIMS User Guide 1-1

DRAFT
September 13, 2004 1:19 pm, 04_UG_Ch1.fm
Chapter 1 Basics
Overview
The SQL*LIMS® v5 software is a powerful laboratory information
management system (LIMS) designed for use in the laboratory
environment. This data storage and retrieval system enables you to:
• Store laboratory data about samples, the tests performed on
them, and the results
• Retrieve these data quickly and easily
• Track the progress of samples from the time they are logged into
the laboratory until testing on them is complete
The functions in the SQL*LIMS application have to do with the life
cycles of samples in your lab:
• Logging (including assigning tests)
• Assigning work
• Entering results
• Approving results
• Tracking (the state of the sample)
1-2 SQL*LIMS User Guide

DRAFT
Overview
About this Guide This SQL*LIMS User Guide is a step-by-step guide for using the
application to perform routine laboratory operations. This guide
contains the following information:
Chapter 1 Explains the concepts and techniques that you

Basics must know in order to perform your daily work with
the SQL*LIMS software. All procedures in the
manual assume that you know how to perform the
standard functions described in this chapter.
Chapter 2 Provides the procedures for manually logging a

Logging sample and for creating a worklist.
Chapter 3 Describes procedures for entering results manually

Entering Results and for displaying earlier versions of a result record
that has changed.
Chapter 4 Describes how to view data from records for

Viewing Data informational purposes.
Chapter 5 Presents procedures for manually approving or not

Approving approving records.
Records
Chapter 6 Gives procedures for editing information in the

Editing database.
Chapter 7 Provides an alphabetical list of all the application

Application options and describes how to choose them.
Options
Chapter 8 Describes how to run an event, customize your

Events and application, set up your user environment, access
Utilities optional SQL*LIMS software products, and exit and
reconnect to the application.

DRAFT
Chapter 1 Basics
Instance Hierarchy
An instance hierarchy consists of related submission, sample, task,
and result records.
• A submission is a group of one or more samples of the same
study.
• Samples are the materials that are analyzed in the laboratory.
• A task is a single unit of work performed on samples, such as an
analysis or assay.
• Results are test data values from tasks.
In this hierarchy, a level can have a one-to-many relationship with the
level below it.
Submission
Sample Sample
Task 1 Task 2 Task 1
Result 1 Result 1 Result 2 Result 1 Result 2

DRAFT
Jobtype
Jobtype
Your jobtype controls your access to functions in the application.
When you are enrolled as a user, your applications manager assigns
you one or more jobtypes. Each jobtype consists of one or more roles.
Each role enables you to do various jobs on the system, such as enter
results, change results, and approve data. Each role is associated with
one or more menu items. When your jobtype contains a given role,
you are allowed access to the related menu items. Only items that are
related to your roles are displayed on the menu when you run the
software.
Datagroup
Your datagroup controls your access to information. Your
applications manager will assign at least one datagroup to you.
Individual instance records also have a datagroup. In order for you to
access a record, the datagroup in the record must match any of your
datagroups. You will not see a record that contains a datagroup that
does not match one of yours. When you select an item (such as a
sample plan) that is associated with multiple datagroups and you
have the same datagroups, you will be prompted to choose from
among them.
Workgroup
A workgroup is a collection of datagroups that functions as a pseudo-
user. If your datagroup is in a workgroup, then you are in the
workgroup. You can only access data assigned to a workgroup if you
share a common datagroup. A workgroup, like any user, can be
defined in any Analyst field in the database. There is an Analyst field
in windows such as Assign Work and Enter Worklist Results. The list
of valid entries for Analyst will show both the user names and the
workgroups that share a common datagroup. Workgroup is also used
in analyst qualification. When an analyst’s qualification expires, he
or she is removed from the workgroup.

DRAFT
Chapter 1 Basics
Status and Condition

The SQL*LIMS software monitors the flow of submissions, samples,
tasks, results, and worklists. It does this by entering two values–a
condition and a status–in each record when it is created during the
logging process. Thereafter, the application automatically updates
these values as the record passes certain milestones. It also allows
you to enter certain condition values. Conditions indicate the
progress of a record through the lab and determine the record
retrieval criteria. For example, records that are INCOMPLETE are
not retrieved for result entry. Most condition changes occur without
direct user action on the condition value, but you can manually edit
condition. When you enter a new condition at the task level or above,
the condition propagates downward to related records lower in the
instance hierarchy. Thus, a record may owe its condition to a direct
change or to a change propagated from a related submission, sample,
task or worklist. Status reflects the state of results entry. Status is
always updated automatically by the application. Actions that you
take cause status changes, but you cannot directly enter a status value
into an instance record. Status propagates up the instance hierarchy:
• The status of a task depends on that of its results.
• The status of a sample depends on that of the tasks to be
performed on it.
• The status of a submission depends on that of the samples in it.
• The status of a worklist depends on that of the tasks on it.
Whenever there is a change to status or condition (with a Commit
command), the system puts a status request into the
NAI_STATUS_REQUESTS table. The object ID, entry point, and the
state PREREQUEST are also stored. When you finish your session,
the state is changed to REQUESTED and the status monitor is
notified. The status monitor begins to synchronize all records
affected by the change. You can check the status and condition of the
objects in an instance tree, view status requests, and view status and
condition changes. You may need to review the status and condition
before approving a result, sample, task, or submission.

DRAFT
Starting the Application
Starting the Application

To use the application, you log on to the database using a Web
browser.
To start the SQL*LIMS application:

1. In the browser Address field, enter the Web address to the
SQL*LIMS application.
At your first session, your SQL*LIMS administrator needs to
tell you the Web address if you do not know it. You can make it a
bookmark or add it to your Favorites list, so that after you enter
the address once, you do not need to type it again.
2. In the Login window enter your user name, password, and
database instance, then click Connect.
3. In the Jobtypes window, select your jobtype, then click OK

If you have several jobtypes assigned to you, they will all be
listed. Select the one that is appropriate to the task at hand.
Otherwise, this window will not appear.

DRAFT
Chapter 1 Basics
After connecting, the SQL*LIMS application window opens.
The SQL*LIMS application window has these main elements:

• Portal Navigator – Displays the functions in various tabs and
provides an alternate way to access the functions. (The drop-
down menus in the menu bar are the other way.)
• Title bar – Displays the instance and username.
• Menu bar – Displays menu names which, when you click one,
displays a drop-down list of commands. Refer to “Menus” on
page 1-14.
• Status bar – Displays messages about the application along the
bottom row. Refer to “Status Bar” on page 1-20.

DRAFT
Exiting the SQL*LIMS Software
Exiting the SQL*LIMS Software

To exit the application, select File > Logout.
The portal navigator also contains a logout button in the top right
corner.
Changing Your Password

Your lab may have an SOP for changing your password on a regular
basis. You should also change your password when you think its
security has been compromised. Follow your laboratory’s
conventions for changing your password.
To change your password:

1. In the menu bar, select Utilities > User > Change Password to
display the Change Password window.
2. In the Old Password field, enter your current password.

3. In the new password fields, enter a new (different) password
twice.
4. Click Submit. At your next session, you will use the new
password.
If electronic signature is enabled for your lab, you will also enter your
password for electronic signature authentication.

DRAFT
Chapter 1 Basics
Accessing Functions
The SQL*LIMS software provides three ways to define and manage
laboratory objects:
• Using the buttons in the portal navigator.
The application has a portal navigator that displays the
SQL*LIMS instance functions in one place. They are grouped
logically so that you can find your way around easily. This flat
display allows you to see in one glance the functions that are
available and aids in navigation as you process your samples and
perform your tasks. The functions in the instance tab in the
portal navigator are buttons that you can click.
The portal navigator consists of tabs for each of the six main
functions and optional products:
Instance – Used for logging, processing, and tracking
samples.
Template – Used for setting up your laboratory objects in the
SQL*LIMS application.
SQL*QA™ – Used for processing lots.
SQL*Stability™ – Used for stability testing.
SQL*Schedule™ – Used for logging routinely analyzed
samples.
Custom – Used to define your own buttons for running
commands (forms) or events..
• Using the instance navigator.
The instance navigator provides one window where you can
carry out all your tasks. Objects in the instance navigator are
arranged in a tree hierarchy similar to Windows® Explorer.
When you use the instance navigator instead of the menu bar,
you can accomplish your task with fewer mouse clicks. The
instance navigator also lets you see in one place and at the same
time the functions that are available to you.
• Using commands in the menu bar.
This is comparable to the menu bar for the main menu and
system menu, where you select tasks from drop-down menus.
This method allows you to view only the object, for example,
study, material, or test, that you are currently working with.
Your role assignment determines which functions you can perform. If
your role does not permit you to perform a function, the button or tab
will appear grayed out.

DRAFT
Accessing Functions
Instance Navigator
The instance navigator lets you log samples and view, approve, and
edit submission, sample, task, and result objects in one form, so that
you can easily navigate from one object to another to perform various
tasks with the fewest mouse clicks.
The Windows navigation conventions have been adopted for the
SQL*LIMS instance navigator.
The SQL*LIMS instance navigator is divided into the following
sections (panes):
• Filter results pane – Lets you limit the display of objects.
• Function pane – Lets you define, edit, and view instance
objects.
• Navigator tree pane – Displays the instance objects and details
about the object that you have selected.

DRAFT
Chapter 1 Basics
The main instance objects – submission, sample, task, result, and

worklist – appear in the center panel. When you select an instance
object, the functions that you can perform appear in the Edit,
Approve, Enter, View, and Miscellaneous panels.
The label of the Edit panel will change based on the object that you
choose:
• You log submissions, samples, tasks, and pooled samples.
• You enter results and worklists.
Navigator Icons The navigator tree displays instance objects in a format that lets you
see the relationship of one object to another. The icons for instance
objects are:
Icon Node or Object
Submission node or object
Sample node or object
Task node or object
Result node or object
Worklist node or object
Pooled sample node or object
The tasks that you perform most often while defining and editing
instance data are easily accessible by buttons that you can click.
These tasks are:
Icon Instance Task
Expand / collapse selected node or entire tree
Refresh node; redisplays the tree with the most

current information.
Clear tree
Show E-sig history

DRAFT
Accessing Functions
Icon Instance Task
Show state history
Show status actions
Show audit log
When you select an object in the tree, detail information appears next
to it. Some information may appear in blue text, for example,
material name. You can click the blue text to display the definition
window for the object, for example, Define Material Name window.
Limiting Display If you know which objects you want to work with, you can limit the
of Objects display so that the navigator tree contains only those objects.
To limit the display of instance objects in the instance navigator:

1. Select the tab (submission, sample, task, worklist, or result) of
the object you want to work with.
2. In the appropriate fields, double-click to select from the list of
valid entries.
You can select information for as many fields as you want. The
more information you enter, the more restrictive the results will
be.
3. Click Build Tree.
The navigator tree displays all the objects that you requested.
Note: Click Clear Tree ( ) between builds to flush objects so
that each build is fresh.
Defining and You can enter, approve, edit, and view instance objects in the instance
Editing Data in navigator. For example, after you select a sample in the navigator tree
the Instance to work with you can perform your tasks on the sample. The
Navigator availability of these functions in the navigator saves keystrokes and
lets you see the sample; its attributes, status, condition, and other
details; and lets you know what tasks you can perform.

DRAFT
Chapter 1 Basics
To work with an instance object in the navigator:

1. In the navigator tree, select the object that you want to work
with.
The function pane displays all the functions that you can
perform
2. In the function pane, select the task that you want.

3. The SQL*LIMS window for the task appears. Proceed as usual.
Click Commit if necessary.
Menus
The SQL*LIMS application menu consists of two menus: the menu
bar and the function menu. All of the menu items are described in this
section; however, you may see only some of these items, depending
on your jobtype. For example, if you are not authorized to approve
results, the Approve drop-down menu is not displayed and the
Approve buttons in the portal navigator are grayed out.

DRAFT
Accessing Functions
Menu Bar When you have logged on to the SQL*LIMS software, the menu bar
is displayed. The menu bar contains these functions:
File – Lets you exit from and log out of the application: Logout.
Log – Lets you log samples and make assignments for them: Enter,
Add, Sample Receipt, Schedule Sample Receipt (for SQL*Schedule
only), Worklist, Assign Work.
Results – Lets you enter test results: by Sample, by Task, by Method,
by Worklist, by Matrix Result Entry.
View – Lets you monitor sample progress through instance records:
Log Requests, Status Requests, Submissions, Samples, Tasks,
Results, Worklist, Work, Customer, Locations, Location History,
State History, Security Log, Audit Log, Esig History, Instance
Navigator.
Approve – Lets you approve related submission, sample, task, result,
and worklist records: by Submission, by Sample, by Task, by Result,
by Worklist.
Edit – Lets you edit records and the condition associated with each;
also lets you edit attributes: Condition, Instance, Attributes, Sample
Location.
Events – Lets you run standard events supplied by the SQL*LIMS
application. Also lets you see event history and install events
customized or created at your installation: Run Event, Install Event,
Event History.
Utilities – Provides access to the SQL*LIMS template and system
menus, which the system administrator uses to set up the SQL*LIMS
software, as well as the menus for optional SQL*LIMS software
products, for example, the Stability menu for SQL*Stability™,
memos, user preferences, changing password, translation, Template
Menu, System Menu, Lot menu, Stability menu, SAP QM Menu,
instrument calibration, analyst qualification (users’ training records),
and Show Application Toolbar check box.
Help and Window – Work the same as typical Windows Help and
Window menus in other applications.

DRAFT
Chapter 1 Basics
Function Menu The function menu replaces the menu bar when you open a
SQL*LIMS window by choosing a command from the menu bar.
The menus that you can open from the function menu have
commands that let you enter, modify, and manipulate data; display
additional information; query the database, and run the application in
general.
File menu – Exits the currently opened window and returns you to
the main menu.
Action menu – Lets you roll back, commit, or execute changes; lets
you print screens, manage application and event options, execute the
break procedure, and turn on or off a SQL trace session.
Edit menu – Transfers information, and displays long fields in their
entirety.
Block menu – Lets you move the cursor and display additional
information. (Block is a term that denotes a region of a window.)
Item menu – The item commands move the cursor and remove and
copy values in fields.
Record menu – The record commands let you manipulate records,
moving the cursor and moving records into view.
Query menu – The query commands place a window in query mode,
and let you enter and execute a search. There are also ancillary query
commands on this menu.
Options menu – The option commands let you display a list of
application or event options. The options on the list vary depending
on cursor position when you display the menu.
Help menu and Window menu – Work the same as other typical
Windows Help and Window menus in other applications.

DRAFT
Accessing Functions
Shortcut Menu The shortcut menu is displayed when you click the right mouse
button. The shortcut menu is context sensitive; that is, it changes
based on the task you are performing and the window that is
displayed. If a command on the shortcut menu is not available, it will
be disabled or it will not display (for example, if a record does not
have attachments, Browse Attachments will be disabled).
The default shortcut menu has the following
commands:
Cut – Delete the data from a field; the data is
in memory so you can paste it into another
field.
Copy – Copy the data, usually so that you can
paste it.
Paste – Put data (that you have cut or copied)
into a field.
List of valid entries – Lists the valid entries
from which you can select.
Application Options – Lists the application
options that are available.
Event Options – Lists the events that you can run.
Edit Attachments/Browse Attachments – Allows you to read or
edit text attached to a record, or to attach new text to a record. You
can also use this command to review essay results. See
“Attachments” on page 1-53.
Attributes – Displays attributes to which you may respond.
Display Limits – Toggles the display of measure limits, detection
limits, and primary and secondary specifications in results windows.
It is displayed below Attributes in Results windows.
Other commands may be displayed below Attributes. The attributes
displayed vary, depending on the location from which the shortcut
menu was opened. These other commands are described in other
sections of this manual.

DRAFT
Chapter 1 Basics
Toolbars
The application toolbar is displayed under the function menu. While
any form or event window is open, the main toolbar is displayed.
Otherwise, the main toolbar is replaced by the function toolbar.
Main Toolbar The main toolbar is shown in the figure on page 1-8. It has these
buttons:
• Exit – If you are at the main SQL*LIMS window, exits the

application, otherwise it returns you to the previous window
( ).
• Menu selector – Lists the SQL*LIMS menus from which you
can select.
Function Toolbar The function toolbar has these buttons:
Icon Purpose
Exits the window (form) or the SQL*LIMS application.
Clears retrieved records from the window, allowing a

new query
Executes a query; retrieves the records into the form.
Displays a list of valid entries from which you can

select.
Prints an image of the active window.
Cuts (deletes the data from) a field; the data can be

pasted.

DRAFT
Accessing Functions
Icon Purpose
Copies a field.
Pastes a field.
Pastes multiple records selected from a list.
Clears unsaved data changes from a field.
Rolls back database changes.
Executes pending log or status requests; you remain in

the form. See “Expediting a Log Request” on page 2-3
for information on the difference between Execute and
Commit.
Commits data to database.
Displays a properties window about the selected

record.
Zooms.
Displays the attributes of a record.
Displays the attachments to a record (browse).
Edits attachments to a record.
Displays application options.
Displays event options.
Goes to the first record.
Goes to the previous set of records.
Goes to the previous record.
Goes to the next record.
Goes to the next set of records.
Goes to the last record.
The first, last, previous, and next record buttons appear in the
function toolbar, if you chose to display the Oracle® toolbar in your
user preferences.

DRAFT
Chapter 1 Basics
Status Bar
Messages about the application’s activities are displayed in the status
bar at the bottom of the application window. They provide error
information and hints for running the program. They also tell you
what the application is doing and what action you should take. The
right side of the status bar contains an indicator that moves back and
forth when the application is busy executing a command.
Note: Check the status bar whenever you are unsure about the
current state of the SQL*LIMS application or database.
Displaying All Text in a Field

Fields in a SQL*LIMS record accommodate a specified number of
characters. Sometimes the field for displaying those characters is not
large enough to show all the characters. A field that appears to be full
may have more text (there is no graphical representation to indicate
this).
To see all the text in a field:

1. Position your cursor in the field whose contents you want to
read. In the menu bar, choose Edit > Edit menu to open the
Editor dialog box.
If the field is editable, you can click Search to search and

replace the text.
2. If the field is editable and you have made changes, click OK to
save them.

DRAFT
Entering Information into the Database
Entering Information into the Database

You can enter or edit data in any white field in a window. You cannot
edit data in the light yellow (buff) fields; these fields are read-only.
Although white and light yellow are the default colors, you can
change either or both colors on the Color Preferences tab by choosing
User > Preferences from the Utilities menu.
You may need to click Enter Query in the toolbar or choose Record >
Clear in the menu bar to clear the window of displayed query results
before you can type data.
Data that you entered are not saved into the database until you click
Commit or Execute. Commit saves data to the database; Execute
saves data to the database and issues a log request. Refer to
“Expediting a Log Request” on page 2-3 for more information.
If you have queries that you execute regularly or often, you can save
them, which allows you to retrieve and execute them easily and
quickly.
Retrieving Information from the Database

Everything you enter is stored in the database. When you want to
view a record or perform some action on it, you must first retrieve it
from the database. The process of retrieving information from the
database is called executing a query.
When you execute a query, you use search criteria to define which
records you want to retrieve. Search criteria narrow the selection
process of a query; they impose requirements that a record must
satisfy in order to be retrieved. Search criteria may be very general or
very specific.
• You can retrieve all the records of a particular type. For
example, you can retrieve all submissions by executing a
submission query with no search criteria.
• You can retrieve a subset of the records of a particular type by
executing a query with search criteria, such as a query for all
submissions that belong to a particular study.

DRAFT
Chapter 1 Basics
Note: Your jobtype may limit your access to certain query functions.
Any query that you perform will retrieve only records that contain a
datagroup label that matches one of your own. The status or condition
of a record may prevent it from being retrieved by a query. Status and
condition may also limit what you can do to a retrieved record.
How to Execute a Query

Queries are executed in the same manner throughout the SQL*LIMS
application. The basic steps are: 1) enter any search criteria, and 2)
execute the query.
To execute a query:
1. Enter search criteria in each field that you want to query. You
can type the search criteria or select them from a list of valid
entries, or leave all fields blank to retrieve all records.
2. Click Execute Query in the toolbar.
OR
Click Find if the window has a Find tab.
The retrieved information is displayed on the tab next to the Find
tab (called the “query results tab” in this user guide).

DRAFT
Saving a Query You can save your queries so that you can execute them again easily
and quickly.
To save a query:
1. In the Find tab, enter search criteria in each field that you want
to query by. You can type the search criteria or select them from
a list of valid entries.
2. Click Save to display the Query Name window.
3. Enter a name for the query that indicates its purpose, then click
OK.
The query is now available in the QBE (query by example) field.

DRAFT
Chapter 1 Basics
How Query The results of your query are displayed differently in different
Results Are windows, depending on which of the two following types of query
Displayed you performed:
• Direct query for records of a specific type. An example of this
query would be: viewing submissions, viewing samples by
samples, or viewing tasks by tasks.
• Query for records of a specific type as they relate to another
kind of record. An example of this query would be viewing
samples by submission, viewing tasks by sample, or viewing
results by task.
In a direct query, each record retrieved from the SQL*LIMS database
is displayed in the window as a row. The figure that follows shows an
example of a direct query where Samples by Sample was chosen
from the View menu.

DRAFT
In a query for instance records that are associated with another kind
of record, the master record appears in the upper part of the window,
and detail records associated with the master record are displayed in
the lower part of the same window.

DRAFT
Chapter 1 Basics
Executing Some queries retrieve two kinds of records: a high-level, general

Second-Level response to the query and a lower-level window with more
Queries information about the object of the main query. For example, when
you query for samples by submission, you obtain the View
Submission Samples window. Retrieved submissions are displayed in
the top of the window and samples in the submission are displayed
below:
You can reduce the number of samples displayed by executing a

second-level query after you execute the initial query. For example,
you could limit the samples to only APPROVED samples.
To perform a second-level query:

1. Position the cursor in a row in the bottom half of the window
that contains one of the records that you want to include in the
new results.
2. To clear data from the fields, you can click Enter Query in the
toolbar.
3. Enter search criteria in a field or fields.

DRAFT
Additional Query Functions

Other items on the Query menu are helpful in the query process.
Displaying the Before you execute a query, you can use the Counts Hits command to
Count of Query count the number of records the query will retrieve. If the number is
Hits too large for your current objective, you may want to further reduce
the number of records your query will retrieve by adding additional
search criteria before executing it. If you have already executed a
query, you can still find out how many records have been retrieved
using the Count Hits command from the Query menu.
To count query hits after a query has been executed:

1. From the Find tab, execute the query.
2. Click Enter Query in the toolbar to clear the window of data, if
necessary.
3. Click the query results tab (which has been cleared of data), then
choose Query > Count Hits. The number of records that have
met your search criteria is displayed in the status bar.
Displaying the In some queries, only one record is displayed in the upper part of the
Next Set of window and its related records are displayed in the lower part of the
Records window. For such queries, you can display the next set of records
(consisting of a record in the upper part of the window along with its
related records in the lower part of the window) using Query > Fetch
Next Set. These records replace the first set of records displayed. The
status bar shows the progressive record count each time another
record set is displayed.
Redisplaying The Last query function redisplays the search criteria that you used
Search Criteria for your last query. You can then use those criteria as the basis for
another query. You might do this when you want to add criteria to
your previous query to reduce the number of records that will be
retrieved.
To redisplay the search criteria for the last query:

From the query results tab, choose Last from the Query menu. Your
previous search criteria are displayed on the Find tab.

DRAFT
Chapter 1 Basics
Types of Queries
You can execute simple or complex queries in order to retrieve
records.
• Simple queries use specific criteria
• Complex queries satisfy several conditions.
Retrieving All To retrieve all records, execute a query without search criteria.
Records
To retrieve all records:
Click Execute Query in the toolbar.
OR
For a window with a Find tab, click Find.
Retrieving To retrieve records selectively, you execute a query with search

Records criteria using one of the following methods:
Selectively • With criteria that must be matched exactly
• Through pattern matching, using wildcard characters
• With criteria that encompass a range of values
You can use multiple search criteria in a query, and you can use
different types of search criteria within a single query. You can also
enter complex queries (refer to “Complex Search Criteria: the SQL
Language WHERE Clause” on page 1-31 and “The SQL Language
ORDER BY Clause” on page 1-34).
To retrieve records selectively:

1. Click Enter Query in the toolbar to clear the window of data.
2. On the Find tab, type the search criteria in the appropriate fields
(or select search criteria from a list of valid entries).
3. Click Find to execute the query.
Exact-Match Searches
In an exact-match query, the application retrieves only the records
that exactly match the search criteria. You use specific values in this
kind of query.

DRAFT
Example:
You want to view results for all samples with the sample plan
PRODUCT 400 and the material name NACL,TECHNICAL
GRADE. You must enter these names exactly as they appear in the
record in order for the record to be retrieved.
If you enter multiple criteria, a record must satisfy all of the criteria
in order to be retrieved.
Pattern Matching
You can retrieve records in which values match a certain pattern. To
do this, use the standard SQL wildcard characters underscore (_) and
percent sign (%) in the query string.
• The percent sign (%) wildcard represents any combination of
characters, including no characters. For example:
%SET% matches every value that contains the letters SET
in any position
S%ET matches every value that contains the letters SET,
where there may be characters or spaces between S and E
(SET, SAAET, and SAABBET)
• The underscore (_) wildcard represents any single character. For
example:
_SET matches ASET and BSET, but not SET or ABSET
S_ET matches SAET, SBET, and S$ET, but not SET or
SAAET

DRAFT
Chapter 1 Basics
Example:
You search in the Material Type field of the View Sample Results
window with the query “%COATED”.
This query would retrieve all sample records with a material name
that includes the character string “COATED,” for example both
“COATED” and “UNCOATED.”
Range of Values: Relational Operators

Note: Using relational operators may result in a statement that is too
long to fit in a field. In this case, you must click More on the Find tab
and use the Where box. Refer to “Complex Search Criteria: the SQL
Language WHERE Clause” on page 1-31.
You can use relational operators to enter a range of values instead of
exact values in one or more fields of your query. Relational operators
are useful when it is not practical to enter (or when you do not know)
the exact values that you want retrieved records to match.

DRAFT
The following table lists some relational operators and gives

examples of how you can use them.
Relational Operator Represents Example
= equal to = ‘SMITH’
!= or <> not equal to != ‘SMITH’

<> ‘SMITH’
> greater than > 100
>= greater than or equal to >= 7.0
< less than < 98.6
<= less than or equal to <= ‘31-AUG-2004’
BETWEEN between two values BETWEEN ‘A’ and ‘C’
IN equal to any member of IN (‘LOGGED’,’ACTIVE’)
As shown in the previous examples, you must enclose fields with

character or date values in single quotes. The relational operators
listed here do not work in time fields.
Examples:
To retrieve all users whose last name starts with a letter between A
and K, enter:
< ‘L’
To retrieve all tasks assigned to analysts other than Karl on August 1,
2004, enter:
!=‘KARL’
01-AUG-2004 (as a specific date, this does not use a relational
operator or single quotes)
Complex Search When you query in a window using either the Query/Where dialog or
Criteria: the SQL the Where box on the Find tab, you can execute long queries such as:
Language • Queries with variable conditions
WHERE Clause
• Queries that must satisfy multiple conditions
• Queries that use the SQL language

DRAFT
Chapter 1 Basics
To enter a WHERE clause in a window without a Find tab:

1. If you are in data entry mode, click Enter Query in the toolbar.
2. In a field in which you want to enter a long query, type a
placeholder. Start by typing a semicolon (:) followed by an
alphabetic character, then type any other alphabetic, numeric,
underscore (_) or percent sign (%) characters. The semicolon
indicates that you have typed a placeholder instead of a value.
3. You can also type unique placeholders in other fields. Your

query may have both search criteria and placeholders typed in
the window.
4. Click Execute Query in the toolbar to open the Query/Where
dialog. Enter conditions.
You can specify any kind of match: exact, pattern, variable

condition, or multiple-condition. A query is case-sensitive. You
can also include SQL language features. For more information,
refer to “The SQL Language ORDER BY Clause” on page 1-34.
Click Search to open the Search/Replace dialog box. You can
search and/or replace any text that you entered.

DRAFT
5. Click OK to close the window and execute the query.
To enter a WHERE clause on the Find tab:

1. Click More to open lower portion of the Find tab.
2. Type your search criteria in the Where box. This search for data
is case-sensitive. Most database values are stored in upper-case
letters.
You can specify any kind of match: exact, pattern, variable
condition, and multiple-condition. You can also include SQL
language features. For more information, refer to “The SQL
Language ORDER BY Clause” on page 1-34.

DRAFT
Chapter 1 Basics
The SQL You can use the SQL language to enter advanced queries, using the
Language WHERE clause. Refer to the SQL Language Reference Manual for
ORDER BY more information.
Clause This section describes the ORDER BY clause as an example. The
ORDER BY clause defines the field that you want to use to sort the
retrieved records, ascending (ASC) or descending (DESC). Name the
field after “ORDER BY” ORDER BY {field} [ASC | DESC]
Put the ORDER BY clause after all other clauses.
For example, to sort by timestamp among sample records with

submission ID greater than 100102377 and logged by other than
DAVE_C, click More in the Find tab and enter in the Where text box:
:SUBID > 100102377 AND :WHO != ‘DAVE_C’ ORDER BY TIMESTAMP DESC
Note: ORDER BY can use any column not used in the query.

DRAFT
Attribute Query
On the Find tab, you can query for submission, sample, or task
records with a common attribute or parameter. Enter the name and
value of the attribute common to the records to be retrieved. Then add
the name and value to the Attribute Search Criteria window and
execute the query.
After the records are displayed, you can edit their attributes or
parameters by clicking the Attributes button in the toolbar. (You can
edit worklist attributes and/or parameters only while editing the
worklist).
After the attributes have been entered, they continue to be used in
queries executed from the same window until you change or delete
them, or until you exit the window.
To execute an attribute query:

1. Click More in the Find tab.

DRAFT
Chapter 1 Basics
2. In the Attributes / Parameters Search region, click either P

(parameter) or A (attribute), then enter the parameter/attribute
name or select it from the list of valid entries.
To reduce the number of records retrieved, you can enter a value
for the parameter/attribute in the Value field. This value is
entered in addition to the name you entered in the Name field.
For example, you want to retrieve all sample records with a lot
ID of 700000068. Assuming that LOT ID is a valid attribute for
the record, enter LOT ID in the Name field and 700000068 in
the Value field.
• Select the Match Case check box to query for the exact
name (and value, if entered).
• Select the Use Wildcards check box if you typed the SQL
wildcard “%” in the Name or Value field.
3. You can enter more parameters or attributes in the second and
subsequent rows to further qualify the records.
4. Click Find or Execute Query to execute the query
Changing and Attribute search criteria continue to be used in additional queries

Deleting Attribute executed from the same Find tab in the same window until you
Search Criteria change or delete those criteria.
To change or remove attribute search criteria:

Repeat the procedure for executing an attribute query, except replace
the unwanted search criteria with different search criteria or delete
the unwanted search criteria from the Name/Value fields before
clicking Find.

DRAFT
Viewing Retrieved Records

After you execute a query, the retrieved records are displayed on the
query results tab to the right of the Find tab. Click the Sample Detail
tab to show details on the selected record.

DRAFT
Chapter 1 Basics
Status Bar Indicators

The Record field in the status bar displays the total number of
retrieved records and indicates the number of the record (from the
total number of records) currently selected.
Initially, the total number of records retrieved is indicated by a
question mark. Selecting the last record replaces the question mark
with a number indicating the total number of records retrieved. After
selecting the last record, selecting another record shows its numerical
order in the listed records.
If the number of records retrieved exceeds the number of records that
the window can display, scrolling the window displays the remaining
records retrieved.

DRAFT
Displaying More Records

If multiple master records were retrieved and the window is
displaying only one, you can display each master record sequentially.
Any detail records that are displayed belong to the selected master
record.
To display the next or previous master record:

Choose Record > Next Master or Record > Previous Master.
OR
Place the cursor in the field where the record is displayed, then press
the up or down arrow on your keyboard until the record you need is
displayed.
To display another detail record in the list:

Use the scroll bar.
OR
Choose Record > First to display the first record or Record > Last
to display the last record. (If the list of records is very long, it may
take some time before the last record is displayed.)
Viewing More from a Retrieved Record

You can display more information from a record, and you can display
more information about the instance hierarchy to which it belongs:
• You can alternate which data are displayed in some columns.
• You can display more data from a record (Detail tab, More
button).
• You can move up and down the instance hierarchy and view
details about each level within the same window (Zoom button).
You can also:
• Display any text attached to a record (see “Attachments” on
page 1-53).
• Display the attributes attached to a record (see “Attributes” on
page 1-50).
Flip Flipping columns replaces the data in a column with different data.
You can redisplay the original data by continuing to flip. A column
that can be flipped is indicated by blue text.

DRAFT
Chapter 1 Basics
Example:
The following two figures show a window in which the Sample
Plan/Material Name column has been flipped. Initially, the Sample
Plan column is displayed. After flipping, the Material Name column
is displayed.

DRAFT
To flip a column:
Click the blue text in the column heading.
This flips the column data, and the column heading. Clicking the blue
text again displays the original column.
The menu equivalent is Block > Flip (or Flip Column in the shortcut
menu).
You can query on any data displayed in the flipped column.
Detail Tab You can view additional data from a record in windows with a Find
tab and a Detail tab. In the tab showing the retrieved record, click the
Detail tab.

DRAFT
Chapter 1 Basics
Displaying To view more data from a record that you have a selected in a
Additional Data window, click the More button. This button is displayed in the
from a Record: bottom, right corner of most windows.
More The window opens with more record information and, depending on
the function, buttons and links. These are described as follows.

DRAFT
• Show Status Actions button – displays the status actions for the
selected record. Refer to “Viewing Status Requests” on
page 4-32.
• Attachments icon – displays the attachment for the selected
record. Refer to “Attachments” on page 1-53.
• Attributes icon – displays the attributes for the selected record.
Refer to “Attributes” on page 1-50.
• Previous/Next Record buttons – displays more data from the
record before or after the one you selected.
• Show Audit Log button – displays audit log details for the
selected record.
• Template Links – displays the template record from which the
data in this field have been inherited (click the underlined data).
Note: If the template record has been deleted from the database,
you will not be able to display it.
• View Calculations Definition button – (not shown) displays
the mathematical expressions used to calculate a result. For
information, refer to “Calculations” on page 3-6.
• Show State History – displays the status and condition changes.
• Show Sample Audit Log – displays the audit trail for a sample.
• Show E-sig History – displays the electronic signature history
for the record.
Viewing the Instance Hierarchy: Zoom

You can display details from the entire instance hierarchy by selecting
a record from your current position in a window, then clicking the
Zoom button in the toolbar.
A tree view of the instance hierarchy (submission, samples, tasks,
and results) is displayed in the left part of the Zoom window. Data
from the selected record are displayed in the right part of the Zoom
window.

DRAFT
Chapter 1 Basics
You can expand or collapse the hierarchy tree.
Note: If you query on data created by one of the optional products,

the Zoom window reflects the structure of the instance hierarchy
created by that product. For the SQL*QA application, the hierarchy
would contain a lot above the submission level. For the
SQL*Stability application, the study hierarchy would appear above
samples.
To explore the instance hierarchy:

1. Select the record from which you want to zoom.
2. Click Zoom in the toolbar to open the Zoom window.
A message is displayed if a Zoom window is not available.
3. To view the entire contents of a record, select it in the
hierarchical display.
Note: You can expand or collapse the entire hierarchy directory or
you can expand or collapse a level, by using the
buttons.

DRAFT
List of Valid Entries

The list of valid entries displays the possible contents of a field. The
application provides a list of valid entries whenever you must enter a
value from the database.
When there is a list of valid entries for a field, List of Values is
displayed in the status bar when the cursor is in that field. When there
is no list, any entry in the field is valid. You can type in a value
instead of choosing from a list, but it must exactly match a value in
the list.
The list of valid entries will be displayed in either of these two ways:
• Window with a list from which you choose a single value, called
a list of valid entries or LOV.
• Window with a list from which you choose one or more values,
called a Multiple Record Transfer list or MRT list. When you
choose multiple values from an MRT list, they are copied at the
same time.

DRAFT
Chapter 1 Basics
In either type of list, you can search to find the value you need.
The number of choices on the list is shown in the status bar. For
example, Choices in list: 9.
The application displays only entries labeled with one of your
datagroups.
Using a List of Valid Entries

This procedure describes how to copy one value from a list of valid
entries.
To copy a single value from a list of valid entries:

1. Double-click in the field where you want to display a list of
valid entries.
B
C
A

DRAFT
2. Enter values to find.

• To display values matching initial characters: With the
cursor in the list, type the characters.
The list automatically filters and reveals the next point
where the characters differ.
Using the illustration above as an example:
a. Open a list.
b. Type s. The list filters to A.
c. Type k. The list filters to B.
d. Type r. The list filters to C.
• To display values matching a query, enter a string in the
Find field. You can include the standard SQL wildcards
“%” and “_” in your string. A “%” wildcard is implicit at
the end of the string.
To redisplay the full list of valid entries, search using an

empty string.
Note: To query on a partial field entry, you or your
applications manager can set up your user preferences (to
restrict for list of values).
If multiple columns are displayed in the list, the search is
only on the left-most column.
Searches are not case-sensitive.

DRAFT
Chapter 1 Basics
3. Click Find to display the new list.
A count is shown in the status bar:

Choices in list: 25
If there are no matches, the area is blank.
4. Double-click a value or select a value, then click OK to copy the
value into the field.
Note: When a list of values is used to show a range of values or
a required format, rather than an actual value, type over the entry
or format using the correct format.

DRAFT
Copying Multiple Values

In some window fields, you can copy multiple values simultaneously
from a list of valid entries. You can only do this for data entry, not for
constructing a query.
To copy multiple values from an MRT list:

1. Double-click the field where you want to display a list of valid
entries. If an MRT list is available, it is displayed.
2. Select the Auto Paste check box, if it is not already selected.
To see more fields, if they exist, use the horizontal scroll bar.
3. Select the check boxes of values to copy, then click OK.
OR
To select all values and copy them in one step, Shift + click the
first check box, scroll to the last value if it is not displayed,
Shift + click the check box of the last value, then click OK.
If you have copied more values than can be displayed at one
time, you can move through them as you would with any other
group of records.
List of Values for Locations

In some windows, you can click the Location button to locate an
entry in a hierarchical list of valid entries.

DRAFT
Chapter 1 Basics
In the illustration below of a list of locations, “Find” does not filter,

but navigates to matching selections in the hierarchy.
Attributes
Attributes provide a way for you to enter custom information about
submissions, samples, tasks, results, and other SQL*LIMS software
objects. For example, to track submissions by an account number,
create an attribute called “Account Number.”
The attribute name can be up to 40 characters. An attribute value can
be up to 255 characters and mixed case is supported. Attribute values
can have a data type. Attributes are stored as nested records along
with the main record.
Note: In the SQL*LIMS software prior to the 4.x release, a feature
called parameters was used instead of attributes. Parameters have
been retained for legacy installations, except for logging where you
can add only keyword attributes. The applications manager decides if
parameters are used. (A parameter prompt can be up to 20 characters.
A parameter response can be up to 40 characters. Mixed case is
supported. Parameters are stored in a separate table.)

DRAFT
Attributes
The Attributes icon ( ) in a row indicates that attributes exist for

that record.
A different parameters/attributes icon is displayed to the left of each

record. A blue-green icon indicates a parameter; red an attribute.
Clicking the icon opens the Attributes/Parameters window, which
displays the record attributes/parameters. Attribute names are in the
left column and corresponding values in the right column.
Note: You can use attributes as search criteria for queries. Refer to
“Attribute Query” on page 1-35.

DRAFT
Chapter 1 Basics
• Attributes may be set up (by your applications manager) as a

name alone, or a name with a response or value.
• Text in the response field on a white background shows an
existing response that you can update, as shown in the previous
figure. Text on a pale yellow background cannot be changed;
these fields are read-only. (Remember, although white and light
yellow are the default colors, you can change these on the Color
Preferences tab by choosing User > Preferences from the
Utilities menu.)
• An updatable response can be changed at any time. A response
that is not updatable is a response that cannot be changed after it
has been committed to the database.
• A check mark to the right of an attribute indicates that the value
is required.
You can enter responses for submission, sample, and parent task
attributes/parameters in the logging windows. You can also enter and
edit these responses (as well as those for tasks) in separate windows
designed for that purpose. You edit worklist attributes/parameters
only from the worklist itself.
If you do not enter a required response/value when you are logging a
record, all records below it in the instance hierarchy may have an
INCOMPLETE condition depending on the setting of the rule. For
example, if you omit a required submission attribute/parameter, that
submission and all related samples, tasks, and results become
INCOMPLETE. This condition keeps tasks off a worklist, and
prevents you from entering results (result entry windows do not
retrieve INCOMPLETE records).
To display attributes and edit values:

1. Click the Attributes icon.
OR
Right-click, then choose Attributes.
OR
Click Attributes ( )in the toolbar.
The record’s Attributes dialog box is displayed.
2. To enter a response (value), select it from the list of valid entries
or type a response (value).

DRAFT
Attachments
3. To edit or remove a response, type over it or delete it.

4. Click OK, then click Close to save any changes and close the
dialog box.
Attachments
There are two kinds of attachments in the SQL*LIMS software:
• Plain text attachments are part of the application and are stored
in the database. You create and edit them from within the
application. These are CLOB column records or NAI_
documents.
• Other attachments are not part of the application.
These include BFiles, which point to a file kept on the operating
system, and BLOBs.
Attachments also include files such as WAV, AVI, or DOC files
that are filed external to the SQL*LIMS software. You can
create, edit, attach, and view text or other attachments, such as
WAV or AVI files, to any record selected in a window.
By default, attachments stored external to the database are placed on
the server running the application, which allows those who have
access rights to browse and/or edit the attachments. You can change
the default storage location to another directory on the server.
When you want to view or edit the attachment, select it from a list.
Attachments are versioned and the version number is incremented
each time the attachment is edited.
Internal attachments (text records) are displayed in the window’s
viewing area; you view and edit external attachments from within
their own application. (You invoke the external application from
within the SQL*LIMS software when you select the attachment.)

DRAFT
Chapter 1 Basics
An attachment icon ( ) displayed in the window indicates that an

attachment exists for the selected record. You can add attachments to
records, whether or not they already have attachments.
To view an attachment:
1. For a record with an attachment that you want to view, click the
attachment icon or select Browse Attachments ( ) in the
toolbar to open the Browse Attachments window.

DRAFT
Attachments
2. Select the attachment from the list. If you want to view a prior
version of the attachment, select the Show All Versions check
box
Note: To view a version that is not CURRENT, you must have
the BUILD_TEMPLATES role assigned to you.
3. Click View.
4. In the Download File To window, select the destination folder.
You should ask your system administrator for advice on where
you should download your files. For example, you may be
instructed to download them only to your local drive.
5. Click Close in the Browse Attachment window.
To view an internal text record:

1. For a record with an attachment that you want to view, click the
attachment icon or select Browse Attachments ( ) in the
toolbar to open the Browse Attachments window.
2. The Plain Text field displays the attachment. You may have to
click More to see the entire attachment.
3. Click Close in the Browse Attachments window.

DRAFT
Chapter 1 Basics
To add or edit an attachment for an instance or template record:

1. Select the record for which you want enter or edit an attachment,
then click Edit Attachments ( ) in the toolbar.
The Existing Attachments window appears if the record already
has attachments.
The Edit Attachments window appears if the record has no

attachments.
2. In the Existing Attachments window, click New to add a new

attachment or click Edit to edit an existing attachment to display
the Edit Attachments window.
3. Select Plain Text or Attachment.

DRAFT
Attachments
4. Enter a description.
• If you selected Plain Text, enter a description, type or edit
the text in the Plain Text field, then click OK to close this
window.
OR
Click Internal Editor, type or search the text in this
window, then click OK. After the text is displayed in the
Edit Attachment window, click OK to close it.
• If you selected Attachment, the window changes.

DRAFT
Chapter 1 Basics
• Enter a description of up to 80 characters.

• For database storage, enter the full path of the file or
browse for a file, then click OK. If you browse, the
application invokes the File > Open dialog box. After
you find the file, click Save.
• In the Edit Attachments window, click OK to save the
document.
• If you selected External Storage, the window changes.
For external storage, enter the full path of the file or browse for a
file. If you want to change the default location of your files,
click Change Def, then click OK. If you browse, the application
invokes the File > Open dialog box. After you find the file, click
Save.
In the Edit Attachments window, click OK to save the
document.
5. Click Commit in the toolbar. The Existing Attachment window
refreshes itself displaying any changes you made.

DRAFT
Using the Calendar
Using the Calendar

You can use the calendar when you construct a query or enter dates.
The format of dates/times is determined by your applications
manager.
For a query, the calendar can retrieve records logged on a date and/or
time or within a date and/or time range. On the Find tab, a calendar
button is displayed to the right of a field in which you can enter dates
and times (for example, the Date Logged field).
For date entry, the calendar can enter the date of a transaction, for
example, the date a sample is edited.
To set a date and/or time for data entry:

1. Click the calendar icon next to a date field on a data entry form,
or use an application option, to display the Date window.
If the data entry form has a date and/or time, the calendar opens
with that date and/or time displayed, otherwise it defaults to the
current date.
2. Click the left or right arrow buttons at the top of the Date
window until the month and year you want are displayed.
3. Click a date number on the month display.

DRAFT
Chapter 1 Basics
4. Set a time by selecting hours, minutes, and seconds from the

pull-down lists.
OR
Click Now to use the current system time (on the chosen date).
5. Click OK to close the calendar and insert the date in the date
field.
To set a date range and/or time period for a query:

1. Click the calendar icon next to a date field on a Find tab to
display the Date window.
2. Select a date as in the “To set a date and/or time for data entry”
procedure above, but click Set beside the Start Date field rather
than OK.
3. Select a date as in the “To set a date and/or time for data entry”
procedure above, but click Set beside the End Date field rather
than OK.
4. Click OK to close the calendar and insert the date range in the
date field.
Saving Your Work Using Commit

When you enter information in the windows, you are not entering
data directly into the database, but into a temporary storage area
called the workspace. Likewise, when you change information, you
are not working directly with the database but with a copy of the
information in the workspace.
Having this workspace allows you to review your work before
actually altering the database. When you are satisfied that the data are
as you want them, you save the data by clicking Commit in the
toolbar or choosing Action > Commit. Clicking OK in a window may
automatically commit any changes you have made in that window.
Alternatively, you can discard changes so that the database itself is
not affected.
Committing moves data from the workspace into the database and
clears the workspace. When you commit data, you save data changes
that you have made since the last time you clicked Commit, decided
not to save changes, or discarded changes by clicking Clear >
Rollback Data in the toolbar.

DRAFT
Saving Your Work Using Commit
When to Commit
You must commit (or discard) data when you leave a window. The
application always prompts you to save any workspace data before
exiting the window.
Whenever you exit a window and there are unsaved data changes in
the workspace, you are prompted to save the changes.
You can commit data more frequently:

• You can commit after each change you make in a record to save
the change.
• You can commit after you have made changes to several records.
(In some cases, you must commit one record before proceeding
to another.)
• You might want to commit only after making changes that you
are sure you want to save, leaving yourself the opportunity to
change your mind.
Discarding Data
Clicking Clear > Rollback Data in the toolbar discards the
workspace contents, clears data from all open windows, and (unlike
the Exit command) keeps the current window open. You must
confirm the Clear > Rollback action by responding to the save
message.
After you commit data to the database, clicking Clear > Rollback
Data cannot discard it. Clear > Rollback Data does not delete any
records from the database.
Choosing Clear from the Block menu also discards the workspace
contents. However, it clears data only from the currently active
window rather than from all open windows.

DRAFT
Chapter 1 Basics

DRAFT
Logging 2 2
This chapter describes how to manually log samples and how to
create worklists.
Expediting a Log Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3
Logging a Planned Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3
Logging an Unplanned Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6
Logging a Planned Submission . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8
Logging a Batch of Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9
Logging Samples by Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10
Receiving Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-11
Adding a Sample to an Existing Submission . . . . . . . . . . . . . . . .2-19
Adding Tasks by Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-22
Adding Methods to Logged Samples . . . . . . . . . . . . . . . . . . . . . .2-23
Assigning Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-25
Logging Many Samples Simultaneously. . . . . . . . . . . . . . . . . . . .2-36

DRAFT
Chapter 2 Logging
The logging function is the process of entering information about

samples into the database. Logging allows you to do the following:
• Enter a routine (planned) sample (either individually or in a
batch using a log plan)
• Enter an unplanned sample
• Enter a planned submission
• Add a sample to a submission
• Add a method to a logged sample
• Add an operation to a logged sample
• Create a worklist, which logs any QC samples attached to it
• Reassign tasks to another or a new analyst
• Logging many samples at once using a grid
Logging creates a complete instance hierarchy that consists of
submission, sample, task, and result records. These records contain at
least an ID, which is used to establish the relationship between
instance records.
When you enter information through logging, each sample/method
combination goes into the database as a log request. Log requests are
records that are created each time you log samples, add methods to
samples, or add samples to submissions. The software then collects
the log requests and creates the instance records.
You may associate reserved keyword attributes with samples or
submissions being logged and their related instance records by using
the Log Request Attributes application option. This option lets you
enter customer information about submissions and samples. The
name for a keyword attribute is predefined in the system; the value
you enter is displayed as part of the instance record. The template
definition can provide the value, which you can update if the attribute
is updatable and the attribute is at the sample or submission level.
Note: Your jobtype may limit your access to any of the logging
functions. A query to retrieve submissions and samples for logging
functions retrieves only records that contain a datagroup label that
matches one of your own. The status or condition of a record may
prevent it from being retrieved for the purpose of adding to it.

DRAFT
Expediting a Log Request
Expediting a Log Request

To save data when logging, you either commit or execute it. Doing
either enters the data into the database; however, executing data also
issues a log request while committing it does not. A log request is a
request to the system to log all the samples that are waiting to be
logged.
• Commit – Enters into the database all new data since the last
time data were entered in it. A log request is not issued when
you commit; the request is issued when you exit the logging
form.
If you log multiple samples of the same study and commit for
each sample, then exit when you are done with all of them, they
will all be in the same submission.
Note: If there are uncommitted data when you exit, you will be
prompted to save the data.
A transaction is not final, that is, sent to be processed, when you
commit, and the screen is not cleared.
The up and down arrow keys redisplay any records committed
since the last time you executed.
• Execute – Enters data into the database and issues a log request.
If you execute after every sample that you enter, each sample
will be in a separate submission. Because the transaction is
complete, the window is cleared when you choose this
command, and you can no longer redisplay records entered
previously.
Logging a Planned Sample

A planned sample is a routine sample based on a sample plan. The
sample plan contains information about the kind of sample you are
logging. This information is inherited by the samples that you log
using this sample plan, reducing the amount of data that you need to
enter. Some of this information is displayed as default information
when you select the sample plan for your sample.

DRAFT
Chapter 2 Logging
Sample Plan is the only field required for a planned sample to be

logged. However, if enabled in the ruleset, until you respond to all
required attributes, the sample condition is INCOMPLETE, which
limits what you can do with the sample.
You can zoom a method to see the method hierarchy.
To log a planned sample:

1. In the menu bar of the Instance tab, select Log > Enter > By
Sample to open the Log Samples window.
2. Select a sample plan from the list of valid entries. In the Log
Samples window, check marks identify required methods. When
you leave the Sample Plan field, the Properties for Sample
window opens for you to enter a user sample ID, respond to
attributes, and enter other information.
3. Respond to any submission and sample attributes. If you do not
respond to required attributes, the condition of the submission
and all related records may be INCOMPLETE. Entering or
changing updatable attributes is optional. Before you close the
Log Samples window or click Execute, you can click More to
redisplay the attributes.
You can defer responding to sample attributes and then use the
Edit Attributes function later to respond to the attributes of
multiple samples at one time.

DRAFT
Logging a Planned Sample
4. To enter a user sample ID, do one of the following:

• In the Properties For Sample window, enter a user sample
ID along with attribute values and other information.
Note: This is the most efficient way to enter information
for multiple records.
• In the Log Samples window, enter a user sample ID.
• In the Log Samples window, click to create a system-
generated ID.
5. To enter a sample location or change the default, in the
Properties for Sample window, click the Location field, then
select a location from the list of valid entries.
6. Click OK to close the sample record window and automatically
commit the sample record. The sample count next to the More
button increments each time you log a sample, indicating your
changes have been applied and saved to the sample record.
7. To change the sample priority, type a value from 1 to 10.
8. If you are logging samples in bulk, enter the number of samples
in the Quantity field. The logger will log as many samples as
you indicate.
9. To attach a method, in the Methods list click an empty Name
field, then select the method name from the list of valid entries.
10. To delete a non-required method, select its name, then select
Record > Delete to delete it from the Methods list.
Note: The commit occurred automatically when you closed the
Properties for Sample window. If you attach or remove method
entries, you must commit before you leave the record.
11. Review the application options for additional functions and
make any necessary changes.
12. To log any additional samples, click Commit or Execute in the
toolbar.
• Commit lets you log another sample. (Press the down arrow
in the Sample Plan field, then click Commit.)
• Execute clears the display automatically.
13. When you have finished logging planned samples, click Exit.

DRAFT
Chapter 2 Logging
Logging an Unplanned Sample

An unplanned sample is a non-routine sample that has not been
described in a sample plan. You log this sample based on the material
instead of sample plan. You must supply all of the information about
this kind of sample, because the database does not have this
information. There must be an appropriate study in the database for
the sample.
Study and material name are the only fields that are required in order
for an unplanned sample to be logged. However, until you respond to
all required attributes, the sample condition may be INCOMPLETE,
which limits what you can do with the sample.
You can click Zoom in a method to see the method hierarchy.
To log an unplanned sample:

Material to open the Log Materials window.
2. In the Study Name field, select a study name from the list of
valid entries.
3. To use a method group, select the Use Method Group check
box, then in the Method Group field, select the method group
name from the list of valid entries.
4. In the Material Name field, select the material name from the list
of valid entries. The Sample window is displayed for you to
respond to attributes and enter other information. If you enter a
new material name when logging a sample, you can save it to
create a material template object, which can be used when

DRAFT
Logging an Unplanned Sample
logging other samples. If you elect not to save it to the Materials

table, the new material is logged as part of the unplanned sample
record only.
5. To enter a user sample ID, do one of the following:
• Enter a user sample ID in the Sample window.
• Enter a user sample ID in the Log Materials window.
• In the Log Materials window, click to create a
system-generated ID.
6. Respond to any submission attributes. If you do not respond to
required attributes, the condition of the submission and its
related instance records may be INCOMPLETE. Entering or
changing updatable attributes is optional. Before you close the
Log Materials window or Execute, you can display the attributes
by clicking More.
7. To enter a sample location or change the default, in the
Properties for Sample window, click the Location field, then
select a location from the list of valid entries.
8. Click OK to close the Sample window and automatically
commit the sample record. The sample count next to the More
button increments each time you log a sample, indicating your
changes have been applied and saved to the sample record.
9. To change the sample priority, type a value from 1 to 10.
10. In the Quantity field, enter the number of samples to log.
11. To attach a method in the Log Materials window, select the method
name from the list of valid entries in an empty Name field.
Note: The commit occurred automatically when you closed the
Sample window. If you attach method entries, you must commit
before you leave the record.
13. To log any additional samples, click Commit or Execute in the
toolbar.
• Commit clears the display so you can log another sample.
(Press the down arrow in the Sample Plan field, then click
Commit.)
14. When you have finished logging samples, click Exit.

DRAFT
Chapter 2 Logging
Logging a Planned Submission

A planned submission is based on an existing study. When you log a
submission, you log it without samples. When samples for the study
are available, you can add them to the submission using the menu
commands Log > Add > by Sample or Log > Add > by Material.
To log a planned submission:

1. In the menu bar of the Instance tab, select Log > Enter > by
Study to open the Log Submissions window.
2. Select a study from the list of valid entries.

The datagroup, log priority, and submission ID are provided.
When you leave the Study field, click More, or press the Enter
key. The Submission window is displayed.
3. Enter the value for any submission attributes, then click OK to
close the window and commit the record.
If you do not respond to required attributes, the condition of the
submission will be INCOMPLETE. Entering or changing
updatable attributes is optional.
4. To change the log priority, type a value from 1 to 10.
6. To log any additional submissions, click Execute or Commit in
the toolbar.
• Commit clears the display so you can log another sample.
(Press the down arrow in the Sample Plan field, then click
Commit.)
7. When you have finished logging submissions, click Exit.

DRAFT
Logging a Batch of Samples
Logging a Batch of Samples

The easiest way to enter a batch of routine samples is to use a log
plan. A log plan automatically enters multiple samples in a batch,
with no user action other than choosing which log plans to execute.
Log plans are defined by your SQL*LIMS® software applications
manager. They contain all of the information needed for logging
samples, including the tests to be assigned and the types and
quantities of samples in the batch. They can include multiple samples
and sample plans, of the same or different studies.
To log a batch of samples:

Log Plan to display the Log Plans window.
2. Select the name of each log plan that you want to include from
the list of valid entries.
4. When you are finished logging samples, click Exit.

DRAFT
Chapter 2 Logging
Logging Samples by Study

Logging samples by study lets you group sample plans to log
together.
1. In the Instance tab, select Log > Enter > Samples by Study to
display the Log Samples by Study window.
2. In the Study field, select a study from the list of valid entries.
3. Click the Log Priority field to display all the sample plans for
the study.
4. To log all the sample plans, click Log.
OR
5. To log some of the sample plans, select the check box for the
sample plan, then click Log.

DRAFT
Receiving Samples
Receiving Samples
You can query the database for records of samples received. You can
receive samples manually or by barcode reader.
During the process of receiving samples you can view and edit the
attributes of the samples and their responses. The samples and their
attributes are displayed in a grid so that you can view and make
changes “on the fly.”
Note: For samples collected on a routine schedule, see “Receiving
Samples” in Chapter 2 of the SQL*Schedule™ User Guide.
The following icons may appear in the General Sample Receipt
window.
Icon Description
The sample has been received; no location.
The sample has been received and is assigned to a

location.
Sample has not been received, but has been assigned

to a location.
To receive samples manually:

1. In the menu bar of the Instance tab, select Log > Sample
Receipt to display the General Sample Receipt window.

DRAFT
Chapter 2 Logging
2. Enter any search criteria, then click Find to display the samples.
3. From the Available Samples list (left panel), select the samples
to be placed/received and move them to the Samples to Receive
(right panel) using the buttons between the lists.
4. To receive a sample, it must have a Date Received attribute. To
add a Date Received attribute to all selected samples that do not
already have that attribute, select the Create Attribute Date
Received check box. When you click Receive (to receive all
samples in the right panel) or Receive All (to receive all samples
in the left panel), all selected samples will be received and the
value of the Date Received attribute will be the system date. If
you do not select the box, only the selected samples that already
have the Date Received attribute will be received.
5. To receive the samples, click Receive. The Date Received
attribute or parameter records the date and time samples are
received.

DRAFT
Receiving Samples
6. To move the samples to a location after arrival, click Place.

Select the location in the List of Locations window, then click
OK.
If a sample already has a location, it will be moved to the new
location.
7. To enter only some attributes for a sample, select the sample
then click Attributes. In the Sample Attributes window, specify
the attribute name, data type, and value for the attributes you
want to attach, or enter an attribute value for an attribute that is
already attached.

DRAFT
Chapter 2 Logging
To enter all attributes for the selected samples, click All

Attributes. The Attributes window displays the attributes for
every sample selected. The values that you enter will be applied
to all the selected samples.
8. To display and/or edit the attributes for the selected samples,

click Grid Attributes to display the Attributes window.

DRAFT
Receiving Samples
To view details about a sample, click the Date Received field

for the sample.
To edit or add an attribute, click in the field that you want to

change. Delete the current attribute, then enter the new one. Do
this for as many fields as you want.
9. Click OK. If electronic signature is enabled, you will be
prompted for your password.
10. In the General Sample Receipt window, click Receive.

DRAFT
Chapter 2 Logging
To receive samples by barcode reader:

1. In the menu bar of the Instance tab, select Log > Sample
Receipt to display the Sample Receipt window.
2. Click the Barcode Receive tab.
3. Click User Sample ID to receive or place samples by their user

sample IDs.
OR
Click Sample ID to receive or place samples by their sample IDs.
4. A sample may already have a Date Received attribute. If not,
select the Create Attribute Received Date check box to attach
that attribute to the sample.
5. Use the barcode reader or type the sample IDs or user sample IDs.
6. To receive or place samples, click Receive or Place.
7. If you are placing samples, select the location in the List of
Locations window, then click OK. The icon next to each sample
indicates that it has been placed.
8. To enter only some attributes for selected samples, click
Attributes, then specify the attribute name and value for an
attribute you want to attach, or enter an attribute value for an
attribute that is already attached.

DRAFT
Receiving Samples
9. To enter all attributes for the selected samples, click All

Attributes. The Attributes window displays the attributes for
every sample selected. The values that you enter will be applied
to all the selected samples.
10. To display and/or edit the attributes for the selected samples,
click Grid Attributes to display the Attributes window.

DRAFT
Chapter 2 Logging
To view detail about a sample, click the Date Received field for
the sample.
To edit or add an attribute, click in the field that you want to

change. Delete the current attribute, then enter the new one. Do
this for as many fields as you want.
11. Click OK. If electronic signature is enabled, you will be
prompted for your password.

DRAFT
Adding a Sample to an Existing Submission

You can add a sample to an existing submission either by sample or
by material. You would do this, for example, to add a sample to the
submission in which it should have been logged.
Note: You cannot move an existing sample from one submission to
another; however, you can add a new sample to a submission.
The procedure is the same for adding by sample as for adding by
material: query to find the submission, then add the sample to it. The
windows in which you enter the planned or unplanned samples for an
existing submission are the same windows used when samples are
logged.
After you retrieve submissions, you can do the following:
• Display the entire record of a selected submission.
• Zoom to display all the related instance records.
• Display attributes and enter/edit the updatable ones.
• Review the application options for additional functions and
To add sample records to an existing submission record:

1. In menu bar of the Instance tab, select Log > Add > By Sample
to display the Add Submission Samples window.
OR
Select Add > By Material to display the Add Materials window.
2. To enter any attributes on which you want to query, click More,
then enter attributes as needed.

DRAFT
Chapter 2 Logging
3. Enter any other search criteria on the Find tab, then click Find.
The software retrieves the submission records that match your
query criteria and displays data from the first one. Only
submission records that meet requirements defined by your
applications manager will be retrieved. This usually includes the
submissions that have at least an ONLINE condition.

DRAFT
4. Select the submission you want, then click Add Samples or

Add Materials to display the Add Samples window or Add
Materials window.
The submission ID is displayed in the window, linking the

sample to the submission.
5. Log the samples related to the submission in the Log Samples or
Log Materials window as described in “Logging a Planned
Sample” and “Logging an Unplanned Sample.”
Note: When the Log Samples window is displayed (after you
query for submissions), the list of valid entries for sample plan
will list only the plans in the study associated with the
submission to which you are adding the sample.
6. When you are finished adding to submissions, click Exit.

DRAFT
Chapter 2 Logging
Adding Tasks by Operation

You can add tasks to samples after the sample is logged. These tasks
are not part of a method, so no parent task/child task relationship is
created.
To add tasks by operation:

1. In the menu bar, select Log > Add > by Operation to open the
Add Operations window.
2. Query for the sample of interest.
3. Select the sample in the list.

4. Click Add Operation to open the Operations window.
5. Select an operation from the list of valid entries.
6. Click OK.

DRAFT
Adding Methods to Logged Samples
Adding Methods to Logged Samples

You can add methods to a logged sample. A method includes the
tasks to be performed on a sample and the types of results expected.
The procedure is to query for the sample, then add the method to it.
You can explore the retrieved samples in the following ways:
• Review the application options for additional functions and
• Zoom to display the associated methods and operations.
To add a method to a logged sample:

1. In the menu bar of the Instance tab, select Log > Add > by
Method to display the Add Methods window.
2. To enter any attributes on which you want to query, click More,

then enter attributes as needed.

DRAFT
Chapter 2 Logging
3. Enter any other search criteria on the Find tab, then click Find.
The application retrieves the sample records that match your
query criteria and displays data from the first one.
4. Select the sample you want, then click Add Methods to display
the Methods window.
5. Select a method from the list of valid entries, then click OK.
6. To add methods to any other samples, repeat steps 1 through 5
for each sample. Click OK after adding methods to every
sample.

DRAFT
Assigning Work
7. To enter method attributes, click the Attributes icon, then enter

the attribute information. For more information on method
attributes, see “Add Attributes” on page 7-3.
8. When you are finished adding methods to logged samples, click
Exit.
Assigning Work
Assigning work is the process of grouping tasks and allocating them
to the analyst who will perform the work, or designating an analyst to
a group of tasks. You can assign work by creating a worklist. The
tasks can be reassigned to another analyst at any time.
Worklist
A worklist is a group of tasks associated under a worklist name. The
tasks can be all unknowns, or a combination of unknowns and
reference standards. A worklist can be assigned to an analyst or to a
workgroup. A worklist indicates which sample to test, which
operation to perform, which instrument to use, and the date for
completion of the tasks. After you create a worklist, you can view it,
edit it, enter results for it, and approve it.
A worklist gives you historical, contextual information, such as on
what day and with what standards a sample was tested. You have the
option of basing a worklist on a worklist plan.
Worklist Plan
A worklist plan determines the structure of a worklist by defining the
sequence of unknowns and reference standards in it. A worklist plan
also defines the method or operation, default analyst or workgroup,
and due date. Attributes attached to a worklist plan are provided to
worklists that are based on that plan.
When you save a worklist, the instance data (submission, sample,
task, and result records) are created for the QC types provided by the
worklist plan. This is the logging function of a worklist.
You can create and access worklists only for analysts or workgroups
with whom you share a datagroup. The datagroup of any task that you

DRAFT
Chapter 2 Logging
assign must match one of your datagroups, and you must share this
datagroup with the analyst or workgroup to whom you assign the task.
To qualify for the worklist, a task must be condition ONLINE and
status ACTIVE or LOGGED. Tasks that are already assigned to an
analyst or workgroup can be placed on a worklist you create for that
analyst or workgroup.
Creating a Worklist
The procedure for creating a worklist is to enter data in the Create
Worklist tab, then generate the worklist. Some of the information you
enter will become the descriptive information in the worklist; other
information will be used in the query for tasks. Query execution
occurs when you click Generate Worklist.
If you select Automatic task selection, tasks are automatically
displayed in the worklist. With the Choose selection, you manually
select the tasks. You can accept the worklist as is, or you can
manipulate it before you save it.
To create a worklist:
1. In the menu bar of the Instance tab, select Log > Worklist to
open the Create Worklist window.

DRAFT
Assigning Work
2. Enter worklist descriptive information.

• Enter the worklist name or select it from the list of valid
entries. This is a required field.
• The name does not have to be unique within your
datagroup. However, the ID for a worklist will always
be unique.
• If this worklist name already exists, an informational
message is displayed when you leave the field. Click
OK to acknowledge the message. You can change the
name at any time.
• In the Quantity field, you may enter or change the
maximum quantity of task records to be placed on this
worklist.
If you select a worklist plan, this value may be overwritten
by a value from the plan.
• If needed, enter a worklist description.
You can change the description at any time.
• If needed, select a worklist plan from the list of valid
entries.
You cannot change any worklist plan data that are defaulted
into the worklist.
• If needed, change the default (worklist) due date.
The default is either today’s date or a date calculated by a
worklist plan.
• In the Worklist Analyst field, enter the analyst (or
workgroup) to whom you want to assign this worklist and
all the tasks in it.
If you are using a worklist plan, the default analyst may be
supplied.

DRAFT
Chapter 2 Logging
3. Enter worklist query information.

• In the Task Current Analyst field, you may select a name
from the list of valid entries, if the tasks that you want to
put on the worklist are currently assigned to an analyst or
workgroup. The tasks retrieved will be only those assigned
to this person or group.
If you leave this field blank, NOT ASSIGNED is the
default. Only those tasks not assigned to anyone will be
retrieved.
If you are using a worklist plan, skip to step 4.
• If you did not select a worklist plan, and you do not want to
select an operation, select a method from the list of valid
entries. The method datagroup is supplied. If you do not
enter a worklist plan, you must enter a method or an
operation.
• If you did not select a worklist plan and you want to limit
the tasks on this worklist to those that use a single operation
from the method, select that operation from the list of valid
entries.
The operation datagroup is supplied. You must enter an
operation if you did not enter a method or a worklist plan.
• To use an instrument name (and instrument class) in the
query for tasks, select an instrument from the list of valid
entries, then select the In Query check box.
OR
To assign an instrument (and instrument class) to the
worklist and the tasks on it, select an instrument from the
list of valid entries and do not select the In Query check
box.
In either case, the instrument must have a condition of
ONLINE in order for the worklist to be created.
• If you select the Automatic option for task selection, you
may enter search criteria in the following fields:
Submission ID, Sample ID, User Sample ID, Date Logged,
and/or Task Due Date.
When either the Choose or Manual task selection option is
selected, these fields are not available and any data in them
are not used in the query.

DRAFT
Assigning Work
4. Select tasks and create worklists.

In the Task Selection field, select an option for the way you want
to assign tasks to the worklist.
• Automatic – The tasks will be assigned by the application.
• Choose – You select tasks from an MRT list.
• Barcode – You select tasks by entering task IDs. (This is
intended for use with a barcode reader.)
5. Click Generate Worklist to query for tasks.
If you left the default option (Automatic) selected in the Task
Selection field, the retrieved tasks are displayed on the Worklist
tab.

DRAFT
Chapter 2 Logging
OR
If you selected Choose in the Task Selection field, the Available
Samples window is displayed. Deselect the check boxes of the
tasks that you do not want in the worklist you are creating, then
click OK. The Worklist tab opens with the tasks you selected.
OR
If you selected Barcode in the Task Selection field, complete the
Select Tasks dialog box by reading in task IDs with a barcode
reader. Click OK to display the Worklist tab, which shows the
tasks in the worklist. (Alternatively, you can enter task IDs from
the list of valid entries.)
Note: A worklist will not be generated for a worklist plan if a

QC type used in the plan has expired.

DRAFT
Assigning Work
6. Explore the tasks on the worklist in these ways:

• Zoom from an unknown to display all the related instance
records. There is no instance hierarchy for a QC type until
it is logged.
• Display more information from a task record by querying
on the task ID and clicking More.
• After you commit the worklist, display task attributes for
the unknowns in the worklist.
• After you commit the worklist, you can display submission
and sample attributes for QC types, as well as worklist
attributes (task attributes will be available after the QC
types have been logged).
7. Exit the Create Worklist window.
Manipulating a Worklist
After the worklist has been created, you can modify it by removing
tasks, adding unknowns, and adding QC types. Afterward, you can
renumber the tasks in it. As you modify the worklist, the tasks change
dynamically to reflect the current contents of the worklist.
Deleting a You can delete a worklist, then create another one.

Worklist
To delete a worklist:
1. In the Create Worklist tab, select the worklist name.
2. In the dialog, set the tasks' analyst to NOT ASSIGNED, another
value, or no change.
3. Select Record > Delete, then click OK.
Removing a Task You can delete individual tasks from a worklist when you are creating
from a Worklist or editing it.
To remove a task from a worklist:

Select the task in the worklist, then select Record > Delete.

DRAFT
Chapter 2 Logging
Adding QC Types If QC types are defined in the method or operation, you can add a QC
to a Worklist type to a worklist from the Application Options menu.
To add QC types to a worklist:

1. In the worklist where you want to add QC types, select the Add
QC Type application option to display the list of valid entries
for QC types.
2. Select the QC type that you want to add, then click OK.
Adding If additional unknowns were found by the query (see Available

Unknowns to a Unknowns on the Worklist tab), you can add them to the worklist
Worklist from the Application Options menu.
To add unknowns to a worklist:

1. In the worklist where you want to insert the unknown, select the
Add Unknown(s) application option to display the Add
Unknowns window.
2. Type the number of unknowns that you want to add, then click
OK.
Renumbering the After you have manipulated a worklist to your satisfaction, you can
Tasks in a renumber the tasks in it to correspond to the new sequence of tasks.
Worklist
To renumber the tasks in a worklist:
On the Worklist tab, select the Resequence application option.
Attributes
Several kinds of attributes can be associated with a worklist:
• A worklist that is based on a worklist plan may have worklist
attributes.
• An unknown may have task attributes.
• A QC type may have sample attributes, and the submission to
which it belongs may have submission attributes.

DRAFT
Assigning Work
You can enter or change updatable attributes. Required submission

and sample attributes will already have been completed in order for a
task to qualify for the worklist.
Note: You cannot respond to any attributes until you commit the
worklist.
Note: DO NOT EXECUTE the worklist yet; that would clear it from
the window and you would have to respond to attributes later by
editing or viewing the worklist.
Use the standard procedure to display and respond to attributes.
You can use the Edit Attributes function to respond to the sample
attributes for all the QC types on the worklist in a single window.
Saving a Worklist
To save the worklist:
1. To create any additional worklists:
Click Execute in the toolbar.
OR
Click Commit in the toolbar.
2. Click Exit.
Reassigning Tasks
You can change the analyst associated with a group of tasks. This can
be a different analyst from the current one, or a new analyst if one
was not previously assigned.
Note: The “Enforce Analyst Result Entry” system default requires
the designated analyst to enter a result; otherwise, anyone in the
workgroup can enter results.

DRAFT
Chapter 2 Logging
To change the analyst associated with a group of tasks:

1. In the menu bar of the Instance tab, select Log > Assign Work
to open the Assign Work window.
2. Enter the new analyst to whom you are reassigning the tasks,
then enter the current analyst from whom the tasks are being
taken.
If the analyst has more than one jobtype, enter the appropriate
jobtype.
3. Enter the quantity of tasks being assigned.
A quantity of 0 will not limit the number of tasks.
4. Enter any search criteria on which to query in the other fields.

DRAFT
Assigning Work
5. Click Find to query for the tasks you want to assign.

The retrieved tasks are displayed on the Tasks tab.
6. Select the check boxes of the tasks that you want to reassign.
You can display more data from a task record by selecting it,
then clicking More or clicking the Task Detail tab.
7. To save the change of analyst to each task you selected, click
Commit in the toolbar.

DRAFT
Chapter 2 Logging
Logging Many Samples Simultaneously

Grid logging enables you to quickly log many samples at the same
time. You can also attach attributes or enter methods and task
attributes for all samples, then remove the methods for individual
samples.
You can log samples by grid:
• By sample plan
• By material
To log many samples at the same time:

1. From the menu bar in the Instance tab, select Log > Enter >
By Grid to open the Grid Logging window.
2. Do one of the following:

Select By Sample Plan, then select the sample plan for the
samples you are logging from the list of valid entries.
OR
Select By Material, then select a study name and material name
for the samples you are logging from the list of valid entries.

DRAFT
3. Enter the log priority, then, if needed, change the sample priority.
Optionally, you can select the user sample ID and location name
from the list of valid entries.
4. Enter the number of samples being logged.
5. If needed, set the navigation for fields in the Samples tab.
• Next field/Same record – Cursor movement is from the
location field to the priority field, then to the user sample
ID field. Next, the cursor moves back to the location field
of the same record.
• Next field/Next record – Cursor movement is from the
location field to the priority field, then to the user sample
ID field. Next, the cursor moves to the location field of the
next record.
• Next record/Same field – Cursor movement is from the
location field of a record to the location field of the next
record, and so on (or the priority field of a record to the
priority field of the next record, and so on; or from the user
sample ID field to the user sample ID field of the next
record, and so on).
6. Click Create to open the Samples tab with the samples to log.
If you entered a user sample ID or location, every sample on the

Samples tab has this same sample ID or location. Every sample
has the same priority.

DRAFT
Chapter 2 Logging
7. If needed, edit the location, priority, or user sample ID for any

one or more samples.
To create a system-generated ID, click Generate User Sample
ID ( ) in the User Sample ID field.
8. To log the samples now (without adding attributes, methods, or
tasks), click Submit. Otherwise, add these as instructed in the
next sections.
Note: If attributes were attached from the template, they are
displayed in the Grid Logging window and are ready for entry
by the analyst.
Editing Multiple Attributes

You can edit multiple attributes by selecting and copying a range of
values in the grid logging window.
To select a column or row of values:

Select a column or row, then Shift-click.
To copy and paste a range of values:

1. To select a range of values, point to the cell that contains the
starting value, Shift-click, then repeat to select the ending value.
2. From the shortcut menu, select Copy.
3. Point to cell to which you want to copy the data, then from the
shortcut menu, select Paste.
To copy the contents of one cell into a range of values:

1. Select the cell that contains the value you want to copy, then
from the shortcut menu, select Copy.
2. Select a range of values.
3. From the shortcut menu, select Paste. The value is copied into
the selected range.

DRAFT
Adding Attributes
You can add attributes once to all samples as needed.
To add attributes to samples that you are logging by grid:

1. Click Add Attributes to open the List of Names window, then
choose the attributes to be added to every sample.
2. Click OK. The attributes are added as columns on the Attributes

tab. You can scroll to see all of the attributes added to the tab.
3. Enter the attribute values for any samples as needed.

DRAFT
Chapter 2 Logging
Adding Methods
If a sample plan was used, one or more methods may already be
present for each sample. You can add methods once to all samples
and then remove methods from one or more samples as needed.
Note: Methods designated as required in the sample plan template
cannot be removed.
To add methods to samples that you are logging by grid:

1. Click the Methods tab. Any methods from the sample plan
associated with these samples will be displayed.
2. On the Methods tab, click Add Methods to open the List of
Methods window, and select the methods to be added to every
sample.

DRAFT
3. Click OK. The methods are added as columns on the Methods

tab. You can scroll to see all of the method columns added to the
tab.
4. Deselect the check box of any methods that you do not want to
add to samples.
Editing Task Attributes

You can individually edit the attributes of the tasks associated with
each sample.
To edit the task attributes of samples logged by grid:

1. In the Grid Logging window, click any field for the sample
whose task attributes you want to edit.

DRAFT
Chapter 2 Logging
2. On the Methods tab, click Task / Attributes to open the Task

Attributes window for the sample.
3. Edit the attribute values for methods as needed, then click OK.
4. To log the samples, click Submit.
Editing Submission Attributes

You can individually edit attributes associated with each submission.
Submission attributes are copied from the study from which the
submission was derived.
To edit submission attributes:

1. Click the Log Info tab.
2. Click Submission Attributes to open the Attributes window,
then edit the attribute values.
3. To log the samples, click Submit.

DRAFT
Entering Results 3 3
This chapter describes how to enter results manually and how to
change results using the Change Result application option.
Results Data Entry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2
Result Value Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
Result Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4
Significant Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5
Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6
Result Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6
Column Headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9
Displaying More Result Information . . . . . . . . . . . . . . . . . . . . . .3-10
Entering Results by Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-13
Entering Results by Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-15
Entering Results by Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-18
Entering Results by Worklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-20
Entering Results for Many Samples . . . . . . . . . . . . . . . . . . . . . . .3-24
Displaying Earlier Result Versions . . . . . . . . . . . . . . . . . . . . . . . .3-28

DRAFT
The results entry function is affected by these user preferences:

• Check Limits Interactively
• Check Secondary Specifications Interactively
• Show Limits Page at Result Entry
• Display Limits Columns in Result Block
• Display Task Attributes
• Out-of-Specification Color
• Out-of-Detection Color
• Out-of-Limit Color.
See the SQL*LIMS Administration Guide for more information.
Results Data Entry

You can enter results manually, or your applications manager can set
up results so that they are entered automatically after a test is run. In
addition to entering results, you can also change results. You can
change them in windows where they can be entered by using the
Change Results application option. You can display earlier versions
of result records that have been changed.
The procedure for entering results is the same for each item on the
Results menu: you query to retrieve result records, then you enter or
change the result. To retrieve result records, query for results as they
relate to another kind of record: to a sample, to a task, or to the tasks
on a worklist. You can also query for results that were produced by a
specific method or that relate to a sample that has specific attributes.
Jobtype, Datagroup, Status, and Condition Considerations

Your jobtype may limit your access to any of the editing functions.
A query will retrieve only records with a datagroup label matching
one of your own.
The status and/or condition of a record may prevent it from being
retrieved for editing. Status and condition may also limit how you can
edit a retrieved record.

DRAFT
Result Value Types
Electronic Signature Considerations

If your applications manager has enabled the electronic signature
requirement, you will have to enter the appropriate password before
committing changes to the database.
Exploring Results
After result records have been retrieved, there are a number of ways
you can explore them (the availability of each depends on which
window is active):
• Zoom to display all the related instance records
• Display all or more information from a record
• Display attributes and enter/edit the updatable ones
• Select from the application option menus
• Display earlier versions of a result record
Result Value Types

Your applications manager has defined the type of value that you are
allowed to enter for each result. These can be exact values or ranges
of values. You can generally determine the type of value from the
component name and the units, and the list of valid entries displays
the acceptable values for measure limits.
The result types are as follows:
• NUMBER – A numeric value, such as a weight or
concentration. Only number values are used in any calculations
done on results.
• TEXT – A text value (up to 80 characters).
• TXTNUM – Can be a NUMBER (set or range), TEXT (from
list or ANY_TEXT), or a modifier with a number. A measure
limit MODIFIER is a symbol such as <, <=, >=, or >.
• TIME – A date and time of day.
• ESSAY – Text longer than 80 characters. You can enter essay
results by clicking Edit Attachments in the toolbar. The text you
enter there is recognized as the result.

DRAFT
Result Format
After you enter the result, it may be reformatted if a specific format
has been defined by your SQL*LIMS software applications manager.
See “Significant Figures” on page 3-5 for information about formats.
For operation, specification, and result plan components and
specifications, you can choose:
• Result Format (not available for specifications)
• Result Format with USP Rounding
• Result Format with ASTM Rounding
• Significant Figures ASTM
• Significant Figures USP
In the Define Operation, Define Result Plan, and Define
Specifications windows, the field Result Format with Rounding is in
the component properties screen. A numeric result format can be
specified, as well as USP or ASTM rounding.
A format must use “.” or “,” for the decimal place depending on the
regional settings in NLS_NUMERIC_CHARACTERS.
Placing a zero (0) or nine (9) restricts the entry of data to the
indicated positions around the decimal. For example, the format
“9.900” or “0.999” allows 1.234 and 0.000, but disallows 10.000,
1.2344, and 9.999 (because it rounds to 10.000).
Placing a zero (0) in a format also specifies trailing or leading zeros
at that position to the right or left of the decimal point. Placing a nine
(9) in a format allows the position to be left blank. For example, the
format “9.900” requires that there be three decimal places to the right
but allows none to the left, so that the entry 1.2 becomes 1.200 and
the entry .7 becomes .700.
If you enter a value larger than allowed by the format, an error
message appears. For example, entering 100 for the format “99.900”
causes an error.
In connection with specifying the number of digits to the right and
left of the decimal, you can choose a method of rounding or choose
no rounding. For example, entering 23.4765 for the format “90.000”
rounds to 23.476 for ASTM rounding and 23.477 for USP rounding.

DRAFT
Significant Figures
The result entry significant figures and the evaluation of

specifications with significant figures are independent of each other.
Synchronize the specifications and the result format to prevent
unexpected out-of-spec errors.
The text_value is rounded, but the number_value is not rounded and
is used in calculations. The calculated result can also use Result
Format with Rounding.
The stored procedure to implement Result Format with Rounding can
be called from:
• ARE™ (automatic result entry)
• Result entry forms
• Results package
• Calculations software
• Specification checking routines
Significant Figures
After you enter the result, it may be reformatted if a significant digit
format has been defined by your SQL*LIMS software applications
manager. For example, if you entered 1.345, this could become 1.34.
If the entered result will undergo a calculation, the original result
entered is used, not the reformatted one; that is, the 1.345 is used
instead of the 1.34.
A significant figure format, if defined, applies to the number part of a
NUMBER or TXTNUM result value. This format is applied to
measure or specification limit results. If multiple specifications have
been defined for a result, the format is applied separately to each
specification of this result. A significant figure format, if defined, is
also applied to any result of a calculation.

DRAFT
Calculations
If the result that you enter will undergo calculations, as defined by
your applications manager, you can view the formulas and calculated
result by clicking the More button in the sample result window.
Calculations can be defined only for results of the value types
NUMBER.
Result Limits
Result values may be subject to limits established by your
applications manager. When you enter or change a result, the
application checks to see if the value falls within three types of limits.
Measure limits – Logical boundaries for results that are attached to
particular units of measure. A result expressed in these units is
subject to the limits. A result that is beyond measure limits will be
displayed in the out-of-limit color as specified in your user
preferences. For measure limits, interactive limit checking is always

DRAFT
Result Limits
enabled. That is, results are always compared against measure limits
as they are entered. Your applications manager determines whether or
not you can override a measure limit by using the Override Limit
application option.
Detection limits – Represent a detection limit for a given analytical
instrument and define an upper and lower limit for a result. If
interactive limit checking is enabled, results are compared against
detection limits during results entry; otherwise, limit checks are
performed by the application as status changes are being processed.
A result that is beyond detection limits is displayed in the out-of-
detection color as specified in the user preferences. Results may be
configured to be COMPLETE or SUSPECT when outside of
detection limits.
Specification limits – The acceptable boundaries for quality control
or regulatory limits. You can enter a result that is outside this limit,
but the status of the result record becomes SUSPECT and the entry
will be displayed in the out-of-specification color as specified in your
user preferences. If interactive limit checking is enabled, results are
compared against primary specification limits during results entry;
otherwise, specification checks are performed by the application as
status changes are being processed.
After querying to retrieve the records for result entry, clicking the
Limits tab of any Results menu window displays the associated
measure, detection, or specification limits. Alternatively, you can set
the application to automatically display the limits using the Show
Limits Page at Result Entry user preference. Refer to the SQL*LIMS
Administration Guide for more information.

DRAFT
Primary and Secondary Specifications

When you select the Limits tab, primary and secondary
specifications are displayed. If you select the Primary/Secondary
Specs check box, the Specification field displays the primary
specification. When the check box is deselected, the Specification
field displays one of the secondary specifications.
A result can have primary and secondary specifications, but there is
only one primary specification. When the Specification field displays
the primary specification, its name appears in the text box under the
check box. When the Specification field displays secondary
specifications, the text box becomes a list of available secondary
specifications. Any significant figures format on the specification
will be applied during specification checking.
Multiple Specifications
If the Check Secondary Specifications Interactively user preference
is set, the application compares result entries against the secondary
specification limits as each result is entered. The original result value
that you enter, not the final result after any significant figure has
been applied to it, is used in this comparison. The cumulative result
of these comparisons is displayed in the status bar as follows:
• If the entered result is outside any specification limit, the
cumulative result of the limit check is OUT.
• If the entered result is within any of the specification limits, and
the result is not outside any of the limits, the cumulative result of
the limit check is IN.
• If no secondary specifications have been defined for the result,
then the value in the status bar will be N/A.
Limit Displays
The limit conditions are displayed in one of three ways:
• The limit condition (IN, OUT, etc.) is displayed in the data
column labeled Spec, SSpec, Det, or Lim in the Results window.
• The code in the column indicates whether or not the result value
is within or outside the specific limit being displayed:
– IN – The result is within the specified limit.
– OUT – The result is outside the specified limit.

DRAFT
Column Headings
– N/A – No limit has been specified for this result.

– ERR – An error occurred during limit checking.
– OVR – The measure limit has been manually overridden.
– OVL – The result is over the detection limit.
– UNL – The result is under the detection limit.
• During data entry operations, the following message indicating
limit conditions may appear in the status bar:
PEN-10016 Specification=XXX Detection=YYY Measure=ZZZ
Secondary spec = AAA
where XXX, YYY, and ZZZ indicate the specific conditions for
each type of limit.
Note: The secondary spec indicator in the status bar will
indicate OUT if any of the secondary specs is out.
• The limit condition is indicated by the color of the displayed
result. You can change the green, blue, or red default colors to
other colors on the Color Preferences tab of your user
preferences. The default settings are:
– Black – The result is within all limits.
– Green – The result is outside the measure limit.
– Blue – The result is within the measure limit, but outside the
detection limit.
– Red – The result is within the detection limit, but outside the
specification limit.
Column Headings
In Result menu windows, the column headings to the right of the
Units column are abbreviated and display the following:
• Lim – (Limits) the condition for measure limits, for example, ERR.
• Det – (Detection) the condition for detection limits, for
example, IN.
• Spec – (Specification) the condition for primary specification
limits, for example, OUT.
• SSpec – (Secondary Specification) the condition for secondary
specification limits, for example, IN, currently selected in the
list box.
• Rp – (Repetition) replicate number of a result. Indicates which
task repetition produced the result value.

DRAFT
Displaying More Result Information

You can view data from the result record by displaying a separate
window, which may provide record details after you enter the result.
To display more results:

Select the record retrieved for result entry, then click More:

DRAFT
Displaying More Result Information
The result record data displayed in the window (after you have
entered the result and then clicked More) may include the following:
• Component – When selected, a link that displays the template
from which the result was logged.
• Text Value – Displays the result after any significant figure or
result format has been applied to it.
• Number Value – Displays the number value of the result exactly
as entered.
• Units – Identifies the units of measure for the result (for
example, PERCENT).
• Significant Figures – Shows the number of significant figures
being applied to the result, for example, 3.
• Result Format – Indicates which result format has been
defined, for example, FXDD-MON-YYYY for a date or 99.99
for a number.
• Measure Units – When selected, a link that displays the
template from which the result was logged.
• Value Type – Refer to “Result Value Types.”
• Result Version – Indicates the version of the result being
displayed. If a result has more than one version, you can click
this link to see a previous version.
• Entered By – Displays the user ID of the person who entered
the results.
• Date Entered – Displays the date the results were entered.
• In Limit/In Spec/In Detection – Refer to “Limit Displays.”
• Limit/Specification/Detection ID – Displays the identification
number of the measure limit, specification, or version limit.
• Limit/Specification/Detection Version – Displays the version
number of the measure limit, specification, or detection limit.
• Status – displays the status value that indicates the progress of
the record through the lab. Together with a condition value,
status indicates the progress of instance records. A status is
always entered automatically by the application.
• Condition – Displays the value that indicates progress of the
record through the lab. Together with a status value, condition
indicates progress of instance records.
• Condition Level – Displays the level in the instance hierarchy
that is responsible for the record’s current condition.

DRAFT
• Analyst – Displays the user ID of the person responsible for the

task that generated the result.
• Req – (Required) Y indicates that a result value in this record is
required (in order for the task to become COMPLETE). N
indicates that a result value is optional. C indicates that a result
value will be calculated by the application from other results for
the same task, and you cannot enter a result value.
• Task Version – Task version consists of an operation that takes
all the task results and rejects them. The operation creates a new
set of empty results with a new task version number. Tasks
themselves have no version.
• Reason – Indicates why the result has been changed, when more
than one version exists.
• Planned – A Y response indicates that the result was logged
using a template, N indicates that the result was added ad-hoc,
through ARE or some other means after logging. A numeric
value determines ordering of the result for calculations.
• Result Origin – An M indicates the result was entered
manually; otherwise, ARE indicates the result was entered
automatically by the ARE application.
• Replicates – Indicates the number of replicates (number of
times a task was performed). Extra sets of the results for the task
are created. Can be imposed if you set task replicates to greater
than 1, or if you add replicates manually.
• Rpt (Report) – User-defined column that can be used by
reports, for example to indicate whether the value should be
shown in the report.
• Method Datagroup – Displays the datagroup to which a
method belongs.
• Customer Datagroup – Displays the datagroup for which a
customer has view access.
• System IDs – Displays submission, sample, task, and result
identification numbers.
• Attributes – Displays any attributes attached to the result.

DRAFT
Entering Results by Sample
Entering Results by Sample

To enter results by sample, you query on sample data to retrieve
samples and results, then you enter a value in the Result field of the
appropriate record in the Results window. Retrieving results by
sample is useful when one analyst is responsible for all the tests on a
sample.
To enter results by sample:

1. In the menu bar of the main menu, select Results > by Sample
to display the Enter Sample Results window.
2. Select a saved query to execute (QBE).

OR
Enter any search criteria on the Find tab. Click More to open the
lower Find tab and enter additional search criteria.
The application may automatically fill the Analyst field with the
user ID of the person responsible for the task that created a
result. When a name is present, only result records for which
that person is responsible (through the task) are retrieved. Your
SQL*LIMS user ID may be provided as a default.
If you want to change the default analyst for the query do so
before you enter any other search criteria:
a. In the Find tab, select the Set Analyst or Clear Analyst
Application Option.
If you select Set Analyst, choose an analyst from the list of
valid entries.
b. Click OK.

DRAFT

The first retrieved sample is displayed. The result records
related to that sample are displayed in the Samples tab.
To select a sample among multiple samples, use the Previous

Record and Next Record arrow keys to move through the
records.
To view more data about the sample, click the Sample Detail tab.
4. In the Samples tab or the Limits tab, enter values select from the
list of valid entries in the Results column. Execute a second-
level query on the results to reduce the number.
To type a result that requires more room than is available in the
Result field, click Edit Attachments in the toolbar.
Use Edit Attachments to add comments about any non-essay
result or add other types of attachments, such as AVI files. (An
audit reason may be required.)

DRAFT
Entering Results by Task
5. Click the Limits tab to determine whether limits exist for the
sample result.
OR
If the Show Limits Page at Result Entry option in your user
preferences is selected, the limits are automatically displayed
when you click in any field in the Results area.
Note: The Limits tab appears if your applications manager has
enabled limits display. The Limits tab displays measure unit
limits, detection limits, and specification limits. For more
information about limits, refer to “Result Limits” on page 3-6.
6. To enter any additional sample results, click Commit, then use
the down arrow to display another sample record or enter
another query.
7. Exit when you are done.

To enter results by task, you query on task data to retrieve tasks and
results, then you enter a value in the Result field of the appropriate
record in the Results window.
Retrieving results by task is useful when an analyst performs a given
test on a range of samples.
To enter results by task:

1. In the menu bar of the main menu, select Results > by Task to
display the Enter Task Results window.

DRAFT

OR
Enter any search criteria on the Find tab. Click More to open the
lower Find tab and enter additional search criteria.
user ID of the person who is responsible for the task that created
a result. When a name is present, only result records for which
application option.
If you selected Set Analyst, choose an analyst from the list
of valid entries.
b. Click OK.
3. Click Find to execute the query. The first retrieved task record is
displayed. Result records related to the task are displayed on the
Tasks tab.

DRAFT
4. To select a sample among multiple samples, use the Previous

records.
5. To view more data about the task, click the Task Detail tab.
6. In the Tasks tab or the Limits tab, enter values or select from the
list of valid entries in the Result column. Execute a second-level
query on the results to reduce the number.
To enter a result that requires more room than is available in the
Result field, click Edit Attachments in the toolbar. (No audit
reason is needed.)
sample result.
OR
information about limits, refer to “Result Limits.”
8. To enter any additional task results, click Commit in the toolbar,
then use the down arrow to display another task record or enter
another query.

DRAFT
Entering Results by Method

A SQL*LIMS software method provides a regular and systematic
way to produce results for the tests that you perform on samples.
To enter results by method, you query on method information to
retrieve the results produced by that method, then you enter a value in
the Result field of the appropriate record in the Results window.
Retrieving results by method is useful when an analyst conducts a
specific series of tests (predefined as a method) on a range of
samples. The result records retrieved may be related to several
different tasks, samples, and submissions.
To enter results by method:

1. In the menu bar of the main menu, select Results > by Method
to display the Enter Method Results window.

DRAFT
Entering Results by Method
2. Enter search criteria on the first tab. A method name and

datagroup are required.
a. In the Find tab, select Set Analyst or Clear Analyst
application option.
valid entries.
b. Click OK.
3. In the Method field, select a method from the list of valid
entries, then execute the query to display the results.
To view more data about the method, click More.

DRAFT
4. In the Methods tab or the Limits tab, enter values or select from
the list of valid entries in the Result column. Execute a second-
level query on the results to reduce the number.
Result field, click Edit Attachments. (No audit reason is
needed.)
sample result.
OR
6. (optional) At the Method tab, use a detail query to filter the
samples displayed.
7. If you have results to enter for another method, choose Commit,
then enter another query.
Entering Results by Worklist

When you enter results by worklist, you are entering results for the
tasks on the worklist.
To enter results by worklist, you query to retrieve worklists and the
associated tasks, then you select individual tasks for result entry.
When the tasks are displayed, you can:
• Display more information from a task record.

DRAFT
To enter results by worklist:

1. In the menu bar of the main menu, select Results > by Worklist
to display the Enter Worklist Results window.

OR
Enter worklist data search criteria on the Find tab. Click More to
open the lower Find tab and enter additional search criteria.
If you want to change the default analyst for the query, do so
before you enter any other search criteria using this procedure:
application option.
valid entries.
b. Click OK.

DRAFT

The first retrieved worklist is displayed. Task records related to
the worklist are displayed in the Worklists tab.
Note: The instrument has a calibration indicator next to its

name. If the instrument is out of calibration ( ), select a
different one.
4. To select a worklist among multiple worklists, use the Previous
records.

DRAFT
5. Click the Tasks tab to see the results for each task in the
worklist. You can execute a second-level query on the tasks to
reduce their number.
6. In the Tasks tab or the Limits tab, enter values or select from the
list of valid entries in the Result column. Execute a second-level
query on the results to reduce the number.
Result field, click Edit Attachments in the toolbar. (No audit
reason is needed.) Use Edit Attachments to add comments about
any non-essay result or add other types of attachments, such as
AVI files. (An audit reason may be required.)

DRAFT
sample result.
OR
information on limits, refer to “Result Limits” on page 3-6.
8. To enter any additional results by worklist, click Commit, then
select another task for result entry, display another worklist with
its tasks, or enter another query.
Entering Results for Many Samples

Entering results by matrix lets you enter the results of many samples
at one time while displaying their components and replicates.
When the samples are displayed, you can:
• Click More to display more information from a result record.
• Use the shortcut menu to display, enter, and edit the updatable
attributes; copy and paste data in grid cells; and view any audit
log records.
Entering Results by Matrix

To enter results by matrix:
1. In the menu bar of the main menu, select Results > by Matrix
Result Entry to display the Results by Matrix window.
2. On the Find tab, select the template matrix for the results that
you want to enter.

DRAFT
3. In the other fields, select additional query criteria from the list
of valid entries.
These additional criteria let you select the instance data for
which you want to enter results.
For example, you may have a matrix template that allows you to
enter results for samples by the instrument the samples were
tested on. In the Find tab, select the template “Samples by
Instrument,” then select the instrument or instrument class that
applies to the results you need to enter.
The additional criteria fields vary depending on the template
you select. For example, if you have a template for selecting
samples by instrument, the Find tab may look like the following
screen:
If you have a template for selecting tasks by submission, the

Find tab may look like this screen:
To speed record retrieval, enter as many search criteria as

possible.

DRAFT
4. Click Find or Execute Query.

A progress counter informs you of progress for retrieving the
records. Displaying the records may take some time.
The data are displayed in grid format on the Result tab.
The column headings will probably indicate component

information, but this may not be true in all cases because the
matrix was designed by your lab manager, who decided the
column and row headers.

DRAFT
5. Enter results data in each field, as appropriate. Press Tab to

move from cell to cell.
If you don’t know the upper and lower limits for a result, click
the Limits tab to display the limits, if any.
6. Click Commit.
Editing Multiple Results

Use the following procedures to edit, copy, and paste multiple results
in the Results by Matrix window.
To select multiple results:

Select a column or row, then Shift-click.
To copy and paste a range of values in a column or row:

1. To select a range of values in a column or row, point to the cell
that contains the starting value, shift-click, then repeat to select
the ending value.
The selected range is highlighted.
2. From the shortcut menu, select Grid Copy.
3. Point to cells into which you want to copy the data, then from the
shortcut menu, select Grid Paste.
To copy the contents of one cell into a range of values:

1. Select the cell that contains the value you want to copy, then
from the shortcut menu, select Grid Copy.
2. Select a range of values.
3. From the shortcut menu, select Grid Paste.
The values are copied into the selected area.

DRAFT
Displaying Earlier Result Versions

Your applications manager has configured study rules or audit rules
that save the version of a result record when it is changed.
The SQL*LIMS software then creates a new record when you change
a result and saves the superseded result record (rather than
overwriting it). Each of these result records has the same result ID,
but they are differentiated by a sequential version number (shown in
the Result Version field).
To display earlier versions of a result:

1. Select the result for which you want to see an earlier version.

DRAFT
Displaying Earlier Result Versions
2. Click More.
A separate window is displayed for the result. The result’s
current version number is displayed in the Result Version field.
3. Click the current version number, and another window is

displayed showing the previous result and its version number.
Continue clicking the version number and displaying result
windows until the result version you want is displayed.

DRAFT

DRAFT
Viewing Data 4 4
This chapter describes how to view data from records for
informational purposes and to track the progress of changes made to
a record.
Viewing Instance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2
Viewing Worklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-16
Viewing Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-18
Customer Viewing of Instance Records . . . . . . . . . . . . . . . . . . . .4-20
Viewing Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-26
Viewing Log Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-31
Viewing Status Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-32
Viewing Status and Condition Changes . . . . . . . . . . . . . . . . . . . .4-34
Viewing the Audit Log of Instance Records . . . . . . . . . . . . . . . . .4-36
Viewing Electronic Signature History . . . . . . . . . . . . . . . . . . . . .4-37
Verifying Electronic Signatures in an Instance Tree . . . . . . . . . . .4-38

DRAFT
Viewing does not allow you to manipulate data, other than to enter or
edit updatable attributes and to enter or edit attachments. In the View
menu you can only view data, which allows you to track:
• All levels of instance records at any time during the life of a
sample
• Worklists
• Tasks assigned to an analyst (work)
• Status and condition changes for instance records (state history)
• Current and previous sample locations
• Instance audit log requests
• Log requests
• Status requests
• Audit history
• Electronic signature history
Note: Your jobtype may limit your access to any of the viewing
functions. A query retrieves only records with a datagroup label that
matches one of your own. The status and condition of a record may
prevent it from being retrieved for viewing.
Viewing Instance Data

You can approach instance viewing from any point in the hierarchy:
submissions, samples, tasks, and results.
View… To View… To View…
Submissions Submission data Submissions
Samples Sample data Samples

Submission data Submissions and Samples
Tasks Task data Tasks

Sample data Samples and Tasks
Results Sample data Samples and Results

Task data Tasks and Results
Method data Results

DRAFT
There are two types of queries for instance viewing:

• Direct query for records of a particular type, used when you
view submissions, view samples (by sample), and view tasks (by
task).
• Query for records of a particular type as they relate to another
kind of record. This query retrieves both types of records and is
used when you view samples by submission, view tasks by
sample, and view results by sample or task.
After the records have been retrieved, there are a number of ways that
you can explore them. The availability of each depends on which
window is active:
• Click More to display more information from a record
• Display attributes and edit the updatable ones
• From the Results windows, display earlier versions of a result
record that has been changed. For details, see “Displaying
Earlier Result Versions” on page 3-28.
You can use Edit > Edit to display text when a display field is not
large enough to show the entire contents of the corresponding field in
the database.
Viewing Submissions
To view submissions, query directly on submission data.

DRAFT
To view submission records:

1. In the menu bar, select View > Submissions to display the View
Submissions window.
2. Enter any search criteria or enter a saved query in the QBE field,
then click Find.

DRAFT
3. To view more information about a submission, select it from the

list of retrieved records and do one of the following:
• Click More to open the Submission window from which
you can view submission information including attributes
or parameters, as well as the study and associated ruleset
from which the submission was derived.
• Select the Submission Detail tab to view the submission
information including the status action and
attribute/parameter count information.
4. (optional) Verify electronic records for a submission.
5. Close the window when you are finished viewing submissions.
Viewing Samples
There are two ways to retrieve sample records for viewing:
• By querying on submission data to simultaneously retrieve
submissions and the related samples
• By querying directly on sample data
Viewing Samples To view samples by submission, query on submission data to retrieve

by Submission both submissions and the related samples.
To view sample records by querying on submissions:

1. In the menu bar, select View > Samples > by Submission to
display the View Submission Samples window.

DRAFT
2. Enter any search criteria, then click Find.

The first retrieved submission is displayed in the upper portion
of the View Submission Samples window. Related sample
records are displayed in the lower portion of the window.
3. To select a record among multiple records, use the up and down

arrow keys to move through the records.
• Click More to open the Sample window from which you
can view sample information including attributes or
parameters, a summary of status actions, as well as the
material name and sample plan from which the sample
record was derived.
5. (optional) Verify electronic records for a sample.
6. Close the window when you are finished viewing samples.

DRAFT
Viewing Samples To view samples by sample, query directly on sample data.

by Sample
To view sample records by querying on samples:
1. In the menu bar, select View > Samples > by Sample to display
the View Samples window.
The retrieved sample records are displayed in the View Samples
window.

parameters, as well as the material and sample plan from
which the sample record was derived.
• Select the Sample Detail tab to view the sample
5. (optional) Verify electronic records for a sample.
6. Close the window when you are finished viewing samples.

DRAFT
Viewing Tasks
There are two ways to retrieve task records for viewing:
• By querying on sample data to simultaneously retrieve samples
and the related tasks
• By querying directly on task data
Viewing Tasks by To view tasks by sample, query on sample data to retrieve both
Sample samples and the related tasks.
To view task records by querying on samples:

1. In the menu bar, select View > Tasks > by Sample to display the
View Sample Tasks window.
The first retrieved sample is displayed in the upper portion of
the View Sample Tasks window. Related task records are
displayed in the lower portion of the window.
3. Select a record.
To select a record among multiple records, use the up and down

DRAFT
4. To view more information about a task, select it from the list of

retrieved records and do one of the following:
• Click More to open the Task window from which you can
view task information including attributes or parameters, as
well as the method and operations from which the task
record was derived.
5. (optional) Verify electronic records for a task.
6. Close the window when you are finished viewing task records.
Viewing Tasks by To view tasks by task, query directly on task data.

Task
To view task records by querying on tasks:
1. In the menu bar, select View > Tasks > by Task to display the
View Tasks window.
Tasks that are displayed without data in the Operation field are
parent tasks that are created from a method. For information on
methods and operations, see the SQL*LIMS Template Design
User Guide.

DRAFT
3. Select a record.
To select a record among multiple records, use the up and down
well as the method and operations from which the task
record was derived.
• Select the Task Detail tab to view the task information
including the status action and attribute/parameter count.
5. (optional) Verify electronic records for a task.
6. Close the window when you are finished viewing task records.
Viewing Results
The four ways to retrieve result records for viewing are by querying
on the following:
• Sample data to retrieve samples and their related results
• Task data to retrieve tasks and their related results
• Method data to retrieve the results produced by that method
• By matrix
You can display earlier versions of a result record that has been
changed if your applications manager has implemented this
configuration. For details, see “Displaying Earlier Result Versions”
on page 3-28.
Note: The display of result records is affected by the Display Limits
Columns in Result Block user preference. See the section on user
preferences in the SQL*LIMS Administration Guide.
Note: For details about the information displayed in these windows,
see Chapter 3.

DRAFT
Viewing Results To view results by sample, query on sample data to retrieve both
by Sample samples and the related results.
To view result records by querying on samples:

1. In the menu bar, select View > Results > by Sample to display
the View Sample Results window.
the window. Related result records are displayed in the lower
portion of the window.

4. To view more information about a sample, click in the Sample
ID field and do one of the following:
• Click More to open the Result window from which you can
view result information including attributes or parameters,
as well as the component measure unit associated with the
result record.

DRAFT
5. To view measure unit limits, detection limits, and specification

limits associated with the results, select the Limits tab.
6. (optional) Verify electronic records for a result.
7. Close the window when you are finished viewing results.
Viewing Results To view results by task, query on task data to retrieve both tasks and
by Task the related results.
To view result records by querying on tasks:

1. In the menu bar, select View > Results > by Task to display the
View Task Results window.
The first retrieved task is displayed in the upper portion of the
window. Related result records are displayed in the lower portion
of the window.

DRAFT

as well as the component measure unit associated with the
result record was derived.
• Select the Task Detail tab to view the result information
including the status action and attribute/parameter count
information.
The Limits tab appears only if Limits display has been enabled.
For more information on limits, see “Result Limits” on
page 3-6.
Viewing Results To view results by method, query on method data to retrieve the
by Method results associated with that method. Querying for results by method
uses method data as search criteria and retrieves only result records.
The result records retrieved may be related to several different tasks,
samples, and submissions.
To view result records by querying on methods:

1. In the menu bar, select View > Results > by Method to display
the View Method Results window.

DRAFT
2. Enter a method name and any other search criteria or enter a

saved query in the QBE field, then click Execute Query in the
toolbar to display the related results.
3. To select a method among multiple records, use the up and down

4. To view more information about a method, select it from the list
of retrieved records, then click More to open the Result window,
from which you can view result information including attributes
or parameters and the component measure unit.
The Limits tab appears only if Limits display has been enabled.
For more information on limits, see “Result Limits” on
page 3-6.

DRAFT
Viewing Results You can view results by matrix (MRE) to see, in a matrix format, the
by Matrix results for the object that you select.
1. In the View menu bar of the Instance tab, select View > Results
> by Matrix Result to display the Results by Matrix window.
2. On the Find tab, select the template matrix for the results that
you want to enter.
3. In the other fields, select additional query criteria from the list
of valid entries.
These additional criteria let you select the instance data for
which you want to enter results.
For example, you may have a matrix template that allows you to
enter results for samples by the instrument the samples were
tested on. In the Find tab, select the template “Samples by
Instrument,” then select the instrument or instrument class that
applies to the results you need to enter.
The additional criteria fields vary depending on the template you
select. For example, if you have a template for selecting samples by
instrument, the Find tab may look like the following screen:

DRAFT
Viewing Worklists
You can view an existing worklist and its related tasks. To view a
worklist, enter search criteria, then query to retrieve the worklist and
the tasks on it.
You can then:
• Display any attributes and edit the updatable ones.
• Browse and edit any attachments for the task and worklist
records.
• Select from the application option menus.
To view worklists:
1. In the menu bar, select View > Worklist to display the View
Worklist window.
OR
To change the default analyst for the query, do so before you
enter any other search criteria by using the following procedure:
a. Click Find.
b. To specify other than the default analyst for the query,
choose the Set Analyst application option, then select an
analyst from the list of valid entries.
c. To remove the default analyst from the search criteria,
choose Clear Analyst to clear the Analyst field.

DRAFT
Viewing Worklists
d. Click OK to redisplay the Find tab.
3. Enter any other worklist data as search criteria, then click Find.
The worklist records that match the query criteria are displayed
in the upper portion of the window. Any task records related to
the worklist record selected in the upper portion of the window
are displayed in the task list in the lower portion of the window.
You can execute a second-level query to reduce the number of

tasks displayed.

DRAFT

• Click More to view task information.
• Select the Worklist Detail tab to view the result information
including the method, operation, and instrument
information.
6. Close the window when you are finished viewing worklists.
Viewing Work
You can view the tasks assigned to an analyst. The analyst can be
yourself. The datagroup of the analyst must match one of your
datagroups.
To view tasks assigned to an analyst, you enter search criteria, then
query to retrieve the tasks. You can then:
• Display any attributes and edit the updatable ones.
• Browse and edit any attachments.
• Select from the application option menus.
To view work:
1. In the menu bar, select View > Work to display the View Work
window.
2. Enter an analyst name.
3. Click once in the Jobtype field to select the jobtype. If there is
more than one jobtype for an analyst, select it from the list of
valid entries.

DRAFT
Viewing Work
4. Enter any other search criteria, then click Find.

The tasks assigned to the analyst that you have entered are
displayed.

well as the methods and operations from which the task
record was derived.
• Select the Task Detail tab to view the task information
information.
6. Close the window when you are finished viewing work.

DRAFT
Customer Viewing of Instance Records

If you are a customer enrolled as a user of the SQL*LIMS® software,
you can track the progress of submissions, samples, tasks, and results
by viewing these instance records. To retrieve and display these
records, your datagroup must match the customer datagroup for the
retrieved records. You can only view the customer forms and data that
has a customer datagroup to which you belong.
Customer Datagroup is a keyword attribute. Users must have:
• The user class CUSTOMER.
• A jobtype with only the CUSTOMER and LIMS_PUBLIC
roles.
• The datagroups for the customer datagroup have been assigned
to the user.
Note: The customer user account should be assigned the datagroups
(study datagroup, material datagroup, and method datagroup) to be
used for the Customer Datagroup field. When using these forms,
only the Customer Datagroup is used to determine what records to
display.
The Customer Visible Tracking Condition system parameter
determines which records are visible by their condition.
Viewing Customer Samples by Submission

To view samples by submission, query for submissions.
To view customer samples by submission:

1. In the menu bar, select View > Customer > by Submission to
display the View Customer Submission Samples window.
The first retrieved submission is displayed in the upper portion
of the window.

DRAFT
Related sample records are displayed in the lower portion of the

window.

parameters, as well as the material and sample plan from
which the sample was derived.
5. Close the window when you are finished viewing submissions.

DRAFT
Viewing Customer Tasks by Sample

To view tasks by sample, query for samples.
To view customer tasks by sample:

1. In the menu bar, select View > Customer > by Sample to
display the View Customer Sample Tasks window.
the window. Related task records are displayed in the lower


DRAFT
4. To view more information on a task, select it from the list of

well as the method and operation(s) from which the task
record was derived.
• Select the Sample Detail tab to view the task information
information.
5. Close the window when you are finished viewing tasks.
Viewing Customer Results by Task

To view results by task, query directly on tasks.
To view customer results by task:

1. In the menu bar, select View > Customer > by Task to display
the View Customer Task Results window.

DRAFT
The first retrieved task is displayed in the upper portion of the

window. Related result records are displayed in the lower portion
of the window.
as well as the component measure unit from which the
• Select the Task Detail tab to view the result information
information.
Note: The Limits tab appears only if Limits display has been
enabled. For more information on limits, see “Result Limits” on
page 3-6.
6. Close the window when you are finished viewing customer
results by task.
Viewing Customer Samples by Result

To view samples by result, query directly on results by sample.
To view customer samples by result:

1. In the menu bar, select View > Customer > by Result to display
the View Customer Sample Results window.

DRAFT

the window. The related results are displayed in the lower

as well as the component measure unit from which the
• Select the Sample Detail tab to view the result information
information.
Note: The Limits tab appears only if Limits display has been
enabled. For more information on limits, see “Result Limits” on
page 3-6.

DRAFT
Viewing Locations
You can view the current and previous storage locations of samples.
Viewing Current Locations

You can view all current locations. For each location, you can display
the location hierarchy established for your laboratory.
To view the current locations by location:

1. In the menu bar, select View > Locations > by Location to open
the View Locations window.
The retrieved location records are displayed. The location
hierarchy of the location selected in the upper part of the
window is shown in the lower part of the window.
3. To view more information in a location record, click More.

The Location window displays detailed information on the
location, including any associated storage units.

DRAFT
Viewing Locations
Viewing Sample Location

You can identify the current location of any sample. The procedure is
to query for the samples for which you want to know the location.
To view the location of a sample:

1. In the menu bar, select View > Locations > by Sample to
display the Locate Samples window.
The samples are displayed in the upper portion of the window.
The lower part of the window displays the location hierarchy for
the selected sample.
Note: If the sample has not been assigned to a location, a

location hierarchy will not appear.
3. To view more information about a sample, select it from the list
of retrieved records, then select the Sample Detail tab.
4. Close the window when you are finished viewing sample
locations.

DRAFT
Viewing Location History

You can display the history of a location and its hierarchy, even if the
location has been deleted.
The location history windows contain a field called Ver (Version) that
tracks modifications to changes. The version number of the location
indicates the number of edits performed on the location. When a
location is created, it is assigned a location version of 1. Renaming a
location or assigning it to another parent increments the version
number.
To view the history of locations:

1. In the menu bar, select View > Location History > by Location
to display the Location History window.
2. Select a location from the list of valid entries.
3. Click Execute Query in the toolbar to display the location
history.
The location is displayed in the upper part of the window.

Hierarchy and history are displayed in the lower part. The Status
field shows the status of each location record.

DRAFT
Viewing Locations
Viewing Sample Location History

You can locate a sample and identify where it has been. The Sample
Location History window has the S (Status) field, which contains a
status code for the location.
The S field contains one of these status codes:
Location
Status Code Location Status Applies to:
C(urrent) Current sample location All locations, sample

locations, and plate
locations
D(ispose) Sample disposal Sample locations

location
F(ormer) Previous sample Locations, sample

location locations
To view the location history of a sample:

1. In the menu bar, select View > Location History > by Sample
to display the Sample Location History window.
2. Enter any search criteria for the sample, then click Find.
The current and previous sample locations, along with the date
and time that the sample location was assigned, are displayed in
the lower portion of the window. This information applies to the
sample record currently selected in the upper portion of the
window.

DRAFT
The location hierarchy shows the relationship of the location

(selected under Location Name and Location Date fields) to
other locations in the hierarchy, the location version, and the
parent.

4. To view more information about the sample, select the Sample
Detail tab to view the sample information including the status
action and attribute/parameter count information.
5. Close the window when you are finished viewing locations.

DRAFT
Viewing Log Requests
Viewing Log Requests

Log requests are records that are created each time you log samples,
add methods to samples, or add samples to submissions. You can
retrieve and view all the log request records.
Log requests reveal which samples have been submitted, and whether
or not they have been logged. If they have been logged, you can tell
where they are in the laboratory workflow.
After you have queried to retrieve log request records, you can:
• Sort by user, date, origin, EP (entry point), or status using the
shortcut menu.
• Select a log request, then click More to display more data about
the request.
• Zoom to display all the records in the instance hierarchy.
• Select from the application options.
To view log requests:

1. In the menu bar, select View > Log Requests to display the
View Log Requests window.
2. Enter search criteria in any of these columns:
Request ID – A number that the program assigns to log
requests.
User – The SQL*LIMS user ID of the person who entered the
log request.
Date – The date on which the log request was entered.
Origin – Area in the application in which the log request was
entered.
EP – (entry point) A number that further describes the Origin.
Status – The log request status: COMPLETE, REQUESTED,
PRELOG, ERROR (#).

DRAFT
3. Click Execute Query in the toolbar to display the log requests.
4. To view more information about a log request, click More to

display the Log Request Detail window.
Viewing Status Requests

Status requests are records that, when retrieved and viewed, show the
requests made to the database for processing status and condition
changes.
After you have queried to retrieve status request records, you can sort
them by request ID, date, time, origin, EP (entry point), or status
using the shortcut menu.

DRAFT
Viewing Status Requests
To view status requests:

1. In the menu bar, select View > Status Requests to display the
View Status Requests window.
2. Enter search criteria in the top columns or any of the table
columns:
Request ID – Number the application assigns to status requests.
Date – Date on which the status request was entered.
Origin – Where the status request was entered.
EP – Entry point number of the function processed (for
example, Submission Condition Change = 210). See the
SQL*LIMS Tables Reference Guide for more information about
numbers.
Status – Request status, such as COMPLETE, REQUESTED,
PREREQUEST.
3. Click Execute Query in the toolbar to display status requests.

DRAFT
Viewing Status and Condition Changes

You can view the status and condition changes (state history) over
time for any submission, sample, task, or result. (If you have the
SQL*QA™ software, you can also see changes for any lot.) Your
applications manager determines which status or condition changes
are saved.
You can query on any of these instance levels for a given time period
or for certain state changes. For each transition, you can see the user
who caused the change, the date of the change, and the initial and
final states.
You can zoom from a retrieved record to display all the related
instance records. Also, you can display more data from a record by
selecting it and then clicking More.
To view status and condition changes:

1. In the menu bar, select View > State History to display the
View State History window.

DRAFT
Viewing Status and Condition Changes
2. Enter any search criteria.

3. Click Execute Query in the toolbar to retrieve the state history
records.
4. To view more information on a retrieved record, click More.

From the window that opens you can view detailed information
on the record including the template information from which the
instance record was derived.

DRAFT
Viewing the Audit Log of Instance Records

If an instance record has a transaction stored in the audit log, you can
view details about the transaction. You can view the audit log of all or
a single instance record.
To view the audit log of all instance records:

1. In the menu bar, select View > Audit Log to display the View
Instance Audit Log window.
2. Select the transaction in the upper part of window.

The details for the selected transaction are displayed in the lower
part of the window.
3. To view the audit log of a single instance record, select the
instance record in a SQL*LIMS software window, then choose
View Audit Log from the shortcut menu.

DRAFT
Viewing Electronic Signature History
Viewing Electronic Signature History

You can view signature history to see the entire electronic signature
history log.
To view the electronic signature history:

In the menu bar, select View > ESig History to display the View
Signature History window.
This window displays the master transaction record in the upper

block and the details for that transaction in the lower block.

DRAFT
Verifying Electronic Signatures in an Instance Tree

You can verify electronic signatures for a submission, sample, task,
result, SQL*Stability™ study, or SQL*QA lot object. You can access
this form using the Esig Verify application option.
From the selected object, an instance tree is built. If electronic
records are present, the validity of each electronic record is verified.
As an item is verified, a region at the bottom left of the screen records
the ID and version, indicates the Core and Full checksum
verifications for signature records, and indicates the presence (or
absence) of Esig History, State History, and Audit Log records.
For results, each result version is displayed with the result version
number. Result checksums are verified against the result version to
which the checksum applied, not against the current version.
You may click an item in the tree to synchronize the property sheet
and log to that item. If you double click an item in the log, then the
tree and property sheet synchronizes to that item.
There is no log of verification or instance tree building.

DRAFT
Verifying Electronic Signatures in an Instance Tree
To view the electronic signature history:

1. After selecting a submission, sample, task, result, SQL*Stability
study, or SQL*QA lot object in a view window, select Esig
Verify to display the ESignature Verify window.
Note: The hierarchy shows the object selected (such as a
sample) and items below it, but does not display higher objects
(such as a submission).
This window displays a tree on the left side and the details for a
node on the right side.
2. Select an object in the hierarchy or the log to display the object’s
property sheet.
The property sheet for an object displays the electronic signature
history or state history, if there are records.

DRAFT

DRAFT
Approving Records 5 5
This chapter describes how to manually approve or not approve
records.
Note: The display of result records for approval is affected by these
user preferences: Show Limits Page at Result Entry, Display Limits
Columns in Result Block, Out-of Specification Color, Out-of-
Detection Color, and Out-of-Limit Color. Refer to “Setting Your User
Preferences” on page 8-8. For an explanation of limits, refer to
“Result Limits” on page 3-6.
Bulk Approval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5
Approving a Submission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-9
Approving a Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-10
Approving a Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-12
Approving a Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-13
Approving a Worklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-15

DRAFT
Your applications manager can set up the SQL*LIMS® software so

that, after results are entered, the system automatically approves
them. Alternatively, after results are manually approved, submissions,
samples, and tasks are automatically approved; or a result can require
manual approval of submissions, samples, tasks, or results.
Manual approval changes the condition of a record to APPROVED,
NOT APPROVED or APPROVED LEVEL 1, NOT APPROVED
LEVEL 1, depending on whether one or two levels of approval is
enabled. The final approval state is APPROVED or NOT
APPROVED (auto-approval has only one level). If intermediate
approval is implemented, the first approval state is APPROVED
LEVEL 1 or NOT APPROVED LEVEL 1.
If only one level of approval is implemented, the following choices
are allowed, depending on the initial state:
Initial State Level of Approval
ONLINE APPROVED/NOT APPROVED
SUSPENDED APPROVED/NOT APPROVED
APPROVED/NOT APPROVED ONLINE

(edit condition forms only)
APPROVED/NOT APPROVED REJECTED

APPROVED/NOT APPROVED DONE

APPROVED NOT APPROVED
NOT APPROVED APPROVED

DRAFT
If two levels of approval are implemented, the following additional
choices are allowed, depending on the initial state:
Initial State Level of Approval
ONLINE (NOT) APPROVED LEVEL 1
SUSPENDED (NOT) APPROVED LEVEL 1
(NOT) APPROVED LEVEL 1 ONLINE

(NOT) APPROVED LEVEL 1 APPROVED
(NOT) APPROVED LEVEL 1 NOT APPROVED
(NOT) APPROVED LEVEL 1 REJECTED

edit condition forms only)
(NOT) APPROVED LEVEL 1 DONE

NOT APPROVED LEVEL 1 APPROVED LEVEL 1
APPROVED LEVEL 1 NOT APPROVED LEVEL 1
The APPROVE DATA role controls access to approval forms. If

manual two-level approval is implemented, the APPROVE LEVEL 1
(APPROVED LEVEL 1 and NOT APPROVED LEVEL 1) and
APPROVED LEVEL 2 (APPROVED and NOT APPROVED) roles
control access to that approval level.
Note: A user with both approval level roles is not permitted to
approve an object at both levels. An exception occurs with a worklist.
Worklists are treated as mechanisms for approving tasks and so
worklist history is not currently saved. Only the tasks are checked. A
user with both levels of approval cannot approve a worklist task at
both levels but can approve the worklist itself at both levels.
Approving the worklist approves the tasks for which the user is
allowed to change approval.
Note: To implement separate approval roles for results, tasks,
samples, and submissions, you must create new roles, such as
RESULTS_APPROVAL, TASKS_APPROVAL,
SAMPLES_APPROVAL, and SUBMISSIONS_APPROVAL. You
also have to modify the LIMS menu so that the roles appear. You can
notify the person who performs the next higher level of approval

DRAFT
when approval has been accomplished at the lower level. A user who
enters results cannot approve any level which contains the result
records, including APPROVED LEVEL 1 to APPROVED. The
system defaults for approval enforce this.
Manual approval can occur at five levels: submission, sample,
worklist, task, or result. An analyst might approve or not approve
each result for which they are responsible, a specific task, or a
worklist. A supervisor might approve or not approve the samples that
produced the results. A project manager might approve or not
approve the related submissions containing the samples.
Note: For automatic approval, when you change the approval status
of a result in the approval windows, the condition change might not
be propagated. For example, changing an erroneous result to within
specification limits and marking it COMPLETE/APPROVED might
leave the task, sample, and submission records in the instance
hierarchy at SUSPECT/NOT APPROVED. To ensure propagation of
a condition change, put the related instance records ONLINE when
you use the Change Result application option. See “Change Result”
on page 7-9.

Your jobtype may limit your access to any of the approval functions.
A query retrieves only records with a datagroup label matching one
of your own.
The status or condition of a record may prevent it from being
retrieved for approval. Status and condition may also limit how you
can edit a retrieved record.
Note: If a change is made to a result (Change Result application
option), the status of the task and sample might not change. Select the
check box to force the instance tree to be ONLINE if a result is
changed.

DRAFT
Bulk Approval

requirement, you will be required to enter the appropriate password
before committing changes to the database.
Exploring Retrieved Records

After records have been retrieved, you can explore them (the
availability of each depends on which window is active):
• Display more information from a record using the More button
• From the Results windows, display earlier versions of a result
record that has been changed (see “Displaying Earlier Result
Versions” on page 3-28)
Bulk Approval
Bulk approval lets you change the condition of many instance objects
(submissions, samples, tasks, or results) at one time. If the current
condition cannot be changed to the new condition for any record in
the object selected, the record’s condition will not be changed. The
reasons for not changing a record’s condition include:
• The record is in use by another user.
• The user does not have permission to change the record
condition.
• The user does not have the role to approve at this level.
You can also manually exclude an instance object from bulk approval.
If many objects were retrieved, there may be one or more that you do
not want to approve.

DRAFT
To change the condition of instance objects:

1. Query for the submissions, samples, tasks, or results whose
condition you want to change. For bulk approval, it is especially
important that your query criteria be as restrictive as possible.
(For this procedure, submissions are used as an example.)
Note: Even though an object (submission, sample, task, or
result) is selected (highlighted) in the top part of the window, the
bulk approval applies to all the objects that resulted from the
query unless you specifically exclude them.
2. In the Current Condition field, select the current condition that

you want to change.
3. In the New Condition field, select the condition to which you
want to change the submissions.

DRAFT
Bulk Approval
4. Click Bulk Approval to display the Bulk Approval window.
The Approve field of the records that are eligible for the new
condition is populated. Records whose Approve field is not
populated did not meet the criteria for approval, but you can
manually modify these records if you want.
5. (optional) To make modifications to specific objects in the list,
in the Approve column, double-click for object that you want to
approve, then select from the list of valid approvals.
6. Click Save to complete the bulk approval.
If you do not have approval authority to change a record, the
system will alert you. That record’s condition will not be
changed.
If auditing is enabled, you will be prompted for a reason for the
change.

DRAFT
To exclude an object from bulk approval:

1. Query for the submissions, samples, tasks, or results whose
condition you want to change. (For this procedure, submissions
are used as an example.)
2. Select the object that you want to exclude, then select Exclude
from Bulk Approval in the shortcut menu.
Objects that are excluded have the icon in the row.
You can toggle excluding and including objects using Include

and Exclude in the shortcut menu.

DRAFT
Approving a Submission
Approving a Submission
To approve a submission, you query on submission data to retrieve
the submission and the samples in it, then select APPROVED,
NOT APPROVED, APPROVED LEVEL 1, or NOT APPROVED
LEVEL 1.
To approve a submission:
1. In the menu bar, select Approve > by Submission to display the
Approve Submissions window.
You enter your query and view retrieved submission records in
this window.
2. Enter any search criteria on which you want to query.
The application retrieves the submission records that match your
query criteria and displays them in the upper part of the window.
The sample records related to the submission record (selected in
the upper part of the window) are displayed in the lower part of
the window.

DRAFT
One or more submissions may have been approved or not

approved previously.
4. In the Approve field, select APPROVED, NOT APPROVED,

APPROVED LEVEL 1, or NOT APPROVED LEVEL 1 for the
submission record.
5. If multiple submissions are retrieved, continue to select and
approve or not approve submission records.
To show the sample records for a different submission, select the
submission in the upper part of the window.
6. When you have finished approving submission records, click
Commit.
Approving a Sample
To approve a sample, you query on sample data to retrieve the sample
and the results for it, then select APPROVED, NOT APPROVED,
APPROVED LEVEL 1, or NOT APPROVED LEVEL 1.

DRAFT
Approving a Sample
To approve a sample:
1. In the menu bar, select Approve > by Sample to display the
Approve Samples window.
You enter your query and view retrieved sample records in this
window.
The result records related to the sample record (selected in the
upper part of the window) are displayed in the lower part of the
window.
One or more samples may have been approved or not approved
previously.

DRAFT

sample record.
5. If multiple samples are retrieved, continue to select and approve
or not approve sample records.
To show the result records for a different sample, select the
sample in the upper part of the window.
6. When you have finished approving sample records, click
Commit.
Approving a Task
To approve a task, you query on task data to retrieve the task and the
results produced by it, then select APPROVED, NOT APPROVED,
APPROVED LEVEL 1, or NOT APPROVED LEVEL 1.
To approve a task:
1. In the menu bar, select Approve > by Task to display the
Approve Tasks window.
Enter your query and view retrieved task records in this window.
The application retrieves the task records that match your query
criteria and displays them in the upper part of the window. The
result records related to the task record (selected in the upper
part of the window) are displayed in the lower part of the
window.

DRAFT
Approving a Result
One or more tasks may have been approved or not approved

previously.

task record.
5. If multiple tasks are retrieved, continue to select and approve or
not approve task records.
To show the result records for a different task, select the task in
the upper part of the window.
6. When you have finished approving task records, click Commit.
Approving a Result
To approve a result, you query on sample data to retrieve samples and the
results for each, then select APPROVED, NOT APPROVED,
APPROVED LEVEL 1, or NOT APPROVED LEVEL 1 for each result.

DRAFT
To approve a result:
1. In the menu bar, select Approve > by Result to display the
Approve Results window.
You enter your query and view retrieved sample records in this
window.
The result records related to the sample record (selected in the
window.
One or more results may have been approved or not approved
previously.

DRAFT
Approving a Worklist

result record.
5. If multiple results are retrieved, continue to select and approve
or not approve result records.
6. To show the result records for a different sample, select the
sample in the upper part of the window. Continue to select and
approve or not approve the corresponding result records.
7. When you have finished approving result records, click
Commit.
To approve a worklist, you query to retrieve worklists, then select
APPROVED, NOT APPROVED, APPROVED LEVEL 1, or
NOT APPROVED LEVEL 1 for the worklist.
When the tasks for the worklist are displayed, you can do any of the
following:
• Display more information from a task record by using the More
button
• Zoom to display all of the related instance records
• Display any attributes for a task and edit the updatable ones
To approve a worklist:
1. In the menu bar, select Approve > by Worklist to display the
Approve Worklists window.
2. You can retrieve a worklist assigned to another analyst or an
analyst in another workgroup.
If you do not want the default analyst assigned to the worklist
approval, you must select a different analyst or clear the analyst
field altogether.
To change the default analyst for the query, you must do so
before you enter any other search criteria.

DRAFT
In the Analyst field, select an analyst for the tasks in the worklist
or clear the analyst that is currently assigned to approve the tasks
in the worklist.
• Select Set Analyst application option.
Choose an analyst from the list of valid entries, then click OK.
OR
• Select Clear Analyst to retrieve records not assigned to
you or your workgroup.
3. Select the worklist that you want to approve from the list of valid
entries.
Enter your query and view retrieved worklists in this window.
The application retrieves the worklist records that match your
The task records (related to the worklist record selected in the
window.
One or more worklist records may have been approved or not
approved previously.

DRAFT

worklist record.
7. If multiple worklists are retrieved, continue to select and approve
or not approve worklist records.
To show the task records for a different worklist, select the
worklist in the upper part of the window.
8. When you have finished approving worklist records, click
Commit.

DRAFT

DRAFT
Editing 6 6
This chapter describes how to use the Edit menu to edit data.
Editing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2
Editing Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3
Editing Instance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-7
Editing a Worklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-12
Editing Attributes and/or Parameters Simultaneously . . . . . . . . .6-14
Assigning Sample Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-15
Assigning Sample Disposal Location . . . . . . . . . . . . . . . . . . . . . .6-17

DRAFT
Chapter 6 Editing
Editing Overview
You can perform these functions by using the Edit menu:
• Edit the condition of submissions, samples, and tasks
• Edit submission, sample, and task instance records
• Edit a worklist
• Edit/enter updatable attribute values or parameter responses
• Edit sample locations
You cannot edit result records from the Edit menu. You can, however,
change result values from the result entry and approval windows. See
Chapter 3, “Entering Results,” and “Approving a Result” on
page 5-13.

Your jobtype may limit your access to any of the editing functions.
A query retrieves only records with a datagroup label matching one
of your own.
The status and/or condition of a record may prevent it from being
retrieved for editing. Status and condition may also limit how you can
edit a retrieved record.

requirement, you are required to enter the appropriate password
before committing changes to the database.

DRAFT
Editing Condition
Editing Condition
Each instance record has a Condition field with a value that indicates
the progress of the record. Most condition changes occur without
direct user action on the condition value, but you can also edit the
condition manually.
You can edit the condition of submission, sample, and task records.
(You can only edit worklist condition when you modify the worklist
itself; you cannot edit the condition of a result.)
The most common reason for editing a condition manually is to
change it from APPROVED back to ONLINE so that you can add a
sample, add a method, or change a result. Other reasons include to
suspend or reject a record.
The procedure is the same for editing the condition of submissions,
samples, and tasks: you query to retrieve the record whose condition
you want to change, then you change it.
After the records have been retrieved, you can explore them in any of
these ways:

DRAFT
Chapter 6 Editing
Editing the Condition of a Submission

To edit the condition of a submission, you query for submission
records, select the new condition, then click Submit.
To edit the condition of a submission:

1. In the menu bar, select Edit > Condition > by Submission to
display the Edit Submission Condition window.
2. Enter any search criteria, then click Find to retrieve the
submission records that match your query criteria.
3. In the New Condition field, select the new condition.

4. If multiple submissions are retrieved, continue to select new
conditions as needed.
5. When you have finished editing the condition of submission
records, click Submit.

DRAFT
Editing Condition
Editing the Condition of a Sample

To edit the condition of a sample, you query for sample records,
select the new condition, then click Submit.
To edit the condition of a sample:

1. From the Edit menu, choose Edit > Condition > by Sample to
display the Edit Sample Condition window.
2. Enter any search criteria, then click Find to retrieve the sample
records that match your query criteria.
3. In the New Condition field, select the new condition.

4. If multiple samples are retrieved, continue to select new
conditions as needed.
5. When you have finished editing the condition of sample records,
click Submit.

DRAFT
Chapter 6 Editing
Editing the Condition of a Task

To edit the condition of a task, you query for task records, select the
new condition, then click Submit.
To edit the condition of a task:

1. In the menu bar, select Edit > Condition > by Task to display
the Edit Task Condition window.
2. Enter any search criteria, then click Find to retrieve the task
3. In the New Condition field, select the new condition for the task.
If multiple tasks are retrieved, continue to select new conditions
as needed.
4. When you have finished editing the condition of task records,
click Submit.

DRAFT
Editing Instance Data

You can edit certain data in submission, sample, and task records.
The procedure is the same for all three kinds of records: you query to
retrieve the record that you want to edit, then you make the change.
You can also edit worklist data. The procedure is similar to editing
submission, sample, and task records, and is described in “Editing a
Worklist” on page 6-12.
There are a number of ways that you can explore the retrieved
records:
• Display attributes and enter/edit the updatable ones
• View application options from the application options menus
You can use Edit > Edit to display text when a displayed field is not
the database.
Editing a Submission
To edit updatable fields of submission records, query to retrieve the
submission records, change the fields, then enter the reason for
change if prompted (field auditing is configured for the audit group).
To edit a submission:
1. In the menu bar, select Edit > Instance > by Submission to
display the Edit Submission window.

DRAFT
Chapter 6 Editing
2. Enter any search criteria, then click Find to retrieve the

submission records that match your query criteria.
3. Edit any updatable field.

Leaving the edited field may open the Audit Reason for Item
window. Select the reason for the change. You can enter
additional information about the change.
Click Editor to open the editing window, type the additional
information, then click OK. The editor window closes and your
comments are saved as a text attachment to the audit record.
4. Click OK to close the Audit Reason for Item window.
The old value, new value, and reason for change are recorded in
the instance audit log. You can view this information (and
additional comments, if you entered them using the text editor in
the previous step) using the Audit Log command from the View
menu. See “Viewing the Audit Log of Instance Records” on
page 4-36. You can also use the View Audit Log shortcut menu
command.
5. To update another field, repeat steps 3 through 5, then click
Commit in the toolbar.

DRAFT
Editing a Sample
To edit updatable fields of sample records, query to retrieve the
sample records, change the fields, then enter the reason for change if
prompted (field auditing is configured for the audit group).
To edit a sample:
1. In the menu bar, select Edit > Instance > by Sample to display
the Edit Sample window.
2. Enter any search criteria, then click Find to retrieve the sample
3. Edit any updatable field.

Leaving the edited field may open the Audit Reason for Item
window. Select the reason for the change. You can enter
additional information about the change.
comments are saved as a text attachment to the record.

DRAFT
Chapter 6 Editing

additional comments, if you entered them using the text editor in
the previous step) using the Audit Log command from the View
menu. See “Viewing the Audit Log of Instance Records” on
page 4-36. You can also use the View Audit Log shortcut menu
command.
Commit.
Editing a Task
To edit updatable fields of task records, you query to retrieve the task
records, change the fields, then enter the reason for change if
prompted (field auditing is configured for the audit group).
You can also add task replicates and versions when the Edit Task
window is open, whether or not you edit the data in the task record.
You can do this by clicking Application Options in the toolbar and
choosing the Add Replicates or Add Versions application option. See
“Add Replicates” on page 7-5 and “Add Version” on page 7-7.
To edit a task:
1. In the menu bar, select Edit > Instance > by Task to display the
Edit Task window.

DRAFT
2. Enter any search criteria, then click Find to retrieve the task
3. Edit any updatable field. Leaving the edited field may open the
Audit Reason for Item window. Select the reason for the change.
You can enter additional information about the change.
additional information, if you entered it in the previous step
using the text editor) using the Audit Log command from the
View menu. See “Viewing the Audit Log of Instance Records”
on page 4-36. You can also use the View Audit Log shortcut
menu command.
Commit.

DRAFT
Chapter 6 Editing
Editing a Worklist
You can modify information about an existing worklist and its
associated tasks. When editing the worklist, you can:
• Dissolve a worklist.
• Change the condition of a worklist.
• Display worklist attributes and enter/edit the updatable ones.
• Remove tasks from worklist.
• Display task attributes and enter/edit the updatable ones.
You can use Edit > Edit to display text when a display field is not
the database.
To edit a worklist, enter search criteria, then query to retrieve the
worklist record and its related task records.
For tasks, you can:
• Display attributes for any task and enter or edit the updatable
ones.
To edit a worklist and its tasks:

1. In the menu bar, select Edit > Instance > Worklist to display
the Edit Worklist window.
2. Enter a query to display a worklist’s information.
Change the default analyst for the query before you enter any
other search criteria, using this procedure:
a. Select Set Analyst application option to select a different
analyst or Clear Analyst to not specify an analyst.
b. If you selected Set Analyst, choose an analyst from the list
of valid entries.
c. Click OK.
Click More to enter additional search criteria.

DRAFT
Editing a Worklist
3. Click Find to retrieve the task records that match your query
criteria.
The first retrieved worklist is displayed in the upper part of the

window. Task records related to the worklist are shown in the
lower part of the window.
To select a worklist among multiple worklists, use the up and
down arrow keys to move through the worklists.
4. (optional) Edit the worklist name, description, instrument name,
instrument class, or due date.
5. (optional) To edit the worklist condition, use the Worklist
Condition application option.
6. (optional) To dissolve a worklist that does not have a condition
of APPROVED or NOT APPROVED, choose Record > Delete.
7. (optional) To reassign tasks, choose Reassign Tasks.
8. (optional) To remove one or more tasks from the worklist or
reorder tasks, use the Resequence Worklist application option.
9. Click Commit in the toolbar.
10. Exit the Edit Worklist window.

DRAFT
Chapter 6 Editing
Editing Attributes and/or Parameters

Simultaneously
Attributes and parameters provide custom information about
submissions, samples, tasks, and worklists. You can edit the attributes
and/or parameters for multiple samples simultaneously.
If there is insufficient space for all the text of a field to display, use
the Edit command in the Edit menu to show all the text.
To edit the attributes and/or parameters of multiple samples at

one time:
The procedure is to query for sample records, enter or edit the
response, then enter the reason for change if prompted (field auditing
is configured for the audit group).
1. In the menu bar, select Edit > Attributes > by Name to display
the Edit Attributes By Name window.
2. If you are editing attributes; click Execute Query.
OR
If you are editing parameters; click the Parameters tab, then
click Execute Query.
The query only retrieves sample records that have attributes or

parameters.

DRAFT
Assigning Sample Location
3. If you are editing attributes: In the Text Value field of the

Attributes tab, enter a new value or edit the existing one for each
sample as needed.
OR
If you are editing parameters: In the Response field of the
Parameters tab, enter a new (or edit the old) response for each
sample as needed.
4. Click Commit.
additional comments, if you entered them in the previous step
using the text editor) using the Audit Log command from the
View menu. See “Viewing the Audit Log of Instance Records”
on page 4-36. You can also use the View Audit Log shortcut
menu command.
Assigning Sample Location

You can assign a new placement or disposal location to a sample, or
you can change an existing placement. Sample location can only be
assigned during sample receipt. See “Receiving Samples” on
page 2-11.
The procedure for assigning the location of a sample is to query for
sample records, select the sample, then assign the location.
To assign a sample location:

1. In the menu bar, select Edit > Sample Location > Place to
display the Place Samples window.

DRAFT
Chapter 6 Editing
2. Enter any query criteria, then click Execute Query.
3. Select the sample.

You can move through the samples using the up and down arrow
keys, or choosing Query > Fetch Next Set in the menu bar.
4. Double-click in the Location Name field to open the List of
Locations window.
5. Select a location, then click OK.
6. Add sample location attachments. Click the location tree, then
choose the Edit Attachments icon to annotate the sample
placement (rather than the sample itself).
7. If you edited the location, click Commit.

DRAFT
Assigning Sample Disposal Location
Assigning Sample Disposal Location

The procedure for assigning the disposal location for a sample is to
query for sample records, select the sample, then choose the disposal
location. After a sample is assigned to a disposal location, its location
can no longer be changed from a location assignment window.
To edit sample disposal sites:

1. In the menu bar, select Edit > Sample Location > Dispose to
display the Dispose Samples window.
2. Enter any query criteria, then click Execute Query.
3. Select the sample you need.

You can move through the samples using the up and down arrow
keys, or choosing Query > Fetch Next Set in the menu bar.
4. Double-click in the Dispose Location field to open the List of
Locations window.

DRAFT
Chapter 6 Editing
5. Select the dispose location, then click OK.

If work on the sample is not finished, the following message is
displayed:
Select Dispose to proceed, or Cancel to quit the procedure.

Note: After a sample has been disposed, it cannot be relocated
to another location. A sample that has been disposed of is
indicated by a D in the Sample Location History window. It is
not available in other queries.
6. Click Commit to save any changes.

DRAFT
Application Options 7 7
This chapter lists all the application options available in windows
opened from the main menu. These options are described in
alphabetical order.
For other application options, see the appropriate SQL*LIMS®
software manual. For example, for Template function application
options, see the SQL*LIMS Template Design User Guide.
Choosing an Application Option. . . . . . . . . . . . . . . . . . . . . . . . . . .7-3
Add Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3
Add QC Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-4
Add Replicates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-5
Add Sample Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-6
Add Unknowns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-7
Add Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-7
Assign New Analyst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-8
Browse Limit Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-9
Change Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-9
Clear Analyst. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-10
Copy Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-11
Create Child Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-12
Create TPL File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-14
Define Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-14
Define Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-15
Define Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-16
Define Sample Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-17
Define Studies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-19
Edit Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-20
ESig Verify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-21
Instrument / Part Check Calibration . . . . . . . . . . . . . . . . . . . . . . .7-22
Instrument / Part Qualification . . . . . . . . . . . . . . . . . . . . . . . . . . .7-22

DRAFT
Location History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22

Log Request Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
Make Status Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
Override Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
Recalculate Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
Resequence Worklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
Sample Pooling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Sample Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
Sample Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
Send Status Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
Set Analyst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
Set Log Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
Set To Requested . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30
Show Status Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30
Status Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31
Submission Samples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33
Suspend/Unsuspend Instrument or Part . . . . . . . . . . . . . . . . . . . . 7-33
Task Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
View All Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
View CMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35
View Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
View Signature Event History . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37
View History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
View Result Specs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
Worklist Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40

DRAFT
Choosing an Application Option
Choosing an Application Option

Application options allow you to open a related window without
closing the active window and increase the functionality of the
window in which you are working.
You can view the application options currently available by clicking
the Application Options button in the toolbar. To choose an
application option, select it, then click OK.
The list of application options varies, depending on the function of
the window area in which the cursor is positioned. The items in the
Application Options window may also have been customized by your
applications manager. You only see those application options that
have been assigned to one of the roles in your jobtype.
The availability of application options is determined by the roles
assigned to the jobtype.
Add Attributes
This application option lets you add attributes and parameters to
instance records from many windows, including results entry,
viewing, approval, and editing. For results, only attributes can be
added.
To add an attribute or parameter, you must enter both a sequence
number and a name. The data type and text value fields are optional.
Responses cannot be required, so the Req check box is disabled.
To add attributes to instance records;

1. In an instance window, choose the Add Attributes application
option to open the Add Attributes/Parameters window.
The name of this window varies, depending on the instance from
which it is opened.

DRAFT
Here, the Add Task Attributes/Parameters window is shown as

an example.
2. Select A (add attributes) or P (add parameters).

3. Enter a sequence number in the first Sequence field. (You must
enter at least this first prompt before you can enter additional
sequence numbers.) This number determines the sequence of the
attribute or parameter in the instance window.
4. Choose one or more names from the list of valid entries. The
data type name is provided automatically for any name that has a
default data type. Data type specifies the kind of response (text
value) that is required.
5. To change the data type, choose from the list of valid entries.
6. You may enter a text value or enter it later.
7. To make an attribute or parameter hidden (Hid) and/or updatable
(Upd), select the corresponding check boxes. A hidden attribute
name is not displayed. An updatable attribute can be edited.
8. Click OK, then click Commit.
Add QC Type
If QC types are defined in the method or operation, you can use this
application option to add them to the tasks on the worklist while you
are creating the worklist.
To add a QC type to a worklist:

1. Position the cursor in the worklist where you want to add the QC
Type.
2. Choose Add QC Type to display the list of valid entries for QC
types.
3. Choose the QC type that you want to add.

DRAFT
Add Replicates
Add Replicates
This option lets you create replicates for a task when you edit it. You
can create replicates only for tasks with an ONLINE condition. The
number of replicates that you can create is controlled by your
applications manager.
When you create task replicates, the application creates that number
of copies of each result record that is currently associated with the
task. These new result records are identical to the existing result
records, except that they have unique IDs and replicate numbers and
contain no result values. Creating a task replicate does not affect
previous result records that are related to the task.
To add task replicates:

1. In the Edit Task window (Edit > Instance > by Task), query the
task that you want to replicate, then select it.
2. Choose Add Replicates to display information about the current
task in the Add Replicates window.
3. In the Number of New Replicates field, enter the number of

replicates that you want to create.
4. Click Add Replicates.
The total number of task replicates is displayed in the Current
Task Replicates field.

DRAFT
Add Sample Attributes

This application option lets you create attributes or parameters for
samples when you log them in the Log Materials, Log Sample Plan,
Add Sample Plan, and Add Materials windows. Creating the
attributes and/or parameters adds them to samples acquired from the
material. To create an attribute or parameter, you must enter both a
sequence value and a name. The data type and text value fields are
optional.
To add attributes to samples:

1. After you create the samples in a sample logging window,
choose Add Sample Attributes to open the Add Sample
Attributes window.
2. Select A (add attributes) or P (add parameters).

3. Enter a sequence number in the first Sequence field. (You must
enter at least this first prompt before you can enter additional
sequence numbers.)This number determines the sequence of the
attribute or parameter in the Log Materials window.
4. Choose one or more names from the list of valid entries. The
data type name is provided automatically for any name that has a
default data type. Data type specifies the kind of response that is
required.
5. To change the data type, choose from the list of valid entries.
6. You may enter a text value or enter it later.
7. To make an attribute required (Req), hidden (Hid), and/or
updatable (Upd), select the related check boxes. A hidden
attribute name is not displayed. An updatable attribute can be
edited. Some objects have required attributes.
8. Click OK, then click Commit.

DRAFT
Add Unknowns
Add Unknowns
This application option lets you add unknowns (when they are
available) to the tasks on a worklist when you create it.
To add unknowns to a worklist:

1. Position the cursor in the worklist where you want the unknown
to be inserted.
2. Choose Add Unknowns to display the Add Unknowns dialog
box.
3. Type the number of unknowns to add, then click OK.
Add Version
This application option lets you replace all results for the specified
ONLINE task with a new set of result records. This option is useful
when testing data have been invalidated, perhaps by abnormal
laboratory conditions.
When you create a new task version, the existing result records
assigned the condition REJECTED. These records no longer appear
on result entry and approval forms. The new result records match the
previous result records in every respect except that the Result fields
are blank, and the Result ID and task version number are new.

DRAFT
To create new task and result versions:

1. In the Edit Task window, query for the task for which you want
to create a new version and select it.
2. Choose Add Version to display information about the current
task in the Add Version window.
3. Click Add Version to create the new task version. The new task
version number is displayed in the Current Task Version field.
Assign New Analyst

This application option changes the analyst or workgroup to whom a
worklist is assigned. When you edit a worklist you can use a
workgroup instead of a user ID.
You can directly edit other fields in the Edit Worklist window, but
you must use the Assign New Analyst application option to edit the
entry for Analyst.
To assign a different analyst to a worklist:

1. In the Edit Worklist window, query for the worklist for which
you want to change the analyst.
2. Choose Assign New Analyst, then select the new analyst's name
from the list of valid entries.
3. Click OK, then click Commit to save the new analyst.
If auditing is enabled, your change may be audited.

DRAFT
Browse Limit Text
Browse Limit Text

This application option allows you to browse attachments associated
with component measure units in a specification.
To display limit text:

1. Select the result record for which you want to view the limit text.
2. Choose Browse Limit Text to display the text in the Browse
Text window.
Change Result
This application option lets you change result values that have been
entered in the database. This option is available from the result entry
windows and from the approval windows for samples, tasks, and
results.
When you change a result, your entries are subject to the same limits
checking as the original results.
In approval windows, you can change results for APPROVED and
NOT APPROVED (or APPROVED LEVEL 1 and NOT
APPROVED LEVEL 1, if two-level approval is implemented)
records. You can also change a result and place approved or not
approved records ONLINE for re-evaluation. (For more information
about manual approval, see page 5-2.)
In result entry windows, you can only change results for ONLINE
records.
Note: When you change the approval status of a result in the
approval windows, the condition change is not propagated. For
example, if the Auto-Approval Rule is ON when you change an
erroneous result to within specification limits, the result becomes
COMPLETE/APPROVED, but the task, sample, and submission
records in the instance hierarchy remain SUSPECT/NOT
APPROVED. To ensure propagation of a condition change, put the
related instance records ONLINE when you use the Change Result
application option.

DRAFT
To change a result value:

1. Select the result record that you want to change, then choose
Change Result to display either the Change Result or the
Change Approved Result dialog box.
2. Type the new result value, choose the reason for change (if
required), then click OK. The new result value is displayed in
the Result field.
The Result Version field in the result properties window is
incremented to indicate the result change. (This is the window
that opens when the result is selected and you click More.)
The audit log records the result's old value, new value, and the
reason for change.
3. In the Changed Approved Result window, to direct the
SQL*LIMS software to re-evaluate a previously approved or not
approved result, select the Put Instance Tree ONLINE check
box.
The entire instance tree is placed back ONLINE for re-
evaluation by the status monitoring program.
Clear Analyst
This application option removes the text from the Analyst field, for a
query, allowing you to retrieve records not assigned to you or your
workgroup.
Note: If you are changing the default analyst or clearing the analyst
for the query, do so before you enter any other search criteria.

DRAFT
Copy Sample
To remove the analyst entry for a query:

1. Choose Clear Analyst. The Analyst field is cleared in the Find
tab.
2. Query for the desired record.
3. Click OK.
Copy Sample
This application option lets you copy the information from a sample
that you are logging and use it to create multiple samples of the same
type at once. You can edit the duplicate records to change any data
that are unique to a record.
You must have entered the required data for the sample before you
can use the Copy Sample application option. Copy Sample copies
everything that has been entered, including attributes, attribute
values, methods, sample location, user sample ID, and status actions.
To create multiple samples of the same type:

1. After entering the sample data and before clicking Execute,
choose Copy Sample to display the Copy From Sample dialog
box.
2. Enter the total number of samples (copies plus original) to log,

then click OK to make the copies and commit the data.
The Count value in the status line indicates the total number of
records created.
3. To edit data in any of these records, display each one using the
up and down arrow keys, then make changes.

DRAFT
Create Child Sample

This application option lets you create child samples for an existing
sample. This option is available from most windows that display
sample records.
Note: The Log By field defaults to the sample plan or material that
was used to create the parent sample. You can change the name.
To create child samples:
1. In the window displaying the “parent” sample, choose Create
Child Sample option to open the Create Child Samples window.
2. In the # of Child Samples field, enter the number of child

samples that you want to create.
Entering the user sample ID is not required. If you enter it, all
child samples will have this user sample ID.
3. Select a sample plan or material for the child samples from the
list of valid entries.
If you select a sample plan, any methods defined on the sample
plan are retrieved and displayed. You can define additional
methods to log, or override non-required methods retrieved from
the sample plan (using the window described in the next step).
If you select a sample plan with a method group, the method group
is not logged (only the additional specified methods are logged).
If you select a material, you can define methods (using the
window described in the next step).

DRAFT
Create Child Sample
4. Click Next to display the Properties for Sample window.
5. You can optionally enter or edit the data in these fields,

including any methods you want to add to a sample plan or
define for materials.
6. Click Finish to copy the information to the specified number of
samples to be logged.
Note: Changes that you have made are copied to all child
samples you have created.
The Log Child Samples window opens, displaying the child
samples.

DRAFT
7. Edit any data for the child samples.

For example, you could use the Add Sample Attributes
application option to add attributes.
8. Click OK to log the child samples.
Create TPL File

The Create TPL File application option creates a TPL file. The
option is only available if you have the SQL*LIMS Template
Procedural Language optional product.
Although this application option is available in the Define Locations
window when you are viewing locations, creating a TPL file is a
function performed by your SQL*LIMS applications manager and is
documented in the SQL*LIMS Template Design User Guide.
Define Materials
While you are logging samples in the Log Samples or Log Materials
window, you can use this application option to open the Define
Materials window to create new materials or modify existing ones.
To define materials for logging:

1. Choose Define Materials to open the Define Materials window.

DRAFT
Define Methods
2. Select the material name, material type, and datagroup from the
lists of valid entries and assign a location to the material, as
required.
3. Click Commit to enter the material into the database, then close
the window.
You must approve the material before the application adds it to
the list of valid entries. If auditing is turned on for the template
object “Materials” you will be prompted for a reason for
defining the material. For information, refer to the SQL*LIMS
Template Design User Guide.
Define Methods
This application option lets you define or modify methods while you
are in the Name field of many of the logging windows if the methods
that you need do not exist.
To define method while logging a sample:

1. Choose Define Methods to open the Define Methods window.
2. Enter the method name and method datagroup name.

DRAFT
3. Select from the available methods and/or operations to add to the

method plan.
4. Click Commit to enter the method into the database, then close
the window.
You must approve the method before the application adds it to
object “Methods” you will be prompted for a reason for defining
the method. For information, refer to the SQL*LIMS Template
Design User Guide.
Define Operations
This application option lets you define or modify operations in
several windows, including the Log Samples and the Define Methods
windows, if the operations that you need do not exist.
To define operations while logging a sample:

1. Choose Define Operations to open the Define Operations
window.
2. Enter the operation name and datagroup.

DRAFT
Define Sample Plans
3. (Optional) Select an instrument and result plan from the list of

valid entries, as required.
• Enter the analyst, cost, and scheduling information, as
appropriate.
• In the Components list, enter the individual results for the
operation.
• Click Properties to display the Properties of Component
window. Select a rounding protocol, enter significant
figures, select a result format, select a result format with
rounding, and define a calculation for the result, then click
OK. For more information on defining component results,
see “Defining Result Formats and Significant Figures” and
“Defining Calculations and Calculation Functions,” in the
“Defining Operations” section of Chapter 4 “Setting Up the
Analysis Template” of the SQL*LIMS Template Design
User Guide.
4. Click Commit to enter the operation into the database, then
close the window.
You must approve the operation before the application adds it to
object “Operations” you will be prompted for a reason for
defining the operation. For more information, refer to the
SQL*LIMS Template Design User Guide.
Define Sample Plans

You can use this application option to open the Define Sample Plans
window from several places, including the Log Samples window. You
can then define new or modify existing sample plans if the ones that
you need do not exist.

DRAFT
To define a sample plan while logging a sample:

1. Choose Define Sample Plans to open the Define Sample Plans
window.
2. Enter the sample plan name.

3. Select from the available material names and material types.
4. In the Method Group Class field, specify whether you want to
attach one or more methods, a method group, or no methods.
5. For each method you want to attach, enter a sequence number
and method name, and specify whether it is required.
If a method is specified as Required in the sample plan, it will
automatically be applied to samples during logging.
6. Click Commit to enter the sample plan into the database, then
close the window.
You must approve the sample plan before the application adds it
to the list of valid entries. If auditing is turned on for the
template object “Sample Plans” you will be prompted for a
reason for defining the sample plan. For information, refer to the

DRAFT
Define Studies
Define Studies
You can use this application option in many of the logging windows,
to define a study “on the fly.” You can also modify studies if the ones
that you need do not exist.
To define studies while logging a sample:

1. Choose Define Studies to open the Define Studies window.
2. For each study that you want to define, enter a study name.
3. Select a study datagroup and a ruleset name from the list of valid
entries, as required.
4. Click Commit to enter the study into the database, then close
the window.
You must approve the study before the application adds it to the
list of valid entries. If auditing is turned on for the template
object “Studies” you will be prompted for a reason for defining
the study. For information, refer to the SQL*LIMS Template
Design User Guide.

DRAFT
Edit Attributes
This application option provides one window for responding to the
attributes and/or parameters for all the samples you have entered
since the last time you clicked Execute from a logging window. This
option is helpful when you have used the Copy Sample application
option to create multiple samples. This application option can also be
used to respond to the sample attributes for all the QC types on a
worklist.
To respond to sample attributes for multiple samples:

1. After saving the sample or worklist, choose Edit Attributes to
display the Sample Attributes window.
2. Respond to the attributes and parameters, then click OK to save

your responses.

DRAFT
ESig Verify
ESig Verify
This application option displays the electronic signature record for a
submission, sample, task, or result.
To check the electronic signature records of an object and objects

below it in the instance hierarchy:
Select a submission, sample, or task, record, then choose Esig Verify
to display the Verify window.

DRAFT
Instrument / Part Check Calibration

This application option forces the check calibration event to run. This
event is routinely run at midnight; however, you can check the
instrument calibration at any time by running this application option.
Instrument / Part Qualification

This application option inserts an entry called QUALIFICATION
into the Operation column of the history record of the instrument or
part, indicating that the instrument or part has been qualified.
Location History
This application option allows you to track the history of storage and
disposal locations of a sample. This application option is available
when you are editing the sample location in the Place Samples or
Dispose Samples window.
The Sample Location History window opens on top of the Place
Sample or Dispose Sample window, allowing you to query for
samples and their location history.
To view the history of locations for a sample:

1. After querying for locations in the Place Sample or Dispose
Sample window, place the cursor in the Sample Plan field.
2. Choose Location History to open the Sample Location History
window.
3. Query for the sample to display its location history.

DRAFT
Log Request Attributes
Log Request Attributes

This application option allows you to associate reserved keyword
attributes with the sample or submission being logged and its related
instance records. A reserved keyword attribute is one for which the
prompt has already been defined and the response is displayed as part
of the instance record.
To create log request attributes:

1. When you are logging a sample or submission, choose Log
Request Attr (Attributes) to open the Log Request Attributes
window.
2. Choose the attribute names and text values from the list of valid
entries.
You must enter a text value for one name before you can enter
the next name.
3. Click OK to save the attributes.

DRAFT
Make Status Request

This option creates a status request for results that have the status
ENTERED, without waiting for you to exit from the window.
When you enter results, they are processed with no further interaction
from you. However, if something such as a computer failure
interrupts this processing, results can be left in an ENTERED state.
You can use the Make Status Request application option to ensure
that any results that might have been left unresolved in the
ENTERED state are placed back in the normal processing queue.
To make a status request:

1. In the Results window, choose Make Status Request.
The request is created for all the results produced by a task, so
that you only have to choose this application option once for
each task represented by the results.
2. If you want the request to be processed before you close the
window, choose the Send Status Request application option.
The Send Status Request application option also displays the
updated status of the results.
Override Limit
When you enter a result that is outside measure limits, you must
either change it to be within limits or use the Override Limit
application option so that it will be accepted into the database. (Your
applications manager determines whether or not you can override a
measure limit.)
When you enter a result that is outside measure limits, OUT is
displayed in the Limit field, and you cannot perform any action until
you resolve the situation by either changing the value or overriding
the limit.
To override a measure limit:

In the Results window, choose Override Limit.
OVR is displayed in the Limit field to show that you have manually
overridden the limit. The result status becomes and permanently stays
SUSPECT.

DRAFT
Recalculate Result
Recalculate Result
When you change an element used in a result calculation, the new
value is calculated and displayed in the Result window. If a situation
interrupts this process, for example, a computer failure, you must use
this application option to recalculate the result.
To recalculate a result:
Select the result to be recalculated, then choose Recalculate Result.
The result is recalculated and displayed.
Resequence Worklist
You can renumber the tasks in a worklist according to their current
order on the list with the Resequence Worklist application option.
Use this application option after you have manipulated a worklist by
adding and removing tasks, or by changing the sequence numbers.
To renumber the tasks in a worklist:

In a window displaying worklists, select a task, then choose
Resequence Worklist.
The tasks are renumbered sequentially starting at 1. Blank lines are
removed.
Rules
This application option displays the rules associated with a
submission. This option is useful when you want to see what is
governing the behavior of the SQL*LIMS software with respect to a
submission that you are viewing.

DRAFT
To display the rules related to a submission:

1. In the View Submissions window or other submission regions,
query for the submission, then select it.
2. Choose Rules to open the Define Rulesets window.
3. Click the tab of interest to view its contents.
Sample Pooling
This application option lets you create a new sample with associated
samples while you are logging samples by material or logging
samples by a sample plan.
To associate (pool) samples:

1. In the Log Materials window or the Log Samples window, enter
data as appropriate.

DRAFT
Sample Pooling
2. Select Sample Pooling application option to display the Sample

Pooling window.
In the Sample Pooling window, the Sample Pooling tab is in the
forefront. It shows the sample that was created in the Log
Materials or Log Sample window.
3. To find more samples for the pool, click the Find tab, enter the
search criteria, as appropriate, then click Find. The existing
samples that meet the search are displayed in the left part of the
window.
4. To add samples to the pool or remove them:
• All the samples – Click Add All ( ).
• Some of the samples – Select the sample in the list. To
select more than one, Ctrl + click the sample, then click
Add ( ).
• To move samples out of the pool, click Remove ( )
or Remove All ( ).
5. Click Accept Changes to add the samples to the pool. (This is
like a Commit.)

DRAFT
Sample Results
This application option opens the View Sample Results window for
the sample that you are viewing, as if you had entered the ID of the
selected sample to query for results by sample.
This is a convenient way to see the results for a sample that you are
viewing; you do not have to close one window to open another. The
first window stays open, and the results for the sample are displayed
over it.
To display results for a sample that you are viewing:

Select the sample record, then choose Sample Results.
Sample Tasks
This application option opens the View Sample Tasks window for the
sample that you are viewing, as if you had entered the ID of the
selected sample to query for tasks by sample.
This is a convenient way to see the tasks for a sample that you are
first window stays open, and the tasks for the sample are displayed
over it.
To display tasks for a sample that you are viewing:

Select the sample record, then choose Sample Tasks.
Send Status Request

When you enter results, they are processed with no further interaction
from you when you exit from the window. If you will be entering
results over a long period of time, you can use this application option
to start processing without having to exit from the window. This
option is similar to using the Execute command to expedite log
requests.
To send a status request:

With the cursor in the Results field, choose Send Status Request.

DRAFT
Set Analyst
Set Analyst
This application option enters or changes an entry in the Analyst
field, for a query, allowing you to retrieve records that are assigned to
a specific individual or workgroup. (A workgroup can be used
instead of a user ID.)
Note: If you are changing the default analyst or clearing the analyst
for the query, do so before you enter any other search criteria.
To enter or change the analyst entry for a query:

1. Select Set Analyst.
2. Query for the desired record.
3. Choose an analyst or workgroup from the list of valid entries.
4. Click OK.
Set Log Priority

This application option lets you change the default log priority for a
sample that you are logging. When several log requests are created at
the same time, the log priority determines the order in which the
logger handles the requests.
To change the default log priority for a sample:

1. While you are logging a sample, choose Set Log Priority to
open the Change Log Priority dialog box.
2. Change the value for priority, then choose OK.

DRAFT
Set To Requested
If something such as a computer failure interrupts the logging
process, you can use this application option from the View Log
Requests window to complete an unfinished logging operation.
The Set to Requested application option changes the status of a log
request from PRELOG to REQUESTED. It also activates the logger
so that these log requests are processed as soon as possible.
To restart the processing of an interrupted log request:

1. In the View Log Requests window, select the log request with
the PRELOG status that you want to change.
2. Choose Set To Requested.
There is no visual indication of the change in status. However, if
you click Execute Query in the toolbar, the log request with the
status that you changed redisplays with a REQUESTED status.
Show Status Actions

You can use this application option to list the status actions attached
to a record.
To list of the status actions attached to a record:

1. Display the record for which you want to see the status actions.

DRAFT
Status Actions
2. Choose Show Status Actions to open the Summary of Status

Actions window.
Status Actions
This application option lets you set up a status or condition value as a
trigger for an action. The action is initiated when the sample or
submission to which it is attached achieves the status or condition
you choose.
You can view a summary of the status actions attached to a record by
using the Show Status Actions application option.

DRAFT
To enter a status action for a sample or submission:

1. From the sample or submission that you are logging, choose
Status Actions to display the Status Actions window.
Field Action
Condition/Status Enter the condition or status that you want as the

trigger for the action from the list of valid entries.
User and Jobtype Choose the user name/jobtype combination of

the person who will carry out the action from the
list of valid entries.
Action Choose the type of status action that you want to

occur from the list of valid entries.
Object Name Enter the object of the action.

The list of valid entries for Object Name is context
sensitive. For example, a list of users is presented
when the action is NOTIFY, and the names of
Oracle Report events are given when the action is
Oracle Reports.

DRAFT
Submission Samples
2. To repeat this status action each time the submission or sample

reaches the specified condition or status, select the Refire check
box.
3. To view a list of the status actions attached to this sample, click
Summary.
4. To enter any additional status actions for this record, click
Commit, then press the down arrow key to open a new record
(clear the window).
Submission Samples
The Submission Samples option opens the View Submission Samples
windows for the submission that you are viewing, as if you had
queried for the samples by entering the ID of the selected submission
or log request.
This is a convenient way to see the samples that are in the submission
or log request that you are viewing; you do not have to close one
window to open another. The first window stays open, and the
submission and samples are displayed over it.
To display submission samples:

Select the submission, then choose Submission Samples.
Suspend/Unsuspend Instrument or Part

This application option allows you to take an instrument or a part
offline (suspend) or put it online (unsuspend). This option is available
from within the instrument calibration utility.
To take an instrument or part offline or put it online:

1. In the menu bar of the main menu, select Utilities >
Calibration > Instruments to display the Instruments / Parts
window.
2. Select the instrument that you want to suspend or unsuspend.
3. Select Suspend/Unsuspend. If the instrument is being audited,
you will be prompted to enter or select a reason for suspending
or unsuspending the instrument.

DRAFT
Task Results
This application options opens the View Task Results window for the
task that you are viewing, as if you had entered the ID of the selected
task to query for results by task.
This is a convenient way to see the results for a task that you are
first window stays open, and the results for the task are displayed
over it.
To display results for a task that you are viewing:

From a task that you are viewing, choose the Task Results application
option.
View All Versions

This application option enables you to view all versions of a
templates. The template that is currently in use has a status of
CURRENT. All previous versions have a status of MODIFIED. The
Ver (Version) column indicates how many times the object has been
modified.
To see the versions of a template object:

1. In a template definition window, such as Define Materials,
select the record that you want to view.
2. Choose View All Versions to open a window that shows all
versions of the template. For more information, refer to the

DRAFT
View CMU
View CMU
This application option lets you see if the CMU (component measure
unit) is used in any specifications or detection limits. This option is
accessible from the detail block of the Define Operations form and
the detail block of the Define Result Plans form.
There is a column called “Limit Type” that displays whether or not
the CMU combination is a specification or a detection limit. If the
CMU combination is part of both specifications and detection limits,
it displays both of them with the column “Limit Type” having the
value “Specification / Detection.” The specification values are
displayed before detection limit values.

DRAFT
View Errors
If an error occurs during logging, the log request status becomes
ERROR(num), and the error number is displayed next to the status.
The View Errors application option displays descriptions of logging
errors.
ERROR_NUM ERROR_TEXT
101 INSTALLATION - RAN OUT OF VM SPACE

203 MISSING - LOG_PLAN
204 MISSING - MATERIAL
205 MISSING - MEASURE_UNIT
206 MISSING - METHOD
207 MISSING - OPERATION
208 Invalid Method Hierarchy
209 MISSING - RESULT_PLAN_LIST
211 MISSING - METHOD PLAN
212 MISSING - SAMPLE_PLAN
213 MISSING - STUDY
214 MISSING - RULE SET
215 MISSING - LOCATION
401 REQUEST TO MONITOR - INVALID ENTRY_POINT
402 INVALID DATAGROUP ASSIGNMENT REQUEST

DRAFT
View Signature Event History
To display descriptions of logging error codes:

In the View Log requests window, select a log request with an
ERROR status, then choose View Errors to display the Error Codes
window.
View Signature Event History

The View Signature Event History application option displays
signature records for the selected instance record. This option is
available from all submission, sample, task, and result blocks as well
as template objects.
The View Signature Event History window verifies the checksum of
the signature against the data. If the record is identical to the time of
the original signature, then both checksums are verified. If the record
has changed, then the full data key will not verify, the core data key
may or may not verify. If the checksum validates, a green check mark
appears to the right of the checksum field. If the checksum does not
validate, a red X appears. The Show Details function displays when,
how, and who made the change.

DRAFT
To view signature event history:

1. Select View E-Sig History application option to display the
View Signature Event History window.
2. You can also display the details.
3. Click Verify to verify the checksum against the data.

DRAFT
View History
View History
This application option displays the status and condition changes that
an instance record has undergone over time and is available when you
are viewing a record. It is similar to the View/State History window.
To display status and condition changes for a record:

• From the instance record, choose View History to open the
View Instance History window.
For each transition, you can see the user who caused the change,
the date of the change, and the initial and final states.
View Result Specs

This application option lets you review all of the secondary
specifications that apply to a particular result.
To view the secondary specifications for a result:

1. In any window with result records, select the result to review.

DRAFT
2. Choose View Result Specs to open the Result Specifications

window with the specifications displayed.
Worklist Condition
This application option lets you change the condition of a worklist
when you are editing it to one of the following values: ONLINE,
REJECTED, or SUSPENDED.
To change the condition of a worklist:

1. In the Edit Worklist window, query for the worklist whose
condition you want to change.
2. Choose Worklist Condition application option to display a list
of conditions.
3. Choose a condition.
The new worklist condition is inserted in the field.
4. Click OK.

DRAFT
Events and Utilities 8 8
This chapter explains how to do following:
• Run an event
• Customize your application and set up your user environment
• Access optional SQL*LIMS® software products
• Exit and reconnect to the application
Note: For information about installing an event or viewing the
history of an event, see the SQL*LIMS Administration Guide.
Running an Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2
Sending and Reading Memos . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-6
Changing Your Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-8
Setting Your User Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-8
Activating and Deactivating Your Datagroups . . . . . . . . . . . . . . .8-10
Translation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-11
Optional Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-11

DRAFT
Events are actions such as reports or programs that you can execute
from the SQL*LIMS software. For example, you can run a report that
shows all the submissions that have a specific condition within a
certain time period.
Note: The term parameters used in this section represents query
criteria for a report.
The SQL*LIMS software is shipped with a set of report events.
You can also design and install your own reports with the Oracle
Reports software. For information on designing reports, refer to the
Oracle documentation for reports.
Running an Event
There are a few ways to run events:
• While in an open SQL*LIMS window with retrieved records
displayed, you can use the Run Event Options toolbar button.
When running an event this way, you can only choose an event
from ones that your applications manager has associated with
the cursor position in the active window.
• From the SQL*LIMS main menu, use the Run Event command
in the Events menu. When running an event this way, you choose
an event from the ones to which you have access.
The tabs displayed in the SQL*LIMS windows when you run an
event vary depending on how the event has been installed. For
example, you may have a Parameters tab without a Distribution tab.

DRAFT
Running an Event
To run an event while in a SQL*LIMS window:

1. In the toolbar, select Options > Event to display the Event
Options dialog box.
If there is only one event available, the Event Options dialog box
does not open. Instead, the event automatically begins running.
If there are parameters or distributions you need to enter, you
will be prompted for them.
2. Select an event, then click OK.

3. If the event window opens, respond as necessary, then choose
OK. The following figure shows an example event window. This
event has both parameters and distributions.
When a distribution of a database is selected, the report output
is stored as a document in the event history record. This new
distribution allows a customer a way to easily reproduce a report
at a later date.
4. If the Oracle Runtime Parameter window opens, make any

necessary changes, then choose Run Report.

DRAFT
5. If the report is displayed in the browser window, choose Print to

print it, then choose Close when you are finished viewing it.
If the destination for the event is cache, the browser window
does not open and the report goes directly to the designated
printer, file, email, database, or other distribution.
To run an event from the application window:

1. In the menu bar of the main menu, select Events > Run Event
to display the Run Events window.
2. Choose an event class from the drop-down list. This restricts the
query in the Event Name list box. Choosing All retrieves all
events, regardless of the class.
3. Click the Event Name field to display the Available Events
window.
4. In the Available Events window, select an event, then click OK.

DRAFT
Running an Event
5. If the event is interactive, you can:

• Enter a response for a parameter prompt
• In the Distribution tab, deselect the Active check box to
cancel distribution.
Uneditable defaults are provided for Distribution Class and
Destination (if applicable for the class). Depending on how
the event was installed, other defaults may also be provided.
6. Click OK to run the event.

7. If the report is displayed in the browser, choose Print to print it
then choose Close when you are finished viewing it. If the
destination for the event is not the browser, the report goes
directly to the designated printer or file.
8. To run another event, select one from the Available Events drop-
down list.

DRAFT
Sending and Reading Memos

The SQL*LIMS software has a memo system that conveys
information to you. The memo system also lets users send memos to
one another. If you want to be notified when a message has been
received, you can select the Memo Minder option in your user
preferences.
To send a memo:
1. In the menu bar, select Utilities > Memos > Send to display the
Send Memo window.
2. In the Receiver field, double-click to display the list of users,

then select the names of the people to whom you want to send
this message.
3. Enter the text in the Memo Text area, then click Send.

DRAFT
Sending and Reading Memos
To read a memo:
1. In the menu bar, select Utilities > Memos > Read to display the
Read Memo window.
2. Enter your search criteria, then click Execute Query in the

toolbar to retrieve any memos.
3. Select the memo that you want to read. The memo text is
displayed in the Memo Text area. Displaying a new memo
changes its status from NEW to READ. To make status changes
permanent, save them before you exit the window.
Note: If a scheduled event fails, a memo can be sent to a user.
Also, the logger and status monitors can send memos.

DRAFT
Changing Your Password

You can change your password yourself. However, your organization
may have security policies regarding computer passwords, who can
change them, and when they should be changed.
To change your password:

1. In the menu bar, select Utilities > User > Change Password to
open the Change Password window.
2. In the Old Password field, enter your current password.

3. In the new password fields, enter a new (different) password
twice.
4. Click Submit.
At your next session, you will enter your new password.
Note: If your lab runs the SQL*LIMS application in single sign-on
mode, this form will not appear.
Setting Your User Preferences

User preferences are settings that determine how some SQL*LIMS
software features work. You will be able to set preferences according
to how your SQL*LIMS applications manager has implemented
them. Any changes you make to your user preferences apply only to
yourself. See the SQL*LIMS Administration Guide for information
about user preferences.

DRAFT
Setting Your User Preferences
To set general user preferences:

1. In the menu bar, select Utilities > User > Preferences to display
the User Preferences window.
2. To set a user preference, select the appropriate tab, then select
the corresponding check box, or select from the drop-down list.

DRAFT
3. On each of the window’s tabs, select or deselect the preferences

as needed. If a preference is displayed in a list, select another
user preference in the list.
4. Click Commit to save your changes.
Activating and Deactivating Your Datagroups

When your applications manager assigns datagroups to you, they are
all active. This means that you can store and retrieve records that
contain one of your datagroups.
Deactivating a datagroup reduces the number of records that a query
will retrieve. Deactivating is useful if you want to be highly selective,
avoiding the need to scroll through extra records. Also, when you
have fewer datagroups, retrieval is slightly faster. You can reactivate
datagroups that you have deactivated. Deactivation affects retrieval
only; it does not affect storage.
To activate/deactivate your datagroups:

1. In the menu bar, select Utilities > User > Datagroups to display
the Change Datagroups window.
This window lists your datagroups and shows whether or not

they are active.
2. Toggle the Active check box to select or deselect a datagroup.

DRAFT
Translation
Translation
The Translation menu is accessed by selecting Utilities >
Translation from the SQL*LIMS menu bar and is described in the
SQL*LIMS Administration Guide.
Optional Products
When you install a SQL*LIMS optional product, its menu name is
added to the SQL*LIMS Utilities menu. For example, if you install
the SQL*Stability™ software, “Stability Menu” is listed on the
Utilities menu.
Choosing an optional product menu name displays the menu for that
product.

DRAFT

DRAFT
Index
A attachments
adding new or editing existing 1-53
Add Attributes application option 7-3 storing 1-53
Add QC Type application option 7-4 viewing 1-54
Add Replicates application option 7-5 attribute query 1-35
Add Sample Attributes application option 7-6 attributes
Add Unknown(s) application option 7-7 about 1-50
Add Versions application option 7-7 editing/entering for worklist 2-32
adding entering/editing 7-20
methods to a sample 2-23 grid 2-14, 2-17
new attachments 1-53 keyword 2-2
sample/material to submission 2-19 log request 2-2, 7-23
samples by operation 2-22 responding to 1-52
tasks by operation 2-22 submission, editing 2-42
analyst attributes/parameters
changing on worklist 7-8 adding to samples 7-3
deleting for query 3-13, 4-16, 7-10 creating for unplanned sample 7-6
editing for query 3-13, 4-16, 7-29 editing or entering for multiple
reassigning tasks to 2-33 samples 6-14, 7-20
Applied Biosystems audit log, viewing 4-36
contacting xiii
customer feedback on documentation xii B
Information Development xii
bold text, when to use xi
Services and Support xiii
Technical Support xiii Browse Limit Text application option 7-9
approval, bulk 5-5 building a tree 1-11
approving records bulk approval 5-5
about 5-2 excluding an object from 5-8
result 5-13
sample 5-10 C
submission 5-9
task 5-12 calculations, result
worklist 5-15 viewing 3-6
Assign New Analyst application option 7-8 calendar/date/time queries 1-59
assigning location 6-15, 6-17 calibration 7-33
check instrument / part 7-22
assumptions, for using this guide xi
instrument / part qualification 7-22
CAUTION, description xvi
SQL*LIMS User Guide Index-1

DRAFT
September 13, 2004 1:57 pm, UGIX.fm
Change Result application option 7-9 D
changing
DANGER, description xvi
password 1-9, 8-8
sample location 6-15 data
clearing window 1-61
checksum
discarding 1-61
definition 7-37
verifying 7-37 datagroup
about 1-5
child sample, creating 7-12
activating and deactivating 8-10
Clear Analyst application option 3-13, 4-16, results editing 6-2
7-10 results retrieval 3-2, 5-4
color coding, limits 3-9 Define Materials application option 7-14
commands Define Methods application option 7-15
function toolbar 1-18
Define Operations application option 7-16
in menu bar 1-10
main toolbar 1-18 Define Sample Plans application option 7-17
menus 1-14 Define Studies application option 7-19
shortcut menu 1-17 delete
Commit vs. Execute 2-3 worklist/worklist tasks 2-31
committing data changes 1-60 Detail tab 1-41
condition Detail window, displaying 1-42
about 1-6 detection limits 3-7
changes, history of 4-34, 7-39 discarding data 1-61
editing instance records 6-3 displaying retrieved records 1-37
editing worklist 7-40
results retrieval 3-2, 5-4, 6-2 disposing a sample 6-17
trigger for status action 7-31 documentation
conditional search criteria 1-31 feedback xii
related to this guide xii
conventions
bold text xi
IMPORTANT! xi E
in this guide xi Edit Attributes application option 7-20
italic text xi
editing
menu commands xi
attachments 1-53
Notes xi
attributes and/or parameters 7-20
user attention words xi
attributes/parameters 6-14
conventions, safety xvi condition 5-2, 5-3, 6-3
Copy Sample application option 7-11 instance data 6-7
counting query hits 1-27 worklist 6-12
Create Child Sample application option 7-12 electronic signature
Create TPL File application option 7-14 results approval 5-5
creating a worklist 2-26 results editing 6-2
results entry 3-3
customer feedback, on Applied Biosystems
documents xii entering/updating
data 1-21
customer viewing of instance records 4-20 text 1-21
Index-2 SQL*LIMS User Guide

DRAFT
ergonomics, safety xvii Information Development
errors, view log request 7-36 contacting xii
essay results 3-3 e-mail address xii
changing 7-9 installing an event 8-1
event instance hierarchy
history 8-1 about 1-4
installing 8-1 viewing more from (Zoom) 1-43
running 8-2 instance navigator 1-10
exact-match query 1-28 italic text, when to use xi
excluding an object from bulk approval 5-8
Execute vs. Commit 2-3 J
existing attachments, editing 1-53 jobtype 1-5
exiting SQL*LIMS 1-9 results editing 6-2
results retrieval 3-2, 5-4
F
files (creating TPL) 7-14 L
filter results 1-11 limiting display of instance objects 1-13
flipping columns 1-39 limits
format, result 3-4 color coding 3-9
defined 3-6
detection 3-7
G displaying 3-8
generating a worklist 2-26 in status bar 3-9
Grid 2-36 overriding 7-24
specification 3-7
grid
text 7-9
attributes 2-14, 2-17
list of valid entries
group sample plans 2-10
about 1-45
copying multiple values 1-49
H copying one value 1-46
hazard symbols. See safety symbols, on using 1-46
instruments using MRT 1-49
history location
event 8-1 sample 4-27
location or place 7-22 viewing all versions 7-34
status and condition changes 4-34, 7-39 viewing current 4-26
viewing 7-39 viewing history 7-22
location hierarchy
viewing 4-26
I location history
IMPORTANT, description xvi sample 4-29
indicators in status bar 1-38 viewing 4-28

DRAFT
Location History application option 7-22 menus
log plan 2-9 description of 1-14
log priority, setting 7-29 using shortcut 1-17
Log Request Attributes application method
option 2-2, 7-23 adding to a sample 2-23
defining 7-15
log requests result entry by 3-18
attributes 2-2, 7-23
result viewing by 4-13
defined 2-2
expediting (Commit vs. Execute) 2-3 multiple attributes, editing
resume interrupted processing of 7-30 grid logging 2-38
viewing 4-31 multiple conditions in query 1-31
viewing errors 7-36 multiple results, editing
logging matrix result entry 3-27
about 2-2
adding sample to submission 2-19 N
Commit vs. Execute 2-3
into the SQL*LIMS application 1-7 navigator
many samples simultaneously 2-36 limiting display of objects 1-13
methods, adding to a sample 2-23 new attachments, adding 1-53
planned sample 2-3 number of query hits 1-27
routine samples 2-9 number results 3-3
samples by grid 2-36
samples by study 2-10
samples using a log plan 2-9 O
submission 2-8 operation
unplanned sample (by material) 2-6 adding samples by 2-22
adding tasks by 2-22
M operations, defining 7-16
Make Status Request application option 7-24 Oracle toolbar 1-19
material ORDER BY clause 1-34
adding sample to submission 2-19 Override Limit application option 7-24
defining 7-14
logging multiple similar samples by 7-11 P
logging sample by 2-6
parameters 1-50
matrix
result entry by 3-24 password, changing 1-9, 8-8
result viewing by 4-15 pattern-matching query 1-29
measure limits pooling samples 7-26
defined 3-6 portal navigator 1-10
overriding 7-24 priority, setting log 7-29
memos
sending and reading 8-6
menu bar commands 1-10
menu commands, conventions for
describing xi

DRAFT
Q entering by worklist 3-20
entering, about 3-2
QC type, adding to worklist 7-4 format 3-4
query limits, defined 3-6
attribute 1-35 limits, overriding 7-24
for all records 1-28 processing of, resume interrupted 7-24
for selected records 1-28 recalculate 7-25
not returning requested records 1-36 significant figures 3-5
number of hits 1-27 values, types of 3-3
previous search criteria 1-27 versions, adding new 7-7
procedure 1-22 versions, displaying previous 3-28
saving 1-23 viewing 4-10, 7-28
second-level 1-26 viewing calculations 3-6
sort sequence 1-34 viewing more information on 3-10
query for selected records 1-28 results by task, customer viewing of 4-23
complex search criteria 1-31 Rules application option 7-25
dates and times 1-59
running an event 8-2
exact match 1-28
pattern matching 1-29
range matching 1-30 S
WHERE clause 1-31
safety
conventions xvi
R ergonomic xvii
repetitive motion xvii
range matching in query 1-30
workstation xvii
Read Memo utility 8-7
sample
reassigning tasks to analyst 2-33 adding to submission 2-19
Recalculate Result application option 7-25 approving 5-10
receiving samples 2-11 child, creating 7-12
records, viewing retrieved 1-37 condition (editing) 6-5
relational operators in query 1-30 data, editing 6-9
editing attributes/parameters 6-14
renumbering tasks in worklist 2-32
plans (defining) 7-17
repetitive motion, safety xvii receiving 2-11
replicates, creating 7-5 result entry by 3-13
Resequence Worklist application option 7-25 results, viewing 7-28
results tasks, viewing 7-28
approving 5-13 viewing 4-5
calculated result 3-6 sample attributes/parameters
changing 7-9 adding 7-3
changing approved 7-10 creating for unplanned sample 7-6
column headings 3-9 entering/editing 7-20
entering by matrix 3-24 sample location 4-27
entering by method 3-18 changing 6-15
entering by sample 3-13 history 4-29
entering by task 3-15

DRAFT
sample logging SQL*LIMS application
multiple similar samples 7-11 optional products 8-11
planned sample 2-3 starting 1-7
unplanned sample (by material) 2-6 state history 4-34, 7-39
using a log plan 2-9 status
sample plans about 1-6
group 2-10 changes, history of 4-34, 7-39
Sample Pooling application option 7-26 results editing 6-2
Sample Results application option 7-28 results retrieval 3-2, 5-4
Sample Tasks application option 7-28 trigger for status action 7-31
samples by result, customer viewing of 4-24 Status Actions application option 7-31
samples by submission, customer viewing status actions, summary of 7-30
of 4-20 status bar
saving about 1-20
data changes 1-60 indicators in 1-38
query 1-21, 1-23 limit display 3-9
your work 1-60 status request 7-24, 7-28
search criteria viewing 4-32
conditional 1-31 studies, defining 7-19
defined 1-21 submission
displaying last 1-27 adding sample/material to 2-19
secondary specifications approving 5-9
in Limits tab 3-8 condition, editing 6-4
second-level query 1-26 data, editing 6-7
editing attributes/parameters 6-14
Send Memo utility 8-6 logging 2-8
Send Status Request application option 7-28 rules associated with 7-25
Services and Support, obtaining xiii viewing 4-3
Set Analyst application option 3-13, 4-16, Submission Samples application option 7-33
7-29 suspend instrument or part 7-33
Set Log Priority application option 7-29
Set To Requested application option 7-30 T
shortcut menu 1-17
task
Show Status Actions application option 7-30
adding methods to a sample 2-23
signature event history 7-37 approving 5-12
significant figures for result values 3-5 condition, editing 6-6
sort sequence for query 1-34 data, editing 6-10
specifications editing attributes/parameters 6-14
limits 3-7, 7-39 reassigning analyst to 2-33
multiple 3-8 replicate, creating 7-5
primary/secondary 3-8 result entry by 3-15
SQL language, using in query versions, adding new 7-7
viewing 4-8, 7-28
ORDER BY clause 1-34
WHERE clause 1-31 Task Results application option 7-34

DRAFT
task results, viewing 7-34 View All Versions application option 7-34
tasks by sample, customer viewing of 4-22 View Errors application option 7-36
tasks on worklist View History application option 7-39
manipulating 2-31 View Result Specs application option 7-39
resequencing 7-25 viewing
result entry by 3-20 current locations 4-26
Technical Support, contacting xiii location hierarchy 4-26
text results 3-3 location history 4-28
text, displaying limit text 7-9 log requests 4-31
time results 3-3 results by matrix 4-15
retrieved records 1-37
toolbar sample location 4-27
application 1-18 signature event history 7-37
Function 1-18
status requests 4-32
Function, button descriptions 1-18 work 4-18
Main 1-18 worklists 4-16
Main, button descriptions 1-18
viewing (customer) instance data
TPL, creating files 7-14 samples by result 4-24
training, obtaining information about xiii samples by submissions 4-20
Translation menu 8-11 samples by task 4-23
trigger for status action 7-31 tasks by sample 4-22
txtnum results 3-3 viewing instance data
typing, data or text 1-21 audit log 4-36
results 4-10
samples 4-5
U status and condition changes 4-34, 7-39
unknowns, adding to worklist 7-7 submissions 4-3
user attention words, defined xi tasks 4-8
user preferences
displaying Oracle toolbar 1-19 W
setting 8-8 WARNING, description xvi
utility WHERE clause 1-31
activating and deactivating
window features 1-21
datagroups 8-10
reading memos 8-7 work, viewing 4-18
sending memos 8-6 workgroup, about 1-5
setting user preferences 8-8 worklist
translation 8-11 about 2-25
approving 5-15
V attributes 2-32
condition, editing 7-40
values, type of result 3-3 creating 2-26
verifying checksum 7-37 deleting 2-31
versions editing 6-12
result 3-28 editing attributes/parameters 6-12
task, adding new 7-7 plan 2-25

DRAFT
QC type, adding to 7-4
resequencing 2-32, 7-25
result entry by 3-20
saving 2-33
tasks, manipulating 2-31
unknowns, adding to 7-7
viewing 4-16
worklist (analyst)
changing 7-8
deleting for query 7-10
editing for query 7-29
Worklist Condition application option 7-40
workstation safety xvii
Z
Zoom window 1-43

DRAFT
Worldwide Sales and Support
Applied Biosystems vast distribution and

service network, composed of highly trained
support and applications personnel,
reaches 150 countries on six continents.
For sales office locations and technical support,
please call our local office or refer to our
Web site at www.appliedbiosystems.com.
Applera is committed to providing the

world’s leading technology and information
for life scientists. Applera Corporation
consists of the Applied Biosystems and
Celera Genomics businesses.
Headquarters
850 Lincoln Centre Drive
Foster City, CA 94404 USA
Phone: +1 650.638.5800
Toll Free (In North America): +1 800.345.5224
Fax: +1 650.638.5884
09/2004
www.appliedbiosystems.com Part Number 4347767 Rev. B

LIMS Thermo Phisher

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

LIMS Thermo Phisher

Caricato da

Copyright:

Formati disponibili

SQL*LIMS

Part Number 4347767 Rev. B

SQL*LIMS User Guide iii

iv SQL*LIMS User Guide

Chapter 3 Entering Results

SQL*LIMS User Guide v

Chapter 5 Approving Records

vi SQL*LIMS User Guide

Chapter 7 Application Options

SQL*LIMS User Guide vii

viii SQL*LIMS User Guide

SQL*LIMS User Guide ix

How to Use This Guide

Text Conventions This guide uses the following conventions:

SQL*LIMS User Guide xi

Examples of the user attention words appear below:

How to Obtain More Information

xii SQL*LIMS User Guide

How to Obtain Support

SQL*LIMS User Guide xiii

xiv SQL*LIMS User Guide

This chapter covers:

SQL*LIMS User Guide xv

Safety Conventions Used in This Document

– Indicates a potentially hazardous situation that,

– Indicates a potentially hazardous situation that,

– Indicates an imminently hazardous situation

– Do not attempt to lift or move the computer or

xvi SQL*LIMS User Guide

SQL*LIMS User Guide xvii

xviii SQL*LIMS User Guide

SQL*LIMS User Guide 1-1

1-2 SQL*LIMS User Guide

Chapter 1 Explains the concepts and techniques that you

Chapter 2 Provides the procedures for manually logging a

Chapter 3 Describes procedures for entering results manually

Chapter 4 Describes how to view data from records for

Chapter 5 Presents procedures for manually approving or not

Chapter 6 Gives procedures for editing information in the

Chapter 7 Provides an alphabetical list of all the application

Chapter 8 Describes how to run an event, customize your

SQL*LIMS User Guide 1-3

Task 1 Task 2 Task 1

Result 1 Result 1 Result 2 Result 1 Result 2

1-4 SQL*LIMS User Guide

SQL*LIMS User Guide 1-5

Status and Condition

1-6 SQL*LIMS User Guide

Starting the Application

To start the SQL*LIMS application:

3. In the Jobtypes window, select your jobtype, then click OK

SQL*LIMS User Guide 1-7

After connecting, the SQL*LIMS application window opens.

The SQL*LIMS application window has these main elements:

1-8 SQL*LIMS User Guide

Exiting the SQL*LIMS Software

Changing Your Password

To change your password:

2. In the Old Password field, enter your current password.

SQL*LIMS User Guide 1-9

1-10 SQL*LIMS User Guide

SQL*LIMS User Guide 1-11

The main instance objects – submission, sample, task, result, and