Data Entry Policy

The Data Entry Policy determines feedback and visual cues for Data Entry pages (which use the gwtdataentrygrid Element). Additional visual cues can be configured with image mapping of values with additional primary, sdidata and sdidataitem attibute values.

Property

Description

OOB Setting

Live Limit Check

After you stop typing, the system waits this time interval before it checks Spec Limits.

1 second

Allow Auto Load Detail Info

Determines if Detail information is automatically loaded each time a cell receives focus.

Yes

Allow Release Blank

Determines if and how a null value can be Released:

Yes	=	Allows null values to be Released.
Yes (For Non-Mandatory Item Only)	=	Allows null mandatory values to be skipped. When you Release data, a check is conducted to determine if any mandatory Data Item selected for Release has a null value. If Yes, a warning message prompts you, and those items are skipped.
No	=	Does not allow null values to be Released.

Yes

Entered Optional Result Require Release

Determines if optional (non-Mandatory) entered Data Items must be Released before the Data Set can transition to "Complete":

Yes	=	All entered Data Items must be Released before the Data Set can transition to "Complete". UnReleasing any Data Items (Mandatory or non-Mandatory) will return the status to "In Progress". This is the default.
No	=	Data Set status transitions to "Complete" when all Mandatory Data Items are Released (regardless of non-Mandatory Data Item status). UnReleasing non-Mandatory Data Items will not return the status to "In Progress".

Enable Dynamic Audit of Result Entry

Determines if "Dynamic Auditing" is enabled during Data Entry. See Dynamic Auditing for a complete description of this feature with examples.

Simple Instrument Result Options

Determines how the system behaves when Data Entry results are populated by Simple Instruments and "Audit Result Entry" (above) is set to "No". If "Audit Result Entry" is set to "Yes", this option is forced to "Save Instrument Results Immediately on Receive".

Option

Description

Allow Manually Edit Unsaved Instrument Results

Allows Data Entry results populated by Simple Instruments to be manually edited by Users before saving to the database. This option is backward-compatible with previous LabVantage versions. Here is how the SDIDataItem records are created:

SDIDataItem

EnteredText	InstrumentId	AuditedInstrumentId	AuditedEnteredText	How the record is created:
2.6	PHM1	PHM1	2.6	EnteredText is populated with the value 2.6 sent from Instrument PHM1 and the value is saved untouched.
2.0			2.0	EnteredText is populated with the manually edited value of 2.0 and saved. InstrumentId is nulled when a result is manually altered.
2.5	PHM2	PHM2	2.5	EnteredText is populated with the value 2.5 sent from Instrument PHM2 and the value is saved untouched.

Do Not Allow Manually Edit Unsaved Instrument Results

Prevents Data Entry results populated by Simple Instruments to be manually edited by Users before saving to the database. When a Data Entry cell is populated with a result from a Simple Instrument, the result becomes read only and begins receiving the next result from the Instrument. After saving, the cell becomes editable and Users can edit the result. The original result from the Instrument is also saved to the AuditedInstrumentId and AuditedEnteredText columns of SDIDataItem, along with the corresponding InstrumentId. Compared to "Allow Manually Edit Unsaved Instrument Results", this option has the added benefit of preventing a User from accidentally overriding Instrument results before saving. However, it does not prevent Users from abandoning Instrument results by not clicking Save. The SDIDataItem records involved in this process are the same as the prevous option.

Save Instrument Results Immediately on Receive

Uses an Ajax call to immediately save Data Entry results populated by Simple Instruments. All results that are parsed from the same Instrument response are saved in one transaction by calling the EditDataItem Action to populate the AuditedInstrumentId and AuditedEnteredText columns of SDIDataItem with the activity "Auto persist result from instrument". Fields should be protected as soon as they are populated with Instrument results, as this is a stricter option than the previous. Compared to "Do Not Allow Manually Edit Unsaved Instrument Results", this option prevents Users from abandoning Instrument results by not saving. However, this option may generate an excessive amount of granular savings to the SDIDataItem table if data from Instruments are frequently compared with normal Data Entry saves. Here is how the SDIDataItem records are created:

