The tree layout for contents has been made available for bundles as a preview. It has not yet been released to customers.


Graphical user interface, application, Teams 
Description automatically generated
 

Show the tree layout  

In the main Chorus editing area, there is a new tree layout option for the Content panels on the left-hand side. To the right of the panel’s search box, there are 2 new buttons: list layout and tree layout. 


Graphical user interface, text, application 
Description automatically generated
 

Reset to default settings 

When levels of the tree are opened, a reset button is also shown. When the tree is expanded, use the reset button to quickly close the open tree levels. 


Tree structure for sections

 

Level 1 - Sections 

Each section in the bundle, spec or master is shown in code order. 

Select the section title to open that section for edit in the centre panel. 

The number in brackets after the section title shows how many headings and clauses are in that section. 

The delete section button is shown on the right-hand side of the section title. 

The arrow to the left of the section title opens the next level down. 


Level 2 - Headings 

Each heading within the section is shown in the order they appear in the main editor panel. 

Select the heading title to scroll the central editing panel to that place in the section. 

The number in brackets after the heading title shows how many clauses are below that heading. 

The arrow to the left of the section title opens the next level down. 


Level 3 – Clauses or articles 

Each clause or article within the heading is shown in the order they appear in the main editor panel. 

Select the clause or article title to scroll the central editing panel to that place in the section. 


Tree structure for systems 

Only available for specs and masters right now. Bundles to follow later during the Uniclass features development phase. 

The Uniclass tree is similar that seen in sectional content sets, but there a couple of small differences. 


Level 1 – Systems and orphaned addable clauses 

Each system is shown in code order. 

Any addable clauses, such as products or activities, that are not linked to a system are shown in the usual Uniclass code order: systems, then activities, then products. 

For Uniclass, the number in brackets after the title also counts the system or orphaned addable clause itself. 


Level 2 - Headings 

Same as for sectional content. 


Level 3 – Clauses 

Each clause within the heading is shown in the order they appear in the main editor panel. This includes, for example:  

  • Any addable clauses (products and activities) linked to the system. 
  • Any execution or completion clauses linked to products that are linked to the system.


Known limitations 

There is more work to do before this feature is released to customers, so please expect to see some of these changes over the next few releases. 


Clause numbers don’t match the editor 

Clauses created within the bundle are shown in the tree view, but currently the clause number will be missing for auto-numbered content sets: 

Graphical user interface, text, application 
Description automatically generated
 

Higher level groups and divisions 

For the moment, the top level is the section. There is a backlog request to group the sections by their parent group or division, so it would be useful to know how important that feature is for you compared with other backlog priorities. 


Completion pie charts are displayed 

The mark as complete feature hasn’t been fully switched on for bundles yet. However, the pie charts are currently visible in the tree and will update in line with some editor actions such parking clauses. 


Tree view in Uniclass bundles 

Authoring Uniclass bundles is a later phase of work, and so currently you cannot create Uniclass bundles. To get a feel for how the tree works for Uniclass, create a project spec or master instead.