You are implementing the Design Document for a large Enterprise Revenue Cloud project having multiple lookup price rules supporting a complex pricing requirement in the Build phase. During construction the customer discovers additional logic and external data stores that need to be incorporated in order to achieve the correct pricing in a particular set of use cases. You estimate the lookup price rules will need to be modified, additional rules will need to be created and API development will be needed. As an Implementation consultant what is the appropriate course of action that should take in this predicament?

Universal Containers has recently implemented and released CPQ to users in their production environment. After an extensive testing Cycle in a sandboxed environment. One of the automations implemented was to set every new quote created as "primary" at the time of creation in order to save clicks. Users immediately began to report errors when trying to create quotes in the production environment for the first time. What could have caused this issue? Revenue Cloud SP23

Universal Containers sell a product bundle named “Corporate IT Solutions”. One of the product options inside this bundle is named Hardware Firewall Universal Containers has a requirement where if the customer has purchased a hardware firewall in the past, the hardware firewall product option should be hidden while configuring the bundle. The CPQ admin has created a product rule to handle this requirement. What should the evaluation event of the product rule be set to?

Should Bundles be a scoping topic of discussion as part of a CPQ project?

Universal Containers sell boxes based on size, Price for a specific product is based on the selection of length and width and height, which cpq pricing functionality should be used here?