SDIDataItem

EnteredText	InstrumentId	AuditedInstrumentId	AuditedEnteredText	How the record is created:
		PHM1	2.6	The value 2.6 was read from Instrument PHM1 but not saved by the User. This value would not have been captured with the two previously described options.
2.0			2.0	A User manually entered 2.0 and saved.
2.5	PHM2	PHM2	2.5	EnteredText is populated with the value 2.5 sent from Instrument PHM2 and saved untouched.
2.0	PHM2	PHM1	3	The value 3 was read from Instrument PHM1 but not saved by the User.
4	PHM2	PHM2	4	EnteredText is populated with the value 4 sent from Instrument PHM2 and saved untouched.

During Data Set Approval, any discrepancy between AuditedEnteredText and saved EnteredText triggers an alert.

Generate Release Events on Edit

Determines if pre- and post-ReleaseData events are generated when the EditDataItem Action modifies the releasedflag column in SDIDataItem. This captures events fired from SDC Rules and Event Plans generated from Data Entry pages. Note that events fired from SDC Rules and Event Plans are generated in the same code line.

Update Released Calcs

Determines how Released calculated values are treated:

Yes

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 the default value if this property is left blank.

Depends on whether the calculated Data Type is N or NC:

•	For NC Data Types: Changing data values that cause a Released NC-type to be recalculated will generate an error.
•	For N Data Types: 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.

Recall that a Numeric Calculation (NC) cannot be manually changed in Data Entry (readonly), and a Numeric with Calculation Expression (N) can be manually changed in Data Entry (editable). For N-Type data, the Calculation is not necessarily honored because the Calculated value can be manually changed during Data Entry.

This property addresses the following scenarios (A, B, C, and D are Parameters):

Case 1: C is a Numeric Calculation (NC)

A	=	10
B	=	20
C	=	A + B
	=	30

Someone Releases C. Another User then changes A to 15. If the "Update Release Calcs" property is set to "Yes", C updates to 35. If the property is set to "No", an error is generated.

Case 2: D is a Numeric with Calculation Expression (N)

A	=	10
B	=	20
D	=	A + B
	=	30

Someone Releases D. Another User changes A to 15. If the "Update Released Calcs" property is set to "Yes", D updates to 35. If the property is set to "No", the entered value of A (15) is saved, but D is not updated to 35.

Entered Limit Met

If entered data is a value defined by a Parameter Limit Type, this forces the defined Limit to be met.

This is used for situations when you have defined a Limit Rule that applies a Transform Rule when a Parameter Limit is met.

Example: A "BDL" Parameter Limit Type is associated with a Parameter Limit of <10. When this limit is met, a Transform Value of 5 is applied. If the user enters "BDL", the Data Entry page displays the Transform Value of 5. The Entered Value and Transfom Value are null values in the SDIDataItem table. This works only if the Transform Value is a literal. For example, it does not work if the Transform Value is a Calculation such as [this]/2.

Reset Approvals on UnRelease

If a Released Data Item is UnReleased, setting this to Yes resets any completed SDI Data Approval. Approval will then need to be conducted again.

Translate Validated Reference Type

This is equivalent to the translate property on the classic dataentrygrid and dataentrylist elements. Furthermore, the Data Entry page presents the RefValue's DisplayValue if defined rather than only showing the RefValueID.

Enter Default Values On Add

This determines how a Parameter "Default Value" is handled with regard to the Data Entry process. The Default Value is specified for each Parameter in the Parameter List Maintenance page, and persisted in the ParamListItem.DefaultValue column.

Value

Description

Yes

Results in this behavior:

