You are here:
Rate Management Limits
Review the default limits for Rate Management components and their usage. To modify the set default values, ask your Salesforce admin to raise a support ticket.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with the Revenue Cloud Advanced license |
Rating Procedures
| Value | Default | Minimum | Maximum |
|---|---|---|---|
| The duration that a rating procedure can remain active | 10000 milliseconds | 1000 milliseconds | 60000 milliseconds |
| The duration that a rating element can remain active | 5000 milliseconds | 4 milliseconds | 10000 milliseconds |
| The number of rating elements in a rating procedure | 70 | 2 | 100 |
| The number of active decision tables in an org | 50 | 0 | 1000 |
| The maximum number of simultaneous lookup inputs allowed per HBPO-based decision table | 1000 | 1 | 8000 |
Rating Discovery Procedures
| Value | Default | Minimum | Maximum |
|---|---|---|---|
| The duration that a rating discovery procedure can remain active | 10000 milliseconds | 1000 milliseconds | 60000 milliseconds |
| The duration that a rating discovery element can remain active | 5000 milliseconds | 4 milliseconds | 10000 milliseconds |
| The number of rating discovery elements in a rating discovery procedure | 50 | 1 | 100 |
| The number of active decision tables in an org | 40 | 0 | 1000 |
| The maximum number of simultaneous lookup inputs allowed for an org’s HBPO-based decision tables of the usage type Rating Discovery | 2000 | 1 | 8000 |
Rate Card Entries
| Value | Limit |
|---|---|
| The number of rate card entries | 1200 |
| The number of adjustment records associated with tier rate card entries | 3000 |
Other Limitations
- Rate Management isn’t supported on mobile devices.
- Rate Management objects don't support the creation of records in Data Cloud.
- Rate Management doesn't support CSV-based decision tables and decision matrices.
- Attribute-based rate cards aren't supported in Usage Selling and Consumption Management. Avoid creating attribute-based rate cards or related customizations.
Did this article solve your issue?
Let us know so we can improve!
