Bursting Broadcast C4C

[DAcker]

Hi all,

I don't understand the bursting feature in broadcasts in C4C.

I want to send a report to every ticket agent daily with a list of open tickets that are older then 3 days.

So I created a report with this condition, and I created a broadcast. I am new to the bursting feature in broadcast. I now want to chose dynamically the receiver of my braodcast (so should be the ticket agent), therefore I put "Agent (DPY_PROC_PTY)" in "Attribute For Email" field, that's the only field I can chose something.

If I test it nothing happens, I just get an error saying that the email address is invalid. I don't know where to start looking for the invalid email address and don't know if this feature works as I assume.

Would be happen to get an explaination how the bursting feature in broadcasts works...

Thanks in advance, best regards

Deborah

[former_member277097]

Hi Deborah,

Following the explanation provided by Nishanth, to use the Bursting feature in your Broadcast you must select an attribute (characteristic field) from the report, which should contain the e-mail addresses to receive the broadcast.
As per the description of your post, I understand you're using the field "Agent (DPY_PROC_PTY)" as attribute. However, this may not be a valid field, as it does not carry e-mail addresses but the agent name instead.

To fit your requirement, the best characteristic field to be used as attribute for Broadcast Bursting would be the field "E-Mail", or another field that carries e-mail addresses and fits better into what you're looking for.

Hope this helps,
Kind Regards
Marlon

[DAcker]

Hi marlon.grawer

thanks for your answer. But I cannot chose "E-Mail" as field in the broadcast. From where is the dropdown of the supported fields generated? Perhaps from the data source of the chosen report?

I can add in the report the addition attribute "E-mail" from the agent. But unfortunately, as separate field I cannot add it in a custom data source. So I assume, that my described use case is not possible with this feature?

BR, Deborah