Custom Fields - NEXGEN 311

Custom Fields - NEXGEN 311

Custom fields can be created in the 311 Service settings and are used to gather more information from users when they are submitting a service request through the NEXGEN 311 Portal. See below for instructions on how to add custom fields to your 311 Portal's submission forms.
Info
Note: If you set custom fields, they will show up on ALL actions and cannot be removed from individual actions. Before adding a custom field, determine if that field is needed on every type of request.

What are Custom Fields in NEXGEN 311?

Custom Fields vs. Standard Fields

Custom fields in NEXGEN 311 are additional fields that users can create to supplement the information collected from a user/customer that  submits a service request from the portal. By default, service requests submitted from the 311 portal will always ask users for the following standard fields:
  1. Location/Address
    1. A location dropdown or address field will be visible depending on the problem type configuration
  2. Description of the Issue/Request
  3. Image
The 3 fields listed above will display on incoming service requests under NEXGEN standard fields as explained in the table below.

311 Portal Field Name

NEXGEN Field Name

Where is the Field Found?

Description of Issue

Description

On a Service Request record’s Description field in the top zone or in the Info tab if on mobile devices.

Location

Location

On a Service Request record’s problem area section underneath the top zone or in the Info tab if on mobile devices.

Address

Incident Address

On a Service Request record’s problem area section underneath the top zone or in the Info tab if on mobile devices.

Image

Attachments

On a Service Request record’s Attachment’s zone or tab if on Mobile devices.


Custom fields on the other hand, will be visible below the "Add an Image" section of a 311 Portal form. 

NEXGEN supports 11 different types of fields (see Custom Field Types and Definitions section) and organizations can add as many custom fields as necessary to forms. When building a submission form for the 311 Portal, the system uses a combination of Custom Fields configured at the Action level, and Custom Fields configured for All Actions.

To better understand how the 311 module utilizes these components to build a form, please review the image displayed below.

Custom fields for all forms will always display before custom fields for a specific action. Standard fields will always appear at the top of the form and contact information fields will always display at the end of a form.



Add Custom Fields

Add a Custom Field to all Submission Forms

Follow the steps below if you have a specific custom field you would like ALL USERS to populate regardless of the request they are submitting (examples can include Location Notes, Priority, 
  1. Navigate to the Custom Fields module by clicking Settings > Integration > NEXGEN 311 > Custom Fields.
  2. Click the + Add button on the right.
  3. Enter Custom Field details.
    1. Attribute Name – Custom Field name. Make sure this is friendly to end users.
    2. Attribute Type – Identifies the kind of field. For field types, see Appendix A.
    3. Checkboxes:
      1. Required – Customer must fill out to continue.
      2. Public – Information is available for the public to view on a 311 Portal ticket.
  4. Click “Save.”

Add a Custom Field to a Specific Problem Type/Action Submission Form

  1. Navigate to the Actions module by clicking Settings > Integration > NEXGEN 311 > Actions.
  2. Find the Action that you would like to modify and click the pencil edit icon.
    1. If you would like a custom field for a specific Problem Type, NEXGEN recommends creating a new action specific to that problem type to capture the appropriate fields without impacting all submission forms.
  3. Click +Add under the Custom Fields zone.
  4. Enter your Custom Field details.
    1. Attribute Name – Custom Field name. Make sure this is friendly to end users.
    2. Attribute Type – Identifies the kind of field. For field types, see Appendix A.
    3. Checkboxes:
      1. Required – Customer must fill out to continue.
      2. Public – Information is available for the public to view on a 311 Portal ticket.
      3. Click “Save."

Custom Field Types and Definitions


Field Type* (Depending on your site design, the field types may have different styling, however, the functionality will be the same as described below)

Use Case

Text – Allows end users to enter text. Examples include location notes, equipment information, or other free text fields. Recommended for text that is short.

Text Area - Allows end users to enter text in multiple lines. Best if you are asking users to submit a form that requires long message or justification of details. Recommended if an entry requires a lot of text.

Checkbox – Allows end users to check a flag. Can be useful if you want an easy way for users to identify a request (ex. internal, Non-urgent, Follow-up, etc). Not recommended for “Yes/No” question types.

Number – Allows users to enter a decimal number. Users can also adjust their entry by using the side arrows. Best for fields where a specific number or cost is needed.

Dropdown – Allows users to select one option from a dropdown. Options must be configured as comma separated options to appear correctly in the portal.

List Box – Allows users to select multiple options from a dropdown. Options must be configured as comma separated options in order to appear correctly in the portal.

Email – Allows users to enter an email address. The system will validate the address. Best if a form requires an additional email address, or if you would like to enforce the entry of a valid email address. Users can add their email information at the bottom of any form without this field.

Date – Allows users to select a date from a dropdown calendar. Users must select from the calendar dropdown; they cannot type in a date.

Time – Allows users to select a time from a dropdown menu. Users must select; they cannot type in a time.

Date/Time – Allows users to select a time and date from the dropdowns.

HTML – Allows you to enter a read only message. You can use HTML to separate your fields into sections.


    • Related Articles

    • Edit or Delete a Custom Field - NEXGEN 311

      Custom fields are fields in NEXGEN 311 that can be customized to obtain more information from your 311 Portal users. These fields in the Custom Fields section of the 311 Service settings and are applicable to all service request submission forms. If ...
    • Configuring NEXGEN 311 Languages - NEXGEN 311

      Users have the ability to display 311 Portal lookups in different languages to accommodate for non-English-speaking NEXGEN users. This feature is useful for giving these users the option to read and complete Service Request forms on the 311 Portal, ...
    • Configuration Guide - NEXGEN 311

      Please see the document linked below for our NEXGEN 311 User Guide.
    • Edit Label Captions - NEXGEN 311

      You can edit text displayed on the 311 Portal to suit your organization's needs. This includes displayu text for fields as well as text that appear =s when a user attempts to bypass a required field. For instructions, see below. Navigate to the 311 ...
    • Edit Notification Templates - NEXGEN 311

      Notification templates help build out the email and text notifications that users receive if they decide to follow a 311 Service ticket. These templates are prebuilt into the NEXGEN site, but if desired, you can edit the text and merge fields ...
    • Recent Articles

    • Video Guide: How to Use NAMI Dashboards

      Where to Access NAMI Changing Tabs and Interactive Functionalities <br> How to Filter, Drill Down, and View Underlying Data <br> Example Flow Using Blue and Green Tabs
    • June 2026 New Feature Webinar

    • Latest Phone Release - Version 2.0.5 (June 2026)

      Phone Application Updates Asset Inventory Users can now type in an asset QR code in the search bar to find an asset in addition to scanning. (#23758) Form A quick action button to create a form will now be visible in the Hotspot. Users can tap to ...
    • iPad Version 3.0.6 (April 2026)

      iPad Updates Bug Fixes Resolved comments cutting off on mobile devices. (#24035) Fixed the issue of a Flag label unintentionally showing when completing assets. (#26071) Users should now be able to request items that are at zero quantity from the ...
    • Version 16.2.1 (04.30.26)

      Web Application Update - May 2026 Web Version 16.2.1 Release items related to a support ticket submissions will be included in parenthesis at the end of a line item. NEXGEN queries should now plot on the map as expected. (#27028) The Show In Store ...