Processors are an optional part of a component configuration. While they are not at all necessary in the development of new components for KBC, we think that you should know about them; they can save you a lot of time in some cases. To get a list of currently available processors, see the official component list.
To be able to configure the processors in the KBC UI, go to the
Developer Portal and add the UI
genericDockerUI-processors to your component. You’ll then see
a new UI element in the component configuration in KBC:
Taking the example component, you might want to use the Add Row Number Column processor in your component to add a sequential number to every row of the table imported into KBC. From the processor documentation you can see that the processor is configured as:
You want the processor to execute on the output of your component; it means that the
above should be inserted into the
after (after your component runs) section:
If you run the above configuration, you’ll receive an error:
Table odd.csv does not have a manifest file.
This is expected because the Add Row Number Column processor documentation clearly states that the processed CSV files must have manifests and not headers. Since the example component is very simple and does not generate manifests (or header-less CSV files), you have to add other processors to do that for you:
after configuration is an array of three processors. The first one creates
manifest files for whatever data files were produced by your component. The manifest
files will contain a header read from the data files. The second processor removes the header
from the data files. The third processor adds the row number column.
Configuring processors is not part of the component development. However, processors allow the end user to customize the input to the component and the output from it. That means that they can be used to implement specific customer requests while keeping the component code general.
Choosing whether to implement a specific feature as a processor or as part of your component may be difficult. A processor might be a good solution if the feature is