Managed Graphs

Managed Graphs allow business logic to be shared with users within your organization and within child organizations. The content within a managed graph is locked and cannot be edited by users of the graph. If you are building a managed graph, please ensure to follow the below best practices:

• Create the Managed Graph in a Separate Project

  • The Managed Graph should be created in a separate project from any projects in which it will be used.

• Avoid Schema Overlap

  • A public variable used in a Managed Graph does not share scope with a public variable of the same name created in a regular project.

For Example:

If the Managed Graph sets a public variable A to hello, and the regular graph that uses the public variable sets A to goodbye.

When the Managed Graph retrieves A, it will receive hello. When the regular graph retrieves A, it will receive goodbye.

This ensures that public variables remain isolated between Managed Graphs and the projects that use them, preventing conflicts and unintended overrides.

Managed Graphs are graphs with parameters that may or may not have connections. Managed Graphs have multiple versions, and new versions can be published anytime. Any user of a Managed Graph will be given the option to update - Managed Graphs will not change automatically in projects without a user action. This allows testing to be performed as the user is conscious of the change.

In order to be able to create a Managed Graph, you need to be an Xponent OEM partner. Please contact your Xponent representative if you are interested in using this feature.

Anyone can use a Managed Graph that is available to them in the Create New window.

Creating a Managed Graph

Managed Graphs are created via the Share button in the top right of the graph window.

The Share Graph window allows sharing as a Graph Template or as a Managed Graph.

• Choose Managed Graph from the Type menu

• Enter a name for the Managed Graph

• Choose a single graph from the graphs shown below

• Enter the Description and Change Log texts in the right-hand panel - you can also edit this later in the Admin window.

The Description and Change Log windows accept Git Hub style Markdown Syntax, which is a simple way to use plain text to create structured documentation.

It is best to use a smaller heading level in the Description box. Heading level 3 ```###``` is small enough to ensure that the text is not too large. In the Change Log box, no heading is usually required.

The Description and Change Log information will be shown as hover text over a Managed Graph node.

Viewing a Managed Graph

Updating A Managed Graph

To update a Managed Graph, choose the Share Graph menu item and then:

• Choose Managed Graph from the Type menu

• Choose the existing Managed Graph from the Select the Managed Graph to Update menu

• Choose a single graph from the graphs shown below

• Update the Description and Change Log texts in the right-hand panel - you can also edit this later in the Admin window

This will publish a new version of the managed graph. The Change Log should be used to convey the changes that have been made in this version of the graph.

There are two areas within Journey Hub where you can manage your journey map, graph templates, and managed graphs: Admin and Library tabs.

The library houses all the journey and graph templates and managed graphs that are created in your organization. Clicking into Library, there are two sections - Templates and Managed Graphs.

Templates are where all the created journey map templates and graph templates exist. Journey Map templates will be at the top, followed by the Graph templates. These templates are viewable only. In the managed Graphs section, you will find all the managed graphs created in your organization. This is a read-only view.