You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, CALM provides a command-line interface (CLI) tool that allows users to visualize nodes and relationships in an architectural specification. While this is valuable for understanding the technical architecture, it does not visualize business flows that traverse these components. Something that is now possible in CALM via #426.
Propose modifying the existing CLI to support the visualisation of business flows. This enhancement would allow users to input a separate flow specification file, enabling them to see how business processes interact with nodes and relationships in the architecture.
Potential solutions
Provide a visualize option where only the flow document is provided as input argument calm visualize -f flow.json
In this solution, a flow definition has links back to the calm document which contains the references node/relationships.
Enhance the existing command to take a flow id which you want to visualise calm visualize -i calm.json -f "flow-001"
This solution implies that calm.json has direct knowledge of all flows that are linked to it i.e. core.json would be updated to contain a flows array.
Specify both the calm.json alongside the flow.json document you want to visualise calm visualise -i calm.json -f flow.json
The text was updated successfully, but these errors were encountered:
Feature Request:
Currently, CALM provides a command-line interface (CLI) tool that allows users to visualize nodes and relationships in an architectural specification. While this is valuable for understanding the technical architecture, it does not visualize business flows that traverse these components. Something that is now possible in CALM via #426.
Propose modifying the existing CLI to support the visualisation of business flows. This enhancement would allow users to input a separate flow specification file, enabling them to see how business processes interact with nodes and relationships in the architecture.
Potential solutions
Provide a visualize option where only the flow document is provided as input argument
calm visualize -f flow.json
In this solution, a flow definition has links back to the calm document which contains the references node/relationships.
Enhance the existing command to take a flow id which you want to visualise
calm visualize -i calm.json -f "flow-001"
This solution implies that calm.json has direct knowledge of all flows that are linked to it i.e. core.json would be updated to contain a flows array.
Specify both the calm.json alongside the flow.json document you want to visualise
calm visualise -i calm.json -f flow.json
The text was updated successfully, but these errors were encountered: