All versions of this manual
X
Welcome to Linkurious user manual v2.9.14. Use the menu to access other documentations.
  1. Introduction
  2. First visualization
    1. At first glance
    2. Create a new visualization
    3. Inspect data
  3. Custom actions
  4. Search
    1. Searching for nodes
    2. Searching for edges
    3. Advanced search
    4. Advanced syntax
  5. Manipulating the graph
    1. Select nodes and edges
    2. Expand nodes
    3. Queries and templates
    4. Lasso
    5. Hide
    6. Layouts
    7. Pinning nodes
    8. Undo/redo
    9. Shortcuts
  6. Design
    1. Captions
    2. Nodes color
    3. Edges color
    4. Nodes size
    5. Edges size
    6. Icons
  7. Filters
    1. Filter panel
    2. Timeline
  8. Edit data
    1. Edit properties and categories
    2. Create nodes and edges
    3. Delete nodes and edges
  9. Geography
    1. Geographic data
    2. Display a geographic map
  10. Manage visualizations
    1. Auto-save
    2. Organize
    3. Duplicate
    4. Share
    5. Publish
    6. Export
    7. Delete
  11. Alerts
    1. Alerts dashboard
    2. List matches
    3. Investigate a match
  12. Guest Mode
 

Custom actions

In this chapter we cover the following topics:

Custom action example

Custom actions allow to open URLs that can be customized using data from the graph.

Custom actions allows a scenario such as:

  • Given a Company node, the user right-clicks on a node and navigates to Custom actions in the context menu.
  • The user clicks on the appropriate custom action (as there may be more than one). Here Open in Salesforce.
  • A new tab is open in the browser and displays the company's profile page in Salesforce.

Opening SalesForce with a custom action

Creating and managing custom actions

Accessing the custom actions panel

The panel can be accessed through the workspace, by opening the main menu and selecting "Manage custom actions ...".

The panel is available only to users who are authorized to create and manage Custom actions.

Opening the custom action panel

Managing custom actions

From the Custom actions panel, a user may:

  • Create a new custom action.
  • Edit or Delete custom actions they own.
  • View the details of custom actions that they have access to.

Managing custom actions

Creating a custom action

In order to create a custom action a user:

  • must give it a name (mandatory).
  • must provide a URL Template (mandatory, see next section about the syntax).
  • may provide a description.
  • may share it with all users.

Creating a custom action

URL template syntax

A Custom action contains a URL template with one of more variables that are replaced by actual values provided by the context.

Example:

  • Template: https://google.com/?q={{node.first_name}}
  • When running this custom action on a specific node, the {{node.first_name}} variable will be replaced by the first_name property of the selected node.

The following variables can be used in a URL template:

