Custom process steps

Besides all the hooks, it is also possible to register custom process steps. How to register a custom step is covered in the Administration chapter. This section describes what a custom step can or should do and what resources are available from within a custom step class.

Custom steps are much more powerful than hooks and should be preferred whenever that makes sense. Custom steps have access to much more information than hooks, although most hooks are more specific. Also custom steps are registered per configuration, which removes the need to test inside them which import configuration is being handled.

Parent class

A custom step class must inherit from abstract class \Cobweb\ExternalImport\Step\AbstractStep. If it does not, the step will be ignored during import. The parent class makes a lot of features available some of which are described below.

All step class instances are created using the \TYPO3\CMS\Extbase\Object\ObjectManager, so Extbase’s injection mechanisms is available inside a custom step class.

Available resources

A custom step class has access to the following member variables:

Instance of the current External Import configuration (\Cobweb\ExternalImport\Domain\Model\Configuration).
Instance of the object model encapsulating the data being processed (\Cobweb\ExternalImport\Domain\Model\Data).
Back-reference to the current instance of the \Cobweb\ExternalImport\Importer class.

See the API chapter for more information about these classes.

Furthermore, the custom step class can access a member variable called abortFlag. Setting this variable to true will cause the import process to be aborted after the custom step. Any such interruption is logged by the \Cobweb\ExternalImport\Importer class, albeit without any detail. If you feel the need to report about the reason for interruption, do so from within the custom step class:

        'Your message here...',
        FlashMessage::WARNING // or whatever error level

In general, use the getters and setters to access the member variables.

Custom step basics

A custom step class must implement the run() method. This method receives no arguments and returns nothing. All interactions with the process happens via the member variables described above and their API.

The main reason to introduce a custom step is to manipulate the data being processed. To read the data, use:

// Read the raw data or...
$rawData = $this->getData()->getRawData();
// Read the processed data
$records = $this->getData()->getRecords();


Depending on when you custom step happens, there may not yet be any raw nor processed data available.

If you manipulate the data, you need to store it explicitely:

// Store the raw data or...
// Store the processed data


Custom steps get to manipulate the whole data set, contrary to many of the hooks, which are called while looping on each entry in the data set.

Another typical usage would be to interrupt the process entirely by setting the abortFlag variable to true, as mentioned above.

The rich API that is available makes it possible to do many things beyond these. For example, one could imagine changing the External Import configuration on the fly.

In general the many existing Step classes provide many examples of API usage and should help when creating a custom process step.

Preview mode

It is very important that your custom step respects the preview mode. This has two implications:

  1. If relevant, you should return some preview data. For example, the TransformDataStep class returns the import data once transformations have been applied to it, the StoreDataStep class returns the TCE structure, and so on. There’s an API for returning preview data:


    The preview data can be of any type.

  2. Most importantly, you must respect the preview mode and not make any persistent changes, like saving stuff to the database. Use the API to know whether preview mode is on or not:



Finally here is a short example of a custom step class. Note how the API is used to retrieve the list of records (processed data), which is looped over and then saved again to the Data object.

In this example, the “name” field of every record is postfixed with a simple string.

namespace Cobweb\ExternalimportTest\Step;

use Cobweb\ExternalImport\Step\AbstractStep;

 * Class demonstrating how to use custom steps for external import.
 * @package Cobweb\ExternalimportTest\Step
class EnhanceDataStep extends AbstractStep
     * Performs some dummy operation to demonstrate custom steps.
     * @return void
    public function run()
        $records = $this->getData()->getRecords();
        foreach ($records as $index => $record) {
            $records[$index]['name'] = $record['name'] . ' (base)';