Correlation ID 

The correlation ID is generated from the form identifier and a unique key to identify associated transfers – as you can start multiple instances from one form and transmit data to a JobData table. The correlation ID is stored in a column in the transfer tables together with the form data. This is useful if you want to check the data from the instance against the original data from the form.

The correlation ID looks like this: form_demo-20_63fca23b1accb where form indicates the ID is generated by a from finisher, demo-20 is the form identifier with the content element uid of the form plugin and 63fca23b1accb is the unique key.

Use the {__correlationId} variable to add the correlation ID.

Localisation labels 

Values can be localised with the help of the localisation labels known from various parts in TYPO3. The variable starts with {__LLL: and holds the path to the translation file and the according key, for example, {__LLL:EXT:your_ext/Resources/Private/Language/locallang.xlf:your.label}.

If the label is not found and therefore cannot be translated the value is untouched.

You can use multiple localisation labels in one form value.

Language information 

The language information defined in the Site Configuration can be used, namely:

{__language.base}

The base URL for the language, for example, https://example.org/en/.

{__language.flagIdentifier}

The defined TYPO3 flag identifier used in TYPO3's backend, for example, flags-gb.

{__language.hreflang}

Language tag for the language defined by RFC 1766 / 3066 for lang hreflang attributes, for example, en-gb.

{__language.languageId}

The language ID defined in the site configuration.

{__language.locale}

The used locale, for example, en_GB.UTF-8.

{__language.locale.countryCode}

The ISO-3166-1 alpha-2 country code, for example US.

{__language.locale.languageCode}

The ISO-639-1 language ISO code, for example, en.

{__language.navigationTitle}

The navigation title defined in the site configuration, used as label within language menus, for example, English.

{__language.title}

The title defined in the site configuration, for example, English.

{__language.typo3Language}

default for English, otherwise one of TYPO3's internal language keys.

Multiple language variables can be used in one form value.

JobRouter language information 

Sometimes it is necessary to use not the language code of the page in your form but instead the language string JobRouter® uses (for example, german instead of de). This can be useful for sending localised emails from the process in the relevant language.

Use the {__jobRouterLanguage} variable for that. The following languages are supported by JobRouter® in recent version:

If the language is not available, an empty string is returned by the variable resolver.

Page properties 

The properties of the page where the form is located can be retrieved. The variable starts with __page.. Any existing page property, such as uid or title, can be used, for example: {__page.title}.

If a page property is not present, the variable is used unchanged.

Example 

As an example we want to resolve a variable to a cookie value with an event listener:

<?php
declare(strict_types=1);

namespace YourVender\YourExtension\EventListener;

use JobRouter\AddOn\Typo3Base\Event\ResolveFinisherVariableEvent;
use Psr\Http\Message\ServerRequestInterface;
use TYPO3\CMS\Core\Attribute\AsEventListener;

#[AsEventListener(
   identifier: 'your-extension/cookie-variable-resolver',
)]
final readonly class TheCookieVariableResolver
{
   private const COOKIE_NAME = 'the_cookie';
   private const VARIABLE = '{__theCookieValue}';

   public function __invoke(ResolveFinisherVariableEvent $event): void
   {
      $value = $event->getValue();

      if (str_contains($value, self::VARIABLE)) {
         // Variable is not available, do nothing
         return;
      }

      $cookies = $event->getRequest()->getCookieParams();

      $variableValue = $cookies[self::COOKIE_NAME] ?? '';
      $value = str_replace(self::VARIABLE, $variableValue, $value);

      $event->setValue($value);
   }
}

Added 

• Compatibility with TYPO3 v14
• Support Ukrainian in JobRouterLanguageResolver

Removed 

• Compatibility with TYPO3 v12 (#1)

Added 

• Compatibility with TYPO3 v13

Removed 

• Compatibility with TYPO3 v11
• Language variables {__language.twoLetterIsoCode} and {__language.direction}

Changed 

• Namespace from Brotkrueml\JobRouterBase to JobRouter\Addon\Typo3Base

Added 

• Processing of an attachment and date as field type
• Compatibility with TYPO3 v12

Changed 

• FieldTypeEnumeration is now an enum named FieldType

Removed 

• Compatibility with TYPO3 v10
• Compatibility with PHP 7.4 and 8.0

Added 

Added 

• Support Lithuanian, Portuguese and Serbian in JobRouterLanguageResolver

Removed 

• Compatibility with PHP 7.3

Added 

• Common translations for dependent extensions
• Support Croatian in JobRouterLanguageResolver

Added 

• Compatibility with TYPO3 v11 LTS
• Variable resolver for page properties

Removed 

• Compatibility with PHP 7.2

Added 

• Show number of days for available transfers in status widget

Changed 

• Text and icon in transfer report widget when no errors occur

Added 

• Dashboard widget for transfer report

Changed 

• Raise minimum required version to TYPO3 10.4.11