00197193-01_IM_SIPLACE_EDM_2_0_EN.pdf - 第32页
EDM V2.0 / Installation Manual Ausgabe 04/2012 Edition 5.3.6.1 Notification Filter It is not always desirable to inform the data prepa ration engineer about a data change o n a Line Server, for example, when a re-optimiz…
EDM V2.0 / Installation Manual Ausgabe 04/2012 Edition
5.3.5.3 Line server
Figure 5-4: Line servers
Here you specify the list of Line Servers for which the application template has to be applied.
● (A list of) Line alias name(s) (as defined in the Lines Settings tab, cf. section 5.3.2) make the
template visible to the specified EDM line(s)
● [All] (the default value) makes EDM present the template to all line servers
5.3.6 Notifications/Filtering…
CAUTION
This part of the system is highly sensitive. In extreme cases, incorrect settings can lead
to the loss of important changes or, on the other hand, the data preparation engineer can
be "bombarded" with notifications regarding irrelevant changes.
The Notification Filter section (5.3.6.1) describes the filter system, which determines what
notifications are not sent to the EDM Master. As default behavior, incoming change notifications on
the EDM Master are collected in the clearing pool. A change notification will not be aggregated in
the clearing pool, if it
● is imported directly into the master database as described in section 5.3.6.2, Direct import of
changed objects to the master database.
● is rejected automatically as described in section 5.3.6.3, Automatic rejection of the changes.
● has conflicting settings for “direct import” and “auto-reject” settings
An email notification is sent for all the alternatives as defined in 5.3.6.4, Email configuration.
31
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