About Map Values
 

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 Process Modeler .
• 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.

Access

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.

Delegation

After initial development and testing, selected map values can be maintained by line business managers rather than by application developers. For each map value in your application, consider which business changes might require rule updates, and whether to delegate the rule to non-developers who then can make such updates directly.

For more details, see How to delegate a rule.

Category

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

	How to unit test a map value
	Standard map values

Decision category

Open topic with navigation