Content

Introduction

This article is meant to provide you with details about the extendedReach Custom Form Builder, used in Activities and Reports. If you have a question not addressed here, you can search at the bottom of this article in Related Topics or you can Contact Support.

Explanation and Purpose of Custom Form Builder

The Custom Form Builder is a tool used to create customized forms within activities and reports. This tool is an upgrade from basic Custom Fields. You can now create up to 200 fields, record narratives, and customize of the layout of forms.

Security Level Requirements and Access

You must be an Agency Administrator to access the “Administration” menu on the left side of your Workspace.

Enabling the Custom Form Builder

From an Activity Type or Report Type, click on Edit mode. Click on the General tab, and scroll down to Configuration.

Image: “Form Builder Advanced Options”

Place a check-mark in the box next to “Use Custom Form Builder”.

Creating a Custom Form

Click on the Custom tab to begin configuring the custom form.

Image: “Custom Tab”

“Custom Fields”

  • Add a Field

This is a Drag & Drop Interface. Add available fields found on the right side of the screen, to the the form by dragging and dropping each field into the “Add Fields Here” space, or by simply clicking on the field.

Image: “Custom Tab: Add a Field”

Field Name Description
Section Break Visually organizes information to be gathered.
Single Line Text This space will remain small for the visual cue that user should provide a short answer.
Date Date Field.
Time Time Field.
Number Number field. Could be used to capture time in minutes.
Dropdown User will be able to pick customizable values from a list.
Paragraph Increase this space of field for the visual cue that user should expand on answers.
Checkboxes User will be able to pick customizable values from a list.
Multiple Choice User will be able to pick customizable values from a list.
Signature If required, user can sign with a mouse or touch screen.

To delete a field, simply hover over the field and click on the red X that appears in the lower right hand corner of the box.

Image: “Custom Tab: Delete a Field”

  • Settings

Click on a field, and then click on the Settings tab to customize that field.

Image: “Custom Field Settings”

  • Label: Add labels to name each field.
  • Required: Check this box if you require this field to be completed before the user can continue.
  • See above Field Descriptions for more field customization details.

“Custom Subform”

This is an advanced option for extendedReach developers and can be ignored.

As always, be sure to SAVE your work.

Agency Use of Custom Form Builder

  • Compliance Checklist

Add activity or report with custom form to the Compliance Checklist. For complete instructions on adding an activity or report to the Compliance Checklist, please see Adding Activities/Reports to Compliance Checklist

  • Workflow

Go to compliance checklist within a case or home, and click on the revised report/activity. Complete form and continue with your workflow process. For more details regarding Workflow, please see our Creating, Approving, and Completing Activities and Reports (Workflow) Article.

  • Use Field Codes to push information into Microsoft Word Documents

Every time you create a new field in Custom Form Builder, a field code number is assigned to that field.

Image: “Custom Field Settings Field Codes”_

There are two ways you can use these numbers as field codes:

1. Pull data from a custom form field into a document or narrative on that same activity or report

For Activities: <YCF[FIELD #]>
For Reports: <PCF[FIELD #]>

2. Pull a field from the last activity/report of a specific type

Case Report Format: <CCREP-CustomField_Value_[FIELD #]-[Report Name]>
Case Activity Format: <CCACT-CustomField_Value_[FIELD #]-[Activity Name]>

For example, to pull the 25th field from the Fire Drill home report use <CCREP-CustomField_Value_25-Fire Drill>

For more details regarding adding Field Codes to documents and case notes, please see our article titled Field Codes.