/
Templates: Generated Documents

Templates: Generated Documents

Generated Documents

Generated Documents are licenses, permits , invoices, inspection reports, notices of various types (of intent to revoke a license, for example). They can be generated from within an activity, by a workflow, and can also be bulk downloaded for printing. Printing might be desired if a program area wants to send out snail mail notices, certified letters and so on.

This type of document uses system variables to capture MiEHDWIS content, and Word formatting and short programming snippets to maintain a consistent look for EGLE documents and to optionally display content that may not be present in the entity’s or activity’s record (examples include the 2nd line of an owner’s address, an entity’s co-owner’s information, or a septage hauler’s DBA).

KL&A’s KBA on Generated Document Management

Here you will find help on selecting and using variables to pull in MiEHDWIS information, using signatures, and pulling information from a dynamic form into a Generated Document.

Editing Generated Documents

Download Microsoft Word Document 

  1. Click on Maintenance. 

  2. Click on Templates. 

  3. Click on the template that needs to be updated.

  4. Click Download.

Edit Microsoft Word Document 

  1. Open the template in Microsoft Word.

  2. Edit the template. 

    1. For templates that display Error! Missing test condition. (see Word Field Codes, below)

  3. Save changes in folder that you can easily find. 

  4. Close the document.

  5. Test this document in a lower environment before uploading in Production

Re-Upload Edited Microsoft Word Document 

  1. While still on the Template Details window in MiEHDWIS, click Edit. 

  2. Click Choose File. 

  3. Locate file and click Open. 

  4. File name is now listed next to Choose File. 

  5. Click Save. 

  6. Confirmation appears, “Successfully updated template.” 

  7. It is strongly recommended that, after uploading the new template, you use the Generate Sample Document to give it a trial run. You will be asked to provide an entity ID and an activity ID. In both fields you can also start typing the entity or activity name to find what you want to use. Check over the sample to make sure everything populated as expected and that the format of everything looks the way you want it to.

Word Field Codes

When you see a generated document template with the Error! Missing test condition. message like the one below, do not worry, there is no error.

WordFieldCodes_exp.png

Some generated documents are designed to pull in MiEHDWIS fields which may or may not be populated. One example is the second line in a street address, as in the image above. If the field is populated, we want it to be displayed, and if it is not populated, we don’t want anything displayed. That is called Conditional Visibilty. There is conditional logic in this document. It has been added by way of using Word’s Field Codes. This is what is actually there, behind the scenes:

WordFieldCodeDisplayed.png

What that bolded piece says is “If there is an Address Line 2 in the entity record, display it, otherwise don’t”.

To be able to see the Field Codes, or if you’d rather NOT see them, you can control this yourself. In Word, go to File, Options (all the way at the bottom left), clicking on Advanced in the left menu of the Word Options box, scrolling down to Show document content and checking (or unchecking) Show field codes instead of their values, then clicking OK.

 

#10 Window Envelope Parameters

Use the settings below to guarantee a template’s address will appear in the right place for this type of envelope, and will not move depending on content.

Word_WindowEnvelope10_Parameters.png

 

 

Here are some handy tips and tricks:

Still need help? Submit a ticket to the Internal MiEHDWIS Help Desk and someone from our team will get back with you.