Baseline
A Baseline is a snapshot of a Project at a particular point in time, including digital content such as Requirements, Tracker items, Wiki pages, Documents, Comments, or attachments. It configures and saves your content across projects. It also lets you go back in time to an earlier version of your project. Compare Baselines and get statistics on what changed over time. Changes are highlighted with information on when the change was made and by whom. Baselines are signed with a unique electronic signature by each user.
Create and compare Baselines for specific Trackers and document directories. Codebeamer X's BPM Workflow engine automatically creates a new Baseline with default workflow actions.
Baseline Content
A Baseline captures the state of your digital content in a particular time, such as marking a particular state of a source code in a Version Control System.
Creating a new Baseline creates a snapshot of your requirements, Tracker items, wiki pages, documents, comments, and attachments. It lets you go back in time to an earlier version of your Project. Compare Baselines and get statistics on what changed over time. Changes are highlighted with information on when the change was made and by whom. Baselines are signed with a unique electronic signature by each user.
A Baseline is useful for audit purposes, including any deviations in previous versions. It's also useful for a certification of approval and maintaining wiki pages for multiple product releases.
A Baseline is a read-only directory of all documents and revisions in a document tree branch, including hierarchy and structure.
Baseline Wiki Page
A Baseline wiki page stores all its content, documents, references, and revisions.
When browsing a wiki page on a Baseline, references are resolved even if target documents have been modified or deleted.
Document
A Baseline is read-only because it stores references to specific document revisions that already exist; it does not copy document data.
A document revision can be referenced by any number of Baselines at the same time.
A document revision referenced in a Baseline is not deleted unless the Baseline holding the reference is deleted. The same goes for deleting a document in a document tree branch or Project.
After creating a Baseline, you cannot edit or remove items from it.
You cannot define permissions for individual items. Item permissions in a Baseline are solely controlled by the Baseline.
Tracker
To create a New baseline on the item tracker, set subject/source of the triggering event.
Tracker Item
When creating a New baseline, a snapshot of the requirements and tracker items is saved.
Comment and Attachment
When creating a New baseline, a snapshot of the comments and attachments is saved.
Association
When creating a New baseline, a snapshot of the associations is saved.
Suspected Alert
When opening a Baseline, suspected alerts are activated. These cannot be cleared by users.
Create Baseline without Electronic Signature
When creating a New baseline, select to not use an electronic signature, leave the signature textbox empty.
Create Baseline with Electronic Signature
To create a Baseline with electronic signature:
1. Go to Tools and select Baseline.
2. Click New baseline.
3. Fill out Name and Description.
4. Select Generate signature and login with your credentials.
5. Click Save.
Create Project Level Baseline
When creating a new Baseline at a Project level, a snapshot of the entire Project is saved.
Create Tracker Level Baseline
To create a new tracker level Baseline:
1. Open the tracker.
2. Click 
.
.3. Select Create baseline.
Browse Baseline
To browse a Baseline, click the Baseline's name on the Baseline list. A new window is loaded with the Baseline's content.
Compare Baselines
To compare two baselines:
1. Go to Baseline.
2. Select two baselines and click Compare baselines.
3. Difference gets highlighted.
Delete Baseline
To delete a Baseline:
Click 
at right side of the baseline.
at right side of the baseline.