Visualization Parameter Set Administration

Visualization parameter sets are named preset configurations of low-level visualization parameters such as the level of detail, filters, and the number of initial steps that control how the lineage is visually displayed in the lineage visualization. They are meant to simplify the use of Manta for users. Manta provides default visualization parameter sets that are available for users on the home page Object catalog| Step-2: Choose How to Visualize Your Data Flows and allows Manta administrators to adjust them or create their own.

Configuring Visualization Parameter Sets

The (predefined) visualization parameter sets can be re-configured or overridden by the Manta administrator. You can add new, remove, or modify visualization parameters.

Go to Admin UI and find the section Configuration > Server > Visualization > Visualization Parameters.
Edit the configuration as according to the following structure and save.

Structure of the Visualization Configuration Set Configuration

The configuration is in JSON format with settings for individual low-level parameters.

Property	Format	Description
`name`	`string`	Name of the set of parameters displayed in the Manta Flow home page dropdown; for example, `Dataset, no transformations`.
`detail`	`string` with value: `Lowest` / `Low` / `Medium` / `High`	Designates at what level of detail the objects is visualized. For example, `Low` detail might mean that only databases and root directories are shown.
`direction`	`string` with values: `Forward` / `Backward` / `Both`	The `Forward` option shows only objects that receive data from selected elements. The `Backward` option shows only objects that send data to selected elements.
`indirectFlows`	`boolean`with values: `true` / `false`	The option to visualize indirect flows also shows other flows that indirectly influence target elements.
`filters`	`string` with ID of the horizontal filter group Configuring Resources \| Horizontal-Filters that should be used	Shows only specific types of objects that are defined in the configuration file.
`steps`	`number` with a value between 1 and 10 (by default) or the max number of steps that are allowed by the viewer limits configuration under Admin UI → Configuration → Server → Common → Maximal Depth	The number of data flow steps initially displayed in the visualization.

Configuration Example

[
  {
    "name": "Dataset, no transformations",
    "detail": "Medium",
    "direction": "Both",
    "indirectFlows": false,
    "filters": "6",
    "steps": 3
  },
  {
    "name": "Dataset, with transformations",
    "detail": "Medium",
    "direction": "Both",
    "indirectFlows": false,
    "filters": "1",
    "steps": 3
  },
  {
    "name": "Attribute, no transformations",
    "detail": "High",
    "direction": "Both",
    "indirectFlows": false,
    "filters": "6",
    "steps": 3
  },
  {
    "name": "Attribute, with Indirect lineage",
    "detail": "High",
    "direction": "Both",
    "indirectFlows": true,
    "filters": "1",
    "steps": 3
  },
  {
    "name": "Attribute, with transformations",
    "detail": "High",
    "direction": "Both",
    "indirectFlows": false,
    "filters": "1",
    "steps": 3
  },
  {
    "name": "Low-detail",
    "detail": "Lowest",
    "direction": "Both",
    "indirectFlows": false,
    "filters": "4",
    "steps": 3
  }
]

Troubleshooting

Admin UI has only basic JSON structure validation. If the visualization settings are misconfigured, it is logged and the default settings are used instead. You can search the Flow Server log for more details.