Linked Process Maps

Connect a high-level activity to the saved subprocess map behind it, then preview and move between parent and child maps.

Last updated · 1 min read

Linked Process Maps works with saved process maps. Guests, unsaved maps, and template previews cannot create or store links. Viewers can browse existing links and previews, while editors can add or remove links.

Links can be anchored to a task, subprocess, or call activity. If you link a plain task, BA Copilot asks you to confirm its conversion into a collapsed subprocess.

  1. Open a saved parent process map.
  2. Select the task, subprocess, or call activity that should open the detailed process.
  3. Open Links in the right sidebar.
  4. Choose the saved child process map.
  5. Review the selected activity and confirm the link. If the activity is a plain task, also confirm its conversion into a collapsed subprocess.

The parent activity receives a link badge. The relationship also appears in the Links sidebar.

Linked subprocess maps in the Links sidebar
Linked subprocess maps in the Links sidebar

Open Links and select Preview for the related map, or select a linked activity on the canvas. Previews load only when requested. Select Go to to open the related map.

On the child map, use Called by to see the parent relationship and return to the calling map. On a parent map, Calls subprocesses lists its child relationships.

Generate linked child maps with BA Copilot

Ask BA Copilot to create detailed child maps for suitable Level 3 activities. The standard chat follow-up can create up to three Level 4 children in one accepted step, subject to the remaining map allowance.

Review the proposed children before accepting them. Each completed child is linked back to its calling activity.

Open Links, select the relationship, and use the remove action. Removing the relationship does not delete either saved process map.

Was this guide helpful?

More in Organising your work