Notification Email Formatting

It seems this is indeed a limitation of those sections. You should add the placeholders into the actual notification body sections. Many of them contain these kinds of object links by default.

It seems this is indeed a limitation of those sections. You should add the placeholders into the actual notification body sections. Many of them contain these kinds of object links by default.

Thanks Joonas -- is there a way to suggest this as a feature? I'm averse to putting common things in each notification action within a workflow. What if the stakeholders decide they want it to look different, or to not include the linked items, etc. -- that becomes a maintenance horror, unless there's another way around that.

I'm also trying to avoid using common placeholders and HTML in these sections since the notification panel in the workflow editor has a length limit and want to make sure that future maintenance by others is as seamless as possible without any web-coding knowledge.

I also want to iterate that if we were able to use variables in the epilog/prolog, we would likely remove the object links from the other existing sections so we can have it be consistent across all notifications for our organization.

My understanding is that prolog and epilog are expected to be generic header and footer and the specific notification content (e.g. links to objects) are included in the message body. These links should be in place by default and you shouldn't typically need to modify that many templates, unless there's for instance some additional information you want to add for specific types of notifications.

It may be worth raising this with your M-Files representative and checking the options if the default notifications don't serve your purposes.

Sounds good, thank you.