00194585-05_Installation_Manual_EDM_EN.pdf - 第56页

Installation Manual, SIPLACE EDM Version 1.1 SP2 Issue 12/2006 5.4.2.2 Configuring a list After a distribution list has been selected, the ema il addresses of the recipients and the object types or EDM events monitored b…

100%1 / 65
Installation Manual SIPLACE EDM Version 1.1 SP2 Issue 12/2006
Figure 20 Configuration of Email distribution lists
The storage location of the configuration file should be specified for informational purposes and
must not be changed. Direct manipulation of the configuration file should also be avoided.
5.4.2.1 Setting up a new list
A line must be selected before a new distribution list can be added. A name and a comment are
assigned to each new list.
55 of 65
Installation Manual, SIPLACE EDM Version 1.1 SP2 Issue 12/2006
5.4.2.2 Configuring a list
After a distribution list has been selected, the email addresses of the recipients and the object types
or EDM events monitored by the list can be entered. All recipients on the distribution list receive
emails regarding notifications which refer to one of the selected object types. Only those
notifications are taken into account that originate from the line for which the distribution list was
created.
If the recipients are to be notified about "Forced Pull" events, this event must be selected in the
"EDM Events" tab.
5.4.2.3 General distribution list
The general distribution list reacts to notifications from all lines simultaneously, but is otherwise the
same as normal distribution lists.
5.4.3 Direct import of changed objects to the master database
It is possible to bypass the clearing pool and import objects changed on the lines directly into the
master database without the data preparation engineer inspecting the data.
Figure 21 Configuration of notifications to be imported directly
56 of 65
Installation Manual SIPLACE EDM Version 1.1 SP2 Issue 12/2006
Configuration is performed in the same way as for filter configuration (see 5.5 Filter configuration),
but is carried out on the master. The configuration options, however, only allow identification of the
data using the:
• object type
• name of the changed object. This restriction is implemented using regular expressions.
The configuration is stored in the file ClearingPoolImportFilterConfig.xml in the config directory.
5.4.4 Automatic rejection of the changes
It is possible to bypass the clearing pool and automatically reject objects changed on the lines
without the data preparation engineer inspecting the data. The changes are rejected without being
saved.
Figure 22 Configuration of notifications to be rejected automatically
Configuration is performed in the same way as for filter configuration (see 5.5 Filter configuration),
but is carried out on the master. The configuration options, however, only allow identification of the
data using the:
• object type
• name of the changed object. This restriction is implemented using regular expressions.
The configuration is stored in the file ClearingPoolRejectFilterConfig.xml in the config directory.
57 of 65