Getting Started with Document Templates

by James Doof

This page contains screenshots from Disco ICT v1 and will be updated shortly.

In this video we discuss how to create, upload and generate document templates. We delve into what's inside a document template and give you a starting point for creating your own. We also see how disco can automatically discover documents using the document dropbox and automatically file scanned-in documents into the correct job, user or device.

Here are some generic forms you can use to get started:

Incident Statement - Used to collect statements from users (eg. in the case of damage to a device). The document could then be used for insurance forms when an incident statement is required.

Recommended Settings:

  • Id: Incident
  • Description: Incident Statement
  • Scope: Job
  • Job Types: All
  • Job Sub-Types: All
  • Always Flatten Form: Yes

Repair Quote - Used to generate a quotation for the repair of devices. Insurance excess logic is also present (hint: update the excessCost value in the expression at the top of the page to match those in your organisation).

Recommended Settings:

  • Id: RQ
  • Description: Repair Quote
  • Scope: Job
  • Job Types: Hardware - Non-Warranty
  • Job Sub-Types: All
  • Always Flatten Form: Yes
  • Filter Expression: JobComponents.count() > 0

Insurance Claim - A sample iBroker insurance form which can be used to submit insurance claims to iBroker.

Recommended Settings:

  • Id: iBrokerClaim
  • Description: iBroker Insurance Claim
  • Scope: Job
  • Job Types: Hardware - Non-Warranty
  • Job Sub-Types: All
  • Always Flatten Form: Yes ('No' if you want to keep making changes after generation then)
  • Filter Expression: JobMetaNonWarranty.IsInsuranceClaim


Some useful hints:

  • The Document Dropbox is used to upload scanned-in documents for discovery by Disco. It is located in you Disco data store which you can view in the Configurations > System menu.
  • You will need a PDF editor (such as Adobe Acrobat) to create or modify forms within a PDF document.
  • Curly Brackets ( '{' and '}' ) indicate the beginning and end of an expression.
  • A tilde ( '~' ) at the beginning of an expression indicates that any errors can be safely ignored. If no tilde is present and an error occurs the error message will be displayed in the form field.
  • QR codes can be embedded into generated documents. The codes can be detected when the document is scanned in and then used to file a document into the correct job, device or user. QR codes also help the detection algorithm split a bulk-import of pages in, and even re-order the pages correctly. To add a QR code to your document, create a square text-box field named 'DiscoAttachmentId' on each page you want detected.
  • Uploaded documents which failed QR code detection can be manually assigned from the Undetected Pages area.
  • You can view the import status of documents being imported in the Import Status area.

Useful Links

Expression Evaluation

Spring.NET Framework