Jadu Connect: Identify Jadu Central Fields to Retain and Put Into Jadu Connect

To carry Jadu Central data forward into subsequent forms, you need to identify what Jadu Central data needs to be stored in Jadu Connect. The data from your Jadu Central fields goes into a corresponding Jadu Connect field. These fields each have a data type associated with them. For more information, see the table defining each field type available in Jadu Connect.

Determining Which Field Data from your Jadu Central Form Needs Storage in Jadu Connect

Things to consider:

  • If accessing the data in a subsequent form, store it in Jadu Connect for later use
  • If the data exists in the form to help the submitter answer other questions, that field may not be necessary later in the process.

Example: A Yes/No question that conditionally shows another group of fields may not need to carry forward to the next form in the process; therefore the data doesn't need to send to Jadu Connect.

Reviewing Existing Fields Available in Jadu Connect for Jadu Central Data Storage

Re-using your Jadu Connect fields across case types helps reduce the length of the field list when adding fields to the case type forms, making it easier to identify necessary fields.

There is a small subset of universal fields available to users. To see a list of these fields and their uses please visit: Global Jadu Connect Fields

Considerations Before Requesting New Fields from OIT

  • Field Names are specific to a unit, with the exception of Global Fields.
  • Field Name best practice: Keep field names simple so they can be re-used by multiple case types within your category. 
    •  For example: a form for requesting a new training course includes a Course Type question to indicate if the course should be in-person or online, and another form used to request a new position includes a Type of Hire question. A generic Jadu Connect field called Request Type may work well for both case types and re-used across your additional future case types. 
  • Field Type: Field types do not always need to match between Jadu Central and Jadu Connect. See the table below for best practice on which field type to ask for in Jadu Connect.

     Jadu Central

    Jadu Connect 


    Date Date

    Required if the date is used in a Jadu Connect rule or if the date passes back to a date field in a subsequent form.

    Example: Sending a reminder email based on a date.

    Date Text  Stores a date as static text.
    Dropdown Text The value or the label can pull into subsequent Jadu Central forms and displayed in editable text fields or display fields. 
    Integrated  {varies}  Each integrated component outputs a different data type. Base the Jadu Connect field type selection on this output.
    Text (or Display) Area  Text Area  Stores large amounts of text. 
    Text (or Display) Field  Text  Stores small amounts of text. 
    {varies} Email 

    Required if the Jadu Central text field contains an email used in a Jadu Connect rule.

    Example: Sending an email from Jadu Connect.

    {varies} URL  Stores a URL that can create a hyperlink for use in a Jadu Connect email.

Completing the Jadu Connect Setup Request Form

After completing steps 1-3, you may request additional fields as necessary. To request new fields from OIT, fill out the Jadu Connect Setup Request Form.


Last modified