Metis Smart Modeling - Rules
From Metis Documentation
(→Description) |
(→Description) |
||
| Line 141: | Line 141: | ||
{| class="wikitable centre" width="100%" style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: transparent; background-color : transparent;" | {| class="wikitable centre" width="100%" style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: transparent; background-color : transparent;" | ||
| - | | width="20%" style=" | + | | width="20%" style="vertical-align: top; background-color : transparent; border-style: solid; border-color: transparent; border-width: 0 1px 1px 0" | |
''No treatment of the rest'' | ''No treatment of the rest'' | ||
| - | | width="80%" style=" | + | | width="80%" style="vertical-align: top; background-color : transparent; border-style: solid; border-color: transparent; border-width: 0 0 1px 0" | |
If this checkbox is ticked, any fractions of output resulting from a rule will not be taken into account. This means that the result will only be composed of whole units. | If this checkbox is ticked, any fractions of output resulting from a rule will not be taken into account. This means that the result will only be composed of whole units. | ||
|- | |- | ||
| - | | width="20%" style=" | + | | width="20%" style="vertical-align: top; background-color : transparent; border-style: solid; border-color: transparent; border-width: 0 1px 1px 0" | |
''White Flag (Offer)'' | ''White Flag (Offer)'' | ||
| - | | width="80%" style=" | + | | width="80%" style="vertical-align: top; background-color : transparent; border-style: solid; border-color: transparent; border-width: 0 0 1px 0" | |
White flags, simply by the presence of an EKB name, are considered to be applied on the order level. The influence in QSBW is that the ordering process will be blocked for the QSBW end user until an ECS control can be performed, but it will still be possible to view and print offer documents. There is no icon to represent the White Flag applied on the order level. | White flags, simply by the presence of an EKB name, are considered to be applied on the order level. The influence in QSBW is that the ordering process will be blocked for the QSBW end user until an ECS control can be performed, but it will still be possible to view and print offer documents. There is no icon to represent the White Flag applied on the order level. | ||
|- | |- | ||
| - | | width="20%" style=" | + | | width="20%" style="vertical-align: top; background-color : transparent; border-style: solid; border-color: transparent; border-width: 0 1px 1px 0" | |
''Grey Falg (Order)'' | ''Grey Falg (Order)'' | ||
| - | | width="80%" style=" | + | | width="80%" style="vertical-align: top; background-color : transparent; border-style: solid; border-color: transparent; border-width: 0 0 1px 0" | |
Grey Flags are intended for systems which do not have EKB names. Similar to the White Flag, they also require QSBW end users to perform a mandatory control of system configuration. The mandatory controls of systems with Grey Flags will have to be performed manually by an especially authorized user as opposed to being handled by Configuration Service like White Flags. Will be applied on the order level, meaning that the ordering process will be blocked for the QSBW end user until a manual control can be performed. It will still be possible for the end user to view and print offer documents, however. | Grey Flags are intended for systems which do not have EKB names. Similar to the White Flag, they also require QSBW end users to perform a mandatory control of system configuration. The mandatory controls of systems with Grey Flags will have to be performed manually by an especially authorized user as opposed to being handled by Configuration Service like White Flags. Will be applied on the order level, meaning that the ordering process will be blocked for the QSBW end user until a manual control can be performed. It will still be possible for the end user to view and print offer documents, however. | ||
|- | |- | ||
| - | | width="20%" style=" | + | | width="20%" style="vertical-align: top; background-color : transparent; border-style: solid; border-color: transparent; border-width: 0 1px 0 0" | |
''Grey Flag (Offer)'' | ''Grey Flag (Offer)'' | ||
| - | | width="80%" style=" | + | | width="80%" style="vertical-align: top; background-color : transparent; border-style: solid; border-color: transparent; border-width: 0 0 0 0" | |
Grey Flags are intended for systems which do not have EKB names. Similar to the White Flag, they also require QSBW end users to perform a mandatory control of system configuration. The mandatory controls of systems with Grey Flags will have to be performed manually by an especially authorized user as opposed to being handled by Configuration Service like White Flags. Will be applied on the offer level. It is basically the same as the Grey Flag (Order) with the added restriction that it will not be possible for the end user to view and print offer documents. | Grey Flags are intended for systems which do not have EKB names. Similar to the White Flag, they also require QSBW end users to perform a mandatory control of system configuration. The mandatory controls of systems with Grey Flags will have to be performed manually by an especially authorized user as opposed to being handled by Configuration Service like White Flags. Will be applied on the offer level. It is basically the same as the Grey Flag (Order) with the added restriction that it will not be possible for the end user to view and print offer documents. | ||
|- | |- | ||