Batched Mapping Configuration in Pimcore

A batched configuration allows one Pimcore Requestador configuration to contain multiple grouped mapping structures within the same action configuration.

This mode is useful when the same Requestador action should process repeated mapping groups, most commonly across multiple target languages.

Use batched mapping when:

• the same action should run for multiple language targets

• one configuration should contain repeated grouped mappings

• the same source values are processed in several contexts

• the action is designed for grouped or repeated execution logic

Typical examples include:

• translation into multiple languages

• repeated multilingual enrichment

• grouped content generation workflows

In batched mode:

• Is batched is enabled

• one configuration contains multiple grouped sections

• each group can represent a language or another repeated mapping context

• each group contains its own input mapping structure

This makes batched mapping especially useful for multilingual translation actions.

Step 1: Open Requestador configuration in Pimcore

In the Pimcore backend, open the Requestador configuration section.

Create a new configuration entry.

Step 2: Select the Requestador action

Choose the action that should be executed from Pimcore.

This action must already exist in Requestador.

Step 3: Select the Pimcore class

Choose the Pimcore class for which the configuration should be used.

Example:

• Product

Step 4: Enter configuration metadata

Title: Provide an internal title for the configuration.

Group: Assign one or more groups if needed for organization or filtering.

Is batched: Enable this option.

• This indicates that the configuration contains multiple grouped mappings.

Languages: Select the target languages or grouped contexts that should be included in the batched configuration.

Example:

• fr

• de

Step 5: Configure grouped input mappings

For each batch group, define the required parameter mappings.

Each group contains its own parameter structure.

Typical mapping types include:

• Pimcore field

• fixed value

• language value

Example structure for: fr

• language → Language → fr

• name → Pimcore field → ProductName → source language en

• short_description → Pimcore field → ShortDescription → source language en

• long_description → Pimcore field → LongDescription → source language en

Example structure for: de

• language → Language → de

• name → Pimcore field → ProductName → source language en

• short_description → Pimcore field → ShortDescription → source language en

• long_description → Pimcore field → LongDescription → source language en

In this setup, the same source content is reused for multiple target-language execution groups.

Step 6: Save the configuration

Click Save.

The batched configuration is now ready to be used in Pimcore.

A batched configuration for a translation action may use:

Action

• pimcore general translate

Class

• Product

Batch mode

• enabled

Languages

• fr

• de

Grouped mappings

• one section for French

• one section for German

Each group maps source Pimcore fields such as:

• ProductName

• ShortDescription

• LongDescription

from source language en into the selected target language.

This allows one configuration to manage translation for multiple languages within one setup.

Non-batched mapping

• one mapping structure

• one execution context

• simpler configuration

• best for single-result workflows

Batched mapping

• multiple grouped mapping structures

• repeated execution context within one configuration

• best for multilingual or repeated grouped workflows

• use batched mode only when the workflow clearly requires grouped execution

• keep all grouped sections consistent in structure

• verify source and target language mappings carefully

• ensure the Requestador action is designed to support batched use

• test with a small number of languages first

• validate the output carefully before broader usage

Batched mapping is used when one Pimcore Requestador configuration must handle multiple grouped mappings inside the same action setup.

It is especially useful for:

• multilingual translation

• repeated grouped enrichment

• actions that apply the same mapping logic across several target contexts

When configured correctly, batched mapping reduces duplication and makes multilingual workflows easier to manage.