In Parodos v2, the chosen workflow system is sonataflow which uses serverless workflow spec.

This sonataflow and serverless workflows replace the easyflow library and should be used not only as a method to serve the same workflow definition, but also as a method to provide non-easyflow features such as:

• Escalation workflow
• Assessment workflow
• Checker workflow
• Fallback (compensation)
• Retries
• etc.

Using serverless workflow, we can define smarter workflows and rely on advanced features than the basic ones that were offered by easyflow.

For example, easyflow had the option to define simple control flows, but more specific ones had to be implemented by code.

The purpose of this epic is to:

• Learn how to provide Parodos concepts, by creating a git repository for all of the examples. This can be served as part of the documentation for the workflow developer and ease the learning curve of the developers.
• Augment current Parodos workflows implementation, e.g. add retries to access REST endpoints in a nicer DSL like (instead of coding it) and more.
• Identify actual gaps when trying to provide the Parodos v1 workflows via serverless workflows.

Please follow this document to start working with sonataFlow/kogito.