Hi @_Manoj_Kumar_!
Sure thing:
The use-case is that we are currently implementing supression rules on our commercial email sendouts in ACC V7. Although the built in pressure type typology rule seems obvious to use, it has some limitiations that we are considered draw backs for us.
The built in requires that we set a contact date in the delivery. However, our way of working is, that every delivery we send is scheduled directly in the workflow and made from delovery templates, and thus no contact date is set. In a previous question I raised, someone suggested to set the contact date dynamically by comuting it in the field. This is a good suggestion, BUT the issue here is, that it requires the delivery activity in the workflow to be a type recurring delivery. This again does not fit into our way of working and we have earlier intentionally chosen not to work with recurring delivery types AT ALL. This leaves 2 types: Continuous delivery, and the standard delivery type actions. Issue here is, that they do not allow for a dynamically computed contact date.
So that leaves me in kind of a void and currently considering my options here. 1 options is therefore to create a control type typlogy and use that to update a recipient field that counts amount of emails received per day. addtionally we will have a utility workflow that will clear this field once a day so the counter is reset every day as well. Lastly we will either simply make a filter in any commercial workflow to filter out recipient who received more than the threshold amound of emails before sendout. OR alternatively create yet another typology that exists later in the execution order to filter these out.
That's the use-case. Currently I am stuck though, with creating a control type typlogy rule that is able to update recipient fields and seeking help to accomplish that.
Thanks.