•	The Parameter "Default Value" is automatically entered as data, i.e., copied-down to SDIDataItem.EnteredText and SDIDataItem.EnteredValue.
•	The AddDataSet and AddDataItem Actions enter the Parameter "Default Value" as data into SDIDataItem.EnteredText and SDIDataItem.EnteredValue (providing a Transformation Rule is not defined).
•	The CopyDataSet Action does not copy entered data, but it copies the Default Value.
•	The AddSDI Action when using an SDI Template does not copy Default Value.
•	The Default Value is not shown in the Data Entry grid cell. This prevents a User from seeing the Default Value if the User clears entered text.

This is the behavior of LabVantage 6.x and earlier.

Results in this behavior:

•	The Parameter "Default Value" is handled by the Data Entry page, which displays the Default Values and lets the User accept them as entered data in SDIDataItem.EnteredText and SDIDataItem.EnteredValue.
•	The AddDataSet and AddDataItem Actions do not enter the Parameter "Default Value" as data into into SDIDataItem.EnteredText and SDIDataItem.EnteredValue.
•	The CopyDataSet Action does not copy entered data, but it copies the Default Value.
•	The AddSDI Action when using an SDI Template copies the Default Value (from ParamListItem.DefaultValue to SDIDataItem.DefaultValue).

NOTE:

When "Enter Default Values On Add" is set to "Yes", the decimal separator for the current User's locale can be used in the Numeric Parameter Default Value, but the system saves the Default Value with the decimal separator defined by the system local.

Regardless of whether this property is set to "Yes" or "No", the AddDataSet Action always copies-down the Parameter "Default Value" to the SDIDataItem.DefaultValue column.

Data Set Indexing

"Yes" indexes Data Sets when entering values for Data Items. This can result in a performance increase. Rather then iterating through large result sets to filter and find items, the filter/find operations use lightweight indexes to quickly find the requested rows.

Visual Policies

Maps "Applicable Id" columns to styles or icons. Any column can be mapped from SDIData, SDIDataItem, or the primary. SpecCondition and IsUserCertified can also be mapped (see note below).

Property	Description
Applicable Id	Column to map.
title	Displayed title.
Visual Mode	"CSS style" maps the "Applicable Id" column to the styles defined by "Value Displays" (below). This is the mode if left blank. "Icon" maps the "Applicable Id" column to the icon defined by "Icon from RefType" and "Value Icons" (below). An "Applicable Id" cannot mix "CSS style" and "Icon" for different values.
Value Displays	If "Visual Mode" is "CSS style", this defines the CSS attribute and CSS value applied to the rendered value.
Icon from RefType	If "Visual Mode" is "Icon", this is the Reference Type that defines the icon to be rendered in the Data Entry cell. Alternatively, you can specify a value and icon using "Value Icons" (below).
Value Icons	If you do not specify an "Icon from RefType", you can specify a value and corresponding icon image source path or URL here.

Icons are rendered next to the entry field or after the display units (if any).

If a column is configured the same as an applied Visual Policy, the Visual Policy is applied to the column with the column position preserved.

NOTE:

IsUserCertified is an attribute of the Data Set for a Data Item. It does not represent a column in SDIDataItem. This "Analyst Certification" value is determined server-side, then rendered as though it is a column in SDIDataItem.

Certification is valid if ParamList.s_TrainingReqFlag is "Y", the user has CertificationStatus = "Valid" or "In Training", and the Certification has not expired (according to the Expired Date and Grace Period).

If ParamList.s_OverrideAllowedFlag is "Y", the value of isusercertified is "A"... otherwise, it is "N". When saving overridden cell values, SDIDataItem.s_ACOverriddenFlag is set to "Y" for Data Items that have changed.

The result is cached by the ConnectionId (equivalent to user session) to prevent the same session from being checked twice.

All possible values of this property are:

(null)	=	Does not require certification.
N	=	Analyst not certified, do not allow override.
A	=	Analyst not certified, allow override.
Y	=	Analyst certified.

Spec Condition Display Option

