Yes, Best practice is to take as a package, but for very minor changes like label / description and so on, depends on the scenario you can make changes in Higher environment. Before making the changes, Make sure that It won't impact other work items and make sure to do the same changes in lower envi...

@Heku_ , Yes. For example, for the error type 'Invalid domain', If the domain of the email address is incorrect or no longer exists, this profile will be targeted again until the error count reaches 5. After this, the record will be set to Quarantine status and no retry will follow.

Hi @DishaSharma , You can configure image in transactional message template in the same way as how you configure image for normal email delivery.

Hi @DishaSharma , One template for push event (real time event - to send communication to one recipient when a soap request is triggered for pushEvent) and another for push events (batch events - to send communication to multiple recipients at a time when soup request is triggered for pushEvents).

Hi @DishaSharma , Refer this document, where step by step explanation has been given for sending a proof using transactional message template.

Hi @A_B_SE , In general, After a development we would be performing a round of testing in lower environment and we will deploy it in PROD once the testing is successful. So when you export-import as a package, all the modification will be reflected in PROD without missing any items. Whereas by makin...

Hi @Heku_ , It depends on the type of bounce and reason for the bounce. Example if a recipient's mailbox box is full, then the recipient email address will be set to quarantine and it is set to valid after 30 days. You can refer this documentation for more details.

Hi @Shrutii , By default, sqlname will get auto-genarated. Example, for attribute name="loyaltyId" of long data type, sqlname will get auto generated as iLoyaltyId (you can see this sqlname for all attributes in preview tab). Instead of iLoyaltyId, if you want to use different sqlname, you can defin...

1) Create a csv file with email address of your seed list. 2) Create an import workflow and insert the records into Seed addresses schema (nms:seedMember), and mention the folder as well.

If you want to hide an attribute in default structure view, you can define advanced="true".