Thanks @navinKumar,Could you please go to the recipient folder and click
on "Display contents of sub-folders":Then, if you sort by last
modification date, you should see your recipients.The folder can be
displayed by a right click into the list, configure list...,
double-click on the folder link.If the folder information is empty, the
recipient is "nowhere" and the foreign key of the folder should be
updated for this recipient in order to add it to a folder.If you need
further information, feel ...
Thanks @navinKumar for the tests and the details,It seems that some
recipients are taken into account thanks to the reconciliation by
email.Is the folder still defined into the update box? If yes, are the
recipients up to date? Into the good folder?ThanksGeoffrey
You can also try to change the "Record identification" to "Using
reconciliation keys" and select the email or the primary key field
(depending on how you want to detect that the recipient is a new one).
Hi @navinKumar,I can see that you defined the operation to "Insert". I
don't know what is the context before the update data box but if the
recipient already exists, the box will not add it.Could you please take
a look at the workflow log, especially the update data box logs? How
many recipient should be added by the box? Also, could you please
control the creation date and last modification date of the recipients
before and after the execution in order to control if the box do
Hi @anoopa24021992, this field is a XML field. Therefore, you can't
order to load the delivery and update the value directly into the XML
returned. Regards. Geoffrey
Bonjour @samirn3178334, Pouvez-vous me donner un peu plus d'infos sur ce
rapport ?Est-ce un rapport natif ou personnalisé ? S'affiche-t-il
correctement dans les rapports d'une diffusion ?Est-ce juste la partie
envoi dans un email qui tourne dans le vide ?
Hello TobeyDallas,Could you please tell me how your unsubscribe link is
built into the delivery?Indeed, I have the @ character in the code when
I include <%= recipient.email %> so I don't understand why you have a
"%40" instead of the @.Thanks,Geoffrey.
Hi jeromen49554524,The name of the function must be
"namespace_name_methodName". In your case, if your schema is named
"cus_cusomtSession_Logon".Example:- Schema namespace: cus- Schema name:
cus_example_getTokenHope that will help you,Best Regards,Geoffrey.
Hi salvdangelo, yashdeepm7845047, arpandas681683,I found a way to
filtering very easily the values of an enumeration coming from a schema.
In fact, you have just to add a "enabledIf" attribute with a
"HasNamedRight('myRightName')": The named right can be applied on an operator
or a group.Please note that an administrator can see all the values even
if he haven't the good right.Regards,Geoffrey.
Hi yashdeepm7845047,The principle works with the enumeration values but
I unfortunately did not found a way to apply this to the enumerations
from schemas.It is possible to create two enumerations in the schema and
call the good one in the form depending on the operator but this
solution means that we have two different fields in the database and I
think it's not really clean.Thanks,Geoffrey.
Hello Abdul,It's more complicated to do that with the groups.Indeed, an
operator can be linked to many groups so it's difficult to set the
"sysFilter" tag.If it's possible, I don't know how. Sorry to can't help
Hi salvdangelo,It's possible to do that with this steps:- Creation of a
relation table between the Operators and the Enumeration Values tables
(N-N), this table will contains the operatorId and the enumValueId (same
principle than between the recipients and the recipients lists).-
Linking the Operators and the Enumeration Values tables with the new
relation table.- Adding a "sysFilter" in the input defined in the input
form: Best Regards.Geoffrey.
Hi felixs51477447,I don't know if another function exists but what I
would do:- Set a lastId parameter to 0- Sorting your records by Id in
your queryDef- Adding a condition tag "id > lastId" in the where tag of
your queryDef- Getting the last id recovered for each queryDef
execution- Exit the loop when the result of the queryDef equal to
Thanks for the context Anita,The recipient tag seems to be created
properly.However, I see that the recipient id is already present, I
assume that you loading the recipient at the start of the web
application.Is the "Update the preload record" ticked in the Storage
Hi Anita,Could you please run a test with the debug mode in order to
display the context, control if the value to store are there and if
there is any error?Feel free to put a screenshot of the web application
context for control of it.Many thanks,Geoffrey.
Hi mustufam59678037,I think that the conditions were not in the winner
delivery.The conditions must be there in the original delivery (winner
delivery) when you create the duplicated delivery:- If yes, the JS code
will modifying the values of the duplicated delivery conditions so the
provided code will be good.- If not, the JS code need to be modified in
order to create the conditions in the duplicated delivery and not just
modifying them.Many thanks,Geoffrey.