Skip Ahead to:<\/strong><\/p>\n Overview<\/a><\/p>\n Navigation<\/a><\/p>\n Why It Matters<\/a><\/p>\n How It Works<\/a><\/p>\n How to Use List Values in Forms<\/a><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n The Lists 2.0<\/strong> menu is aimed at modernizing the way reusable dropdown values are managed across your Nimblework workspace. Traditionally, administrators and project managers used the Master Lists interface to define static dropdown values. Lists 2.0 enhances this concept by leveraging the flexibility and consistency of Form 2.0. By creating a List-type form<\/strong>, users can now define structured sets of options, like country codes, departments, or product types, through a cleaner, more intuitive form-driven approach.<\/p>\n Each list behaves like a simplified, focused form that is optimized for capturing and managing these values. Lists 2.0 makes it easier to govern dropdown data both at the project and enterprise level while improving usability, reusability, and traceability.<\/p>\n This menu displays only those forms that you create in Forms 2.0<\/strong> by setting the Type<\/strong> = List<\/strong>. These forms are specifically configured to function as reusable dropdown data sources rather than standard interactive forms. You can use this interface to manage the instance values that power dropdown fields.<\/p>\n This article outlines the purpose and usage of Lists 2.0, differences from Master Lists, how to define and manage list instances, and how these lists integrate into other forms.<\/p>\n Navigate to the project, hover over the top breadcrumb, expand the Configure<\/strong> module, and select Lists 2.0<\/strong>.<\/p>\n The Lists 2.0<\/strong> menu displays all the List-type forms<\/strong> that have been published via the Form 2.0<\/strong>.\u00a0Each List-type form listed here allows you to define and maintain its dropdown entries\/options. These options form the selectable values that appear in Lookup<\/strong> fields when configuring other forms. In essence, Lists 2.0 centralizes the management of dropdown data for consistency, traceability, and ease of reuse.<\/p>\n Within Lists 2.0:<\/p>\n The interface provides an intuitive way to maintain your dropdown lists without switching between different configuration areas. It’s optimized to make editing quick and controlled, depending on the origin of the list (project or enterprise).<\/p>\n List-type Form: Countries<\/strong> Think of this screen as a spreadsheet-like grid where each row is a predefined option that appears in a dropdown field when referenced by other forms.<\/p>\n Each change to a list (like adding or removing an instance) dynamically updates the available options in any form using that list via a Lookup field.<\/p>\n Some other examples can be:<\/p>\n Payment Method List: <\/strong>Credit Card, PayPal, Bank Transfer, Cash, Check, Cryptocurrency, etc.<\/p>\n<\/li>\n Issue Type List:<\/strong>\u00a0Bug, Enhancement, Task, Feature Request, Incident, Support, etc.<\/p>\n<\/li>\n Location List:<\/strong>\u00a0New York, London, Bangalore, Sydney, Tokyo, Paris, etc<\/p>\n<\/li>\n Employee Type List: <\/strong>Full-Time, Part-Time, Contract, Intern, Freelance, Temporary, etc.<\/p>\n<\/li>\n Region List: <\/strong>North America, Europe, Asia-Pacific, Middle East, Africa, Latin America, etc.<\/p>\n<\/li>\n<\/ul>\n Once your list is configured, you can use its entries in any Form-type<\/strong> form:<\/p>\n Form: Vendor Onboarding<\/strong> Imagine a Project Manager wants to allow users to select a country in a Vendor Onboarding <\/strong>form via a dropdown. Instead of configuring this manually or relying on legacy Master Lists, they use Lists 2.0 to streamline it.<\/p>\n Think of the Lists 2.0 interface like a spreadsheet: each row is a country, and each column can hold values like name, abbreviation, or custom metadata. These rows become selectable options in a dropdown menu elsewhere in the system. Now, whenever a Lookup field references the Countries<\/strong> list, users will see the exact values defined here. If the Project Manager later adds “France (FRA),” that option appears instantly in every connected form.<\/p>\n This makes dropdown lists dynamic and maintainable.<\/p>\nOverview<\/h2>\n
<\/a>Navigation<\/h2>\n
<\/a>Why It Matters<\/h2>\n
\n
<\/a>How It Works<\/h2>\n
Step 1: Create a List-Type Form<\/h3>\n
\n
![\"\"](\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/05\/List2.0-1024x396.png\")
<\/p>\nStep 2: Manage List Instances<\/h3>\n
![\"List](\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/05\/List-Listing-1-1024x348.png\")
<\/p>\n\n
![\"List](\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/05\/List-Instance-1024x606.png\")
<\/li>\nExample:<\/h3>\n
\nInstance entries: India (IND), Japan (JAP), Australia (AUS), Germany (GER), Canada (CAN) and more<\/p>\n\n
<\/a>How to Use List Values in Forms<\/h2>\n
\n
Example:<\/h4>\n
\nLookup field: Country<\/strong>
\nValues: Pulled from List-type form Country List<\/strong>\u00a0(India, France, Japan, etc.)<\/p>\n![\"\"](\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/05\/Country-List-1024x639.png\")
<\/p>\n\n