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:
- Can
D_pyEmailAddressesByFilterValue(or the composer) be aware of the calling context - action and target field? - If not, is there a supported way to provide a different recipient source per field/context?
- If not customizable, what’s the recommended Constellation pattern for a controlled forward-to list?
Thanks a lot!
