v1.6.0

Version Number

1.6.0-1

New Features

• SCMOD-4279 - The image is now based on openSUSE Leap 15.0. The release notes for openSUSE Leap 15.0 can be found here.
• Added Nodejs8 compatibility.
  Changed the base image for data processing service container from Nodejs6 to Nodejs8.

Known Issues

• None

v1.5.0

Version Number

1.5.0-390

New Features

• SCMOD-4732: Repository configuration store
  The Data Processing Service has been enhanced with the facility to store repository specific configuration. After a repository setting has been registered with the service values, it can then be stored on a per-repository basis.

Known Issues

• None

v1.4.0

Version Number

1.4.0-274

New Features

• SCMOD-3477: A new feature to allow the management of global configs.
• SCMOD-3111: Tenant configuration store
  The Data Processing Service has been enhanced with the facility to store tenant specific configuration. After a tenant setting has been registered with the service values can then be stored on a per-tenant basis.
• SCMOD-3282: Added Nodejs6 compatability.
  Changed the base image for data processing service container from Nodejs4 to Nodejs6.

Bug Fixes

• CAF-3352: Not condition children underneath Not conditions could not be edited.
  When a Not condition was created with condition set to another Not condition it was not possible to edit the next level of conditions being negated. This has been fixed to allow Rule and Action Condition API calls to retrieve conditions at all levels in the Not chain.
• CAF-3350: Removal of 'fragment' and 'text' conditions from processing API contract.
  The condition types 'fragment' and 'text' have been removed from the swagger contract for the processing API. Logic behind this is that fragment conditions are too complex to expose to users and text conditions require the processing API to have access to a running Elasticsearch instance which the default Data Processing deployment does not enable for the processing API.
• CAF-3328: Updating a processing rule cleared actions that were set on the rule.
  Fixed an issue in the update logic for a processing rule in the processing API where actions set under a rule were lost following an update request to the rule.

Miscellaneous

• The data-processing-initialization project has been moved into its own repository which can be found here.
• Classification Service has been deprecated and all references to it have been removed from this project. This includes the database container no longer has the Classification database pre-installed along with removal of the Classification Service and Classification Worker.

v1.3.0

Version Number

1.3.0-70

New Features

• CAF-3295: Add support to initialization library to remove existing processing workflows, classification workflows, boilerplate expressions and tags before creation based on their names.
  The initialization library classes for processing, classification and boilerplate all support the overwriteExisting property when creating entities through the classes. Default behaviour when the property is omitted is to remove existing entities based on their names matching the current names to be used in creation. The task submitter supports changing this behaviour through a new environment variable CAF_TASKSUBMITTER_BASEDATA_OVERWRITE_EXISTING.

Bug Fixes

• CAF-3352: The negated condition on Not condition could not be edited.
  When action or rule conditions of type boolean are created the IDs of their children are returned and they can be updated, retrieved and deleted. Attempting to perform operations on the condition that was negated in a Not condition returned an error message. Fix has been applied to bring Not conditions in line with Boolean conditions allowing edits of the negated condition directly. This means that either the entire Not condition can be used in operations or just the negated condition (varying the ID appropriately).

Known Issues

v1.2.0

Version Number

1.2.0-49

New Features

• CAF-3056: Create a Family Task Submitter
  The "Data-Processing-Family-Task-Submitter" has been added which queries Elasticsearch using a family reference for a document that has already been indexed, reconstitutes the document and its attachments to construct a policy message, and sends this to a specified policy worker queue.

• CAF-3156: Data Processing Family Classification
  Uses the latest classification-service libraries which add the classificationTarget property to classifications, allowing control of the scope of classification evaluation e.g. root document only, or root document and children that were passed.

• CAF-3198: Extract Workflow Initialization Logic to a separate project
  The data-processing-initialization library has been added which is a utility project with logic to initialize base data for the Processing and Classification workflows and the Boilerplate expressions and tags.

• CAF-3290: Add ability to extend or override default workflow
  Extended the workflow initialization code with the ability to use an overlay type of file or structure which can then be merged into the base definition. This allows use of the default workflow but with replacements/extensions injected during provisioning, thus simplifying upgrades.

Known Issues

v1.1.0

Version Number

1.1.0-20

New Features

• CAF-2928: Added environment variable control over saving the task data only, and cleaning up the Data Store after processing, in the Task Receiver.
• CAF-2952: Added support for priority queues.

Bug Fixes

• CAF-2928: Content of storage references where not output by the Task Receiver.

v1.0.0

Version Number

1.0.0-3

New Features

• Initial open source release of data-processing-service on github.com. Service defines an API that allows creation and management of processing concepts against a Core Policy backend.

Known Issues