Restrict editing ability on an attribute field level

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

The application administrator created some user-defined custom attributes on the Project Object and placed them on subpages. We have configured our pages with security so that some end-users can view only or edit the values on the pages. This is okay, but we want to be able to control some individual fields on the page so that only a select set of end-users will have the ability to edit the values.

Environment

Release: All Clarity releases

Resolution

The application security model does not have a feature for configuring or defining security access rights at the attribute/field level, however with the Business Process Management (BPM) feature, the administrator can create a BPM Process definition that will 'lock' specific attribute fields. The idea is to create a process that will 'auto-start' and 'lock' the appropriate attributes. A second BPM process will also be created to allow specific end-users, with proper security access to the process, to 'unlock' the attributes to allow controlled editing.