History of Changes During R5.2 (DM0503) |
Document Revisions |
|
|
Revision | Date | Description |
110315-52 | 03/15/2011 | Initial document release to support LABVANTAGE R5.2. |
Index to LABVANTAGE R5.2 New and Enhanced Functionality |
|
|
These link to descriptions of new and enhanced features in LABVANTAGE R5.2:
To view the history of changes made to LABVANTAGE from V1.1 (11/02/1999) through R5.1 (06/18/2010), see:
|
History of changes prior to LABVANTAGE R5.2 |
Product Name Change |
|
|
LabVantage Solutions, Inc. has changed the name of SAPPHIRE to "LabVantage". Accordingly, the changes listed below have been made to this document:
• | Build files have been renamed to LabVantageDoc.chm, LabVantageDoc.htm, and labvantagedoc.war. |
• | References to "SAPPHIRE" have been eliminated from table of contents entries, except where such references apply to named APIs and API objects. |
• | Window titles and headers containing "SAPPHIRE" have been changed to "LabVantage". |
• | Textual references to "SAPPHIRE" have been eliminated or replaced with "LabVantage", except where such references apply to named APIs and API objects. |
• | References to "SAPPHIRE" in graphic images are being examined and modified on an ongoing basis. |
Note that shortly before release, the case of the product name was changed, i.e., "LabVantage" is now "LABVANTAGE". This change will be addressed in documentation that supports the next major LABVANTAGE release.
Actions |
|
|
Features |
|
These new Actions have been added:
|
|||||||||||||||||||||||||||||||||||||||||||||||
|
These core Actions (exposed through the Action Public Interfaces) have
been modified:
|
Document Changes |
|
Click the links above to open the Action in the Javadoc for the System Action Public Interfaces. |
AQC |
|
|
Features |
|
During data entry, AQC calculations are now immediately executed to provide "live feedback" (rather than having to save prior to seeing the results). | |
|
"Create Worksheet Rules" have been added to QC Methods for integrating AQC with Worksheets. | |
|
The Sample Life Cycle depends on data entered for the mandatory Data Items associated with Samples in the QC Batch and Data Items of the QC Batch Params. |
Document Changes |
|
In QC Batches:
|
|||||||
|
In Entering Data for QC Batches, added AQC Calculations to the "Data Entry (Procedural)" section. | |||||||
|
In QC Methods, added QCBatch Params, Variant, Version, QCBatch Params Spec, Version and Create Worksheet Rule. | |||||||
|
In QC Batch
Life Cycle:
|
|||||||
|
Added AQC Policy. | |||||||
|
Updated documents to reflect that (due to definition of Parameter List Type in the QC Batch), Batch status changes from Initial to InProgress if any Preparation or Procedural data are entered for the Batch. This formerly stated that Batch status was inProgress, DataEntered and Completed based only on Procedural data. |
Calculations |
|
|
Features |
RedoCalculations |
|
The RedoCalcuations Action has been enhanced. RedoCalculations now updates
a calculated data value only if it has changed. This prevents updating
of incorrect ModBy and ModDt columns in the SDIDataItem table and eliminates
unnecessary Audit records. The RedoCalculations Action is also called
when a Data Item is marked as an "Outlier".
Note that this behavior applies only to RedoCalculations (and SetCalcExclude, which calls RedoCalculations). It does not apply to the Data Entry process when RedoCalculations is not executed. If you are entering data and you change any values, all Calculations are updated and Audit records are cut for all updates... as long as neither of these Actions is executed. |
Updating Released Data |
|
In R5.2, there is a new "Update Released Calcs" property for
the Data Entry Policy:
Y = Whether or not data are Released, if you change the calculated value, the system will accept your change and update the Released value. This is R5.1 behavior. N = For NC-type data, changing data values that cause a Released NC-type to be recalculated will generate an error. For N-type data, changing data values that cause a Released N-type to be recalculated will not generate an error. The newly entered data are saved, but the N-calculated value is not updated. |
Workitem DataSet Filter |
|
In R5.1, when referencing Data Sets by an SDIData column, the Data Set
filter could be applied to either SourceWorkitemId or SourceWorkitemInstance.
In R5.2, the Data Set filter can be applied to both by specifying either of these new syntaxes:
|
Document Changes |
|
In Reference Calculations: Explicit Reference to a Single SDI, added a notice that whenever RedoCalculation is executed, calculated data are updated and an audit record is cut only if the data value has changed. | |
|
In the RedoCalculations Action, removed references to "all Calculations for all UnReleased Data Items". | |
|
In the Data Entry Policy, added the "Update Released Calcs" property. | |
|
In Referencing Data Sets by an SDIData Column, modified Workitem filter to specify new workitem=<workitemid> and workitem=# syntax. |
Certifications |
|
|
Features |
|
New "By Form" certifies Users for a Form. | |
|
New "Forms" tab added to "By Analyst" for certifying Forms for an Analyst. |
Document Changes |
|
Made these changes to Certifications:
|
Configuration Reports |
|
|
Features |
|
You can now create a Configuration Report in XML format. | |
|
New Configuration Report Diffing feature compares current configuration data to a reference report to show modifications, additions, deletions, and unchanged items. |
Document Changes |
|
In Configuration Reports:
|
Data File Definitions |
|
|
Features |
|
Enhancements to Data File Definitions:
|
Document Changes |
|
In Data File Definition:
|
|||||
|
In Data File Parser, added the concept of the "Input" field to the "Fields" section to correspond to additional properties passed to the ImportDataFile Action. |
Data Set, Test, and Worksheet Management |
|
|
Features |
Analyst and Instrument Assignment |
|
Removal of Tramstops
|
Data Set Management |
|
New "Manage Data Sets" Tramstop
|
|
Duplicate Functionality
|
Test Management |
|
New "Manage Tests" Tramstop
|
|
Duplicate Functionality
|
Worksheet Management |
|
New "Manage Worksheets" Tramstop
|
Document Changes |
|
Added new documentation for Manage Data Sets, Tests, and Worksheets. | |
|
Removed Analyst and Instrument Assignment from the Table of Contents. | |
|
Add a note to the old Assignment documentation that it is provided for backward-compatibility only. | |
|
In Concepts of Data Entry, updated Adding Tests to Samples. |
Display Format |
|
|
Feature |
|
Literal strings can now be returned using an eval expression without
throwing an error. For example: [eval;if ([this] < 10, "'<10'", "'>10'")] now returns the literals <10 and >10. |
Document Change |
|
In Parameter Lists, added Returning Literals to provide an example of eval usage, plus an explanation of what happens if single quotes are not included in other expressions. |
Document Corrections and Updates |
|
|
|
Fixed 162 broken/orphaned links in the table of contents and other areas that use bookmark and running index references. | |
|
Two typographical errors on the Units Maintenance page have been corrected to provide an accurate example of using conversion factors. These typographical errors had the effect of reversing the intended conversion factors. | |
|
Updated Parameter List Display Format to delete the $#,##0;($#,##0) format and include the "AsEntered" format. | |
|
In Expression Editor Expression Library, updated the format of "max" and "mod" functions. | |
|
In Request Controller Syntax, updated the logoff example to "rc?command=logoff&url=logon.jsp". | |
|
In the Javadoc for the System Action Public Interfaces, modified the custom Javadoc Doclet class (docflex.class) to show the ActionId during full-text searches. |
eForms Technology |
|
|
Features |
The following changes and enhancements have been made to eForms.
Worksheet Forms |
|
New "Worksheet" Form Type You can now create a special type of Form called a "Worksheet". Worksheet Forms can be bound to database records. Worksheet Forms provide:
Automatic Datasource creation, automatic processing and saving, and the automatic and manual creation options are available out-of-the-box (referred to as "Context-Driven" Worksheets). Context-Driven Worksheets provide a high level of automation in the Worksheet creation and saving process. All Form processing rules for Context-Driven Worksheets are automatic. No user-defined processing is allowed. You can also create advanced and customized Worksheets manually with custom processing rules (referred to as "Adhoc" Worksheets). |
Form Definition |
|
New Form Definition Options
|
eForm Manager |
|
New Form and Document Search Utility
|
|
New Document Viewing and Selection Options
|
|
New Document Toolbar Operations
|
|
New Field Toolbar Operation
|
|
New Group Operation Buttons
|
|
New Attachments Functionality
|
|
New Followup Functionality
|
|
General Enhancements
|
Formlets |
|
Versioning
|
|||||
|
By Reference
|
|||||
|
Formlet Definition
|
Form Builder |
|
User Interface Enhancements
|
|
Form Builder Fields
|
|
Form Builder Groups
|
|
Form Builder Sections
|
|
Form Builder Elements
|
|
Form Builder Pages
|
EForm Page Type |
|
Property Changes
|
JavaScript |
|
New JavaScript Functions These new JavaScript functions are not exposed in a *.js file. They are created dynamically in Google Web Toolkit when a Form is created:
|
|
Request Parameters and Old JavaScript Functions
|
Actions |
|
System Actions
|
Modules |
|
Module-Specific Functionality
|
Document Changes |
To support related functionality, these changes have been made to this document:
|
Introduction to eForms
|
|
Form Definitions
|
|
Form Builder: Overview
|
|
Form Builder: Fields
|
|
Form Builder: Groups
|
|
Form Builder: Sections
|
|
Form Builder: Elements
|
|
eForm Manager
|
|
eForm Worksheet Principles Added new topic to describe basic Worksheet functionality:
|
|
eForm Worksheet
Advanced Concepts Added new topic to describe advanced Worksheet functionality:
|
|
Field and Formlet Definitions
|
|
eForm Data Entry Examples
|
|
eForm Document Reference
|
|
EForm Page Type
|
|
Forms Policy
|
|
Form Builder: APIs
|
|
Added "Create Worksheet Rule" and "Forms" detail to:
|
|
In Enhanced Data Entry Pages, added "Worksheet" to Data Set Detail Panel with information and link to SDIData locking. |
|
In System Configuration User Options, added new Notifications Format property. |
External Authentication (LDAP) |
|
|
Features |
|
In External Authentication, a new "LDAP to User Message Mappings" property collection allows LDAP error messages to be displayed in a more user-friendly manner. You can specify a literal string, which is matched to the error message issued by the LDAP server. You can specify a custom message to display when a match is found. The custom message accepts a literal text string and the [currentuser] and [ldaperrormessage] tokens. For example, this can be a string such as "Password expired" or "User not found for [currentuser]". If these values are not specified, a generic message is issued to maintain backward-compatibility. |
Document Changes |
|
In External Authentication, added new LDAP to User Message Mappings property collection. |
JavaScript Global API |
|
|
Features |
|
A new sapphire.util.url object handles encoding and passing Unicode charcters through the request. All navigation routines have been changed to use the sapphire API which, in turn, uses this new url object. The APIs for opening URLs (sapphire.page.navigate) and windows (sapphire.lookup.open) were also enhanced to encode the URL using the new API. Also, more new methods and objects have been added as enhancements (see "Document Changes" below). |
Document Changes |
|
See the JavaScript Global API to access these objects from the object tree. |
Object | Change |
sapphire.browser | Added new object properties and deprecated "id"
object property.
Deprecated "determine" method. |
sapphire.connection | Added "isDevMode" object property. |
sapphire.events | Added "vFunction" property to attachEvent method.
Added detachEvent and fireEvent methods. |
sapphire.page | Added getKeyId2, getKeyId3, maximizeLayout, minimizeLayout,
toggleLoading, and getPageType methods.
Added a note to describe that the navigate method now works with Unicode. |
sapphire.page.maint | Added getRowCount, getAllColumnValues, getLocked, and getLockedBy methods. |
sapphire | Added translate and translatePartial methods. |
sapphire.util.script | New object. |
sapphire.util.dom | New object. |
sapphire.util.date | New object. |
sapphire.util.url | New object. |
sapphire.util.url.href | New object. |
Maint Page Formatted Text Editor |
|
|
Features |
|
In the maint Element, a new "formattedtext" Column Mode renders a new "Formatted Text" editor that lets you enter formatted text into a CLOB column. The editor consists of an editing pane and basic self-explanatory toolbar. Features that do not work with Reports are noted in the documentation. |
Document Changes |
|
In maint Element, added formattedtext mode and Formatted Text Editor, including a link to Reporting Caveats. | |
|
Deleted the RTF Editor API from the documentation. It has been declared for internal development use only. |
Naming Restrictions |
|
|
Features |
|
SDC/SDI naming restrictions have been extended to include Reference Types and Reference Values. |
Document Changes |
|
In Naming Restrictions and Syntax Standards, extended SDC/SDI naming restrictions to include Reference Types and Reference Values. |
Packages |
|
|
Features |
|
In R5.1, the status of Samples in a Package is set to Received when the Receive Sample when Package is Received lets you continue this behavior, or change it so that Sample status is not changed when the Package is Received. |
Document Changes |
|
In BioBankingPolicy, added Receive Sample when Package is Received property. |
Reporting |
|
|
Features |
|
Jasper Reports has been upgraded to version 3.7.4. | |
|
The compatible JasperSoft iReport installer is no longer provided with the LabVantage distribution CD. | |
|
The JasperReportScriptlet class is no longer provided as a standalone file (it is now accessible only through the Java Public API). | |
|
Caveats exist in various areas of Reporting. |
Document Changes |
|
In Concepts of Reporting:
|
|||||||
|
In Using Unicode in Jasper Reports, added stipulation that the Unicode font must go into the root of the EAR. | |||||||
|
Added Reporting Caveats. Also added warning and link to Concepts of Reporting, Reports and Execute Reports, Formatted Text Editor, and Adhoc Queries. |
Simple Instruments |
|
|
Features |
|
A new "Simple Instruments" feature allows data to be transferred
from a "simple" laboratory instrument to Data Entry. A "simple"
instrument is defined as one that uses a protocol such as RS-232, generates
raw test results without knowing Sample Ids,
synchronously receives commands, and optionally sends back responses. Examples
include weight balances and pH meters.
You can define "Instrument Response Parsing" rules to specify how the raw response from an instrument is parsed to fields and field values in Data Entry and eForm pages (Interfaces are available on Enhanced Data Entry pages and Form Fields configured with Instrument properties). An instrument can be simulated using the example response when running an instrument in "simulation mode". When running in simulation mode, all configurations related to an instrument are tested except for actual connectivity to the instrument. This functionality is available at these Lab Admin → Certifications and Resources tramstops:
|
Document Changes |
|
Added new documentation for Simple Instruments. | |
|
Added Simple Instrument interface button to Enhanced Data Entry Page Toolbar. |
Specifications |
|
|
Features |
A new Specification Transform Rule is now executed during Data Entry to transform the entered data value immediately before evaluating the Specification Limits.
|
Problem in R5.1:
|
|||||||||||||||||||||||||||||||||||
|
Solution in R5.2:
|
Document Changes |
|
In the Specification Maintenance page, added "Transformation Rule" to the "Parameter Details" tab to define the new Specification Transformation Rule. | |
|
In How Transformations and Calculations are Processed (formerly "How SAPPHIRE Handles Data Entry"), changed process to include new Specification Transformation Rule. This is in preparation to adding a separate topic covering the entire Data Entry process (to be done in a future document revision). | |
|
In Concepts of Transformations and Calculations and Parameter List Maintenance page, changed descriptions of N and NC Data Types. | |
|
In the Parameter List Maintenance page, added a link to Concepts of Transformations and Calculations. | |
|
In the Limits Detail Panel for Enhanced Data Entry pages, updated screen capture to show "Checked Value". |
Storage |
|
|
Features |
|
In SAPPHIRE R5.1, adding a child to an existing Storage Location was a two step process. In R5.2, a new "Add Child" button on the Storage Units Tree page lets you add a child to a single parent in one step. Validations are also done to make certain you have selected only one Storage Location. For consistency of operation, "Add Child" provides the same wizard for building the child hierarchy as in the parent. |
Document Changes |
|
Updated screen captures and added Adding a Child Storage Location to reflect shift from detail element operation to "Add Child" button operation. |
System Monitor |
|
|
Features |
|
"Trending" (System Admin → Monitoring → Trending) provides a graphical representation of trends regarding ToDo List Maintenance, Performance Statistics, System Monitor, User Connections, and JVM. Trending can aid with problem diagnosis or monitoring system stability. Options are provided for showing "Historical Trends" over extended time domains, and "Live Trends" currently in process. |
Document Changes |
|
Added new Trending section to Monitoring. |
Web Page Designer |
|
|
Features |
|
A new "Node Finder" lets you find a specific node on a large Property Tree. Enter a search string, and nodes containing the search string are highlighted in yellow. |
Document Changes |
|
Added new Node Finder feature to Web Page Designer: Properties Overview. |
Web Services |
|
|
Features |
|
Thirteen new Web Service methods have been added to allow direct object
interaction with SOAP languages:
Recall that LabVantage R5.1 Web Services provide generic calls to the Java Public API (such as getSQLDataSet and processAction). However, they also use LabVantage-specific XML structures to send/receive data to/from the Web Service, i.e., XML is sent within XML. This has proven to be inefficient, since objects must be manually serialized to LabVantage XML structures, then deserialized in the client using the XML structure to create the objects. Note that the LabVantage propertylist and dataset XML does not use standard XML ddt or schema, and is therefore not recognized by other languages. New Transport Beans have been created for classes that handle things such as for Data Sets, Property Lists, and SDI Data. These are Java Bean Wrappers for current classes that are built from primitives and expose get and set properties. Each complex LabVantage API object is therefore wrapped by a primitive Java Bean The current Web Service methods have been enhanced to accept and return these new Java Bean objects. This means that the SOAP interface in LabVantage's Axis engine and on the .NET (or other language) client is responsible for serialization. We therefore need not know anything about the object. The object can then be used "as-is" on the client. This allows direct object interaction with SOAP languages such as .NET. For example, you can send a Property List object to the Web Service call to process an Action. With the old methods and XML structures, you would have to send a Property List XML string... which the 3rd party vendor does not know how to build. For backward-compatibility, all methods continue to accept the older (pre-R5.2) XML structures. New complex methods such as getSDIData, getSDCProperties and getDatabaseList have been added to let you use the LabVantage Java Public API and query the database using the recommended techniques. You can therefore query SDCs for primary and detail tables from any external language, rather than having to know the exact SQL and data structure. Client code and LabVantage object .NET equivalents have been integrated into a centralized .NET library that is still in the process of being created for future use. This new wrapper class will hide the complexities of the Web Service and LabVantage architecture (such as connection management) and will manage logging and pinging. A new Web Service method is also available to create and update Attachments. |
Document Changes |
In Web Services, added the new Web Service methods accompanied by background information.