#Revenue Cloud87 discutindo

Hi everyone, 

I'm currently working on attribute-based pricing in Salesforce Revenue Cloud and came across a scenario I'd like some guidance on. 

For example, I have an attribute called Color. If Color = Blue, I want to apply a 5% discount. This pricing rule should apply to every product in my product catalog. 

Using Price Adjustment Schedules , the pricing adjustment is tied to a specific product. This works well for a small catalog, but in a large product catalog with thousands of products, creating and maintaining separate Price Adjustment Schedules for each product is time-consuming and difficult to manage. 

Is there a way to define the pricing logic once and have it apply to all products instead of configuring it product by product? 

I'd appreciate any suggestions or best practices. Thanks!   

@* Salesforce Revenue Cloud * 

I have a scenario when the Product A added to the quote and i try to add any other product then i should have a error. Also if i have added other products then i should not be allowed to add a Product A. Can this be done just with RCA configurations or CML?

Does anyone know if to disqualify a product, we strictly need to create a Product disqualification record?

The use case I have is that we want to replace entitlement policies with disqualification rules, and basically we have a custom field on the product2 object, we want to disqualify (and hide in our storefront) all products that don’t have an specific value on that picklist field (value != goodValue). 

All examples I could find involved creating records for the disqualification standard object, and I want to know if that is the only way. Category disqualification is not applicable as we still want to see those specific categories on the storefront, only products hidden.

If there is no way to do that then I would need to create a disqualification record for each product I want to disqualify, which would be a lot of tech debt. 

Hi everyone,

I’m facing an issue with Renewal Opportunities in Revenue Cloud.

Assets are created successfully after Order Activation, and Amendments are also working correctly. However, the Renewal Opportunity is not being created, even though the Create and Update Renewal Opportunities flow is active.

Has anyone faced a similar issue or knows what configuration needs to be checked for Renewal Opportunity creation?

Any suggestions would be really helpful. Thank you! 

I have created a product category disqualification.  But, under quote when I click "Browse Catalogs" that particular category is visible.  I have even refreshed decision tables(Product Qualification, Product Disqualification) but still it isn't working.  Can anyone help me?     @* Salesforce Revenue Cloud * 

We are using Agentforce Revenue Management (RCA). Our client uses Quote Line Groups with ramped segmentation. When we contract the quote, we get assets with asset state periods for each segment.

When we create a renewal quote using Renew Asset Action for a contract, renewal quote gets created without any groups and segments. Although the original asset has three segments, renewal quote creates lines without original groups and segments. It creates only quote line for only one year although the original contract was for three years. 

If there is no out of the box solution, how can this be accomplished?

Is there any out of the box solution to create renewal quote with the original contract term and segments with future renewal dates.

Hi Team,

I have a question regarding the use of Salesforce Record-Triggered Flows in Revenue Lifecycle Management (RLM).

I'm trying to determine whether a Record-Triggered Flow can be used to dynamically update the List Price and Total Amount based on specific business conditions.

In my use case, the List Price is not fixed—it depends on different combinations of field values. For example:

•  If Jurisdiction is populated, then the List Price should be XXX. 
•  If both Market and Jurisdiction are populated, then the List Price should be YYY. 
•  Additional combinations may result in different List Prices. 

My current thought is to implement this logic using a Decision element in the flow to evaluate the conditions, followed by Assignment

elements to set the appropriate List Price and recalculate the Total. 

Then how we can use in pricing prodecedure ?? 

Or Pricing procedure override my flow list price.??