Objects and Attributes Exposed to Syntax Scripts based upon the Syntax Type

Syntax Type enum	Syntax Type	Objects exposed	Purpose and usage
1	Job Code	Job, Laboratory, Client, RegistrationUser Although these objects are exposed in the syntax, it does not make any sense to use the following in the Job.Code generation: ActivatedUser, ArchivedUser, AuthorisationUser, FinalisationUser, OwnerUser, ReceptionUser, RegistrationUser, ValidationUser.	To generate a job code. The syntax used is the one in scope that has a Syntax Code of JOB_CODE_SYNTAX and a Syntax Type of Job Code.
13	Job Name	Job, Laboratory, Client, RegistrationUser Although these objects are exposed in the syntax, it does not make any sense to use the following in the Job.Name generation: ActivatedUser, ArchivedUser, AuthorisationUser, FinalisationUser, OwnerUser, ReceptionUser, ValidationUser.	To generate a job name. The syntax used is the one selected by the user from those in scope that have a Syntax Type of Job Name.
2	Sample	Sample, Job, Laboratory, Client, RegistrationUser Although these objects are exposed in the syntax, it does not make any sense to use the following in the Sample.Name generation: ActivatedUser, ArchivedUser, AuthorisationUser, FinalisationUser, OwnerUser, ReceptionUser, ReleasedByUser, ValidationUser.	To generate a sample name. The syntax used is the one in scope that has a Syntax Code of SAMPLE_NAME_SYNTAX and a Syntax Type of Sample.
3	Quote	Future use.	To generate a quote number.
4	Standard Lot	Laboratory, Standard, StatusChangedByUser	To generate a standard lot number. The syntax used is the one in scope that has a Syntax Code of STANDARD_LOT_SYNTAX and a Syntax Type of StandardLot.
5	Batch Code	Job, Laboratory, Client, BatchedByUser Although these objects are exposed in the syntax, it does not make any sense to use the following in the laboratory batch Job.Name generation: ActivatedUser, ArchivedUser, DispatchedByUser, OwnerUser, ReturnedByUser, SubcontractedByUser.	To generate a laboratory batch job code. The syntax used is the one in scope that has a Syntax Code of BATCH_CODE_SYNTAX and a Syntax Type of Batch Code.
14	Batch Name	Job, Laboratory, Client, BatchedByUser Although these objects are exposed in the syntax, it does not make any sense to use the following in the Batch (as a Job) Name or Code generation: ActivatedUser, ArchivedUser, DispatchedByUser, OwnerUser, ReturnedByUser, SubcontractedByUser.	To generate a batch job name. The syntax used is the one selected by the user from those in scope that have a Syntax Type of Batch Name.
6	Report	Report, Job, Laboratory, Client, CreationUser	To generate a report code. The syntax used is the one in scope that has a Syntax Code of REPORT_CODE_SYNTAX and a Syntax Type of Report. To generate a internal report code for workbook reports. The syntax used is the one in scope that has a Syntax Code of WORKBOOK_REPORT_CODE_SYNTAX and a Syntax Type of Report.
7	Invoice	Future use.	To generate a invoice number.
8	Statement	Future use.	To generate a statement number.
9	Report Request	ReportRequest, Job, Laboratory, Client, Although these objects are exposed in the syntax, it does not make any sense to use the following in the report request code or name generation: ReportedByUser. Note that if the report request contains multiple jobs, then the first reportable job is the one exposed to the syntax.	To generate a report request code. The syntax used is the one in scope that has a Syntax Code of REP_REQ_CODE_SYNTAX and a Syntax Type of Report Request. To generate a report request name. The syntax used is the one in scope that has a Syntax Code of REP_REQ_NAME_SYNTAX and a Syntax Type of Report Request. To generate an email subject for report emailing. The syntax used is the one in scope that has a Syntax Code of EMAIL_SUBJECT_TEXT and a Syntax Type of Report Request. To generate an email message for report emailing. The syntax used is the one in scope that has a Syntax Code of EMAIL_MESSAGE_TEXT and a Syntax Type of Report Request. To generate a report number for preliminary and final certificate reports. The syntax used is the one in scope that has a Syntax Code of REPORT_NUMBER_SYNTAX and a Syntax Type of Report Request. To generate a report number for internal workbook reports. The syntax used is the one in scope that has a Syntax Code of WORKBOOK_REP_REQ_CODE_SYNTAX and a Syntax Type of Report Request.
10	Report Filename	ReportRequest, ReportRequestReport, Job, Laboratory, Client, ReportTemplate	To generate a filename for reports. For example: ${ String folder = Preference.fetch("G6Folder") String lab = Laboratory.name.asEllipseValue String job = Job.name.asEllipseValue String rrt = ReportTemplate.code.asEllipseValue otherVar = folder + lab + "/" + job + "/" + rrt + "/r_" return otherVar }${yy}${MM}${dd}${HH}${mm}${ss}
11	Other	Laboratory, Sample, Job, Laboratory, Client, ActivatedUser, ArchivedUser, AuthorisationUser, FinalisationUser, OwnerUser, ReceptionUser, RegistrationUser, ReleasedByUser, ValidationUser Although these objects are exposed in the syntax, it does not make any sense to use the following in the Sample Code generation: ActivatedUser, ArchivedUser, AuthorisationUser, FinalisationUser, OwnerUser, ReceptionUser, ReleasedByUser, ValidationUser.	To generate a sample code. The syntax used is the one in scope that has a Syntax Code of SAMPLE_CODE_SYNTAX and a Syntax Type of Other.
12	Instrument Uploader	Laboratory, ConverstionScript, InstFileCategory	To generate an instrument upload code for all uploader items. The syntax used is the one in scope that has a Syntax Code of UPLOADER_CODE_SYNTAX and a Syntax Type of Instrument Uploader.

