ResourceCategoryConversionExecutorProcessor

Version #1

Description:

Represents the conversion of a resource category. This processor has the ability to execute multiple subflows representing the conversion.
It automatically handles origin resource files.
Its logic is optimised in a manner which reduces the number of conversions needed to represent the full conversion. To achieve this you must provide information about the conversion, namely which data change should trigger the real conversion. This can be set in the configuration.
If there is no conversion needed, the resource conversion is skipped end every converted file will get a Keep request. To achieve this, every time you return your requests they must be tied to the appropriate resource ID.
Note that category conversion is executed every time the complexity of checking the need for conversion. You are also free to implement your logic in the category conversion flow and you can also return Keep requests.
A resource converter may be executed multiple times by using forEachIf on each resource. If you do not configure when the conversion is needed the default behaviour is to execute it for each resource.
Note that forceConvert will ignore the conditions in a way that everything will be executed.
Note that you are not required to provide both subflows. If a flow ID is not specified it will be assumed that no conversion is needed. Therefore no files should be present and all existing converted files tied to the according type (resources or the category) will be deleted.

Interface:

Internally used structures:

Basic sample:

<processor id="<FLOW_SCOPED_ARBITRARY_ID_GOES_HERE>" name="ResourceCategoryConversionExecutorProcessor" version="1" />

Advanced sample:

<processor id="<FLOW_SCOPED_ARBITRARY_ID_GOES_HERE>" name="ResourceCategoryConversionExecutorProcessor" version="1">
  {
    "allResources": ALLRESOURCESCONVERTEREXECUTIONCONFIGSTRUCTURE:V1,
    "postGenerate": POSTGENERATEEXECUTIONCONFIGSTRUCTURE:V1,
    "singleResource": SINGLERESOURCECONVERTEREXECUTIONCONFIGSTRUCTURE:V1
  }
</processor>

Chainable processors: