You are here:
Set Up a Custom Pricing Step for Attribute-Based Pricing
After you implement the Apex classes, calculation procedures, and matrices included in the Attribute/Volume Based Pricing DataPack, create a new step in the Default Pricing Plan.
After you create your custom pricing plan step, see attribute-based pricing in action: Attribute Based Pricing at Runtime.
- Go to Vlocity Product Console.
- In the Dashboard in the Pricing area, click the search icon next to Pricing Plan, and press Enter. The Default Pricing Plan is displayed.
- Click on the Default Pricing Plan, and then click Pricing Plan Steps in the sidebar.
- Click New Item.
-
Enter the following information.
Property
Value
Notes
Name
Calculate Attribute Based Pricing
If you create multiple steps for each type of attribute-based pricing, change the Name to reflect each type.
Description
Custom pricing step
Implementation Name
CustomPricingPlanStepImpl
The Apex class included in the Attribute/Volume Based Pricing DataPack
Method Name
GetMatrixPrice
The method in CustomPricingPlanStepImpl.cls
Sequence
[0-9]
Must be less than 10 All attribute-based pricing steps must occur before the Initialize Pricing Context step.
Active
Click to select
The Active flag is honored by the Pricing Plan Service, so you can use this flag during testing to turn steps on or off.
Parameters
Click the pencil icon and follow the instructions below.
These parameters are passed to CustomPricingPlanStepImpl.cls.
- Create Pricing Plan Step Parameters and review Additional Pricing Plan Step Parameters.
Create Pricing Plan Step Parameters
If you do not see the parameters field, confirm that your deployment is on the Summer '18 or later release of Salesforce Industries Communications, Media, and Energy. If it is, then you must complete the post-install steps.
In the Parameters dialog, enter as many parameters as needed. To get started, click the plus icon.
The table below lists the parameters that are used in the calculation procedures and matrices that are supplied as part of the Attribute/Volume Based Pricing DataPack.
First Box |
Second Box |
Notes |
|---|---|---|
ProcedureName |
Enter the name of the calculation procedure |
If you have imported the Attribute/Volume Based Pricing DataPack, enter the appropriate calculation procedure from the list below:
|
MatrixName |
Enter the name of the calculation matrix |
If you have imported the Attribute/Volume Based Pricing DataPack, enter the appropriate calculation matrix from the list below:
|
UseDisplayTextForValues |
false |
(Optional) The default behavior is for PricingPlanHelper.cls to evaluate attribute display labels when looking for a match. You can change this behavior using the UseDisplayTextForValues parameter. To use attribute picklist item's values rather than display labels, set this to |
Additional Pricing Plan Step Parameters
The following table lists additional parameters that are supported for source-target or range attribute-based pricing.
First Box |
Second Box |
Notes |
|---|---|---|
Path1 |
[Root<Parent1<Parent2...<Product] |
Create as many paths as needed to specify the context in which you want the child product in a bundle to be priced. See the example below. |
RangeFields |
[API field names on Order Product, Quote Product or Opportunity Product] |
Range fields must be of data type Number. Multiple values must be separated by semi-colons. |
RangeAttributes |
[Product attribute names] |
Separate multiple values using semi-colons. |
Target Products Within a Bundle Using Target Path
If you want to price a product differently based upon the bundle it is in, pass the target product and path using a parameter in the pricing plan step. The target path must be formatted as follows:
[root product name]<[parent1 product name]<[parent2 product name][...]<[product name]
For example,
Back to School Student Offer<Home Internet Solution<DSL Service
You can have multiple path parameters. Each path named in the first box in the parameter dialog must be listed in your SourceTargetAttributePricingMatrix in the Target Product Name column for the appropriate product configuration. For more information on how to enter this data in your matrix, see Source Target Attribute-Based Pricing.
