The idea

One cannot see the wood for the trees

Some time ago, when I started as a Boomi Consultant (in 2020), when I jumped straight into my first customer project I had the feeling that I wanted to see more than just processes and components. At the customer, there was a repository with thousands of components, distributed over hundreds of folders, deployed to different environments, and, of course, no documentation.

A process calling a sub-process, calling another sub-process, routes to several sub-process, mapping in this folder, another mapping with the same name in another folder, process properties created in the top process, used in the fifth level of sub processes ... how could I understand what has been built?

Component Relationship Diagram

So, my first idea was, I need something like a dependency graph that shows me which components are used in a process (incl. all sub-processes and routes) and I wanted to know, in which folder I can find all referenced components, like mappings, profiles etc.

Create UML Component diagrams

Et voilà: UML - Diagrams were born!

Evolution

Since then, many other needs have arisen. Especially the lack of a Components Set functionality (vs. Packaged Components) was a pain for me in the beginning. I was working on a set of components and I wanted to quickly document and deploy the components in my working-set, instead of clicking-clicking-clicking-deploying each single component.

Deployments

I also wanted to re-deploy and visualize the status of a set of components, especially when it came to promoting all components to a different environment: DEPLOY - Deployments

Excel visualizing the deployment status of a Component Package - containing severall processes

Export profiles

Last but not least, I wanted to see my Json and Xml profiles in their native format. Have you ever tried to export JSON or XML or other profiles?

Exported Profiles