Description:
The user-defined and stock attributes created on the 'Project Financials Properties' object are secured properly when accessed on the Project > Financial subpage, but are not secured properly when accessed from the Project List View or other Project Property subpages. Similar behavior is seen for Non-Project Investments.
We are using the following Financial security access rights in combination with the 'Project - Edit Management - All' right.
The Project Edit Management right should not encompass the financial properties rights.
Project - Edit Management - All
Allows user to edit the general and management properties, staff and tasks for any project that has been enabled for management. This includes the ability to add sub-projects to that project as well as to edit it in Microsoft Project and Open Workbench. This right also allows the user to create processes on any project and to edit the processes that he or she creates.
Project - Edit Financial - All
Allows user to view and edit general properties, processes and financial information on all Projects. Also allows the user to enable financial fields on a Project.
Project - View Financial - All
Allows user to view the general and financial properties and processes on all projects. This right does not include the right to view the financial plan (budgets/forecasts).
In exploring the behavior of these rights with respect to user-defined attributes it appears that the two rights only affect fields placed on the Project > Financial Properties subpage.
If we place the user-defined or stock attributes on the Project List View or other Project Property subpage, and if the end-user has the ability to edit the project, these financial user-defined or stock attributes can be edited in these other places.
Steps to Reproduce (Setup):
<Please see attached file for image>
<Please see attached file for image>
<Please see attached file for image>
<Please see attached file for image>
<Please see attached file for image>
Steps to Reproduce (Resource1):
<Please see attached file for image>
<Please see attached file for image>
Steps to Reproduce (Resource2):
<Please see attached file for image>
<Please see attached file for image>
Expected Result: The 'Project Financials Properties' Object attributes should be secured in all places
Actual Result: The attributes are not secured by the 'Project - View Financial - All' right in all places
Additional testing:
Add the user-defined and stock attributes to other Project Property subpages. When the end-user navigates to these other pages within the project, since they have the ability to edit the project instance, these fields are also open for editing on these other subpages.
Non-Project Investment Financial Properties:
Similar behavior is seen for Non-Project Object Investment Types (NPIOs): Asset, Application, Product, Other Work, Service (not Idea)
Steps to Reproduce (Setup):
<Please see attached file for image>
Steps to Reproduce (Resource2):
<Please see attached file for image>
<Please see attached file for image>
<Please see attached file for image>
<Please see attached file for image>
<Please see attached file for image>
<Please see attached file for image>
<Please see attached file for image>
<Please see attached file for image>
<Please see attached file for image>
<Please see attached file for image>
Solution:
WORKAROUND:
None.
STATUS/RESOLUTION:
Resolved in Clarity 12.1.3
Resolved in Clarity 13.0.1, 13.1.0
Keywords: CLARITYKB, CLRT-61986, CLRT-61985, CLRT-58196, clarity12resolved, clarity1213resolved, odf_view, finpropertiesUpdate, projmgr, projectproperties, odf_view=finpropertiesUpdate.projectCreate, nmc.userGlobalAssoc, revmgr, clarity13resolved, clarity1301resolved, clarity1310resolved.