00197193-01_IM_SIPLACE_EDM_2_0_EN.pdf - 第33页
EDM V2.0 / Installation Manual Ausgabe 04/2012 Edition The filter configuration list comprise s a set of “OR” rules.This means that as soon as at least one of the defined conditions applies to the incomi ng notification,…
EDM V2.0 / Installation Manual Ausgabe 04/2012 Edition
5.3.6.1 Notification Filter
It is not always desirable to inform the data preparation engineer about a data change on a Line
Server, for example, when a re-optimization is being performed on the line. In this case, a number
of internal SIPLACE Pro objects (for example HeadSteps, i.e. individual process steps for a head)
are changed, and these changes would then need to be commented accordingly by the user and
put in the Clearing Pool, but they do not contain any information. Furthermore, there are customer
processes that imply a selection of change notifications, for example, when just the pure product
data (board, components, etc.) is centrally administered and the process-specific data is recreated
on each line. In such a scenario, only changes to the product data are of interest, and changes to
the jobs and recipes are not.
The notification filter rules are intended to take these circumstances into account. You specify the
object types and objects for which no change notifications are to be sent to the Master Server. The
notification filer rules only affect a Line Server.
Change notifications can be filtered using a combination of:
● object type
● sub-object type
● individual properties of objects/sub-objects
● type of change to the object
● user names
● name of the changed object.
This restriction is implemented using regular expressions.
In the standard installation, a filter configuration is created that captures all irrelevant changes
made during optimization. Changes to the filter rules should only be made based on these default
settings.
Figure 5-5: Configuration of the notification filter
32
EDM V2.0 / Installation Manual Ausgabe 04/2012 Edition
The filter configuration list comprises a set of “OR” rules.This means that as soon as at least one
of the defined conditions applies to the incoming notification, the notification is rejected (no
comment dialog box is opened and the notification is not transferred to the Master Server). A
defined rule is enabled if the associated box is checked.
Figure 5-6: Configuration of a single rule
Every condition checks a subset of the properties of the notification. This set has an “AND” logic,
i.e. only when all the properties checked by the condition have the values specified in the
condition, the notification is rejected by this condition.
The following properties can be assessed by a condition:
● Name (regular expression)
● Object type
● Sub-object type
● Property of object or sub-object
● Deletion of sub-objects of a particular object (association delete)
● Type of notification
● SIPLACE user or Windows user
There is a separate tab for each of these properties. If no value is selected in any of the tabs, this
property is not checked. If one or more values are selected, the value of the property in the
notification must match one of the values for the notification to be filtered.
33
EDM V2.0 / Installation Manual Ausgabe 04/2012 Edition
5.3.6.2 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.
The configuration is performed in the same way as for filter configuration. However, the
configuration options only allow identification of the data using:
● object type
● user names (SIPLACE Pro and Windows)
● name of the changed object.
This restriction is implemented using regular expressions.
Figure 5-7 Configuration of notifications to be imported directly
The configuration is stored in the ClearingPoolImportFilterConfig.xml file in the config folder.
34