AddSDISpec
Description:
Adds Specifications to SDIs.
Input Properties
sdcid
Description:
Identifier of the SDC.
Required:
Yes
keyid1
Description:
Identifiers of the SDIs.
Required:
Yes
keyid2
Description:
Identifiers of the SDIs.
Required:
Only for multi-key SDCs.
keyid3
Description:
Identifiers of the SDIs.
Required:
Only for multi-key SDCs.
specid
Required:
Yes
Comments:
Identifier of the Specification.
specversionid
Required:
Yes
Comments:
Version number of the Specification.
applyspec
Required:
No
Comments:
Determines if spec will be applied or not(i.e. to create sdidataitemspecs if applied), default YES. If spec is applied, it is evaluated as well against the data entered.
oosgeneratingspec
Required:
No
Comments:
Determines oosgenerating flag of SDISpec, if not passed in action input takes from Spec definition
autoapplyflag
Required:
No
Comments:
Determines autoapplyflag flag of SDISpec, if not passed in action input makes it 'N' considering it as instance data
savespecversionascurrent
Required:
No
Comments:
if this property value is passed in action input as "Y" and spec version is passed as 'C' or empty value, then specversion is saved as 'C' in SDISpec table and it is not applied even though it is a non customer or OOSgenerating Spec. Default value of this property is considered as "N". If for a Spec both savespecversionascurrent and applyspec property values are passed as "Y", then AddSDISpec will throw invalid property error.
rsetid
Description:
Identifier of the RSet passed into this Action.
Required:
No
Comments:
This is useful if you have created an RSet in another Action and want to use those values in this Action.
For example, suppose you have created an RSet in Action-001, and the Rset contains SDCId and KeyId values from multiple SDIs. You want to pass these values into Action-007. Rather than specifying all of these values in Action-007, you can simply specify the RSetId from Action-001.
An added advantage is that if data are locked in the Action-001 RSet, they will be locked in Action-007 as well.
applylock
Description:
Determines whether or not (Y/N) data are locked during Action processing.
Required:
No
auditreason
Description:
Auditing information recorded in the "Reason" column of the TraceLog table.
Required:
No
auditactivity
Description:
Auditing information recorded in the "Activity" column of the TraceLog table.
Required:
No
auditsignedflag
Description:
Auditing information recorded in the "SignedFlag" column of the TraceLog table.
Required:
No
auditdt
Description:
Auditing information recorded in the "ModDt" column of the TraceLog table.
Required:
No
Additional Information
Additional information concerning this Action:
To add multiple Specifications to multiple SDIs, use this example as a guideline:

sdcid = Sample
keyid1 = S01;S02;S03
specid = QC;Final
specversionid = 1;3
applyspec = Y;N
This adds QC (Version 1) and Final (Version 3) to Samples S01, S02, and S03.

This Action inserts a new record in the SDISpec table.

sdidataitemspecs are created for QC only and sdispec.appliedflag is set as 'Y' for it. For the Spec 'Final', sdidataitemspecs are not created and appliedflag is set 'N'

This action enhanced in 8.4 to evaluate Spec on data after adding SDISpec, for the Specs which are applied

Copyright © 1999-2016 LABVANTAGE Solutions, Inc.