Number range (Events)

Event action – Abstract
Event
Description
Warn threshold exceeded
This is triggered when the percentage warning threshold for the Number range is reached or exceeded for the first time.
Number range exceeded
This is triggered when an active Number range is requested whose capacity is already exceeded so that it can no longer supply a value.
Number range disabled
This is triggered when a Number range is disabled because an error occurs when trying to generate a number.

Event	Description
`Warn threshold exceeded`	This is triggered when the percentage warning threshold for the Number range is reached or exceeded for the first time.
`Number range exceeded`	This is triggered when an active Number range is requested whose capacity is already exceeded so that it can no longer supply a value.
`Number range disabled`	This is triggered when a Number range is disabled because an error occurs when trying to generate a number.

The following events are offered to control number ranges:

Event	Description
`Warn threshold exceeded`	This is triggered when the percentage warning threshold for the Number range is reached or exceeded for the first time. Example: A number range with a warning level of 80 (%) counts up starting from 1 'Run numbers' with an increment of 1. With a maximum value of 100, the 'Warn threshold exceeded' event is triggered precisely when the number 80 is 'drawn'.
`Number range exceeded`	This is triggered when an active Number range is requested whose capacity is already exceeded so that it can no longer supply a value. Example: Following the example above, the event 'Number range exceeded' is triggered exactly when the numbers 1 to 100 have already been drawn and another request is received.
`Number range disabled`	This is triggered when a Number range is disabled because an error occurs when trying to generate a number. The event 'Number range exceeded' is also classified as an error, so that the two events always occur in direct succession when a number range is exhausted. ►NOTE◄ The event is not triggered if the active property of a Number range is assigned the value `false` interactively, by an import profile, or by event handling. After the warning threshold has been exceeded, there should be sufficient reaction time to configure a successor for the number range type concerned. This can be given a lower priority than its predecessor, linked to suitable association criteria and also set to 'active' immediately. Then this successor still comes into play within request that triggers the deactivation of its predecessor immediately and can provide 'uninterruptible' return values. ►WARNING◄ Under no circumstances should an attempt be made to reactivate an exceeded number range in the event handling for 'Number range disabled', for example so that messages are sent again with every further request. Otherwise, the reactivated number range is immediately requested again, reports 'exceeded' again, is deactivated and a cycle closes.

Event

Description

Warn threshold exceeded

This is triggered when the percentage warning threshold for the Number range is reached or exceeded for the first time.

Example: A number range with a warning level of 80 (%) counts up starting from 1 'Run numbers' with an increment of 1.

With a maximum value of 100, the 'Warn threshold exceeded' event is triggered precisely when the number 80 is 'drawn'.

Number range exceeded

This is triggered when an active Number range is requested whose capacity is already exceeded so that it can no longer supply a value.

Example: Following the example above, the event 'Number range exceeded' is triggered exactly when the numbers 1 to 100 have already been drawn and another request is received.

Number range disabled

This is triggered when a Number range is disabled because an error occurs when trying to generate a number.

The event 'Number range exceeded' is also classified as an error, so that the two events always occur in direct succession when a number range is exhausted.

►NOTE◄ The event is not triggered if the active property of a Number range is assigned the value false interactively, by an import profile, or by event handling.

After the warning threshold has been exceeded, there should be sufficient reaction time to configure a successor for the number range type concerned. This can be given a lower priority than its predecessor, linked to suitable association criteria and also set to 'active' immediately. Then this successor still comes into play within request that triggers the deactivation of its predecessor immediately and can provide 'uninterruptible' return values.

►WARNING◄ Under no circumstances should an attempt be made to reactivate an exceeded number range in the event handling for 'Number range disabled', for example so that messages are sent again with every further request. Otherwise, the reactivated number range is immediately requested again, reports 'exceeded' again, is deactivated and a cycle closes.

In event handling, the number range object (Number range) can be accessed via resolvers (see also Resolvers).

Example

images/download/attachments/78255654/image2018-8-14_14_37_33-version-1-modificationdate-1628513715286-api-v2.png

As the Triggering event, 'Warn threshold exceeded' is defined here.
The Validating rule links a type check for 'Number range' with the requirement that the current number range belongs to the number range type 'Barcode (BARCODE)'.
As the Action on passed rule, a message is sent to the user via the Show alert (Popup) event action if the validating rule is passed. The percentage value of the warning threshold is displayed informatively.

In practice, a simple popup that is only seen by the user causing the limit violation is certainly not a target-oriented reaction to the event. Instead, however, an E-Mail, e.g. to an administrator, could then also contain more details about the affected number range.