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.
- Log in to Dev Studio.
- Review the default channel mappings by using the Clipboard tool to inspect the channelPrefixMapping property
on the Declare_MKTSystemSetting node-level page.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.
- 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.
- Run the SetChannelPropertyMappings activity under the
PegaMKT-System-Setting class and enter the current and new channel
mappings as parameters for the activity.
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). 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.
- After the activity runs successfully, review the channel mappings in the Clipboard tool to confirm that the channel map has been correctly updated.
- 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
- Identifier - <your_channel_name>
- Field Name - Channel
- Apply to - PegaMKT-Work-Offer
- Verify that the new channel shows in the list of available channels when you create a
new contact policy, as in the following figure:
- Save the contact policy and test the end-to-end behavior to verify that it works as expected.