Several variables can be used in the same template (e.g. https://google.com/search?q={{node.city}}+{{node.country}}), with the constraint that "node" and "edge" variables cannot be mixed.

Variables

Node ID

  • Usage: insert the ID of the currently selected node in the URL template.
  • Syntax: {{node}}

By default, a custom action with a {{node}} variable will be available on all nodes. To make this custom action available only for Company nodes, use the following syntax: {{node:"Company"}}.

If multiple "Node ID" variables (or "Node property" variables) are used in a a single custom action, they need to all have the same node-category constraint (see example 3).

Examples:

  1. https://example.com/details?node={{node}}
  2. https://example.com/details?node={{node:"Person"}}
  3. https://example.com/node?id={{node:"Person"}}&name={{(node:"Person").name}}

Node property

  • Usage: insert the value of a property of the currently selected node in the URL template.
  • Syntax: {{node.property_name}} or {{node."property name"}} (if the property name contains spaces of special characters).

By default, a custom action with a {{node.property_name}} variable will be available on all nodes. To make this custom action available only for Account nodes, use the following syntax: {{(node:"Account").property_name}}.

If multiple "Node property" variables (or "Node ID" variables) are used in a a single custom action, they need to all have the same node-category constraint (see example 4).

Examples:

  1. https://google.com/search?q={{node.firstName}}
  2. https://google.com/search?q={{node.firstName}}+{{node.lastName}}
  3. https://google.com/search?q={{(node:"Person")."First name"}}
  4. https://google.com/search?q={{(node:"Company").name}}+{{(node:"Company").city}}

Edge ID

  • Usage: insert the ID of the currently selected edge in the URL template.
  • Syntax: {{edge}}

By default, a custom action with a {{edge}} variable will be available on all edge. To make this custom action available only for Transaction edge, use the following syntax: {{edge:"Transaction"}}.

If multiple "Edge ID" variables (or "Edge property" variables) are used in a a single custom action, they need to all have the same edge-type constraint (see example 3).

Examples:

  1. https://example.com/edge_details?id={{edge}}
  2. https://example.com/edge_details?id={{edge:"Transaction"}}
  3. https://example.com/edge?id={{edge:"Transaction"}}&amount={{(edge:"Transaction").amount}}

Edge property

  • Usage: insert the value of a property of the currently selected edge in the URL template.
  • Syntax: {{edge.property_name}} or {{edge."property name"}} (if the property name contains spaces of special characters).

By default, a custom action with a {{edge.property_name}} variable will be available on all edge. To make this custom action available only for Transaction edge, use the following syntax: {{(edge:"Transaction").property_name}}.

If multiple "Edge property" variables (or "Edge ID" variables) are used in a a single custom action, they need to all have the same edge-type constraint (see example 5).

Examples:

  1. https://google.com/search?q={{edge.amount}}
  2. https://google.com/search?q={{edge.amount}}+{{edge.date}}
  3. https://google.com/search?q={{(edge:"Transaction")."credit card"}}
  4. https://google.com/search?q={{(edge:"Transaction").country}}+{{(edge:"Transaction").amount}}

Visualization ID

  • Usage: insert the ID of the visualization in the URL template.
  • Syntax: {{visualization}}

Examples:

  1. https://example.com/details?viz={{visualization}}
  2. https://example.com/details?viz={{visualization}}&node_id={{node}}

SourceKey

  • Usage: insert the SourceKey of the current data-source in the URL template.
  • Syntax: {{sourceKey}}

Examples:

  1. https://example.com/details?source={{sourceKey}}
  2. https://example.com/{{sourceKey}}/{{node:"Company"}}

Base URL

  • Usage: insert the base URL of the Linkurious Enterprise server in the URL template.
  • Syntax: {{baseURL}}
  • Note: the inserted base URL value always ends with a /.

Examples:

  1. {{baseURL}}workspace/new?key={{sourceKey}}&populate=edgeId&item_id={{edge}}
  2. {{baseURL}}workspace/new?key={{sourceKey}}&populate=nodeId&item_id={{node}}
  3. {{baseURL}}plugins/my-plugin/show?key={{sourceKey}}&node={{node}}

Set of node IDs

  • Usage: insert the IDs of all currently selected nodes in the URL template.
  • Syntax: {{nodeset}}
  • Note: the node IDs are inserted as a comma-separated string, e.g. 55,4,128,12

By default, a custom action with a {{nodeset}} variable will be available on all nodes. To make this custom action available only for Account nodes, use the following syntax: {{nodeset:"Account"}}.

Example:

  1. http://example.com/nodes?ids={{nodeset}}
  2. {{baseURL}}plugins/my-plugin/show?nodes={{nodeset:"Company"}}

Set of edge IDs

  • Usage: insert the IDs of all currently selected edges in the URL template.
  • Syntax: {{edgeset}}
  • Note: the edge IDs are inserted as a comma-separated string, e.g. 55,4,128,12

By default, a custom action with a {{edgeset}} variable will be available on all edges. To make this custom action available only for HAS_ACCOUNT edge, use the following syntax: {{edgeset:"HAS_ACCOUNT"}}.

Example:

  1. http://example.com/edges?ids={{edgeset}}
  2. {{baseURL}}plugins/my-plugin/show?edges={{edgeset:"HAS_ACCOUNT"}}