UppercasePostExecuter

The UppercasePostExecuter is used to replace all lowercase letters of a text with uppercase letters.

Typically, it is used in phase 6 of a profile to prepare the output for a response path in an EDI-compliant manner if a recipient is only supposed to receive capital letters.

In the configuration of the response path in the Content Settings tab, there is a section called Set Post execution for this purpose:

• The UppercasePostExecuter can be selected under Treatment of data post execution.

• For formal reasons, the definition of a valid path to a Config file (see below) is absolutely necessary.

• The option 'Post execution' before compressing data must be set if the response path in the Archive Settings section requires compression. Otherwise, the UppercasePostExecuter 'handles' the already compressed data, which usually makes the archive file unusable.

The Config file can be assigned to the charset parameter to specify the character set to be used for output.

If no charset is specified in the Config file, the output is generated with the EDI-typical character set ISO-8859-1.

►IMPORTANT◄ The assignment for the characters set (charset) must not be empty or invalid, otherwise the profile terminates with an error at runtime.

►NOTE◄ In principle, the UppercasePostExecuter can also be used in phase 5 of a profile in order to 'post execute' the result of an Integration Unit specified there uniformly for all response paths. However, it should be considered that the names of data elements (e.g. field names in JSON or element and attribute names in XML) may be output in upper case and thus become unusable for the respective recipient.