When an SDI has multiple Specifications for the same Data Item, this determines if the SDI Condition is evaluated using the "Worst Matching Spec" (worst OOS Spec Condition evaluated for a Data Item) or "First Matching Spec" (first OOS Spec Condition evaluated for a Data Item). In the OOB configuration, this is set to "Worst Matching Spec". Switch to "First Matching Spec" for backward-compatibility.

Spec Conditions
(Best First, Worst Last)

These properties essentially map a Spec Condition to an interpretation that can be represented by text or an icon.

Spec Conditions should be specified in best-to-worst order. This can be seen in the OOB configuration, where Spec Conditions are set in the order Pass, Notification, Warning, Fail, Undetermined.

The "SpecCondition" Reference Type is not editable. It is maintained here. If the "Sync to Spec Condition RefType" property is set to "Yes", changes made here (such as adding/removing Spec Conditions, changing their order, etc.) are also made in the Spec Condition Reference Type.

Property	Description
Spec Condition	Spec Condition to be mapped. This is free text to facilitate adding new Spec Conditions from here.
Interpretation	Interpretation mapped to the Spec Condition (Fail, Pass, or Warning).
Warning on COA	Indicates if Warnings are noted in the COA Report.
Icon	Icon displayed for the Spec Condition.
Sync to Spec Condition RefType	Synchronizes the Spec Conditions defined here to Reference Values in the SpecCondition Reference Type when the Data Entry Policy is saved.

NOTE:

If these Spec Conditions are not synchronized with the SpecCondition Reference Type, saving the Data Entry page or calling the EnterDataItem Action will issue an error message that tells the User to synchronize. This may be the case during upgrades.

Rule for Undetermined Spec Limits

Determines how to handle cases where a Specification Limit cannot be evaluated:

Property	Description
Honor Entered Operator in Limit Evaluation	Ignores the operator in entered data. This can be used for backward-compatibility with versions prior to LabVantage 6.
Use Condition For Undetermined Condition	Sets the specified Spec Condition ("Pass", "Notification", "Fail", or "Warning") if the entered data contains an operator and does not fall within the defined Specification Limits.

Rule for Undetermined Param Limits

Determines how to handle cases where a Parameter Limit cannot be evaluated:

Property	Description
Honor Entered Operator in Limit Evaluation	Ignores the operator in entered data. This can be used for backward-compatibility with versions prior to LabVantage 6.
Use Limit For Undetermined Condition	Sets the specified Condition ("Limit Met", "Limit Not Met", or "Skip Limit") if the entered data contains an operator and does not fall within the defined Parameter Limits.

Note:

With regard to the next two properties ("Honor Null in Relational Expressions" and "Honor Null in AND/OR Conditional Expressions"), the following definitions apply when evaluating an if(b, t, f) function that contains null values:

•	"Backward-Compatible" null evaluation refers to LabVantage R5.0 MR10 and lower. In these older versions, if any Parameter in the expression was null, the function returned a null.
•	"Current" null evaluation refers to LabVantage R5.0 MR11 and higher. In these newer versions, nulls are logically evaluated to provide more consistent results.

Examples of "Backward Compatible" and "Current" null evaluation:

		Value Returned
Expression	Value of p1	Backward-Compatible	Current
if ( isnull( [p1] ) or [p1] < 1 , true, false )	null	null	true
if ( [p1] < 1 , true, false )	null	null	false

Note that setting both properties to "Yes" results in "Backward-Compatible" null evaluation.

Honor Null in Relational Expressions

Applies to expressions using a relational operator ( = != < > <= >= ):

Value	Behavior
Yes	"Backward-Compatible" null evaluation (returns null if any Parameter of a relational expression is null as shown in the examples above).
No	"Current" null evaluation (returns true or false whether or not any operand is null as shown in the examples above).

Honor Null in AND/OR Conditional Expressions

This is applicable only if "Honor Null in Relational Expressions" is set to "Yes":

