Attributes on secure subpage are editable on Resource list view
search cancel

Attributes on secure subpage are editable on Resource list view

book

Article ID: 107688

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Even though attributes (examples: 'Open for Time Entry' or 'Active') are on secured subpages, the fields are still editable from the list page. The expectation is that the secured sub-page should prevent users from updating this field while still being able to edit other fields. 

Steps to Reproduce (using example of Open for Time Entry field on Resource list view)

  1. Navigate to Home > Resource Management > Resources
  2. Create a New resource called 'Test'
  3. Navigate to Administration > Studio > Object > Resource
  4. Go to views > Click on [Layout:Edit] for 'Resource Labor'
  5. Click on Subpage for 'Settings' and set display conditions i.e project time tracking
  6. On the Resource List view > 'Options' set the AVP to: Use display conditions and secured subpages to protect attribute values on this list
  7. Navigate to Home > Resource Management > Resources
  8. Click on 'Test' resource > Properties the setting page is secured and hidden > Click on 'Return' button
  9. Add 'Open for Time Entry' to the resource list view 

Expected Result: The 'Open for Time Entry' shouldn't be editable 
Actual Result: The 'Open for Time Entry' is editable

Environment

Release: All Supported
Component: Clarity Studio

Cause

This issue was reviewed as DE39961 by Product Management and it is determined to be working as designed.

Resolution

To make the fields un-editable, the condition will need to be set on other type of resources as well (i.e Material, Equipment, and Expenses). Once the condition is placed on all types of resources, the expected results will work.

Note:

If a field is on a secured subpage on all resources types, it will either need to be removed from all unsecured subpages on the four role types or added to secure subpage on the roles as well as the resources. Only then will all the fields on the secured subpage on the role be un-editable on the list page.