User gets error on new status report: API1007 you are not authorized to post resources.
Why would a user need to be able to post resources to print a report?
What rights added to to the user will fix this?
Do you have PMO addin installed?
I think it is... we're SAAS so whatever they load into SAAS by default is what we have. I think that does include the PMO add on.
The addin must be installed but you need to apply the same also and thats is part of PPM administration via UI.
I find that response confusing...
HOWEVER, AS IT turns out the add-in had nothing to do with it.
The user must have the rights for "Status Report - Create" and "Status Report - Edit All"
According to support, the error message has absolutely nothing at all to do with the error.
After adding these two rights to the Group, I found that the error message is now suppressed.
To the opposite effect, I now find that users in the newly udated Group can now create and edit Status Reports for Projects that they are not the PM for, superceding settings in the OBS security.
I wonder if there is a way of not completely opening up access for any PM to create/edit any Projects' Status Report.
Currently this is a design limitation for the status reports in the NewUX – you are not able get the fully granularity of the security rights that you have in Classic PPM.
The way some other customers are utilizing the NewUX status reports is that since it is a PDF, it can be sent via email to stakeholders and you don’t have to manage the rights for each PM.
Also, it is mentioned in the documentation below that these rights need to be given to the PM for the New UX
New User Experience: Compare with Classic CA PPM - CA PPM - 15.3 - CA Technologies Documentation
Retrieving data ...