Post Upgrade: Our company does not allow resource managers access to the Financial Properties subpage for the resources they manage, how to disable the Resource - Edit Financial access right after upgrade

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

After upgrading PPM, we find that the Resource - Edit Financial access right is readded to the resource managers. Our company does not allow them to see Financial Properties subpage, so we would like to disable the Resource - Edit Financial access right, how to proceed?

Environment

Starting PPM 15.2, the file is no longer added with the PPM installation, and has to be downloaded and installed per this article

Resolution

Remove the Resource - Edit Financial access right.
 
If your company policy does not allow resource managers access to the Financial Properties subpage for the resources they manage, you can remove that capability.
 
Run a post installation script to perform the following actions:

1. Remove the Resource - Edit Financial access right from all current resource managers.
2. Clear the setting for the financial option that automatically grants the access right to new resource managers.

 
Note: To maintain existing behavior, this right is granted during the upgrade. This right replaces the automatic right that was removed as part of the Financially Enabled Roles feature.
 
 
 
Follow these steps:
0. Copy the attached file to the PPM server, in <clarity_home>/bin directory
1. At the command line on the same server, navigate to the <clarity_home>/bin directory.
 
The directory contains the dbpatch script. We recommend you to always run the command from here.
 
2.Run the following command:
 
Windows:

dbpatch -install -file RevokeResEditFinRightFromResourceMgrs.xml -apply

 UNIX:

./dbpatch -install -file RevokeResEditFinRightFromResourceMgrs.xml -apply

3. You may now remove the file from the /bin directory
 
Note: You may use another directory to copy the file, just correct the commands to have the full path to run it.
 

Additional Information

Logged as DE39299, solution provided in the article.