Non-Batched Mapping Configuration in Pimcore Requestador

A non-batched configuration is the standard mapping mode in Pimcore Requestador.

Use this mode when one Requestador action should process one logical set of mapped values at a time.

This is the recommended configuration style for simpler actions and is usually the best starting point when testing a new Requestador workflow.

Use non-batched mapping when:

• one action processes one object with one mapping structure

• only one target language is involved

• the workflow has one input set and one response structure

• the action returns one logical result set

Typical examples include:

• category generation

• short and long description generation

• one-language enrichment

• one-language translation

In non-batched mode:

• Is batched is not enabled

• each parameter is mapped once

• each response field is mapped once

• one configuration represents one logical request structure

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: Leave this option disabled.

This indicates that the configuration should use one standard mapping structure.

Step 5: Map action input parameters

For each action parameter, define how the value is provided.

Typical mapping types include:

• Pimcore field

• fixed value

• language value

For each parameter, configure:

• parameter name

• whether it is required

• type

• source field or value

Example

A non-batched content generation action may use:

• description → Pimcore field → ArticleDescription

• technical → Pimcore field → TechnicalDescription

• language → Language → en

Step 6: Configure response field mapping

Define how fields returned by the Requestador action are written back to Pimcore.

For each returned response field, define:

• response field name

• target Pimcore field

• language, if the target field is localized

Example

• ShortDescription → ShortDescription → en

• LongDescription → LongDescription → en

Step 7: Save the configuration

Click Save.

The configuration is now ready for use in Pimcore.

Furniture description generation

A non-batched configuration for a product enrichment workflow may use:

Action

• pimcore generate furniture descriptions

Class

• Product

Inputs

• description → ArticleDescription

• technical → TechnicalDescription

• language → en

Outputs

• ShortDescription → ShortDescription

• LongDescription → LongDescription

This is a typical single-language, single-result configuration and is a good example of non-batched mapping.

• start with non-batched mode for new actions

• use this mode when the workflow is simple and single-purpose

• keep input mappings minimal and explicit

• verify that response field names exactly match the Requestador output

• test on one object before using the configuration more broadly

Non-batched mapping is the standard configuration mode for Pimcore Requestador.

It is best suited for actions that:

• process one logical request at a time

• use one mapping structure

• return one response structure

This is the simplest and most direct way to configure Requestador in Pimcore.