Value

Behavior

Yes

"Backward-Compatible" null evaluation (returns null if either side of a conditional AND/OR expression is null).

"Current" null evaluation. Behavior depends on the type of expression:

Type of Expression

Behavior

Conditional AND

•	If both sides of the conditional expression are null, returns null.
•	If both sides of the conditional expression are true, returns true.
•	Otherwise, returns false.

Conditional OR

•	If both sides of the conditional expression are null, returns null.
•	If either side of the conditional expression is true, returns true.
•	Otherwise, returns false.

Empty Text Parameter Mode

For "Text" Data Type, determines whether a null or an empty string is returned if no value is entered for a Parameter:

Value	Behavior
Always Return Null	Returns a null.
Always Return Empty String	Returns an empty string.

Workitem Force New

Determines behavior of the Force New option for Test Methods:

Property

Description

Retain Selective Force New

When set to Yes, these areas of the OOB LabVantage configuration will continue to work as they did in LabVantage 6.0.2 and earlier, i.e., they will call the AddSDIWorkitem Action with Force New = Yes, which is the equivalent of Force New = Yes in LabVantage 6.0.2 and earlier:

•	AddSDI Action when applying SDIWorkitems associated with Sample Templates.
•	"Add Tests" button on the Sample List page.
•	Automatic addition of Tests in a BioBanking Study.
•	CopySDIDetail Action when used "Quick Login" to add Tests by copying down from Product SDI to Sample SDI.

When set to No (default), Force New for the functionality listed above is set to Force New = No, and the Always Force New property below is enabled.

Always Force New

When set to Yes (and Retain Selective Force New is set to No), all areas of LabVantage that call the AddSDIWorkitem Action will be set to Force New = Yes. The Force New setting is disabled in the Test Method (SDI Workitem) Maintenance page and cannot be changed.

When set to No (default), Force New depends on the setting in the Test Method Maintenance page.

Require All Mandatory Approval Steps

Determines how Approval Steps are handled with regard to Data Set Status:

Value	Behavior
Yes	The system waits for all Mandatory Approval Steps to be completed before the Data Set Status transitions to "Completed". This is the default.
No	The system does not wait for all Mandatory Approval Steps to be completed before making a determination on the Data Set. Data Set Status transitions to "Completed" if final Approval is unambiguously determined (such as if the ApprovalFlag is P or F (Pass or Fail) and there is no other ambiguity).

Auto Add Instrument to Calibration Data Set

When set to "Yes" (default), the InstrumentId column of the SDIData table is populated with the Instrument associated with the Certification Sample, providing the Parameter List for the Sample is associated with the same Instrument Model (or Instrument Type).

WorkItemItem Rule

Defines the SDC or Reference Type used for Include Rules in Test Methods. See Test Methods → Rules.

Property

Description

Include Rule Column

Defines conditions under which Availability or Add Rules are applied.

Property	Description
Column Id	ColumnId to check when applying the Rule.
Column Display Value	Text used to display value in the Test Method Rule interface.
Editor style Id	Editor style to use for this interface.

Spec Rules Evaluation Options

When a Data Set is Cancelled, Remeasured or Retested, or Data Items are marked as Outliers, the relevant Specification Rules can be re-evaluated to arrive at a new SDI Condition based on these options:

Option	Description
Include Cancelled Data Sets	"Yes" includes Cancelled Data Sets when evaluating Specification Rules. "No" ignores them.
Include Remeasured Data Sets	"Yes" includes Remeasured Data Sets when evaluating Specification Rules. "No" ignores them.
Include Retested Data Sets	"Yes" includes Retested Data Sets when evaluating Specification Rules. "No" ignores them.
Include Outlier Data Items	"Yes" includes Outlier Data Items when evaluating Specification Rules. "No" ignores them.

In the OOB configuration, these options are set to "No" (ignore) in the Sapphire Product node. If required, backward-compatibility can be maintained using these options.