Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

About Map Values

Updated on May 17, 2024

Use a map value to create a table of number, text, or date ranges that converts one or two input values, such as latitude and longitude numbers, into a calculated result value, such as a city name. Map value rules greatly simplify decisions based on ranges of one or two inputs. Use a map value to record decisions based on one or two ranges of an input value. A map value uses a one- or two-dimensional table to derive a result.

Through cascading — where one map value calls another — map values can provide an output value based on three, four, or more inputs.

Complete the Configuration tab before the Matrix tab.

Where referenced

Rules of five types can reference map values:

  • In a flow, you can reference a map value in a decision task, identified by the Decision shape in a flow.
  • In an activity, you can evaluate a map value using the Property-Map-Value method or Property-Map-ValuePair method.
  • A Declare Expression rule can call a map value.
  • A map value can call another map value.
  • A collection rule can call a map value.


Use the Application Explorer to access the map values that apply to work types in your application. Use the Records Explorer to list all the map values available to you.

After you complete initial development and testing, you can delegate selected rules to line managers or other non-developers. Consider which business changes might require rule updates and if delegation to a user or group of users is appropriate. For more details, see Delegating a rule or data type.


Map values are part of the Decision category. A map value is an instance of the Rule-Obj-MapValue rule type.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us