Skip to Main Content
Feature Request FR-2000
Product Area Application Builder
Status ROADMAP

34 Voters

Programmatically create email templates

doug gault Public · Sep 27 2021

Idea Summary
Allow for the programmatic creation of email templates. 

Use Case
In several cases recently (Pandemic Apps, GBU Apps, etc) we are being faced with the requirement of allowing end users to build and test email templates dynamically. This also included the requirement for those templates to be translated to multiple languages. 

For example, for the pandemic applications we were built our own tables because there was no way to programmatically create templates. 

Preferred Solution (Optional)
Provide API's that allow for the creation, import and export of templates (including alternate languages)  to/from APEX.

This is currently on the roadmap for a future release of Oracle APEX.

Comments

Comments

  • cf OP 3.7 years ago

     I basically have a parallel custom email handling packages for the sole reason that apex email templates can not be updated outside the builder. I would much rather scrape all that code.

  • jayson hanes Admin OP 3.3 years ago

    Once there is an API, this should be easy!

    https://apex.oracle.com/ideas/FR-2059 - "The ability to copy Email templates in shared components"

  • jason.blankenship OP 2.4 years ago

    @cf would you be willing to share your email handling package?

  • ino.laurensse OP 2.4 years ago

    Currently we have our own template builder in a Rich Text Editor in our application. 

    Putting updateable templates in Shared Components sounds risky. Too easy to overwrite templates by an import of a new release from development. It should be something outside the Shared Componens, like user and role management.

  • shane_bentz OP 1.3 years ago

    Too easy to overwrite templates by an import of a new release from development.

    Perhaps, but there is already facility in the export of an application to not overwrite public/private IR/IG saved reports. You'd think there could be a checkbox/switch during the export of the application to indicate whether or not to overwrite the content of the email templates.

  • mark.w OP 1.3 years ago

    As a developer I would like to have an API to create new email templates or modify existing ones. This can give application users the power to define their own templates or to modify them according to their needs (via the application). That API should take clob parameters for HTML-/text-only content and varchar2 for the subject, as well as a parameter for the template id. 

    Of course the developer should think about which templates should be predefined components of the application. If the application has functionality for modification / creation of email templates by users it should prevent those predefined templates from being overwritten. I think this is the responsibility of the developer and should not be an obstacle to that feature.