Item13304: Add exclusion based on last transition user, and fix email templates

The last user who changes the topic to another state will be stored in the workflow-attribute as LASTUSER_{state}, similar to the LASTTIME_ and LASTVERSION_ fields. To conveniently access the last user, the macro %WORKFLOWLASTUSER{"state"}% is introduced. The reason for this feature is to be able to send a notificiation to the user who last changed the topic to a specified state, e.g. if a topic is rejected the user who requested approval should be notified.

In our use-case it is not allowed for the user who requested approval to be the one who approves the final document even though this user may be generally allowed to. Thus this user can be excluded with the value not(LASTUSER_{state} in the Allowed column of the transition table.

The last change concerns the handling of custom email templates. If one or many custom email templates are specified, the default email will not be sent. Every additional email-address in the column will be stored in the EMAILTO-macro thus making them available in the custom email templates. However if there are no additional email-addresses specified, the custom email templates must state the addresses themselves.

-- MarkusGerhold

Many thanks for this, Markus. I'd appreciate if you could add a topic like this one for tracking if you make any other changes.

-- CrawfordCurrie - 11 Mar 2015

Commenting is disabled while not logged in