HTM Processor
The HTM floclient allows for custom configuration of each property that can be sent to the HTM service. This is done through the 'HTM Processor' interface. It is possible to register a processor for each individual task type.
Default HTM Processor
The default HTM processor is used as a fallback for any task type where a custom processor has not been provided. It has the following properties:
| Property | Default Implementation |
|---|---|
Idempotency |
Checkpoint + "_" + HTM Request Name |
Due Date |
Current Time + 1 Day |
Supporting Data |
If no business elements provided, this is empty. If 1 business element provided, this is used as the payload. If 2 or more business elements are provided, this throws an exception. |
Meta Tags |
Returns the static data list only. |
SupportedTypes |
Returns the generic fallback entry. == Idempotency The HTM application requires a unique key to be passed that uniquely identifies a given task. This is used to ensure that it is not possible to create multiple identical tasks (through retries etc). The Floclient application default uses a combination of the current checkpoint in the flow and the task type to generate this key. |