Clarity

Hi All,

We have many custom folders in Jaspersoft. We have make those custom folders under 'organization' instead of CA PPM.

For each custom folder, we have created custom role. (Lets take an example, we have a business called 'X' and it have role like, cfo, pso, rm, im. Each roles have access to different report. hence we have created folder 'X' under organization and subfolders as 'X- CFO', 'X- PSO',' X -RM', 'X-IM', and created role as 'X- CFO', 'X- PSO',' X -RM', 'X-IM')

For 'organization', we have given role_user has read only access. all our custom roles have no access.

then for our folder 'X', roles like  'X- CFO', 'X- PSO',' X -RM', 'X-IM' has given read only, but role_user was giiven ' no access'

And for each  custom subfolder 'X- CFO', 'X- PSO',' X -RM', 'X-IM' were given 'Read+Write' access. and all custom report file was given 'read only' 

Now users having roles 'role_user' and custom roles (like 'X-CFO') is not able to schedule report, but can run in immediate mode.

getting error as below.

"

You do not have permission to view this page.

Please contact your system administrator or log in as a user with permission.

"

As an administrator, i can schedule reports.

Jaspersoft details:

JaaS Release Version = 2.2.1
JaaS Build Number = 54
JasperSoft Version = JasperReport Server 6.2.1 Enterprise (20160322_0602)
CA PPM Jaspersoft Release Version = 5.2.1
CA PPM Jaspersoft Build Number = 54
CA PPM Jaspersoft Release Patch Version = 5.2.1.2
CA PPM Jaspersoft Patch Build Number = 6

Could anyone please help to fix the same ?

Thanks,

Agin

All,

Please let us know, who all have the permission to schedule a JS report in 6.2.1

Thanks,

Agin

Hi Agin,

You need to have ROLE_USER and ROLE_REPORT_DESIGNER.provided at folder level, even though you are administrator in PPM the rights gets cascaded to CA PPM folder level and not at custom folders 

For out of box we have a technical document Which CA PPM access right is required in order to schedule a report via Advance reporting 

Regards

Suman Pramanik 

Thanks Suman. It works.

Thanks,

Agin

Great to hear Agin. Please mark this thread as answered so that other members can benefit from the same. 

Regards

Suman Pramanik 

Hi Suman,

We are also facing the same issue after upgrading to v15.1.

The users are able to schedule reports on v14.2 without granting them "Advanced Reporting - Report Create" right, they just have "Advanced Reporting - Report Navigate" right and are able to schedule reports that they have access to with any issues.

we do not want them to have the create right as we don't want them to see the create option / or create their own adhoc-views/ reports. I tried granting a test user "Advanced Reporting - Report Create" right in v15.1 and he is able to schedule reports BUT he sees create option too which is not desired. The same user with same role & access rights (minus report create right) is able to schedule reports on v14.2

Any thoughts?

Thanks,

Ashmi

Hi Ashmi,

This is how its designed at this point of time.

Regards

Suman Pramanik 

if it helps ,we were able to do this without adding report designer, despite how it is designed.   We did not grant that role, and just ensured that our custom role had the rights: 

two ways:

1. Wherever the report resides, is where the system defaults the repository when scheduling. The role associated to the user must have read/write access.  (ex: Role_user or a custom role to CA PPM folder- main - and any custom directories)- we then adjusted the subfolders under CAPPM to prevent access there (Execute only or read only)

 the Role_user must have  read/write to the temp folder too for saving parameters. 

2. If you have separate folders where you want people to save their reports, then you would need to train users to change the output location when scheduling a report. Those this had its advantages, we found it was not user friendly so we went with option 1. 

This allowed standard users to log in NOT see the report tile (I agree, that is a poor design and can cause confusion for users since they won't be creating anything) and we trained our users to go to the Library to find reports We NEVER mentioned the view>repository to greatly reduce confusion and risks. We encouraged the use of Favorites too. 

hope that helps