Dependency Field

Note: The Dependency Field is an Enterprise Plan feature but can be added as an add-on for Growth Plan users. It is essential to configure the required metadata fields as "Use as Collection" for them to appear as dependency fields. Only metadata fields with "Use as Collection" properties will be available for selection. For configuration instructions, refer to Manage Metadata Fields.

A Dependency Field is a type of metadata field that establishes a hierarchical or conditional relationship between different fields within the system. This feature allows users to create and manage dependencies between fields, ensuring that the selection of one field dictates the available options in another.

Example

• Primary Field: Packaging Type (e.g., Bottle, Box, Bag)
• Dependent Field: Material Type (e.g., Glass, Plastic, Cardboard)
  • If "Bottle" is selected as the packaging type, the material type field options can be limited to "Glass" and "Plastic."
  • If "Box" is selected, the material type field option can be restricted to "Cardboard."

How do I set up a dependency field?

1. Log in to your ManageArtworks account.
2. Navigate to the Admin module.
3. Click the Dependency Field tab.
   
   
    
4. In the upper-right corner, click the Add button to create a new hierarchy.
   
   
    
5. A Add Dependency pop-up window will appear.
6. Enter details in the form:
   • Hierarchy Name: Provide a descriptive name.
   • Select Metadata Fields: Choose the metadata fields to include in the hierarchy (e.g., Brand, Category, Size) from the available list.
     • Note: You can select up to 8 fields. Only metadata fields configured with the "Use as Collection" option will appear in the list. For details on how to enable metadata fields as collections, refer to Manage Metadata Fields. 
   • Use the drag icon (::) to arrange the fields in the desired order. The topmost field will act as the primary field, and the others as dependent fields.
7. Once configured, click Create to finalize the hierarchy.

Data Mapping

After creating the hierarchy, you need to map data to it:

1. Click the Data Mapping button associated with the desired hierarchy.
2. Click Add Row to start mapping.
   
   
    
3. In the pop-up window, fill in the fields based on the hierarchy (e.g., Brand, Category, Size).
4. Fill in Data:
   • Click on each field to either select from existing options or enter new values. For example, clicking on the "Brand" field will show master data from Lists and Teams.
5. After filling out the fields, click Create to save the mapping.
6. Continue adding rows as necessary.

Example of Data Mapping:

• Category: Wafer | Brand: KitKat | Size: 10g
• Category: Prepared Dishes | Brand: Maggi | Size: 50g

End-User Behavior:

On the end-user side, when the user clicks the "Category" field, only relevant options (Wafer and Prepared Dishes) will be shown and if "Prepared Dishes" is selected, then "Brand" field will only show "Maggi."

Form Template Mapping

Dependency field hierarchies can be mapped to form templates, allowing dynamic management of form fields.

To Map a Dependency Field Hierarchy to a Form Template:

1. Navigate to the Create/Edit Form Template page.
2. Click Add Field.
3. Select Hierarchy from the list.
4. Click the drop-down icon and choose the desired hierarchy to add it to the form.
   • The fields from the selected hierarchy will be dynamically inserted.
5. Publish the template to update the changes.

Note:

• If a field from the hierarchy already exists in the form, the hierarchy will be linked, but the duplicate field won't be added.
• If a field linked to a hierarchy is removed from the form, the entire hierarchy will be removed.