@acdbm I see the same behavior. I wish before the offer status changes from approve to archive or draft status, it should warn that the offer has already been used on the decision scope.
@Skotmor I'm curious, did you try applying the visibility condition at a structure level when you have a 2:2 column structure like this? Is that not working? and also did you try to apply the visibility condition for both columns separately?
Can you try along these lines,
serializeList(#{ExperiencePlatform.Profile.Account.all(currentDataPackField.pymntType == "CreditCard").lineOfBusiness}, ",", true)
Expected output: BB,CC
@Kaarthuul If the recipient is unsubscribed from the email then it will set the "No longer contact by email" to true and we should not include them in the email we are sending.
@Michael_Soprano Use the journey test mode to test and specify more than one item to see how it works. Also, have a look at this similar post on how to get productlistitems data to display in the front end.
@Michael_Soprano Small correction to the response posted by dugganab.
{{#each context.journey.events.event_ID.productListItems as |product|}}<table><tbody><tr><td><b>{{product.name}}</b></td><td><b>{{product.quantity}}</b></td><td><b>${{product.priceTotal}}</b></td></tr></tbody></table>{{/each}}
@Skotmor Here are my comments,
1- That I can tell, that visibility expression can only be done with limited fragments. Ie it only is available as an option for the photo in the structure in Col 1 and not the copy block in Col 2 within the same structure. - Yes. Visibility condition applied at a stru...
@rajivkamathacc Take a look at this documentation on how to write back to journeyevents dataset. If the requirement is to validate that the message has been sent out for a profile or not and that requires a custom process then ingesting the feedback data via the flat file/API into AEP/AJO that uses ...
@Rohan_Aditya, Looks to me this is a batch segment. If it's a batch segment wait it will get evaluated on a 24 hr window. You can verify this from the segment overview screen when the last batch is completed and the next batch is scheduled. Look at some of the other recommendations from this thread....