Many organizations use email notifications to notify or remind workflow participants about work assignments.
Typical uses of email notifications in workflow system applications include such notifications as:
To help facilitate use of email notifications, IBM® provides a set of default email notification files. These email notification (.MSG) files are text files (containing HTML-formatted content) that are available for you to customize.
Modifying Email Notification Files
Use the following procedure to modify the default email notification files:
\Program Files (x86)\IBM\FileNet\ProcessEngine\msg\0 on the primary Content Platform Engine server Windows host
/opt/IBM/FileNet/ProcessEngine/msg/0 on the primary Content Platform Engine host that is not running the Windows platform
\Program Files (x86)\IBM\FileNet\ProcessEngine\msg\1 on the primary Content Platform Engine Windows host
/opt/IBM/FileNet/ProcessEngine/msg/1 on the primary Content Platform Engine host that is not running the Windows platform
\Program Files (x86)\IBM\FileNet\ProcessEngine\msg\2 on the primary Content Platform Engine Windows host
/opt/IBM/FileNet/ProcessEngine/msg/2 on the primary Content Platform Engine host that is not running the Windows platform
\Program Files (x86)\IBM\FileNet\ProcessEngine\msg\3 on the primary Content Platform Engine Windows host
/opt/IBM/FileNet/ProcessEngine/msg/3 on the primary Content Platform Engine host that is not running the Windows platform
\Program Files (x86)\IBM\FileNet\ProcessEngine\msg\4 on the primary Content Platform Engine Windows host
/opt/IBM/FileNet/ProcessEngine/msg/4 on the primary Content Platform Engine host that is not running the Windows platform
\Program Files (x86)\IBM\FileNet\ProcessEngine\msg\5 on the primary Content Platform Engine Windows host
/opt/IBM/FileNet/ProcessEngine/msg/5 on the primary Content Platform Engine host that is not running the Windows platform
\Program Files (x86)\IBM\FileNet\ProcessEngine\msg\6 on the primary Content Platform Engine Windows host
/opt/IBM/FileNet/ProcessEngine/msg/6 on the primary Content Platform Engine host that is not running the Windows platform
\Program Files (x86)\IBM\FileNet\ProcessEngine\msg\7 on the primary Content Platform Engine Windows host
/opt/IBM/FileNet/ProcessEngine/msg/7 on the primary Content Platform Engine non-Windows host
\Program Files (x86)\IBM\FileNet\ProcessEngine\msg\8 on the primary Content Platform Engine Windows host
/opt/IBM/FileNet/ProcessEngine/msg/8 on the primary Content Platform Engine non-Windows host
\Program Files (x86)\IBM\FileNet\ProcessEngine\msg\9 on the primary Content Platform Engine Windows host
/opt/IBM/FileNet/ProcessEngine/msg/9 on the primary Content Platform Engine non-Windows host
\Program Files (x86)\IBM\FileNet\ProcessEngine\msg\10 on the primary Content Platform Engine Windows host
/opt/IBM/FileNet/ProcessEngine/msg/10 on the primary Content Platform Engine non-Windows host
\Program Files (x86)\IBM\FileNet\ProcessEngine\msg\11 on the primary Content Platform Engine Windows host
/opt/IBM/FileNet/ProcessEngine/msg/11 on the primary Content Platform Engine non-Windows host
\Program Files (x86)\IBM\FileNet\ProcessEngine\msg\100 on the primary Content Platform Engine Windows host.
The integer directories at the end of the path match the VWSession.WEBAPP* fields.