5th step: Result and invoice template - LabCollector

Search Knowledge Base by Keyword

5th step: Result and invoice template

You are here:
← All Topics

The next step is to create a result or report template.

LSM has multiple report types.  These include

1) Results / Processing Results
2) Invoice
3) Batch
4) Chain of Custody

 

You can create reports and invoices templates to personalize documents that you will deliver to your customers.
The lab can edit template pages for results and invoices. The editor offers numerous options to customize templates. 
Each type of report has slightly different options and each is available at different times while doing an LSM job

The chain of custody and batch reports are designed as typical internal reporting documents.  These are accessible via the LSM interface, but not the LSMRemote.  The Results and Invoice reports are designed to be sent to customers/clients, partners and are accessible through the LSMRemote.

A template is related to a test and an invoice. For multiple assays in a project, different templates can be applied, for both the normal results report and the processing results report.

Within the LSM admin menu navigate to Admin > Preferences > Result and Invoice Templates.

Here we create a results form.
The example in the picture is simple. However, note that the editor allows HTML, images, special characters and has a special copy and paste options for programs such as MSWord.
Note the use of tags will be replaced by information from the job. For example ##job_number## will be replaced by the job number assigned to the particular job.

List of tags available:

Results template / Processing template
##results## – Will be replaced by results narrow table
##results_extended## – Will be replaced by results wide table
##process_extended## – Will be replaced by processing parameters table
##details## – Will be replaced by results detailed table
##matrix## – Will be replaced by results matrix
##samples## – Will be replaced by samples list
##requester_name## – Will be replaced by requester name
##requester_address## – Will be replaced by requester address
##requester_email## – Will be replaced by requester email
##job_number## – Will be replaced by job number
##job_date## – Will be replaced by job date
##job_param## – Will be replaced by job custom parameters
##job_submitter## – Will be replaced by the job submitter’s name
##operator_name## – Will be replaced by operator name
##validator_name## – Will be replaced by validator name
##protocol_name## – Will be replaced by protocol name
##protocol_description## – Will be replaced by protocol description
##report_number## – Will be replaced by report unique identifier
##labname## – Will be replaced by lab name
##reagents## – Will be replaced by reagents list
##equipments## – Will be replaced by equipments list

Invoice template
##details## – Will be replaced by invoice details
##requester_name## – Will be replaced by requester name
##requester_address## – Will be replaced by requester address
##requester_email## – Will be replaced by requester email
##job_number## – Will be replaced by job number
##job_date## – Will be replaced by job date
##job_submitter## – Will be replaced by the job submitter’s name
##invoice_number## – Will be replaced by invoice number
##invoice_date## – Will be replaced by invoice date
##tax_number## – Will be replaced by requester tax number
##purchase_order## – Will be replaced by job purchase order

Batch report template
##details## – Will be replaced by batch samples list
##batch## – Will be replaced by batch


CoC report template

##details## – Will be replaced by Chain of Custody (CoC) list
##requester_name## – Will be replaced by requester name
##requester_address## – Will be replaced by requester address
##requester_email## – Will be replaced by requester email
##job_number## – Will be replaced by job number
##job_date## – Will be replaced by job date
##job_submitter## – Will be replaced by the job submitter’s name

Dynamic tags
Any parameter can be used as tag adding ## around it. e.g. ##tag_name##

6th step: Create a test in the LSM