Text

See also: Value from localization

Resolver – Abstract

Purpose: Defines a static text value (String) in the context of a value configuration.

images/download/attachments/128387171/image2023-1-18_11-4-28-version-1-modificationdate-1676010925270-api-v2.png

IMPORTANT◄ All resolvers for Static values ignore the input value. Within a resolver chain (see Verketteter Wertauflöser) this prevents the processing of all preceding resolvers (if any).

The Text resolver defines a static text value (String) in the context of a value configuration.

It appears by default as a suggestion for value configurations from which a String value is expected.

NOTE◄ Before each use of the Text resolver in a value configuration, it has to be evaluated whether the respective text value should be implemented statically or via a reference to the Localization or Company specific localization. Even if there is no acute need for a 'localization' in the sense of a specific expression of the static text for the Current locale in a session, the use of the Value from localization resolver should be considered to enable a later localization. Of course, there are also many uses for technical strings, such as defining parameters in a configuration (e.g. 'variable name' in the Variable resolver), raw data for a file (see File reference), or to define a data object (see JSON to object, etc.). For such content, there is the Text resolver.

Configuration

The Text resolver offers a Text field element with the display type 'multiline text' with the following properties:

  • The height and width of the input field can be changed by drag & drop on the gray marked corner (bottom right).

  • Depending on the width, an automatic line break may become active, which has no influence on the returned text value.

  • As far as necessary, a vertical scroll bar appears on the right (as in the image).

  • The static string can contain line breaks etc. and can be of any length.

images/download/attachments/128387171/image2023-1-18_11-11-27-version-1-modificationdate-1676010925246-api-v2.png

Special case: Direct input for a text parameter


If a text value is expected for a parameter in the context of a configuration, which should be definable either as static text or by any other value configuration, the user interface initially offers a Text field for the direct input of static text.

Example: Default error message parameter in the Abort event action.

images/download/attachments/128387171/image2023-1-18_11-5-3-version-1-modificationdate-1676010925267-api-v2.png

  • If direct input is used by entering static text into the Text field, then the input is assigned to a Text resolver as a text value in the background.

  • However, the Text resolver is typically not displayed even if static text is already defined:
    images/download/attachments/128387171/image2023-1-18_11-5-56-version-1-modificationdate-1676010925265-api-v2.png

  • Only a click on the small gray arrow at the bottom left of the Text field activates the usual display of the value configuration for the parameter:

    images/download/attachments/128387171/image2023-1-18_11-6-16-version-1-modificationdate-1676010925262-api-v2.png


  • A click on the [+] symbol on the right side of the value configuration allows access to the text in the Text resolver:

    images/download/attachments/128387171/image2023-1-18_11-6-43-version-1-modificationdate-1676010925260-api-v2.png


Example

In the context of event handling, an Abort is executed under certain circumstances, which displays a default error message (CORESYSTEM_BaseDataManager_uniqueKeyViolationWithField) to the user.

The localization of the error message uses a parameter ({0}), which in our context should be assigned a static text value ('GTIN'):

Localization for error/CORESYSTEM_BaseDataManager_uniqueKeyViolationWithField (Deutsch)
{0} must be unique.

Configuration:

The Abort event action is parameterized as shown on the right:

  • The Error type selected for the given example is 'Notification: Error'.

  • The Error code CORESYSTEM_BaseDataManager_uniqueKeyViolationWithField refers to the respective resource name in the bundle error of the Localization. There the specific localization of the error per Locale is defined.

  • A Default error message is not specified.

  • Exactly one Parameter is added by clicking the images/s/-95e2zf/9012/8yg2g7/_/images/icons/emoticons/add.svg symbol. At runtime, the assigned text value will replace the string{0}in the localization text for the Current locale.

  • The parameter is assigned the static text value 'GTIN'.

images/download/attachments/128387171/image2023-1-18_11-7-20-version-1-modificationdate-1676010925251-api-v2.png

Runtime example: