The CloverDX Designer allows you to build the vast majority of our your transformation logic using visual components.
Visual only tools, however, always have limitations and when you hit those limitations it can be extremely frustrating. And when you hit those limitations, you are usually left with nowhere to go.
Example - Field mapping logic using code
Debugging - a full code debugger
CloverDX Designer and Server are both designed to be as open as possible, allowing many sorts of customization wherever needed.
The source format for CloverDX transformations is XML. If you encounter edge cases, being able to modify a transformation by altering the transformation source allows you to deal with almost any scenario you are likely to encounter.
There are many locations where configuration of items such as database parameteres, lookups, data structure definitions etc. are stored.
All of these can be modified without having to use a CloverDX front end.
The text based nature of CloverDX allows developers to collaborate using tools such as Git and Mercurial and integrate transformations into devops type workflows.