Assessment workflow differs from common workflow due to its output which alludes to the actual workflows the invoker of the assessment may be interested in.

In v1 the assessment workflows were defined statically, however, with time, the intention would be to invoke a workflow to analyze the use case. The options available for it today are the custom-code or serverless spec.

It is important to define the structure of the output of the assessment statically, so it can be common for all of the assessment workflows and known by the frontend plugin.

References: https://sonataflow.org/serverlessworkflow/latest/core/defining-an-input-schema-for-workflows.html#_output_schema

Acceptance criteria: 

• An example of a workflow of type assessment using SonataFlow CR (specifically CR is needed to identify no gaps from the serverless workflow spec)
• A software template with required jsonInputSchema and jsonOutputSchema