We state that many of our components have already been prepared in an ‘opinionated’ manner. What does that actually mean? We are happy to explain.
From the beginning
We would like to explain how Dovetail flow building works, because that helps us to show how opinionated components are used.
After a paper mapping* has been made of the desired flow situation and all data has been collected to gain access to the applications (such as API keys, tokens, API documentation, contact details, etc.) integration flows can be built.
For each flow, a start and end point is determined and is determined what should be done with the data. A component can be added for every action in the flow, for example;
- Splitting data, where different parts of a message have to be processed in a different way
- Converting data from one format to another, such as CSV to XML, XML to JSON or EDIFACT to XML
- Aggregating data (information is collected and expressed in a concise form, for purposes such as statistical analysis)
- Enriching data, for example from another system
- Determining rules, what should happen with the data that comes in
- Link with other integration flows, to build new integrations even faster
- Filtering and routing messages, not every message that comes in has to follow the same route
When it has been determined which start and end points there are and what should be done with the data, components can be selected by simply dragging and dropping and a flow can be created.
For each component the options must be set; very specific information such as the API key, but also a lot of information that is the same for everyone. For these standard information options, that are generally fixed values, we have pre-set the components and therefore we call it an opinionated component.
Using these opinionated components makes building integration flows achievable by non-developers. Only the customer-specific values now need to be entered. This can easily be done by someone with knowledge of the business.
We call the entry of the standard data “opinionated”, with this we want to indicate that we have already entered many standard values because we know in advance that these data are the same for everyone.
Benefits of using Dovetail
Because Dovetail flows can be created by the process experts within the business, it becomes accessible for all organizations with an increasing digitization need, but who have limited resources and/or access to developers.
Dovetail also ensures a short time-to-market for a new integration. Any integration specialist who has already created a Dovetail flow can build the next flow very quickly.
There is also a lot of information available in the Dovetail Academy, which can serve as a handy reference book.
Want to learn more about the low code/no code iPaaS Dovetail? Click here
*Paper mapping: Visual overview on paper or PC, including work instructions, datasets as reference, up to and including identified inefficiencies or pain points for improvement.