Process and Logic Visualization

Content

Introduction

This feature allows its user to generate detailed end-to-end diagrams to offer a visual representation of your system's processes and logic. Furthermore, pinpoint issues with ease and facilitate swift problem-solving. Visualize data flows and dependencies to enhance clarity and streamline decision-making. Analyze and optimize individual components efficiently without extensive navigation. Identify and prevent potential logical loops in your system by accessing metadata and component links easily. This ensures seamless integration and reference. Furthermore, gain valuable insights into best practices for plugin and extension development, empowering you to enhance your system's capabilities with confidence.

Please ensure that you have configured your integrations. See here: Integrations

System Visualization

  • Auto-generate end-2-end diagrams of the entire system’s process and logic

  • Identify issues through the generated diagrams

  • Visualizations of data flows and dependencies

  • Understand component details without skimming through your environments

  • Identify potential logical loops

  • Find associated metadata and links to components

image-20240306-081522.png

Step-by-Step Instructions

Below is an example illustrating how to adapt the process for your system's components.

The Visualization feature allows for searching components loaded into the cache. In this example, the “Notify Account Advisor” [Workflow] is examined as a component within Dataverse.

Step 1: Enter a component name or desired keyword in the search bar. Click on the component name when it appears.

Step 2: Wait for the analysis to complete and for the component to be visually displayed.

Step 3: Once done, click on the component name again to open the diagram with the visualized components.

Step 4: The diagram box will provide the detailed information you need through visualization.

  1. Component's source. In this example, it refers to “Dataverse”.

  2. Component type. In this example, it refers to “Workflow”.

  3. Related source name to the component. In this example, it is ”GoletDev1”.

  4. Component name

  5. Detailed information. See Step 5 below for more details.

  6. Events that trigger the component

  7. API calls are used by the component

  8. Related source to the event

  9. Details about the event

  10. Event name

  11. Visualize the event

Step 5: For additional details about the component, click on the 'i' icon or the extend icon. In this example, it refers to Workflow.

Step 6: To analyze the 'Create Account' event and identify the affected components, click on the triangle icon (image-20240306-081805.png ). Then, click on the “Create Account” event to analyze the affected components.

Step 7: Once finished, you will see the components that are affected by the “Create Account” event: “TestGolet”, “Sync to SAP”, “SynctoSAP” and “AccountPlugin”.

This feature visualizes relationships and dependencies between components and events, while also providing insights into potential problem areas.

Remove elements from the Visualization

Components can be removed by clicking the delete button on the component.

image-20240319-081641.png

A Dataverse event can be removed by right-click with the mouse at the event.

Then a dialog will show up, asking if the user wants to remove the event.

image-20240319-081806.png

Best Practice Violation in Visualization

Best Practice Violations are implementations within your systems that go against Microsoft's or industry best practices. (See more: Best-practice Check)

Users can find these violations in the 'Best Practices Check' feature as well as in the visualization. In the example below, you can see that the 'AccountPlugin' component has 5 best-practice violations, indicated by a red rectangle with a number representing the count of violations.

To view more information about the Best Practice Violations of the component, simply click on the red rectangle, and a pop-up with additional details will appear (see screenshot below)

Need help? Contact support