Revenue Cloud Developer Guide
j
No Results
Search Tips:
- Please consider misspellings
- Try different search keywords
Procedure Plan Evaluation Input
Input representation of the details used to evaluate a procedure plan
definition.
- JSON example
-
This example shows a sample request to evaluate a
procedure plan definition by using a primary
object.
{ "idList": ["a01DU000000BylcYAC"], "evaluationDate": "2024-07-08T10:15:30.000Z", "sectionType": ["PricingProcedure"], "subSectionType": ["Revenue"] } -
This example shows a sample request to
evaluate a procedure plan definition by using a definition
name.
{ "evaluationDate": "2024-07-08T10:15:30.000Z", "sectionType": ["PricingProcedure"], "subSectionType": ["Revenue"] } - Properties
-
Name Type Description Required or Optional Available Version evaluationDate String Date when the evaluation is applicable. This property value must be within the date range when the procedure plan definition is effective. Required 62.0 idList String[] List of record IDs of the procedure plan definitions to be evaluated. Required only if you’re invoking the Procedure Plan Evaluation By Object (POST) API . 62.0 sectionType String[] Name of section to be evaluated. Valid values are: - PricingProcedure
- ProductDiscoveryProcedure
- ProductQualificationProcedure
- PricingDiscoveryProcedure
- DiscountSpreadServiceProcedure
- RatingProcedure
- Custom
- RatingDiscoveryProcedure
Optional 62.0 subSectionType String[] Name of subsection to be evaluated. Optional 62.0 The combination of the sectionType and subSectionType property values must be unique for every procedure plan version.