Hey Danny,it will depend on your typology rules. If you have any
typology rule set to limit your deliveries based on your capacity to
handle the possible income messages that you'll receive after the
delivery, it could be applied to your workflow or adhoc communication
(if you want).In the other hand, if there are no typology rules set, I
assume that you won't have any limitations of that kind:Source:
Hey sonikad8559822,I think it's possible. You will just have to create a
link between your cus:recipients and your cus:services tables.For
drop-down fields: they are displayed on visual query editor when the
field has the enumeration property set. So, in order to do that, you
will have insert the following lines into your cus:services
Then, on your attribute label, you can add the enum
field just as the following: I think it should
work.Vipul Raghav, would it?Regards,Lucas.
Hey Sid,there's another thing that you should take into consideration
before doing that: converting the entirely html content into an image
file will probably give you some headaches with spam-check filters.
Depending on your delivery strategy it could ruin your domain's
authority.By the way, I think taht the only way to solve your issue is
by using external sources, like the CloudConvert API, to convert your
html into a png file. So you can import it back to your assets folder
via workflow. I'm...