Capability on release

Coming soon

Limited browser support

For this release, you must use Chrome. We do not support any other type of browser.

We will support all modern (HTML5 capable) browsers.

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.

Simplified view in Quick LINQ

When you capture using Quick LINQ, LINQsets remain expanded. To create the more simple view, you will need to collapse LINQsets manually using the - button in the top left hand corner of the LINQset. Making use of “Fit to View” and “Layout” in the toolbar will ensure that you get the initial feedback you need as you create your diagram.

Quick LINQ will operate in simplified view as its default behaviour. This will enable you to generate your top level views focused on Value Cascading more easily.


The auto-layout capability will also continue to evolve as we learn more about your layouts and how and when auto-layout should be performed.

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.


At times, auto-layout can cause nodes to move across the canvas during the capture process, or, the layout may not automatically lay out new nodes as the value cascading capability creates new LINQsets.


For now, please use the Fit Content button  on the toolbar, or the Apply Layout  button to refresh your canvas before you continue to work.

We continue to work on auto-layout and other canvas behaviours and these will incrementally improve with future releases.

ID# LINQ-448



Edges between nodes cannot be re-routed

At the moment we are not supporting you re-routing existing edges to new nodes, i.e. you drag the connect point of the edge from the node it is already connected to, to another unconnected node.



The workaround is to add a new node, drag the connection from or to the node you are connecting to, then select and delete the edge that you wish to remove, or vice versa depending upon the node connectivity rules:

Edge re-route.gif

A future release will support re-routing of edges by picking the edge end-point up and dragging it to a new node.

ID# LINQ-442



Tab button focus is not working correctly

The order of focusing access to capability in LINQ canvas is not working correctly if you use the Tab button to enable that focus.



Buttons in the toolbar do not highlight when they have the focus meaning it is difficult to know where the focus is currently set.



Access to the Help and Settings menus via the Tab button only working when the top level menu is highlighted and the down cursor arrow is used to expand the menu. Tab then scrolls through the options.



For now we would recommend using the mouse and clicking on the required option rather than using the Tab button.

This will be resolved in a future release.

Cannot delete a LINQset which contains nodes

At this release, you cannot delete a LINQset which contains nodes. You must select and delete the nodes within the LINQset first, creating an empty LINQset, and then delete the LINQset.



There are many delete rules that we need to enforce as LINQ evolves to enable an organisation to re-use nodes across business units. For example, if someone in another part of the business has connected to a node you have created and we allow you to delete it, it will impact elements of the Information Supply Chains that you may not be aware of.



This Private release of LINQ is delivering a “sketch” capability; your diagrams cannot be shared with other users, so this isn’t an issue, but to begin to enforce some of the rules of LINQ, this presents what may be seen as an irritating behaviour.

In future releases of LINQ we will establish more robust rules for the deletion of nodes. This will come as part of the increased capability around organisations users, business units and access to content created in LINQ.



The differentiation between “sketch” and “authoritative” views will become clearer which will necessarily establish lifecycle processes for changing a node’s state.

ID# LINQ-404



Node connections involving collapsed LINQsets

There are some circumstances where additional edges are shown when the LINQset is collapsed based on the connections within the LINQset. Two examples of note are:

- When you attach a System node to the Capture Action and collapse the LINQset, you will see an edge displayed from the collapsed LINQset  to the Capture Action:




- When you connect an Action node to an Information node which has "popped out" from a collapsed LINQset, it will create what appears to be a loop. Simply expand and collapse the LINQset to resolve this:

Node connections to collapsed LINQsets 2.gif

- If you connect a People node to a Capture Action node and a System node to an Output Information node, then collapse the LINQset, additional edges will be shown coming from the LINQset:




- If you add those nodes against a collapsed LINQset, the nodes will be consumed into the collapsed LINQset and the edges shown as loops:



LINQset collapse behaviour will extend to cope with additional scenarios in future releases.

ID# LINQ-358



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

If you choose to re-size your browser window to the point that tools in the LINQ Canvas toolbar drop below the grey toolbar position, any tools below the grey toolbar will not work:





