Main difference between Property-Map-Value method and Property-Map-ValuePair method is
-
(a) Property-Map-Value calls a Rule-Obj-MapValue once, and Property-Map-ValuePair calls it twice
-
(b) Property-Map-Value can call a Rule-Obj-MapValue and pass a single row input, and Property-Map-Value-Pair can call a Rule-Obj-Map Value and pass two row inputs
-
(c) Property-Map-Value can call a Rule-Obj-MapValue and pass a single row input, and Property-Map-Value-Pair can call a Rule-Obj-Map Value and pass a single row input and single column input
-
(d) Property-Map-Value can call a Rule-Obj-MapValue and pass a single row input, and Property-Map-Value-Pair can call a Rule-Obj-Map Value and pass multiple row inputs
Property-Map-Value calls a Rule-Obj-MapValue with a single row input. Property-Map-ValuePair calls the same Rule-Obj-MapValue but passes a single row AND a single column input, allowing lookups that depend on two dimensions. Option A is incorrect about the number of calls. Option B incorrectly mentions 'two row inputs'. Option D incorrectly mentions 'multiple row inputs'.
In Pega/PRPC, Property-Map-Value is used for a simple one-dimensional lookup: it calls a Rule-Obj-MapValue and passes a single row input (one key) to retrieve a value. Property-Map-ValuePair is used for two-dimensional table lookups: it also calls Rule-Obj-MapValue but passes both a row input and a column input (a pair of keys) to pinpoint a value in a matrix-style mapping table. Option (c) captures this precisely. The other options misstate either how many times MapValue is invoked or how many inputs are passed, which doesn't match how these two rule-mapping mechanisms actually differ.