Miscellaneous

The Miscellaneous section contains various Cradle options which are separated over two tabs. The first tab contains General settings:

The second tab contains Configuration Management System (CMS) settings:

General Settings

• Enable recovery of deleted items - When a non-baselined item is deleted, its status is set to Recoverable therefore it can be undeleted at a later stage if required.
• Mandatory comments - Whether a set of comments must be recorded when reviewing items in the Configuration Management System (CMS) or changing item ownerships, or in an item’s change history (if history is switched on).
• Auto-generate child data definitions - If set, if a change has been made to the COMPOSITION frame of a data definition, then the contents of the frame would be generated as child data definitions, if this option isn't set, the contents of the frame would generate pseudo links.
• Do not reuse PDUIDs for same items - If enabled, when items are deleted (fully deleted, not merely placed on the recoverable list), and later re-created a new PDUID is assigned to the item. By default, the previous PDUID is re-used for the re-created item.
• Disable editing RTF frames - Control whether you can edit RTF frames
• Hide automatic scope queries - If enabled automatic scope queries are hidden from all combo boxes. Please note this will not prevent automatic queries from being generated.  Although you will still be able to run them from the Definitions sidebar and the Quick Access Bar.This option is off by default.
• Allow full login (including plain text passwords) in Cradle URL generation - If enabled allows the display of plain text passwords in a generated Cradle URL. PLEASE USE WITH CAUTION!!!
• Maximum UI image dimension - Allows you to enter a maximum image size in the range 256 to 4096.
• Default Start Page - Set the default start page for the project.

Initialisation Defaults

• Copied items preserve history - If set this option will be preset in the Copy dialogs
• Copied items preserve discussions - If set this option will be preset in the Copy dialogs

Configuration Management System (CMS) Settings

The Configuration Management System (CMS) options are split into the following sections:

Baseline

• Enable CMS logging in Configuration Management log - If set enables logging of CM events by the CMS, changes to this value are also logged. This option is enabled by default.
• All attributes are mandatory - If set all attributes are mandatory for baselines (Name, Title, Reference, Purpose, Summary and Comment).

Items

• CMS discard change histories - When an item is registered into a baseline, its change history is discarded.

• Leaders of top-level teams who have BASELINE privilege can register items into baselines - If the checkbox is set then a user who is the leader (has the privilege TEAM_LEADER) of a top-level team and who has BASELINE privilege, can register items into baselines. If false (default) the only users who can register into a baseline are users whose team is PROJECT and who have BASELINE privilege.

• Project-level reviewers are in PROJECT team, not top-level team leaders - If set to true (false by default) Project Setup will set the reviewers of project-level reviews (reviews of information that will be placed into a baseline) to be members of the PROJECT team with APPROVAL privilege. If false, the reviewers are users with APPROVAL and TEAM_LEADER privilege of top-level teams. Users with BASELINE and APPROVAL and users with QA_MGR are always included.

• Disable copying of baseline items - Controls whether or not users are allowed to copy project-owned items to create user-owned instances of these items. By default, users can do this but if the setting is changed then users cannot copy project-owned items, i.e. users are then forced to use change requests (CHRs) and change tasks (CHTs).

• Allow baseline item copy to new item - Allows an item in a baseline to be copied to a new item, i.e. not a new draft instance but a new item with a new identity.

• Allow showing baseline items as suspect - Controls whether baselined items are to be considered as suspect, this is off by default.

Change Requests

• Allow registered Change Requests to be edited by - Option to choose which users can edit change requests that have been registered (and so are underway) as one of:

• None - Change requests cannot be edited once they are underway
• Users in author's team with Edit Change Requests (CHR_EDIT) privilege - A user can edit a change request that is underway if it was raised by a member of the same team
• Users with Edit Change Requests (CHR_EDIT) privilege - A user can edit any change request that is underway (this is the default value)

In this context, edit means the ability to:

• Change the contents of text attributes and frames inside the change request

Change requests cannot be edited if they are rejected or when they are complete.

Please note that change requests can also be edited when they are under review by any user who has CHR_APPROVE and CHR_EDIT privilege. In this context, edit means to:

• Change the contents of text attributes and frames inside the change request

• All attributes are mandatory - If set all attributes are mandatory for change requests (Originator, Priority, TEXT, Reviewers, Title and Summary).

Change Tasks

• Baseline must be closed before Change Tasks can be completed - This is set by default. If this checkbox is deselected then you can complete a change task if the latest baseline is open or closed.

• Allow CMS Change Tasks to be raised with no items - If set allows change tasks to be raised with no associated items. Therefore items can be moved into them from other already-underway CHTs.

• Allow registered Change Tasks to be edited by - Option to choose which users can edit change tasks that have been registered (and so are underway) as one of:

• None - Change tasks cannot be edited once they are underway
• Users in author's team with Edit Change Tasks (CHT_EDIT) privilege - A user can edit a change task that is underway if it was raised by a member of the same team
• Users with Edit Change Tasks (CHT_EDIT) privilege - A user can edit any change task that is underway (this is the default value)

In this context, edit means the ability to:

• Change the contents of text attributes and frames inside the change task
• Remove items to or from the list of items associated with the change task
• Delete items associated with the change task, which removes the items from the list of items associated with the change task and will optionally delete the item

Change tasks cannot be edited if they are rejected or when they are complete.

Please note that change tasks can also be edited when they are under review by any user who has CHT_APPROVE and CHT_EDIT privilege. In this context, edit means to:

• Change the contents of text attributes and frames inside the change task
• Add or remove change requests to or from the list of change requests associated with the change task
• Add or remove items to or from the list of items associated with the change task

• All attributes are mandatory - If set all attributes are mandatory for change tasks (Changer, Item(s), Change Request(s), TEXT, Reviewers, TITLE and Summary).

---

Related Topics