SDL Desktop - Reports - User Defined Reports

User Defined Reports

In recent updates we have added RTF User Defined Reports to Zoning and Code Enforcement.  This functionality will allow you to create your own letters and reports based on the values on the application or inspection, much like a mail merge from the datagrid.  Although they do have some limitations, such as using columns, this should greatly increase your reporting options.  If you don't like our violation notice you can create your own.  All print outs can be saved as pdf attachments much like our internal reports  Note we have added this to several other forms: Escrow, COAH, Projects, Complaints.  Please let us know of any other form you would like to added.

All files are word documents saved as a .RTF (Rich Text Format) type.

It is recommended to use an image for your entire header, Town seal and contact info.

All images must be saved as a .bmp (bitmap)

Settings for margin widths can be set in the options

On the Form

Any form that has the control pictured below will allow you to add User Defined Reports.  The “Manage Reports” link will allow you to Add/Edit/Delete your reports for that application type.  Each application type will have it’s own list of reports, so a Zoning Application Form will have a different list then the Zoning Board Form. Once you have your reports added you would click “View” to see the report filled in with that application's data.  Checking the “Add As Attachment” box will add the report to that application’s attachment list after you view the report

Report Management

Clicking “New” will open an attachment form and allow you to select your RTF file.  This will copy the file to the SDL server so all users will have access.  Once you add the file, any changes you make to your local copy will not affect the file in SDL.  You will need to either read your local copy or click “Edit” on the management form to make changes to the copy on the SDL Server.  When you add your RTF document, make sure to fill in the “Description” field as this is what will display on the application control (pictured below).

The Edit button will only work if you have Microsoft Word installed on your computer.

Creating your Reports

To create your report, open Word and either copy over the letter that you want to use or edit another report that you want to emulate. The report works by adding field names to the RTF document that represent the fields on the Application in the format of [!FIELDNAME].  When you run the report it will find any matching field names and put the value of that field onto the report.  So [!OwnerName] will show the application's owner name when you view the report. 

Note: Holding Shift and clicking VIEW on the Application will provide a list of available fields or use teh link on the Report manager form. Make sure you save the document as an .RTF by clicking “File” at the top left, then “Save As” and then select the file type as .RTF.

Example RTF Document

Example of Final Report

Settings

There are a number of settings located in the module options. For instance, you can set the margins and the recursion level. Margins are based on our report settings so 1 inch is 1400. If you want half inch margins, set the value to 720. The recursion level decides how deep into the application object you want to dive. 2 should be enough, but you can enter a higher number to get access to more information on the form.  

Tips

-When you view the fields available a text file called FieldTemplates.txt gets created in the technical support logs folder.  Go to Help Menu | Technical Support logs to get to the folder

-As stated only .bmp images can be used in the RTF.  All images get put on the left side of the report so if you want something on the right add white space to your image on the left side

-Due to issues with columns it is recommended you use an image of your document header, once again this must be a .bmp (see example below).

-You can also use an image for the signature area if you would like.

-All reports can have a date printed on them by adding [!DatePrinted] as a tag