For now, you will need to increase the width of your Browser window and allow all of the tools to be placed within the grey toolbar space.

The toolbar will react better to screen re-size in a future release.

Don’t Quick LINQ to Information Supply Chains you have modified

You may encounter some issues with your diagram if after you have added detail to any element, for example you have described an automated action by connecting a System node to an Action node, and then you then decide to use Quick LINQ to connect to nodes in that more detailed Information Supply Chain to another information outcome node.


If value cascading through Quick LINQ would cause node values to be the same after Quick LINQ has performed its grouping, you may lose nodes you have captured.



For now, once you have started to elaborate elements of your diagram, please don’t use Quick LINQ in association with those elaborated elements. You can continue to use it for other connections, although we would suggest ensuring that your Output Information nodes have been valued so that you can spot potential issues.



Undo is your friend here! If you spot an issue, use Undo and Re-layout your diagram.



A good process to follow, is to get as much information captured using Quick LINQ, before you then start to add detail into your diagram as necessary. Use the Value Cascading to help drive you to where more detail is necessary.

In a future release, Quick LINQ will create parallel paths when you use it against Information Supply Chains you have added detail to, even if node values become common. This will allow you to add detail and continue to benefit from Quick LINQ’s ability to generate your Information Supply Chain topology with ease.



Value cascading will account for Node UUID as well as the calculated value ensuring that only legitimate dissolves of nodes take place.

ID# LINQ-405



A Capture node in the middle of an Information Supply Chain will break the visualisation of the supply chain

At this release, please be aware that if you have a Capture Action node in the middle of your Information Supply Chain, when you collapse the LINQset containing that Capture Action node, the result will look like this:



      Collapsed                                       Expanded




This happens because we are currently describing a Capture Action as a source action, linked to an Information node, the information created by that capture. We have rules which pop the source action and information out of a LINQset when they are collapsed and this scenario currently breaks those rules.



The current workaround is to set that action node as a generic action or a process which will prevent the pop-out from happening.

In a future release, we will enable users to define their own types of Capture Actions. This may be by setting a status on a particular action to identify it as the action creating source information. This will enable Quick LINQ and the LINQset collapse rules to recognise what to do with any node set as source or outcome.

ID# LINQ-374



Cutting a LINQset

If you select a LINQset and the nodes contained within it (please note that selecting a LINQset currently doesn’t select all of the nodes within it), and then use the Cut tool, the result will show an empty LINQset on the canvas, rather than the LINQset and its nodes disappearing from view. On paste, the LINQset is correctly restored. If you delete the empty LINQset before pasting the cut, the LINQset is also correctly restored.



Cutting LINQsets.gif


This behaviour will be improved in a future release.

Strange Cut behaviour

You may see some odd behaviour when pasting nodes against which you have used the Cut tool. Typically LINQsets can be collapsed and might look a little strange. Simply use the Apply Layout to redraw your diagram with the LINQset collapsed or expanded. No data is lost, it just looks a little strange.



We continue to work on capabilities such as Cut and Paste.


In a node-edge graph, cut is quite a complex task as you have to understand the context of the relationships also being cut; they are all different based on the number and type of nodes and their corresponding edges. This will all improve with future releases of LINQ.

Undo is too granular

In this release, undo works against every single action that you perform. This means that each character you type into the node description field requires an undo. Of most significance is the undo associated with capturing the cost of an action node.



If you were to type an hourly rate into a People node, then duration and frequency into an Action node, each numeric value entered becomes an undo action.



LINQ calculates the cost of the Action node in real time as you enter the final values into the Action node. As undo removes values, the cost is recalculated. If you were to assume that Undo removed the full value entered in any field, you would see that your cost calculation has in fact reduced based on the new number in the Frequency field after removing the last digit you entered.




In a future release, we will make Undo work on a less granular level. Undo will undo the whole of the last actions, in the order that they were performed.



The Undo tool tip will also give you a history list, so you know exactly what it is that you are undoing.

 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.