[Constellation CS '25] Email composer – can we filter recipients in context?

User Experience
, , ,
1

Hi all,

We’re studying Inbound Email on Constellation Customer Service '25 for a banking client. We’re designing for Constellation, not porting their UI-Kit screen one-to-one, so we’re open to adapting the requirement if there’s a better supported pattern.

The outcome we need: when an agent forwards an email, the “To” dropdown content should come from a controlled predefined list (internal teams, CLM, escalation queues), not the full operator directory. This is specific to forwarding content.

What we’ve already explored:

  • Overriding D_pyEmailAddressesByFilterValue (Available=Yes) to return a curated predefined list: works.
  • But the data page gets no calling context i.e., not the action (Reply/Reply All/Forward), not the field (To/Cc/Bcc). So the override hits every recipient dropdown in every context, not just the Forward “To”.

Questions:

  1. Can D_pyEmailAddressesByFilterValue (or the composer) be aware of the calling context - action and target field?
  2. If not, is there a supported way to provide a different recipient source per field/context?
  3. If not customizable, what’s the recommended Constellation pattern for a controlled forward-to list?

Thanks a lot!

2

@VikasRaidhan, @MarcCheong, @Kamil_Janeczek apologies for the bulk tagging but your feedback would be extremely valuable :slightly_smiling_face:

3

  1. No. Neither the data page nor the composer widget receives the calling action (Reply/Reply All/Forward) or the target field (To/Cc/Bcc). The same override runs everywhere it is called, with nothing built in to tell one dropdown apart from another.

  2. No. There is no supported setting or parameter that lets Forward’s “To” field pull from one source while other fields keep the standard directory. Whatever the data page returns applies uniformly across every recipient dropdown in the composer.

  3. Enforce the restriction at send time instead of at the dropdown. Leave the data page returning the full list, and use the pzValidateSendRequest extension point, which does know the action being performed and the recipients chosen. Set it up so that when the action is Forward, it checks the To addresses against your approved list and blocks the send with an error if any address falls outside that list. This relies on an extension point Pega already supports, so the standard composer stays intact.