The flags MustExist and MustBeAnswered can have an influence on the way prices are retrieved based on the way the request is done.

Basically, price calls can be done in the context of a BRC, with the pricing method CPE used as an alias or inside a macro, or via an external API call. Depending on this call, the two flags, set at the Pricing Method level, can be either taken into account or ignored by the engine.

The following table summarizes the different engine behaviors depending on the situation:

PRICING CALL	ENGINE BEHAVIOR
In a configuration, FP.value.PRGM is used as alias of a BRC	MustExist and MustBeAnswered flags are checked.
In a configuration, use of getObjectByCPE on FP.value.PRGM via an external API	MustExist and MustBeAnswered flags are not checked.
In a configuration, use of getObjectByCPE on FP.value.PRGM within a macro	MustExist and MustBeAnswered flags are not checked. (This call can be considered as an external API call)
Matching	MustExist and MustBeAnswered flags are not checked.
Direct UI price calls	MustExist and MustBeAnswered flags are not checked. (uses getObjectByCPE on FP.value.PRGM via an external API)

Reference: For more details on getObjectByCPE, please refer to the CPQ Macro Language Reference Manual.