Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Configuring additional channels for use with volume constraints

Updated on May 30, 2022

Volume constraints limit the number of actions which are offered to customers, for example, to comply with corporate or regulatory guidelines. Volume constraints can apply per action, per action property, or per channel. If the default channels do not fulfill your requirements, you can create additional channels for use with volume constraints.

  1. Log in to Dev Studio.
  2. In the Application Explorer, switch to the PegaMKT- class, as in the following figure:
    Application explorer
  3. Click Data ModelField Value.
  4. Open a field value, for example, Channel Email.
  5. Click Save as.
  6. Enter a label for the new channel, for example, Telemarketing.
  7. In the Add to ruleset list, select the ruleset for your custom rules. By default, this is <your implementation application>-Rules.
  8. Click Create and open.
  9. Click Check out.
  10. In the Translate To field, enter the name of the new channel, as in the following figure:
    Sample channel
  11. In the History tab, in the Description field, enter a new description for the channel, for example, Field value for the Telemarketing channel.
  12. Save and check in your changes.
  13. In the Application Explorer, switch to the PegaMKT-System-Setting class.
  14. Click TechnicalActivity.
  15. Open the SetChannelPropertyMappings activity.
  16. Click Private edit.
  17. In the Parameters tab, add the new field value in one of the unused rows, as in the following figure:
    Sample field value
    Note: The parameter value is case-sensitive.
  18. Click Save.
  19. Click ActionsRun.
Result: You can now use the new channel in your volume constraints and contact policies, as in the following figure:
Sample volume constraint

    Have a question? Get answers now.

    Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

    Did you find this content helpful?

    Want to help us improve this content?

    We'd prefer it if you saw us at our best.

    Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us