Skip Ahead to:<\/strong><\/p>\n Overview<\/a><\/p>\n Navigation<\/a><\/p>\n Define Master Lists<\/a><\/p>\n Default Master Lists<\/a><\/p>\n Defining Master Lists Relationships<\/a><\/p>\n Associating Form Fields using Master Lists Relationship<\/a><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n In the application, various master lists are available. The application allows maintaining these Master Lists that are activated in the organization and within projects i.e. you can add, change, or remove any values from the Master lists.<\/p>\n The Master Lists feature enables you to:<\/p>\n In the left navigation panel, expand the Apps<\/strong> menu and select Account Space<\/strong>. <\/a>Hover over the Process Governance breadcrumb at the top, expand the Process Governance<\/strong> module, and select Master Lists<\/strong>.<\/p>\n Note:<\/strong> If you’ve onboarded after version 8.13, the Process Governance<\/strong> module will display ‘Account Space’<\/strong> instead, and it will be available under the Administration<\/strong> module.<\/p>\n Prerequisite: <\/strong>The Master Lists module should be available to add and edit Master Lists in the Administration.<\/p>\n To modify a Master List, click the Edit\u00a0<\/strong>icon under the Actions column of the required Master Lists. After the Master Lists are added, you can only modify the Sort By at the level where the Master Lists were created i.e. Organization or Project.<\/p>\n Once the Master Lists are added, they will be listed in the Master Lists view.<\/p>\n Active\/Inactive<\/b>: Use the <\/span>Active<\/b> toggle to mark values as active or inactive.<\/span><\/p>\n You can also export\/import values from XLS, XLSM or CSV files or export the existing list for bulk updates.<\/span><\/p>\n Currently, icons added to Master List values are displayed in the following areas for enhanced visibility:<\/span><\/p>\n Project Level<\/b><\/p>\n Organizational Level<\/b><\/p>\n Project Listing<\/strong>: Provides quick visual cues for the Projects<\/span><\/p>\n User Listing<\/strong>: Provides quick visual cues for the Users in the Organization<\/span><\/p>\n Dashboard<\/strong>: Displays icons alongside text in dropdown fields in the chart setting for better contextual understanding.<\/span><\/p>\n Values configured at the organization level will flow along with their associated icons to the project level.<\/span><\/p>\n Following are a few of the default Master Lists and their descriptions:<\/p>\n Project Type<\/b>: Create project types to categorize projects and templates when creating them. For example, SAP implementation, maintenance projects, and so on.<\/p>\n<\/li>\n Unit of Measurement (UOM)<\/b>: Create a Unit of Measurement to add effort estimates\u00a0or\u00a0user story\u00a0estimates. For example, FP (Function Points) for Effort Estimation.<\/p>\n<\/li>\n User Levels<\/b>: Create broad groups for\u00a0user access in the hierarchy. Different users in the application have access to different Workspaces, Modules Groups, Modules, and Features of the application depending on their role within the organization. Access levels determine what data users can view, create, and edit.\u00a0<\/span><\/span><\/p>\n<\/li>\n<\/ul>\n See Defining Master Lists Relationship to set relationship between two Master Lists, which enables to select values in one Form field, depending on the value selected in another field of a workitem. This also requires fields to be associated in the required Form of the workitem.<\/p>\n Following are some rules that are to be considered for Master Lists created in the organization’s hierarchical tree structure.<\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n Consider the following scenario where the Root Organization is the parent organization. Assume that the child organizations of the parent organization are Sub-Organization1 and Sub-Organization2. In the above diagram, Root Organization and Sub-Organization1 are one hierarchical tree structure and Root Organization and Sub-Organization2 is another hierarchical tree structure.<\/p>\n The rules that apply to all the items in the Master Lists are mentioned below:<\/p>\n For example<\/strong>: Assume that in Sub-Organization1 there is a master list item named: Item1. And if you try to create a master lists item with the same name in the Root Organization, then there is an option in which, that particular item in the Sub-Organization1 is displayed only in the Root Organization. A confirmation message is displayed when you try to do so.<\/p>\n For example: Assume that in Sub-Organization1 there is a master list item named: Item1 and also in Sun-Organization2 there is a master list item named: Item1. In such a situation, you cannot create a master list item named: Item1 in the root organization.<\/p>\n For example<\/strong>: Assume that in the Root Organization, there is a master list item named: Item 2, and in Sub-Organization1 there is a master list item named: Item1. If you try to modify the name of the master lists item named Item2 with Item1 then two things happen:<\/p>\n <\/a>For example:<\/strong> Assume that in the Root Organization, there is a master lists item named: Item 2. Then when you switch context to Sub-Organization1 you can view Item2 but you cannot modify\/delete Item2.<\/p>\n You can configure Form fields defining relationships between them using the Master Lists. This enables Form fields in workitems to display a dynamic list based on the selection in one field.<\/p>\n For example, assume there are two Master Lists-\u00a0Industry Type<\/strong>\u00a0(consider as Parent Master List) and\u00a0Functional Area<\/strong> (consider as Child Master List). You have defined a Master Lists Relationship between these two fields in the Change Request Form. When a Business Analyst creates a Change Request and selects Financial Services as Industry in the Industry Type list. Depending on the functional areas mapped in the Master Lists Relationship, the areas will be displayed in the Functional Area Lists, such as Banking,\u00a0Insurance, and\u00a0Loans.<\/p>\n Prerequisites<\/strong><\/p>\n The Master Lists module should be available for adding and editing Master Lists Relationships in the Administration.<\/p>\n The Master Lists\u00a0are created between which you want to define the relationship.<\/p>\n<\/div>\n To create a Master Lists relationship:<\/p>\n To add or delete any values in the Parent or Child Master lists, go to Master List view and click the Detail<\/strong> link for the required Master List.<\/p>\n If Projects are allowed to add or remove Master List values (where\u00a0Allow addition of values at the project level<\/b>\u00a0option is selected in Master List Relationship created in the organization), the additional\u00a0Inherited Values<\/b> pane displays the inherited values as you select the Parent Master List value. For your project, you can add an inherited value associated with one Parent Master List value to another Parent Master List value, for example, E-Learning Functional Area associated with Education Industry Type can also be associated with IT Outsourcing Industry Type. Check the association between Parent and Child Master Lists before saving. On saving the Master Lists Relationship, it is listed on the Master Lists Relationship page.<\/p>\n <\/a>If projects are not allowed to edit the Master List relationship, it will be shown in the read-only view.<\/p>\n After the Master Lists Relationship is defined,\u00a0add a Form field<\/span>\u00a0(as the parent field which will control the child field, for example, Country) in the required\u00a0Field Segment,<\/span>\u00a0for example, Details.<\/p>\n When adding the parent Form field, select Dynamic List in the Data Type list and the Drop-Down box in the Control Type list. In the Dynamic List Type, select the Parent Master List, which is included and set in the Master Lists Relationship. When adding the child Form field, select Dynamic List in the Data Type list, Drop-Down box in the Control Type list, and then select the Master Lists Relationship that you have set.<\/p>\n When you are looking for the Master Lists you defined, note that the custom master list has ‘List’ suffixed after the Master Lists Name, for example, Country List.<\/p>\n<\/div>\n Now, for example, when you add a Change Requests, you will see the two Form fields, Industry Type and Functional Area. As you select an Industry in the Industry list, the Functional Area list will display the related areas.<\/p>\nOverview<\/h2>\n
\n
![\"\"](\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/Screenshot-2025-08-01-133255.png\")
<\/a><\/p>\n<\/a>Navigation<\/h2>\n
Define Master Lists<\/h2>\n
\n
\n
\n
\n<\/span>Index-wise- Master Lists values are to be displayed in the ascending order of the Index code on adding the values to the Master Lists.<\/span>
\n<\/span>Alphabetically-Master Lists values should be displayed alphabetically in ascending order when the user has to select the field of an item.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n![\"\"](\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/Master-Lists_Details-1.jpg\")
<\/a><\/p>\n<\/div>\nManaging Master List Values<\/b><\/h3>\n
Adding Values to the Master List<\/b><\/h4>\n
\n
\n
\nFollowing are the categories you can choose icons from:<\/span><\/span><\/span><\/p>\n\n
![\"\"](\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/Screenshot-2025-08-01-151359.png\")
<\/p>\nModifying Master List Values<\/b><\/h4>\n
\n
Icon Usage Across the Application<\/b><\/h4>\n
\n
Notes:<\/b><\/h4>\n
\n
<\/a>Default Master Lists<\/h2>\n
\n
![\"\"](\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/Image.jpg\")
<\/a><\/p>\n\n
\n
\n
\n
\n
Defining Master Lists Relationships<\/h2>\n
![\"\"](\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/Build-New-1.jpg\")
<\/a><\/p>\n\n
\n
\n
Associating Form Fields using Master Lists Relationship<\/h2>\n
![\"\"](\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/Section_Fields_inside-details.jpg\")
<\/a><\/p>\n\n