Visualization settings
Permission: Settings management
Visualization setting is used to configure visualization functionality.
Configuration
-
Left menu - settings
-
In panel "Settings list" use icon "Update" for setting "VISUALIZATION".
-
Enter JSON configuration and confirm by pressing "Save" button.
Default configuration
Default configuration contains several default attributes to see how configuration should looks like. Probably this configuration doesn't match model of your data but can serve as example of short configuration.
-
Left menu - settings
-
In panel "Settings list" use icon "Update" for setting "VISUALIZATION".
-
Press button "Default" and store by pressing button "Save".
Automatic configuration
Automatic configuration is used to generate configuration which contains automatically detected "nodeLabelAttr".
This automatically generated configuration can be used as good starting point to create own configuration.
-
Left menu - settings
-
In panel "Settings list" use icon "Update" for setting "VISUALIZATION".
-
Press button "Automatic", wait for generator to generate JSON and store by pressing button "Save".
Description of configuration
Configuration is entered as JSON. Example of JSON:
{
"nodeLabelAttr" : "LOGICAL_NAME",
"edgeLabelAttr" : "RELATIONSHIP_TYPE",
"nodeTooltipAttrs" : [
{ "dataAttr":"TYPE" },
{ "dataAttr":"SUBTYPE" }
],
"edgeTooltipAttrs" : [
{ "dataAttr":"RELATIONSHIP_TYPE" },
{ "dataAttr":"RELATIONSHIP_SUBTYPE" }
],
"tabDetailNodeInfoAttrs" : [
],
"tabDetailEdgeInfoAttrs" : [
],
"nodeSnippetAttrs" : [
{ "dataAttr":"TYPE" },
{ "dataAttr":"SUBTYPE" }
],
"tabAllNodeFilterAttrs" : [
]
}
Explanation of JSON properties:
Property |
Values |
Default |
Description |
Usage |
nodeLabelAttr |
String |
First node DB property in Data schema |
Name of DB property used in several places in visualization (node title, tooltip title, tab Detail title, node snippet title) to identify node. For best results it should be DB property with unique identification or name for nodes. If set to null or not defined then the first attribute from "nodeAttributes" in Data schema is used. |
Visualization |
edgeLabelAttr |
String |
|
Name of DB property used as relationship title in visualization. If set to null or not defined then no relationship labels are shown in visualization. |
Visualization |
nodeTooltipAttrs |
Array of objects |
|
Array of node DB properties which are listed in node tooltip. Each property is defined as simple object with only one property dataAttr. All properties have to be defined in Data schema. If set to null or not defined then no DB properties are printed in node tooltip. Ordering in GUI is the same as in this setting. Example: "nodeTooltipAttrs" : [ { "dataAttr" : "TYPE" }, { "dataAttr" : "SUBTYPE" } ] |
Visualization |
edgeTooltipAttrs |
Array of objects |
|
Array of relationship DB properties which are listed in relationship tooltip. Each property is defined as simple object with only one property dataAttr. All properties have to be defined in Data schema. If set to null or not defined then no DB properties are printed in relationship tooltip. Ordering in GUI is the same as in this setting. Example: "edgeTooltipAttrs" : [ { "dataAttr" : "RELATIONSHIP_TYPE" }, { "dataAttr" : "RELATIONSHIP_SUBTYPE" } ] |
Visualization |
tabDetailNodeInfoAttrs |
Array of objects |
All node DB properties defined in Data schema |
Array of node DB properties which are listed in node detail tab in the control panel in visualization. Each property is defined as simple object with only one property dataAttr. All properties have to be defined in Data schema. If set to null or not defined then all DB properties from "nodeAttributes" in Data schema are used. Ordering in GUI is the same as in this setting. Example: "tabDetailNodeInfoAttrs" : [ { "dataAttr" : "TYPE" }, { "dataAttr" : "SUBTYPE" } ] |
Visualization |
tabDetailEdgeInfoAttrs |
Array of objects |
All relationship DB properties defined in Data schema |
Array of relationship DB properties which are printed in relationship detail tab in the control panel in visualization. Each property is defined as simple object with only one property dataAttr. All properties have to be defined in Data schema. If set to null or not defined then all DB properties from "edgeAttributes" in Data schema are used. Ordering in GUI is the same as in this setting. Example: "tabDetailEdgeInfoAttrs" : [ { "dataAttr" : "RELATIONSHIP_TYPE" }, { "dataAttr" : "RELATIONSHIP_SUBTYPE" } ] |
Visualization |
nodeSnippetAttrs |
Array of objects |
|
Array of node DB properties which are used as additional node identification in visualization tabs, e.g. in search or in node details. If set to null or not defined then no additional information is used in GUI and the only identification of node is nodeLabelAttr. Example: "nodeSnippetAttrs" : [ { "dataAttr" : "TYPE" }, { "dataAttr" : "SUBTYPE" } ] |
Visualization |
tabAllNodeFilterAttrs |
Array of objects |
All node DB properties defined in Data schema with dataRole="dimension" |
Array of node DB properties which are used in advanced filter in the search tab in visualization. If set to null or not defined then all DB properties from "nodeAttributes" in Data schema which have dataRole set to "dimension" are used. Ordering in GUI is the same as in this setting. Example: "tabAllNodeFilterAttrs" : [ { "dataAttr" : "TYPE" }, { "dataAttr" : "SUBTYPE" } ] |
Visualization |