Releases: CAFDataProcessing/worker-workflow
Releases · CAFDataProcessing/worker-workflow
v4.0.0
Version Number
4.0.0-466
Breaking Changes
- SCMOD-6784 - Workflow and settings js files are no longer supported as workflows are now defined using yaml.
New Features
- SCMOD-6857 - Update to read queue names from configuration.
More details can be found here. - SCMOD-6932 - Enrichment & Ingestion workflows wont adjust Bulk Indexer failure queue and this is handled by adding
terminateOnFailureflag on each required worker - SCMOD-7133 - Reading the workflow name from root document
- SCMOD-7132 - Error handling on the workflow has been improved
- SCMOD-6931 - Worker Versions recorded as objects in a field
- SCMOD-7711 - The Name and Version of the workflow used, is retrieved from application object
Bug Fixes
- SCMOD-7698 - Fixed poison message handling
Known Issues
- None
v3.0.0
Version Number
3.0.0-335
Breaking Changes
- SCMOD-5747 - The workflow worker does not use the processing-service and the
workflow-admin anymore. Workflows are loaded from files saved on disk (look at the worker-workflow README for more info).
New Features
- SCMOD-5739 - The Data Processing Service and Policy were replaced with Settings Service.
Known Issues
- None
v2.0.0
Version Number
2.0.0-250
New Features
- SCMOD-5144: Workflow Id no longer required
Workflow Id can now be substituted for the name of the workflow to use. - SCMOD-4898: Discard superfluous tracking messages.
The CAF_WORKER_DISABLE_ZERO_PROGRESS_REPORTING environment variable can be set to true to cause zero-progress tracking messages not to be sent.
Known Issues
Breaking Changes
- SCMOD-5326: Source parameter to workflow updated
Source parameter in workflow can now be either a string on an object under different circumstances, this is discussed and examples shown in documentation. TenantData Source is no longer supported and workflow produced now takes custom workflow configuration settings that are supplied to the script on the customdata for the document being processed.