Attribute Mapping setup when quote not created in Oracle CP
Summary:
How to setup Attribute Mapping of a Price Attribute when the Pricing Portal is called via Calculate Price REST Endpoints?
Content (please ensure you mask any confidential information):
Hi CPQ specialists,
Is there a difference in the way we setup the Attribute mapping of a pricing Attribute when the pricing engine is called via REST API, meaning the quote/transaction does not exist in CPQ? Or the setup is the same and when calling the REST API, we will have to enter a value for the Attribute mapped to the pricing Attribute as parameter?
As of today, it is not planned to create any transaction in CPQ, only to setup the pricing portal and have external CRM calling it via REST API to get the price.