Difference between revisions of "Notification and subscription messages"
| Line 5: | Line 5: | ||
These are the default values: | These are the default values: | ||
| − | {| border="1" | + | {| border="1" cellpadding="5" cellspacing="0" |
! align="left"| notification.message.subject | ! align="left"| notification.message.subject | ||
| <nowiki>OpenKM - NOTIFICATION - $documentName</nowiki> | | <nowiki>OpenKM - NOTIFICATION - $documentName</nowiki> | ||
| Line 52: | Line 52: | ||
These are the default values: | These are the default values: | ||
| − | {| border="1" | + | {| border="1" cellpadding="5" cellspacing="0" |
! align="left"| notify.message.subject | ! align="left"| notify.message.subject | ||
| <nowiki>OpenKM - NOTIFICATION - {0}</nowiki> | | <nowiki>OpenKM - NOTIFICATION - {0}</nowiki> | ||
Revision as of 10:15, 23 April 2010
When you are subscribed to a document, any change in the document will be notified by email. These email messages are created using some defined templates. You can modify these default templates to create messages adapted to your company style. This modification is done editing the file OpenKM.cfg.
 |
New feature in OpenKM 4.1 |
These are the default values:
| notification.message.subject | OpenKM - NOTIFICATION - $documentName |
|---|---|
| notification.message.body | <b>Document: </b><a href=\"$documentUrl\">$documentPath</a><br/><b>User: </b>$userId<br/><b>Message: </b>$notificationMessage<br/> |
| subscription.message.subject | OpenKM - $eventType - $documentPath |
| subscription.message.body | <b>Document: </b><a href=\"$documentUrl\">$documentPath</a><br/><b>User: </b>$userId<br/><b>Event: </b>$eventType<br/><b>Comment: </b>$subscriptionComment<br/> |
| subscription.twitter.status | OpenKM - $documentUrl - $documentPath - $userId - $eventType |
And these are the substitution variables used:
Notification message subject & body
- $documentUrl - Document URL
- $documentPath - Document path
- $documentName - Document name
- $userId - User id
- $notificationMessage - Notification message
Subscription message subject & body & twitter
- $documentUrl - Document URL
- $documentPath - Document path
- $documentName - Document name
- $userId - User id
- $eventType - Event type
- $subscriptionComment - Subscription comment
 |
Take care of the OpenKM.cfg format: this is a Java properties file and has some limitations, for example, this file have to be coded in ISO-8859-1 format. Also single quotes (') should be protected with another single quote (''). |
More info on this can be found at:
- http://java.sun.com/j2se/1.5.0/docs/api/java/text/MessageFormat.html
- http://www.w3schools.com/tags/ref_entities.asp
If you want to elaborate a more complex template, the limitations of Java Properties are a disadvantage. In this case you can set the subscription.message.subject property to a template filename (for example, ComplexSubcriptionSubject.vm). The template file should have the .vm extension and needs to be locate at $JBOSS_HOME directory.
More info about Velocity templates at Apache Velocity User Guide.
OpenKM 4.0 and older
These are the default values:
| notify.message.subject | OpenKM - NOTIFICATION - {0} |
|---|---|
| notify.message.body | <b>Document: </b><a href="{0}">{1}</a><br/><b>User: </b>{3}<br/><b>Message:</b>{4}<br/> |
| subscription.message.subject | OpenKM - {0} - {1} |
| subscription.message.body | <b>Document: </b><a href="{0}">{1}</a><br/><b>User: </b>{3}<br/><b>Event:</b>{4}<br/><b>Comment: </b>{5}<br/> |
And these are the substitution variables used:
| NOTIFY MESSAGE SUBJECT | NOTIFY MESSAGE BODY |
|---|---|
| {0} - document path | {0} - document URL |
| {1} - document name | {1} - document path |
| {2} - document name | |
| {3} - user id | |
| {4} - message |
| SUBSCRIPTION MESSAGE SUBJECT | SUBSCRIPTION MESSAGE BODY |
|---|---|
| {0} - event type | {0} - document URL |
| {1} - document path | {1} - document path |
| {2} - document name | {2} - document name |
| {3} - user id | |
| {4} - event type |
