Mail Layout |
||||||||||||||||||||||
The layout of the e-mails, which are used to inform the user about work items, can be configured individually. The html-file template fragments in the | folder can be adapted.||||||||||||||||||||||
Please consider the variables tagged with <AXA>...</AXA> : | ||||||||||||||||||||||
Default Variables:
|
||||||||||||||||||||||
Additional available variables:Depending on the relation of the work item to other workflow objects, the following variables are available:
|
||||||||||||||||||||||
Add Additional Variables |
||||||||||||||||||||||
To add an additional variables use the following construction: <AXA>Entity=<entity name>,Field=<field name></AXA> |
||||||||||||||||||||||
![]() |
If the combination of entity / field name, or the value does not exist, the construction will be replaced by "--"! | |||||||||||||||||||||
Example 1:To add the existing value of T_ACT_DAT.ACT_STATE to the mail template... search the field name ACT_STATE in ABS_<env-name>.ini: [Repository\ObjTypes\Activity\Attributes\Phase] The construction should lool like: <AXA>Entity=Activity,Field=Phase</AXA> |
||||||||||||||||||||||
Example 2:In case your field does not exist inside ABS_<env name>.ini, add it manually. Field T_PRC_DAT.PRC_TYPE, currently not inside ABS_<env name>.ini... |
||||||||||||||||||||||
Create a new repository entry (the mapping name, here Type, should be unique for this entity): [Repository\ObjTypes\Process\Attributes\Type] |
||||||||||||||||||||||
Redeploy Your Application |
||||||||||||||||||||||
Redeploy your application to make your changes available. To use these new attributes, see the example construction above. | ||||||||||||||||||||||
![]() |
To make the changes available for all environments, use tpl_ABS_env.ini and redeploy all applications! | |||||||||||||||||||||
File |
||||||||||||||||||||||
Configure timing and mailing settings of the notifier in the | file. The following parameters with values in <...> are set automatically during the installation: The other parameters can be changed manually.||||||||||||||||||||||
A short functional explanation is written after the : | ||||||||||||||||||||||
... [WorkflowExecutor] [Notifier] [Messenger] |
||||||||||||||||||||||
Timing |
||||||||||||||||||||||
The section [Notifier] contains
delay=<value in seconds>. This entry defines
the time delay in seconds between two active phases of the notifier calculated from
the start of the Business Service. During an active phase, e-mails are sent
for the new work items immediately the notifier starts with delay. [Notifier] |
||||||||||||||||||||||
![]() |
When using the Notifier in productive environments, set the time periods to at least 1000 sec (~ 15minutes) or higher (e.g. delay=2000). | |||||||||||||||||||||
Mailing |
||||||||||||||||||||||
In the ... [Messenger] |
file, the following default e-mail parameters are set automatically during the installation:
||||||||||||||||||||||
![]() |
It is required to insert values for ADMIN_UIC in the messenger section of the abs.ini file! The user who is designated for the ADMIN should have privileges for the workflow module and the manager rights to create persons or change user data! | |||||||||||||||||||||
SSL and Authentication for SMTP Mailing |
||||||||||||||||||||||
Workflow and server-side external mailing provide SSL and authentication for mailing.
|
||||||||||||||||||||||
Default Data |
||||||||||||||||||||||
![]() |
In case there are no notifications sent, first check the
values of the EDB-WFL-NOT flags in the database.
Clicking ![]() |
|||||||||||||||||||||
![]() |
||||||||||||||||||||||
![]() |
The name and the value assigned to the EDB-WFL-NOT entry indicate whether and how often notifications are sent. If a user has a special setting (e.g. immediately, hourly) this setting will have priority compared to the users GLOBAL or SYSTEM. If a user doesn't have an entry, the system first searches for the user GLOBAL. If GLOBAL is not available, the system searches for SYSTEM. The GLOBAL and SYSTEM settings are valid for all user without a special entry. It is quite "dangerous" to define GLOBAL and SYSTEM with NONE since then the system wouldn't send out any notifications if there are no other users defined! | |||||||||||||||||||||
Concatenation of Notifications |
||||||||||||||||||||||
![]() |
If several new work items appear during an inactive phase of the notifier, the notifications for the same person are automatically concatenated and sent as one notification! | |||||||||||||||||||||
As an example, the settings below will have the following effect on the concatenation of notifications: | ||||||||||||||||||||||
![]() |
Set the value for | to .|||||||||||||||||||||
![]() |
In the | do the following settings:|||||||||||||||||||||
Set the notifier to 10 min. Set the watchdog period to 20 min Set the watchdog batch period to 2 min |
||||||||||||||||||||||
![]() |
Create three simple workflow processes with only one activity and set the following values: | |||||||||||||||||||||
- Duration = 2 minutes - Limit = 12 minutes |
||||||||||||||||||||||
![]() |
Please note that when entering the time value via the corresponding mask, the selection menu doesn't offer to select minutes. However, the value for minutes can be entered manually (e.g. 2 mi)! | |||||||||||||||||||||
Effect:
After having started these three processes, the following emails will be sent: - After 10 minutes one email will be sent to the user concatenating new
work items. |
||||||||||||||||||||||
Opening Tasks with the Java Client |
||||||||||||||||||||||
Instead of using the Web Client it is also possible to use the Java Client to open the tasks contained in the workflow notifications. | ||||||||||||||||||||||
![]() |
Because both links are available, please delete the unused link definition. | |||||||||||||||||||||
Internationalization |
||||||||||||||||||||||
Extentions for the Workflow Mailing |
||||||||||||||||||||||
![]() |
The encoding of HTML or TXT snippets is UTF-8. All non-ASCII characters have to be replaced with either HTML or Decimal escapes. All TXT snippets have to be encoded as UTF-8 files without ByteOrderMask. E.g. "ä"
|
|||||||||||||||||||||
Extentions for the Server-Side External Mailer |
||||||||||||||||||||||
![]() |
By default, the encoding is set to UTF-8. | |||||||||||||||||||||
The encoding is done on server side with the given encoding, or if missing with UTF-8 encoding. If this fails, the original text is send without encoding. Thus, the parameter -k must be set if the encoding in a text file differs from UTF-8 encoding. If you want to send an XML file, which is usually encoded in UTF-8, you do not need the -k parameter. In case of any text file written on the client side (e.g. windows clients have usually the encoding windows-1252) the encoding has to be -k'windows-1252'. |