PROBLEM

Since the "normal" Export in case of errors in the OKAPI process generates an Export-ZIP still (with an "export-error.txt" file inside) these erroneus exports will be synced to the Hotfolder (especially with workflow-automation).

SOLUTION

We need to improve the export-process. Instead of the "ZIP with error-message inside" a failed export should lead to an error-message for the user exporting and the export-worker should defunc with an exception:

• The error in the GUI should be like "The Export failed, plese see the last error in the task-events for details (failed Worker: OkapiExportWorker)"
• The task-eventlog entry stays the way it is
• The Worker should throw an Exception leading to be defunct (this may defuncts the whole sequence up to the parent export worker: must be checked)
• Usually, in export-workers (like  OkapiExportWorker) an exception is logged manually for the task. Throw it instead ...
• There must be a config to force the old behaviour (customer level). The text of the config should hint at the dangers for remote consumers like hotfolder
• One general Problem is to find the error caused by the defunct worker e.g. with a failed export (this also is a problem for other operations)
• To solve this, the existing field "worker" in the tables LEK_task_log should be filled with the worker in case of exceptions. There is code to achieve that (ZfExtended_Logger::fillWorker) but apparently it does not work. Evaluate why & fix it. If it is not fixable, pass the worker as additional (new) param in ZfExtended_Worker_Abstract::runQueued to the logger
• A notification/warning should be sent to the configured default-PM (-> runtimeOptions.plugins.Hotfolder.defaultPM, -> runtimeOptions.plugins.CotiHotfolder.defaultPM) in case an export fails - just like with the import

These changes should enable the Hotfolder & CotiHotfolder Exports to properly react on failed exports. The needed Changes there are part of this issue.