CAWA DE r.12 - granting group access

[Kenneth Chrapczynski]

Hello,

When setting up group access and granting permissions what permission gives the group ability to release an Application that is in APPHOLD status?

Does that fall under APPLX, or APPL. If it is APPL what access do you choose Alter, or Update? I would like to only allow the group to Hold, Complete, Release and Unwait the application. I do not want them to be able to trigger, or insert a job.

Ken Ski

[Nitin Pande]

Hello Ken,
The APPLX permission allows you to execute application.
See here.


Thank you,
Nitin Pande

------------------------------
Support
Broadcom
Toronto
------------------------------

[Kenneth Chrapczynski]

Hi Nitin,

That is what I was hoping you would reply. I have the group setup and the users can perform commands against jobs w/o issue, it is just the Application they say they get an error. I asked them to show me the error but they were not able to share their screen or capture the error, they said it closed before they can capture it. 

I am attaching the group and one of the applications that were in question. Do you see anything more I need to add to the group?

[Kenneth Chrapczynski]

Hi Nitin,

I was able to have the user show me the error. It has to do with how all jobs are named in the Application. None of the jobs in this app have DW_* in the name. So they get the following error. How do I grant the group permission where they won't get this error? Do I need to rename all of the jobs and have DW* as part of the name?

[Kenneth Chrapczynski]

I would think the current setting should be enough since there are all asterisks for job name, qualifier and command?

[Nitin Pande]

Hi Ken,
So I think that if you give * for Job Name field in  DW* applications then users should be able release and resubmit the application and all the jobs in it.  You don't have to rename the jobs.
Try that and see if you get the same error as before.

Thank you,
Nitin Pande

------------------------------
Support
Broadcom
Toronto
------------------------------

[Kenneth Chrapczynski]

That is what the setting is already. Am I missing something?

[Nitin Pande]

Hi Ken,
Are they having problems with just this application?
I also noticed a DENY permission for RESET DEFINITION.  Normally deny takes precedence over allow.
Can you remove that temporarily and then try it again?

Thank you,
Nitin Pande

------------------------------
Support
Broadcom
Toronto
------------------------------

[Kenneth Chrapczynski]

I removed the reset definition one and received same error. I don't know hoe the hierarchy for permissions works/is, but it seems to not honor the asterisk on the job names. So, I also renamed 2 jobs, triggered them in and still received the same error. 

This is the screenshot of testing w/o reset definition. I didn't capture the second test after renaming the jobs, but it was the same error message.

[Ravi Kiran Kunduri]

Hi,

Looking at the permissions, it should have worked. Can you please look if there are any user level permissions for the user who is running this command.

Ravi Kiran

[Ravi Kiran Kunduri]

Hi,

Can you please open a ticket to investigate this further. 

Ravi Kiran