Back Forward About Map Value rules

Decision category
New  Matrix   Input  Results
Pages & Classes History   More...

Purpose

Use a map value rule 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 rule to record decisions based on one or two ranges of an input value. A map value rule uses a one- or two-dimensional table to derive a result.

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

Complete the Input tab before the Matrix tab. Optionally, to restrict the possible results to one of a small known list of literal constants, complete the Results tab before the Matrix tab.

Where referenced

Rules of five types can reference map value rules:

Access

Use the Policy Decisions slice (Decision slice) or Application Explorer to access the map value rules that apply to work types in your application. Use the Rules by Type Explorer to list all the map value rules available to you.

Delegation

After initial development and testing, selected map value rules can be maintained by line business managers rather than by application developers. The Matrix tab of the Map Value form provides managers access to the fields most often updated.

TipFor each map value rule 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. See How to build for change.

Category

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

Related topics How to unit test a map value rule
Standard rules Atlas — Standard map value rules

zzz Decision category
Help System home pageHome