174
Views
4
Comments
Creating custom template for news letter email by end user in Outsystems reactive app
Application Type
Reactive

Hi,

I am working on an Outsystems reactive reusable application for sending newsletters when new posts/components are added. I need to allow admin of application to create custom newsletter email templates. The user(admin) should be able to create their own templates from scratch. Once template is created, the admin should be able to add contents into it and save it. The template with contents should be the body of the email sent to other users. 

1) How can I implement this feature in my application ? It should provide easy-to-use user interface to create/edit templates like allow user to drag and drop the necessary fields (buttons/textarea etc.) instead of typing the html code. 

2) How can I store and manage these templates in the application once created? 

3) How this template with contents in it can be passed as input to the body of email ?

Any help or advice would be appreciated. 

Thank you in advance,

Avi




2023-04-06 11-24-23
Paulo Zacarias

Hi @Avithesh B 

Please consider checking this component. I think it can help you. 

https://www.outsystems.com/forge/component-overview/14403/customemails

Regards

UserImage.jpg
Avithesh B

Hi Paulo Zacarias,

Thanks for your response.

I wanted to implement in such a way that the end user can create template and add tags to the content fields where the contents can be retrieved dynamically from the entity.

For example, User creates new post which will have title, description, image, link to post and save it to the entity. Admin of the application can create template for email where he can add tags for these fields of posts, so that whatever contents/posts are added will be automatically mapped to these tags added in the email template. After this admin can send email which will have all these details.

2023-04-06 11-24-23
Paulo Zacarias

Hi, 

So first you will need to come up with a possible data model that has the email template entity, the tags entity, and the connection between these concepts, let's say a 'many to many' TemplateTags entity with the EmailTemplateId and the TagId.

Then you will need a back office to create these tags and the templates, you can grab an idea of how to achieve it by looking at the application I suggested above.

Then you need an action that will return/replace the tag. You send a tag code and you receive a tag value. Some tags, like the day of the week, can be mapped dynamically through logic.

What do you think? 

Regards

UserImage.jpg
Avithesh B

Hi,

Yes. Let me try this way. Hope this meet my expectations. I will revert back to you if I need with further assistance. 

Thanks and regards!

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.