We are pleased to announce a new release of Automatiko - 0.6.0
In many situation awaiting response when interacting with workflow instances might not be desired behaviour. It might be due to various reasons such as
Async execution is provided by an HTTP header and can also request a callback to post data once execution is completed.
Have a look at Automatiko documentation for more information about async execution.
In many cases there are needs to simply do basic operations - like sending email to notify about created incident. Such operations are usually reusable and as such should be easily configured within workflow tasks. This is what has been started in 0.6.0 release of Automatiko - an addon services. With this version following services are delivered
Have a look at Automatiko documentation for more information about addon services provided out of the box.
When workflow instance reaches its end (either by completing successfully or by being aborted) there might be situations that requires it to be handled in one way or another. For this exact purpose, end of instance strategies are provided. These allow to have different behavior depending on your needs. For example due to legal requirements instances must be kept for given amount of time, or they should be archived to another location for reference. Automatiko provides three out of the box strategies:
Have a look at Automatiko documentation for more information about end of instance strategies.
Workflow as a Function Flow is a very powerful concept that allows high scalability based on KNative Eventing but allowing developers to focus on complete business use case rather just individual functions. Automatiko 0.6.0 brings support for Google PubSub as event sink instead of default http based one. The main advantage of this sink is to be able to take advantage of managed KNative environment that is Google CloudRun. With the support of this component users can run workflow as a function flow directly on managed service and rely on higly scalable messaging infrastructure - Google PubSub.
A complete blog post dedicated to this topic is in the works and will be published within few days!
Apache Camel connector has been supported for quite some time. It allows to take advantage of any of the supported
Apache Camel connector as implementation behind message events (both sending and receiving). Until now, it had a missing feature
- to be able to specify headers (headers are frequently used by Apache Camel components to provide configuration).
Since Automatiko 0.6.0 you can specify any of the headers as part of custom attributes of the message event. All entries
that starts with
Camel will be considered headers.
When working with business rule tasks that invoke decision you can now take advantage of error handling. That can be either
DecisionEvaluationFailure. In addition, error information can be mapped to workflow instance variable that will be of type
Mapwith following entries:
error- string representation of all error messages returned from the evaluation
results- data returned from the evaluation (might be partial)
Photographs by Unsplash.