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.
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.
- Map Values
- Completing the Matrix tab
Map Value form - Completing the Matrix tab
- Completing the Configuration tab
Complete the fields on this tab to guide your inputs on the Matrix tab and define the possible values returned by this map value.
- Completing the Pages & Classes tab
Identify what is known about the class of each page that is referenced on other tabs. See How to Complete a Pages & Classes tab for basic instructions.
- Configuring property evaluation in a decision tree
The run-time result of a decision tree can depend on the value of a property or the optional, third parameter of the Property-Map-DecisionTree method.
- Unit testing a map value
You can test a map value individually, before testing it in the context of the application that you are developing. Additionally, you can convert the test run to a Pega unit test case.