1

Job Code

Job, Laboratory, Client, RegistrationUser

Although these objects are exposed in the syntax, it does not make any sense to use the following in the Job.Code generation: ActivatedUser, ArchivedUser, AuthorisationUser, FinalisationUser, OwnerUser, ReceptionUser, RegistrationUser, ValidationUser.

To generate a job code. The syntax used is the one in scope that has a Syntax Code of JOB_CODE_SYNTAX and a Syntax Type of Job Code.

13

Job Name

Job, Laboratory, Client, RegistrationUser

Although these objects are exposed in the syntax, it does not make any sense to use the following in the Job.Name generation: ActivatedUser, ArchivedUser, AuthorisationUser, FinalisationUser, OwnerUser, ReceptionUser, ValidationUser.

To generate a job name. The syntax used is the one selected by the user from those in scope that have a Syntax Type of Job Name.

2

Sample

Sample, Job, Laboratory, Client, RegistrationUser

Although these objects are exposed in the syntax, it does not make any sense to use the following in the Sample.Name generation: ActivatedUser, ArchivedUser, AuthorisationUser, FinalisationUser, OwnerUser, ReceptionUser, ReleasedByUser, ValidationUser.

To generate a sample name. The syntax used is the one in scope that has a Syntax Code of SAMPLE_NAME_SYNTAX and a Syntax Type of Sample.

3

Quote

Future use.

To generate a quote number.

4

Standard Lot

Laboratory, Standard, StatusChangedByUser

To generate a standard lot number. The syntax used is the one in scope that has a Syntax Code of STANDARD_LOT_SYNTAX and a Syntax Type of StandardLot.

5

Batch Code

Job, Laboratory, Client, BatchedByUser

Although these objects are exposed in the syntax, it does not make any sense to use the following in the laboratory batch Job.Name generation: ActivatedUser, ArchivedUser, DispatchedByUser, OwnerUser, ReturnedByUser, SubcontractedByUser.

To generate a laboratory batch job code. The syntax used is the one in scope that has a Syntax Code of BATCH_CODE_SYNTAX and a Syntax Type of Batch Code.

14

Batch Name

Job, Laboratory, Client, BatchedByUser

Although these objects are exposed in the syntax, it does not make any sense to use the following in the Batch (as a Job) Name or Code generation: ActivatedUser, ArchivedUser, DispatchedByUser, OwnerUser, ReturnedByUser, SubcontractedByUser.

To generate a batch job name. The syntax used is the one selected by the user from those in scope that have a Syntax Type of Batch Name.

6

Report

Report, Job, Laboratory, Client, CreationUser

To generate a report code. The syntax used is the one in scope that has a Syntax Code of REPORT_CODE_SYNTAX and a Syntax Type of Report.

To generate a internal report code for workbook reports. The syntax used is the one in scope that has a Syntax Code of WORKBOOK_REPORT_CODE_SYNTAX and a Syntax Type of Report.

7

Invoice

Future use.

To generate a invoice number.

8

Statement

Future use.

To generate a statement number.

9

Report Request

ReportRequest, Job, Laboratory, Client,

Although these objects are exposed in the syntax, it does not make any sense to use the following in the report request code or name generation: ReportedByUser.

Note that if the report request contains multiple jobs, then the first reportable job is the one exposed to the syntax.

To generate a report request code. The syntax used is the one in scope that has a Syntax Code of REP_REQ_CODE_SYNTAX and a Syntax Type of Report Request.

To generate a report request name. The syntax used is the one in scope that has a Syntax Code of REP_REQ_NAME_SYNTAX and a Syntax Type of Report Request.

To generate an email subject for report emailing. The syntax used is the one in scope that has a Syntax Code of EMAIL_SUBJECT_TEXT and a Syntax Type of Report Request.

To generate an email message for report emailing. The syntax used is the one in scope that has a Syntax Code of EMAIL_MESSAGE_TEXT and a Syntax Type of Report Request.

To generate a report number for preliminary and final certificate reports. The syntax used is the one in scope that has a Syntax Code of REPORT_NUMBER_SYNTAX and a Syntax Type of Report Request.

To generate a report number for internal workbook reports. The syntax used is the one in scope that has a Syntax Code of WORKBOOK_REP_REQ_CODE_SYNTAX and a Syntax Type of Report Request.

10

Report Filename

ReportRequest, ReportRequestReport, Job, Laboratory, Client, ReportTemplate

To generate a filename for reports. For example:

${
String folder = Preference.fetch("G6Folder")
String lab = Laboratory.name.asEllipseValue
String job = Job.name.asEllipseValue
String rrt = ReportTemplate.code.asEllipseValue
otherVar = folder + lab + "/" + job + "/" + rrt + "/r_"
return otherVar
}${yy}${MM}${dd}${HH}${mm}${ss}

11

Other

Laboratory, Sample, Job, Laboratory, Client, ActivatedUser, ArchivedUser, AuthorisationUser,
FinalisationUser, OwnerUser, ReceptionUser, RegistrationUser, ReleasedByUser, ValidationUser

Although these objects are exposed in the syntax, it does not make any sense to use the following in the Sample Code generation: ActivatedUser, ArchivedUser, AuthorisationUser, FinalisationUser, OwnerUser, ReceptionUser, ReleasedByUser, ValidationUser.

To generate a sample code. The syntax used is the one in scope that has a Syntax Code of SAMPLE_CODE_SYNTAX and a Syntax Type of Other.

12

Instrument Uploader

Laboratory, ConverstionScript, InstFileCategory

To generate an instrument upload code for all uploader items. The syntax used is the one in scope that has a Syntax Code of UPLOADER_CODE_SYNTAX and a Syntax Type of Instrument Uploader.