🖇️Connections Between Dashboards

Composite Kanban allows to drag cards between its children Kanbans. To manage this dragging, a relations between children dashboards should be set and configured. These relations are set for dashboard cards; all of them, set from one Kanban to another, are forming connection between these dashboards.

To be able to have connections, composite dashboard should have at least 2 containers with child dashboards configured. If hover mouse over any of child dashboards, a "Add Connection" icon will be shown:

If hover mouse on this icon, a tooltip will be shown:

To start setting a connection, drag this icon to another Kanban container and drop it there:

A "Configure Connections..." popup will appear. It will contain data for Source Kanban (which card will be dragged from) and Target Kabnan (which card will be dropped to). By default popup will contain:

• names of these Kanbans

• list of cards from Source Kanban

Each card will show a number of its connections:

Source and Target Kanbans names are links - if click them, proper Kanbans will be opened in Kanban Builder in the new browser tab.

Select card in the Source Kanban you want to configure relations to (realtions are the same as Column Junctions on standard dashboard). A list of Source Columns belonging to the Source Kanban will appear. Each column will show a number of it's connections:

If select a Column of the Source Kanban, the list of available Target Columns (belonging to the Target Kanban) will be shown. Each Target Column will show amount of Actions that will be executed by card dropping:

Each Source Column for each Card has the own list of Target Columns with own actions.

Check Target Columns where selected Card can be dropped from selected Source Column to. Badges with numbers of connectors will become yellow, and numbers of Actions will become red - this indicates that proper cards and columns have no actions set to their connectors:

Select Target Column. A list of Actions set for this connection (Card - Source Column - Target Column) will be shown. By default it is empty. Also, Source/Target Drop Behavior forms will be displayed:

You can select a Target Column that was not checked. After adding at least one action it will become checked, thus, a connection will be set automatically.

Click "Add" link to add a new or existing Action or Action Group (this process is the same as adding Actions on Standard Dashboard). You can add several actions by selecting them together. After being added Actions and Action groups will appear in the list. They can be rearranged by clicking ordering arrows and deleted. To delete actions check checkboxes near unnecessary actions and click "delete" link. Also, Actions / Action Groups can be edited by clicking "Edit" buttons:

Actions can be copied to another connections. To copy actions and action groups, select them with checkboxes and click "Copy" link . After this proper information will be displayed. Actions will be copied to built-in application clipboard:

To paste copied actions first select necessary Target Column in necessary relation (it even can be a connection between other dashboards), then click "Paste" link. Actions will be pasted from app clipboard:

If copy another actions, they will replace previously copied in the app clipboard. To clear the app clipboard click the proper link.

To set how should behave Source and Target Columns when card is dragged and dropped, select necessary behaviors in the proper form.

Behavior of source column can be set to:

• Remove Card - card will disappear from the source column

• Refresh - source column contents will be refreshed and the card will remain there

• Remove Card and Refresh - card will be removed from the source column; source column contents will be refreshed; if the record, represented by dragged card, still match the source column conditions, card will appear there again

• Do Nothing - source column will not change it's contents

Behavior of the target column can be set to:

• Refresh - target column contents will be refreshed

• Do Nothing - target column will not change it's contents

After connections has been set and saved, an Output Relations section of the Source Kanban properties sidebar will show it. If click the link representing the connection, it will be opened in "Configure Connections..." popup for editing:

The same connection will be also shown in "Input Relations" section of the Target Kanban properties sidebar:

Useful hints

If you have a composite dashboard with several containers and they contain the same child dashboard (e.g., like Calendar Dashboard), you do not need to configure connectors between each pair of containers: system uses namely dashboards when storing connections. For example:

• You have composite dashboard with containers A, B, C, D, E and F

• Containers A, B, C and D have child dashboard X, and containers E and F have child dashboard Y

• In this case if you configure connections in the direction A -> F, you make junction X -> Y and you do not need to duplicate it with other connections (A->E, B->E, B->F, C->E, C->F, D->E, D->F). And to make junction from Y to X (Y->X), you need to configure only one of the following connections: E->A, E->B, E->C, E->D, F->A, F->B, F->C, F->D.

If you configure:

• connections between containers that all are containing the same dashboard, and

• child dashboard has junctions and actions configured (like on Calendar Dashboard)

you do not need to repeat these junctions and actions in Connections Between Kanbans popup. The only thing you need, is to add actions to junction between source and target column when they are the same (because in composite kanban you can have the same column as source, as target in the same time - they will just be in different containers). So, in the given example with Calendar Dashboard:

• actions for card dragging are configured in child dashboard

• junctions in child dashboard are set for all source columns to all target columns

• dragging from the source column to itself is not allowed within child dashboard

• composite dashboard has connections between child dashboard as source and same dashboard as target

• in these connections each source column is connected to one target with the same name and has proper action set - because dragging to other source column is already allowed in child dashboard