/
(Multi Level Cascade) Selecting Warehouse Location for Stock Delivery Orders

(Multi Level Cascade) Selecting Warehouse Location for Stock Delivery Orders

This document describes how to use the Multi Level Cascade (MLC) field to manage warehouse location selection for stock delivery orders.
Each delivery order is represented by a Jira issue, and selecting the correct warehouse location ensures accurate logistics coordination and inventory tracking.

You will also learn how to use several features in TGNG app such as:

Introduction

In a global company with warehouses located in multiple cities across regions, managing stock deliveries requires precise and standardized location data.
To avoid manual errors and to support downstream logistics processes (e.g. routing, regional stock allocation, performance reporting), a Multi Level Cascade custom field named "Location" is used in the stock delivery issue.

To standardize this input and prevent inconsistencies (e.g. "NYC" vs "New York"), a Multi Level Cascade field named "Location" is used with 3 levels:

  • Region (e.g. North America, Europe, Asia)

  • Country (e.g. USA, France, Vietnam)

  • City (e.g. New York, Paris, Hanoi)

This helps ensure clean, consistent data across all requests and improves automation and reporting capabilities.

image-20250707-101628.png

Prerequisites

  • User logged into their account, installed Table Grid Next Generation App

  • User created a related Jira project and issue

  • User had the admin role on Jira

  • User had a database system such as: MySQL, Postgres, SQL Server, etc.

  • An existing data source configured using TGNG app: https://tablegrid.atlassian.net/wiki/spaces/TGCD/pages/2229046

  • A Multi Level Cascade custom field named "Location" must be created with 3-level hierarchy.

Post-condition

  • User can download/upload the Configuration for personal usage.

  • The selected Region / Country / City is stored in the Jira issue.

Conditions

  • Required fields are marked with a red asterisk *

  • User have to set the name of Column to be an exact match with Column of the database.

User need to type the correct statement for the “SQL query”. For example:

SELECT column1, column2, ... FROM table_name;

  • Each grid must contain at least 1 column, or else it will show the pop-up message “table-config-column-config-required”.

  • The database table name must be distinguished. If not, the system shows a pop-up message:

    “Table wasn't created

    Maybe table with this name already exists in the database”.

  • The database table name can only contains alphanumeric characters and underscores.

Use Case Flow Diagram

Connect to “Location” data source

You need to have an existing data source that contains data of regions, countries, cities.

Basic Flow

Actions

Actions

1

Click Add Data Source in Data Source

image-20241113-040303.png
2

Fill all required information in Data Source

image-20250705-110225.png
3

Click Test Connection to examine the connection between Database and Jira

4

Click Save to save information of Data Source 

Exceptional Flow

Users can’t connect to database

Continued from step #3 in the Basic Flow:

Step

Description

4a

An “Errors” message appears 

Use case stops.

Configure “Location” Multi Level Cascade Field

Basic Flow

Actions

Actions

1

Click Add Field in Multi Level Cascade Configuration screen

image-20250707-084115.png
2

Fill information for Name = “Location”

3

In Configuration - Levels, select “Location” as Data Source

image-20250707-084404.png
4

In Configuration - Levels, click + button to add level

5

User fill information for Label and Identifier

Type “Region“ as Label and type “region” as Identifier

Type SQL query:

select * from Locations

Click Get data

In Display column field, select “Region” to display value in this level

image-20250707-084801.png

Click button to save the level configuration

6

In Configuration - Levels, click + button to add level

7

User fill information for Label and Identifier

Type “Country“ as Label and type “country” as Identifier

Type SQL query:

select * from Locations where Region = '{level:region:Region}'

In Display column field, type “Country” to display country values in this level

If you use placeholder (example: {level:region:Region} in level configuration, you have to type name of Display column instead of selecting.

image-20250707-090814.png

Click button to save the level configuration

8

In Configuration - Levels, click + button to add level

9

User fill information for Label and Identifier

Type “City“ as Label and type “city” as Identifier

Type SQL query:

select * from Locations where Region = '{level:region:Region}' and Country = '{level:country:Country}'

In Display column field, type “City” to display country values in this level

If you use placeholder (example: {level:region:Region} in level configuration, you have to type name of Display column instead of selecting.

image-20250707-090957.png

Click button to save the level configuration

10

Click Save to save the field configuration

image-20250707-091128.png

Exceptional Flow

Users click “Cancel” and click “Yes” while saving the config

Continued from step #9 in the Basic Flow:

Step

Description

10a

The system will automatically come back to the “Multi Level Cascade Configuration” page

Use case stops. 

Apply “Location” Field To Issue Screen

  1. Open the configured project and click “Create Issue” button

  2. Select value for levels in Location field

image-20250707-101324.png

  1. Click “Save” to save value for Location field

  2. Click “Create” to create issue

Result:

image-20250707-101554.png

Conclusion

Using a Multi Level Cascade field for warehouse location selection helps ensure accurate, consistent, and structured data entry in every stock delivery order. It reduces human error, simplifies reporting, and enables smarter automation in logistics workflows.

Feel free to adapt the hierarchy to ensure the right warehouse team receives your order and helps keep our stock movement efficient and traceable.