Publish Subject Items in Document Publisher

Using the ‘Publish Subject Items’ option

The Publish Subject Items option in the Hierarchy Table can allow a user to stop items being published. This is based on a link(s) existing or not. Users need to understand it affects not only the type it is on but can affect the Subject type as well.

Publish Subject items Options
Hierarchy Details – Publish Subject items Options

Publish Subject Items – Always

When the option is set to ‘Always’, this means that the target items will be published in the document. It does not matter if there are linked items below or not.

Publish Subject Items – ‘Only if link exists’

When the option is set to ‘Only if link exists‘ then the item type will only get published if the item linked to the source has the correct link type and is not excluded because of a filter.

With ‘Only if link exists‘ set on the ISSUE item type and a filter:

– Requirement (Source Item)

– ISSUE (Target Item with filtering)
– RISK (Target Item)

With the hierarchy set as above, if a Requirement only had 1 ISSUE linked to it and this link was removed due to filtering. This means the source item will not be published as there are no linked items to be output. If the Requirement has 2 ISSUEs linked to it and only one is removed through filtering then the source item, the single linked ISSUE and any linked RISK items will be published .

With ‘Only if link exists‘ set on the ISSUE item type and no a filter:

– Requirement

– ISSUE
– RISK

With the hierarchy set as above, the Requirement will be published as well as both ISSUEs and any linked RISK items.

Publish Subject Items – ‘Only if link does not exist’

When the option is set to ‘Only if link does not exist‘ is set on a target item then the source item is only output if the target item is not linked.

With ‘Only if link does not exist‘ set on the RISK item type:

– Requirement

– RISK

Any Requirements that are not linked to a RISK or have the wrong link type will be published. Those Requirements that are linked will not be published.

Publish Subject Items – ‘Only if all links exist’

When the option is set to ‘Only if all links exist‘ then the source item will be output if all linked items have the correct link type and are not removed through filtering.

With ‘Only if all links exist ‘ set on the ISSUE item type and a filter:

– Requirement

– ISSUE (with filtering)
– RISK

If the Requirement has a single ISSUE linked to it and the filtering removes this link then neither the Requirement nor the ISSUE will be published.

When a Requirement has two ISSUEs linked to it and the filtering removes one link then neither the Requirement nor the ISSUEs will be published.

With the filtering removed from the ISSUE item type then the Requirement, ISSUEs and RISK items will be published.

Publish Subject Items – ‘Only if all link do not exist’

When the option is set to ‘Only if all links do not exist‘ then the source item will be output as long as non of the linked items have the correct link type or at are removed through filtering.

With ‘Only if all links do not exist ‘ set on the ISSUE item type and a filter:

– Requirement

– RISK

If a Requirement has a RISK linked in the right way then the source item will not be output. If a Requirement has either no linked RISK items or the link type is wrong then the source item will be output.

For help on Document Publisher click here

For blog posts on Document Publisher click here

Cardinality Control in Link Rules

The Cardinality Values and Uses

In the latest release of Cradle using Cardinality in a cross reference has been introduced. This extends the capability of controlling cross references to the point of how many relationships an item can have.

The Many-to-Many Relationship

This is the default option for a rule when it is first set. This is also the default option when a rule is imported from an older version which does not have this option. This cardinality relationship is applied to:

  • Most of the link rules in the as-supplied Cradle demonstration databases DEMO and SYSM
  • Most of the link rules in the as-supplied default schema and quick-start
Demo Link Rules showing the Cardinality
Showing One to Many and Many to Many Cardinalities

The One-to-Many Relationship

This cardinality is used for parent-child relationships between items of the same type. Furthermore this option is applied to:

  • Parent-child link rules in the as-supplied Cradle demonstration databases DEMO and SYSM
  • Parent-child link rules in the as-supplied default schema default and quick-start

The Many-to-One Relationship

This option will allow many items linked down to a single item. Many users can be assinged to one Requirement.

The One-to-One relationship

This is mainly for links like a single result file to a single test file.

Link Rule Setup options
Showing the Cardinality option within the Link Rule Setup

The new cardinality option is for all item types which includes all the modelling types as well.

Hence if a user tries to set linked items which are against the rule they will see an error which will deny the links and the links will not be created.

Stopped by Link Rule Error Message
Error Message

Restrictions on use

Finally there are restrictions in how this option is accessed. For instance a Link Group cannot be used in conjunction with the Cardinality. Also the options to create or modify cross references must be checked or the Cardinality option will be disabled.

For information on getting started in Link Rules click here

August 2017 Newsletter

Hello August

Wow what a busy month July has been here at 3SL. The last weeks before a release are always complex. So many things to do checking off the release checklist.

Cradle 7.3 is Here

Cradle 7.3
Cradle 7.3

Cradle 7.3

3SL are pleased to announce the new features of Cradle 7.3

  • Cross reference cardinalities in link rules – One to Many, Many to Many, or Many to One, you decide.
  • Categories – Control read-write access by a user’s skills.
  • Frames – Those containing a category picklist can have a default value.
  • Frames – Colour usage defaults for picklist frames.
  • Frames – Extend Find/Replace to also work with RTF frames.
  • Dashboard dials – Support for a ‘Line’ pointer style added.
  • Metrics – Support for  element calculations.
  • InstallShield – Improved and  simplified
  • Configuration Management – Submission of  related items, and integrity checks for baselines
  • Items – Deleting/recovering items will record in the modification date.
  • Items – Set owner can including related items.
  • Cradle URL – Support to optionally specify a view.
  • Views -New Generic Configuration Management system view.

Social Media

Twitter

Welcome new followers. The Lake District became a UNESCO World Heritage Site which caused quite a bit of chatter on Twitter

The English Lake District from Barrow-In-Furness
View of the Lake District from Barrow

Hints of the Month

Need to create a default schema for your new projects? This article New Default Schema tells you how.

Got one of those oops moments or changes of mind? Reverse or rewind the item’s changes.

Let’s chat about this requirement/feature/risk. Why not add a discussion?

If you have lots of projects you need to keep logging in and out of, let Project Manager take the strain.

You can read Hints & Tips in the 3SL Blog.

Cradle 7.3 – Now Available

We are pleased to announce the release of Cradle-7.3!

3SL customers with active maintenance have been sent an e-mail notification of this release, and details of which enhancement requests and bug reports are in it.

Cradle 7.3
Cradle 7.3

New Capabilities

Cradle-7.3 contains a range of new capabilities that are described in its release notes:
https://www.threesl.com/downloads/download.php?version=v7.3&section=software&filename=rm00777-V73ReleaseNotes.pdf

Some of the highlights are:

  • Metrics – Calculations on metric results
  • Configuration Management – Related item submissions
  • Categories – Skill based control
  • Link rules – Cardinality control
  • Item Ownership – Set item ownership of item’s related items
  • New Cradle and Toolsuite installers

Download

Cradle-7.3 available from our website here:  https://www.threesl.com/downloads/software.php

You need a new Security Code for Cradle-7.3, other Security Codes cannot be used. There is a database conversion from 7.2 to 7.3. The converter will run automatically if you install Cradle-7.3 over the top of, in the same directory as, the earlier version of Cradle from which you are upgrading.

You must upgrade all Cradle installations to 7.3. Cradle-7.2 clients cannot connect to a Cradle-7.3 server, and a Cradle-7.3 server cannot serve Cradle-7.2 clients.

We hope that you will welcome the new capabilities in Cradle-7.3!