00197458-01_UG_EDM_V2.2_en - 第51页
EDM V2.2 / U ser Guid e Ausgabe 10/2013 E dition 51 5.1.7 Notific a tions / Rules … C AUT IO N This par t of the s y stem is highl y sensitive. I n extrem e cases, incor rect sett ings can lead to the los s of im portant…
EDM V2.2 / User Guide Ausgabe 10/2013 Edition
50
5.1.6.2 Overwriting
Figure 5-8: Settings for overwriting object types
You can select the object types to be overwritten when the data is imported to the line here.
5.1.6.3 Line Server
Figure 5-9: 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, see section 5.1.3) make the
template visible to the specified EDM line(s).
● [All] (default value) makes EDM present the template to all line servers.
EDM V2.2 / User Guide Ausgabe 10/2013 Edition
51
5.1.7 Notifications / Rules …
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.
NOTICE
With version EDM 2.1, this part of the EDM system has undergone major changes.
Notification filter definitions used in former versions of EDM are barely compatible to the
rules system. It is strongly recommended to re-implement the filters in use on the
installation site, based on the users’ wishes.
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 consider these circumstances. You specify the object
types and objects for which no change notifications are to be sent to the Master Server. The
notification filter rules only affect data changed on an EDM Line Server.
5.1.7.1 The Rule Set
By default, changes on EDM Line computers are transferred to the EDM Master and collected in
the Clearing Pool.
The predefined set of rules prevents that changes by EDM specific actions and typical user
scenarios (e.g."Level 3 Optimization" on the EDM Line) are sent to the EDM Master. Its behavior
may be changed by editing or adding a rule to the rule system.
A defined rule is enabled if the associated box is checked.
Active filter rules are shown in bold letters, active processing-only rules in italic letters. On the
right-hand side of the GUI, a summary description of the selected rule is given.
EDM V2.2 / User Guide Ausgabe 10/2013 Edition
52
Figure 5-10: Notification Rules set editor
Rule Set Evaluation
● The rules are evaluated in descending order of the rule set list.
► Use the up and down buttons to control the sequence of the rules.
● The handling option of the first rule that matches the incoming notification determines its target
destination, and the evaluation of the rule set is terminated.
However, a matching rule with Not Specified handling option just applies its processing
instructions (e.g. sending an e-mail or changing the comment), and the evaluation continues
with the next rule in the list.
● If none of the rules matches, the default behavior (showing a comment dialog on the EDM Line
and sending the changes to the clearing pool) is applied.
5.1.7.2 Notification Rules
A notification rule consists of two parts:
1. Patterns to describe the set of notifications the rule applies to.
2. Actions to be applied on matching notifications:
● Handling options to describe the target destination of the notifications
– Filter at line server. Matching notifications are discarded on the EDM Line, and no
data is transferred to the EDM Master.
– Auto Reject. Changes are discarded on the EDM Master. These changes bypass the
data preparation engineer.
– Direct Import. Changes are imported into the Master database, without being
displayed in the clearing pool. These changes bypass the data preparation engineer.
– Not Specified. Special rule that only applies "processing instructions".