Issues from Previous Notes fixed in this Release 


Capability on release

Coming soon

ID# LINQ-610

Limited browser support

As well as complete Chrome support, early support for Mozilla Firefox and IE 11 is now available.

Firefox support does have one issue remaining: node label editing hides the first and last character of the label - they were entered and captured, but are not visible on the label. The workaround is to view or edit the description in the properties panel.

IE 11 support also has one issue remaining: The toggle buttons for enabling and disabling the navigator, properties, find, and palette panels vanish when the panels are disabled. You can still click the area to enable the panels.

We will support all modern (HTML5 capable) browsers.

ID# LINQ-448


Edges between nodes cannot be re-routed

An existing edge can now be re-routed to another node. Re-routing of edges follows the LINQ connection rules.

One important addition to the rules involving edges is that you may not select an edge which is shown connecting to a minimized LINQset. In order to alter these edges, you will need to expand the LINQset first. This is the expected behaviour.

ID# LINQ-442


Tab button focus is not working correctly

Tabbing between controls on the canvas page has been implemented. You may now tab between all menu options and buttons in the canvas view.

ID# LINQ-404

Node connections involving collapsed LINQsets

Based on feedback and working with this internally, we are leaving the standard result for collapsing LINQsets to include connections to supporting nodes being shown between the collapsed LINQset and the popped out nodes as this assists in understanding connections that have been made within the LINQset.



ID# LINQ-358


The Canvas toolbar collapses when the browser window is resized to a very small width

The canvas toolbar now correctly displays at smaller screen sizes.

ID# LINQ-374


Cutting a LINQset

When you cut a LINQset, all of the nodes and the LINQset container are now cut correctly.


New Features


Capability introduced

Node description, editing and display   

  • Descriptions displayed on node labels have been improved so that longer descriptions are shown. Up to 50 characters are now displayed over two lines
  • Node descriptions can now be edited directly by double-clicking on the label to enter edit mode
  • For nodes that do not already have a description, selecting the node and typing will add a description to the node
 Toggle panels on and off
  • The new panel toolbar displayed on the left hand side of the screen now controls which panels are visible. The buttons toggle the panels on and off
  • Panels now have an 'X' close button which closes them
 Search for nodes and properties
  • A new search panel has been added. You can now search for nodes in your open diagram
  • Search is case-insensitive and will compare against all properties on a node

 Expand/collapse all LINQsets

  • Two new buttons have been added to the toolbar. These collapse and expand all LINQsets in your diagram
  • These are useful when you are performing your initial high-level capture using Quick LINQ
 Pause Layout

  • The automatic layout that occurs after adding a node or creating an edge can now be disabled using the new Pause button on the toolbar
  • When the Pause button is toggled on, no automatic layout will occur. You will need to run a full Layout using the Layout button to clean up your diagram
  • This is useful when you are performing capture and want to prevent the auto-layout from moving nodes away from the area you are working in


Behaviour Changes


Behaviour Change

New edge connection rules
  • System nodes cannot connect to Organisation or Outcome nodes. The reason for this change is that a system cannot perform an Organisation and a system cannot perform an Outcome
  • Information nodes cannot connect to Capture nodes. The reason for this change is that Capture nodes should only be used to inject new information nodes into and Information Supply Chain
  • Existing diagrams that break these rules will continue to be displayed correctly, but functionality, such as Value Cascading, may not work as expected
Disable edge connection to minimized LINQsets
  • Edges that are displayed coming out of a minimized LINQset are now not selectable and therefore not able to be deleted or re-routed
  • To delete or re-route one of these edges, expand the LINQset first 


Remaining and New Issues


Capability on release

Coming soon

Firefox support - Node label editing not working properly.

LINQ-727, 696

Firefox support has one issue remaining: node label editing hides the first and last character of the label. They have been entered and captured, but are not visible. The workaround is to view or edit the description in the properties panel.  Complete Firefox support is due very soon.
IE 11 support - Panel toggle buttons disappear when disabled


IE 11 support also has one issue remaining: The toggle buttons for enabling and disabling the navigator, properties, find, palette panels vanish when the panels are disabled. You can still click the area to enable the panels.  Complete IE 11 support is due very soon.
Canvas toolbar button focus can be a bit confusing.


When you click a button on the canvas toolbar, the button gets a border drawn around it to show it is 'focused'. This is a bit confusing because it looks really similar to a toggle button that has been turned on. For example, in the image below the layout pause button looks like it is turned on, but it is actually just focused. The button colour is darker when it is actually turned on. 

We will improve the button images and state colouring to clearly show when a button is active vs just focused.
Large node descriptions overlap in the navigator panel.


Longer node descriptions can start to overlap in the navigation panel, and make nodes hard to identify in the navigation panel. 


The navigation panel will be able to expand to a much larger size, and we will auto-truncate labels to ensure readability when the panel is at its smallest size.

Adding people and system nodes which already exist in the diagram.

You will need to duplicate People and System nodes manually in order to adhere to the LINQ rules regarding the 1:1 relationship between People and Actions and Systems and People.


You can either;


- drag nodes from the palette and then connect them, or

- you can copy and paste an existing node and then connect it to the relevant node.

The 1:1 relationship is necessary as we develop the insights from the LINQ Core. This relationship enables us to perform specific calculations using the metadata you capture.

We will be improving the user experience to enable several ways of connecting these nodes:


1. You will be able to drag from the palette and drop onto the target node which will automatically create the edge between the nodes,


2. You will be able to create a “template” node in your own palette space, called “My Palette”. This People node could for example be “Fred” with his hourly rate already specified. When you drag from your palette to the canvas and you connect your nodes, any information captured in your template will be honoured,


3. Once you have a node in your diagram which you want to re-use, for example “Fred”, you will be able to drag an edge from “Fred” to another action and LINQ will automatically create a new “Fred” node and will connect it to the action node for you.


As LINQ develops, the User Experience (UX) for capturing content into LINQ will become easier through view pivots and other capture techniques aimed at simplifying how you create your Information Supply Chains.

Quick LINQ connectivity  If you start to add content to a diagram you have created initially using the Quick LINQ capability and then you try to use Quick LINQ to build your Information Supply Chain topology to a new Information Output, you might find that it will not work. For example, if you have connected a System node to your Source Information node, you will not be able to connect that Source Information node directly to an Output Information node via Quick LINQ.

The workaround is to temporarily delete any System nodes attached to source information nodes, if you want to use Quick LINQ to make new connections to outcome Information nodes.

We recommend that Quick LINQ work is completed before moving on to capture detail. That’s because the purpose of Quick LINQ is to identify high value areas to prioritise capture.

 The rules will continually be developed to provide a user experience which enables Quick LINQ to be used even after detail has been added to Information Supply Chains initially created using Quick LINQ.


However, we always recommend that Quick LINQ work is completed before moving on to capture detail.

Loops in your Information Supply Chains If you create loops in your Information Supply Chains, i.e. an outcome information node is used as an input to an action upstream in the Information Supply Chain, value cascading will not work.


For now, please avoid depicting loops in your LINQ diagrams.

 We will enable this behaviour as part of our continued work in calculating value as it cascades through local, organisational and global Information Supply Chains.
Support for Mobile At present, we do not support LINQ running on any type of mobile device; phone or browser.

If you do try and use LINQ on your iPad for example, you will be able to do some things which happen to work, but the user experience is not end to end.

 This is on our road map for a future release.