SHAR was designed to facilitate workflow first or code first development. This system is underpinned using Task Specification files.

Task Specification files are simple human-readable YAML text files that completely describe a services inputs and outputs, any errors that can occur, and the retry behviour.

Zero Code Workflow Execution.

A Task Specification can designate the task as a ‘Mock’. When a Mock Task is used, SHAR will use the example parameters described in the Task Specification allowing you to test your workflow without having to provision the service.

Workflow First

With workflow first development, you define the workflow, giving each service task in your workflow a set of input an output parameters.

Once you have defined your workflow, you can use the SHAR CLI to generate the Service Task Specification files, so a developer can start building the service tasks.

Code First

A developer defines the Service Task Specification files, and then uses the SHAR CLI to generate the skeleton code template so they can provision the functionality.

The SHAR CLI can then generate a ‘Contact Sheet’ with BPMN Service Tasks ready to drop into a workflow.

Parallel Development

A Business Analyst and a Developer can define the Service Task Specification files. Then as the business analyst crafts the workflow, the developer can use the SHAR CLI to generate the skeleton code ready to provide the functionality.