Hi @Srinivas1254 The @ParthaSarathy solution is smart, explanations are
very complete, I suggest you to use it. In another hand, I made an other
solution, but more technical and less understandable. Just to have a
link somewhere I put it here (it's a package) :
When we choose a model / delivery from a folder in the "delivery"
activity, the value (compute-string) used is not the real @_CS to fill
the label of the field, but the first displayed colunm Example (french
instance, sorry) : If I choose to display the "Typology" field first, it
fills the "label" f...
Hello @Milan_Vucetic Thank you for the explanations. Also, I have a
question about this specific part : in one of my cleanup processes, I
have a very long process for this update. It logs "Mise à jour des
statistiques RDBMS effectuée en 10h 1mn 52s", which means "RDBMS
statistics update done in 10h"...
Hi @Annie19 We used custom connector for special channel, it use
external API, requesting HTTP endpoint. So for us, processing 1000
messages at a time instead of 8 increased the speed considerably. It
depends of what you are doing in your connector, but you can see if
anything is wrong with the logs...
Hi @balakrishnavalavala I'm really sorry but I don't have a lot of
knowledge in SMS technical parts. I can't help you more for your problem
😞 My experience was on mobile push channel. Hope you'll find someone to
help you with your issue. Cedric
Hi @Annie19 We had this issue last week, so the answer is very easy : By
default, processDeliveryPart gets 8 messages each call. This can be
configured, but it is not a server paramareter. It's a delivery
parameter : Delivery additional parameters, then Delivery tab, and
Message batch quantity. This...
Hi @balakrishnavalavala I'm not sure this is the same problem, but we
had a similar issue with deliveryParts beeing processed 8 by 8 (default
wave length when not specified) in each MTAChild, and we looked in the
server configuration. But this is not where we had to look. In the
delivery itself > De...
Hi, You can use the proof sending, with substitution mode. With this
mode, you'll be able to provide a set of address that will replace some
randomly chosen original target addresses. This won't send any real
message to the actual target. But you must be sure that the target has a
least 1 final mess...
Hi @campaigns01 ,There are some tools to help you to comunicate to
Webapp, JSSP etc.)You can use HTTP request, with severals objects, you
can find some documentation here