Skip to main content
D
dschultz8-Gravel
8-Gravel
February 21, 2017
Question

Email Task Notification Customizations

  • February 21, 2017
  • 2 replies
  • 2635 views

Add ability to customize task notification emails.

More than...

  • The handful of additional calls that can be added to the subject/body an message per the Help (Workflow EMail Notifications - activityAttributes, activity NotificationUrl and getDeadline).
  • Or the suggestion of using Email Robots or Expression Robots that require updates to all workflows and does not work for previously started processes.

It seems as if modifying the General.html (and locale) and registering a custom template processor is not a supported customization because it impacts all emails. 

    2 replies

    M
    MatthewKnight1-Visitor
    1-Visitor
    February 22, 2017

    Thumbs up.

    I believe that as of at least 10.2 M030, some of the relevant workflow-notification-related calls are still hardcoded and non-overridable, making them very difficult to get to through standard service property modifications, class/method extensions/overrides, etc.

    As you said, I think you can still get what you want by:

    • Creating the necessary templates along with their required property additions and new classes, and
    • Customizing the OOTB templates (e.g. General_<locale>.html) so that they invoke processSubTemplate against your newly created custom templates.

    Your custom template processor class should have access to the related wfobjects/business objects/etc, so it would then be up to you as to how your new class would implement the business logic you need.  Your invocation against your own template processor doesn't necessarily require that you write anything to the OutputStream.

    All that being said, it looks like the template processor stuff is being phased out anyways.  Its documentation has definitely become scarce.

    Z
    Zoltán13-Aquamarine
    13-Aquamarine
    October 3, 2023

    Hi!

     

    Did a solution pop up during the last 6,5 years?

    Terms & ConditionsCookie settingsAccessibility statement