Number range value
Value resolver – Abstract
Purpose: Attempts to retrieve a number range value for the specified Number range type.
The Number range value value resolver attempts to retrieve a number range value for the specified Number range type.
Whether the value resolver returns a number range value depends on whether a number range:
is configured for the Number range type,
is set to active,
is applicable in the given context (see note below) and
is not yet 'exhausted'
For further details see Number range.
If one of these criteria is not met, 'no value' ($null) is returned.
►NOTE◄ The dynamic assignment of number ranges for the selected Number range type takes into account the input value for the Number range value value resolver as a data context, which may differ from the reference object applicable in the context of a concatenation.
The input value is passed to the number range assigned, if any, together with the variables valid in the context of the Number range value value resolver. The corresponding data can be used in its configuration to define number parts (see Wert über Resolver (Nummernteil)).
Configuration
The only Number range type parameter is not formally a required field. However, without any selection for the Number range type, 'no value' ($null) is always returned.
The selection field for the Number range type parameter refers to the dynamic enumeration Number range type and supports a search function as shown to the right. Dynamische Aufzählungsfilter for the Number range type applicable in the context of the configuration can limit the selection options. Such restrictions have no influence on the runtime behaviour. |
|
Example
Whenever the account of a user (see Users) or guest user (see Guest users) is created, modified or deleted, an e-mail should be sent to an administrator with a number range value in the subject line as a unique identifier for the 'Account Transaction'.
Specifically, the number range combines a six-digit incremental run number with an identifying letter for the transaction ('C'=CREATE, 'U'=UPDATE, 'D'=DELETE') and the type of account involved.
Runtime example:
In the example on the right, the sequence number (#58) appears and is followed by the letter 'D' (DELETE) and the internal class name for the deleted object of the guest user (GuestUser) type. |
|
Configuration:
An event handler is configured as shown on the right:
The Subject for the e-mail is completely defined here by configuring a number range with the Number range type 'Account Transaction'. This contains 5 number parts as shown in the screenshot below:
|
|
|