LogoLogo
Getting StartedDevelopersDeployment GuideGet Help
  • Quick Links
  • Welcome to Form.io
    • Getting Started With Form.io
    • Launch a Form
    • Overview of Form.io
  • Developer Tool Ecosystem
    • PDF Solution
    • Enterprise Form Builder
    • Form View Pro
    • The Security Module
    • Accessibility Compliance Module
    • Developer License
    • SQL Connector - Deprecated
    • Integration Libraries
    • Form.io CLI Tool
  • User Guide
    • Introduction
    • Form.io Developer Portal
    • Teams
    • Projects
      • Project UI
      • Project Settings
      • Stages
      • Multi-Tenancy
    • Resources
      • ResourceJS
    • Forms
      • Form Creation
      • Form Types
      • PDF Forms
      • Embedding a Form
      • Form Revisions
      • Form Settings
    • Form Building
      • Form Builder UI
      • Form Components
        • Component Settings
        • Basic Components
          • Resource as Select Component Data Source
        • Advanced Components
        • Layout Components
        • Data Components
        • Premium Components
          • Nested Forms
        • Custom Components
      • Logic & Conditions
      • Existing Resource Fields
      • Actions
    • Submissions
      • Accessing Submissions
      • Importing Submissions
    • Form.io eSignature - Coming Soon
    • Form.io Reporting Module
    • PDF Template Designer
    • Form View Pro
    • Form Manager
    • Enterprise Form Builder Module
  • Developer Guide
    • Introduction
      • Application Development
      • API Documentation
    • Form Development
      • Form Renderer
      • Form Builder
      • Form Embedding
      • Form Evaluations
      • Form Templates
      • Custom Components
      • Translations
    • JavaScript Development
      • JavaScript SDK
      • JavaScript Frameworks
      • JavaScript Utilities
    • Authentication and Authorization
      • SAML
      • OAuth
      • LDAP
      • Resource Based Authentication
      • Email Authentication
      • Two-Factor Authentication
    • Roles and Permissions
      • Field Match-Based Access
      • Field-Based Resource Access
      • Group Permissions
    • Integrations
      • Email Integrations
      • File Storage
      • Google Developer Console
      • eSign Integrations
      • Relational Databases
    • Modules
    • Fetch Plugin API
    • CSS Frameworks
    • Offline Mode
    • Audit Logging
  • Deployments
    • Self-Hosted Deployment
      • Local Deployment
        • Local File Storage
      • Kubernetes
      • Cloud Deployment
        • AWS Deployment
          • AWS Lambda
          • Form.io/AWS Elastic Beanstalk End-To-End Encrypted Deployment
        • Azure Deployment
          • Azure App Service
            • Azure MSSQL Connector - Deprecated
          • Azure Virtual Machine
          • Azure Kubernetes Service
          • Set up the DB
        • GCP Deployment
          • GCP Cloud Run
      • On-Premise Deployment
      • Enterprise Server
      • PDF Server
    • Deployment Configurations
      • DNS Configuration
      • Load Balancer Configuration
    • Licenses
      • License Management
      • Library Licenses
    • Portal Base Project
      • Portal SSO
      • Portal Translations
    • Maintenance and Migration
      • Changes to Premium Libraries
  • FAQ
    • FAQ
    • Tutorials & Workflows
      • Password Reset
      • Dynamic Select Filtering
      • Approval Workflow
      • SSO Email Token
      • Embedding A Video
      • Data Source Validation
      • Select Data Source Options
      • Nested Form Workflows
        • Nested Wizard Forms
      • Save as Draft
      • Role-Based Conditions
      • Custom Component
      • Dynamic Radio and Select Box Values
      • Override CKEDITOR
    • Errors
    • Examples
    • License Utilization Checks
  • Contact Us
Powered by GitBook
On this page

Was this helpful?

  1. User Guide
  2. Form Building

Existing Resource Fields

Use the Existing Resource Fields to add pre-defined fields to your forms.

PreviousLogic & ConditionsNextActions

Last updated 4 months ago

Was this helpful?

What are Existing Resource Fields? Existing Resource Fields are components within your Resources that can be re-utilized in other Forms or Resources using the Form Builder. Existing Resource Fields carry over component settings, like validation and input masks, that have already been pre-configured within your Resource.

Why should I use Existing Resource Fields? Existing Resources Fields are very beneficial in the fact they save time and allow consistency when using the same type of fields and settings. This concept allows users to create a dedicated resource for pre-configured fields. This is an efficient way of configuring fields that you know will be needed for other Forms or Resources.

How do I use Existing Resource Fields? Start by creating a Resource and adding certain field types. Configure the field settings as needed.

Create a new Form or Resource. The Existing Resource Fields are found at the bottom of the Form Builder component list. Clicking the Existing Resource Field tab will display each Resource within your project. Clicking a Resource within this list will display the components found in that specific Resource. Simply drag and drop a field just like any other component to add to a form.

Any field added to a Form from the Existing Resource Field list will carry over all pre-configured settings. Below is an example of a Date/Time field configured for Date of Birth input with required validation and a tooltip to provide users information about the field. Because this field was configured within a Resource, the Date of Birth field can be added to any Form or Resource and retain all settings and configuration.

Best Practices & FAQ

  • Create a specific Resource to house all of your pre-defined fields

  • Existing Resource Fields can be further modified once they have been added to a Form.

  • Create your own 'Groupings' of components by adding a Layout component to your Resource and adding your fields within the layout type. Dragging the Layout component will also include the fields saved within that layout. This can be beneficial when a grouping of fields will be reutilized within other forms. For example, creating a User Information panel with fields like Name, Email, Phone Number, etc.

  • Existing Resource Fields do not link Resources and Forms together

  • If a field within a Resource is updated or changed, that field will not dynamically update if it has previously been added to other Forms. Users will need to remove and add the field again to their Form or Resource to update the settings. Alternatively, you can manually update the field settings instead of deleting and adding the field back to the form from the Existing Resource Field list.

  • The field's property name can only be changed from the Resource side. Ensure the Property Name is correct within the Resource before using the field.

Create your pre-defined fields within a Resource