Skip to main content

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

Optional: Configuring additional channels for use with contact policies

Updated on August 3, 2022

Contact Policy rules use an internal mapping scheme to support up to 10 channels to which the contact policy can apply. This mapping is not externally exposed. However, you may need edit the mapping if you created a new channel and want to use it in your contact policies.

  1. Log in to Dev Studio.
  2. Review the default channel mappings by using the Clipboard tool to inspect the channelPrefixMapping property on the Declare_MKTSystemSetting node-level page.
    Example channel mappings in the channelPrefixMapping property
    Example channel mappings
    In the figure above, channels 1, 3, 5, 7, and 8 are mapped. Channels 2, 4 ,6, 9, and 10 are unused.
    Note: The above figure shows an example configuration. Channel mappings may be different in your application, so you must review the mappings on your system before proceeding.
  3. Select an unused channel mapping that you can use to map the new channel, and take a note of how the channels are currently mapped.
  4. Run the SetChannelPropertyMappings activity under the PegaMKT-System-Setting class and enter the current and new channel mappings as parameters for the activity.
    Caution: The SetChannelPropertyMappings activity replaces the current channel map with a new map. The current channel mappings are not populated or validated by the activity. Because of that, you must enter the current channel mappings exactly as they exist in your system, to avoid issues resulting from incorrect mappings.
    The following figure shows the parameter values for the previously mapped channels 1, 3, 5, 7, and 8, as well as the new mapping for channel 9 (whatsapp).
    Running the SetChannelPropertyMappings activity
  5. After the activity runs successfully, review the channel mappings in the Clipboard tool to confirm that the channel map has been correctly updated.
  6. To ensure that the new channel is available as a selectable option on the Contact Policy rule, create a new Field Value with the following keys:
    • Identifier - <your_channel_name>
    • Field Name - Channel
    • Apply to - PegaMKT-Work-Offer
    For example:
    Example Field Value definition
  7. Verify that the new channel shows in the list of available channels when you create a new contact policy, as in the following figure:
    New WhatsApp channel in the contact policy definition
  8. Save the contact policy and test the end-to-end behavior to verify that it works as expected.
    • Previous topic Configuring additional channels for use with volume constraints
    • Next topic Defining real-time container triggers

    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. is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us