---
title: "Create a value map using the cascade select configuration"
canonical: "https://support.appfire.com/space/SUPPORT/89135902/Create%20a%20value%20map%20using%20the%20cascade%20select%20configuration"
format: markdown
---
# Description
[Substitution variables](https://appfire.atlassian.net/wiki/spaces/CSOT/pages/68752493) are of great help when it comes to configuring field values for issues. Want to use a field value using a value map? For instance, you want the Jira user to see one value on the screen, but internally, you need a different value to be set in a custom field. How can this be done easily? This shows how to do this using a cascade select configuration in an non-typical way. [CSOT-103](https://appfire.atlassian.net/browse/CSOT-103) has more details on the configuration access capability use in this example.
# Example of a value map
| **Key** | **Value** |
| --- | --- |
| joe | joe@xxx.com |
| sally | sally@xxx.com |
## Steps
The following steps demonstrate how to configure Create on Transition, regex inspection of the project using a built-in function:
| **Step** | **Example** |
| --- | --- |
| Create a cascade select custom field
- Field is not intended for use
- It is just for saving configuration values |  |
| Add a parent entry with the key value of your map |
| Create a child entry with the value part of your map |
| Repeat for each key and value pair |
# Use substitution values
Suppose your cascade select custom field is called: **myMap**
| **Example** | **Result** |
| --- | --- |
| %values_myMap(joe)% | joe@xxx.com |
| %values_myMap(sally)% | sally@xxx.com |
| %values_myMap(%entry%)%
- when using multiple issue creation
- processing the **sally** entry | sally@xxx.com |