Visual, <span class="green">hackable</span> and <span class="red">open architecture</span>
  • Write code to tailor transformations

    Hack your transformations

    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.

    code simple

    Example - Field mapping logic using code

    code debug

    Debugging - a full code debugger

    Other points of interest

    • The underlying source code is XML, so you can hack this or even generate your own transformations from code.
    • Use source control systems such as Git, Mercurial and SVN.
    • Make it fit with developer workflows.
  • Open architecture

    Open architecture

    CloverDX Designer and Server are both designed to be as open as possible, allowing many sorts of customization wherever needed.

    open

    Transformation source

    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.

    Configuration points

    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.

    Developer workflows

    The text based nature of CloverDX allows developers to collaborate using tools such as Git and Mercurial and integrate transformations into devops type workflows.