User can mark any baseline as current revision even when Current Revision attribute is secured.

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

User can mark any baseline as current revision even when Current Revision attribute is secured.

Steps to reproduce:

1. Create business rule in blueprint to disable edit of Current Revision based for an access group.
2. Assign blueprint to a project.
3. Log in as user from the access group where they are prevented to edit current revision.  Navigate to the Baseline module, create a baseline called “Baseline 1”, this baseline is automatically marked as the Current Revision.  Create another baseline called “Baseline 2”.  The Current Revision attribute is blank.
4. Double-click on the Current Revision checkbox for Baseline 2.

Expected Results: User cannot mark Baseline 2 as Current Revision.

Actual Results: Current Revision for Baseline 2 cannot be edited.  However, user can mark Baseline 2 as current revision when right-click on Baseline 2 and select option Make Current Revision.

Resolution

As per current design Actions are not controlled by business rules.