Timesheet Approval Rights

[Paul Schofield]

Up until now, at this client, all timesheets were approved automatically via a GEL script that has a XOG step that picks up submitted timesheets and uses a XOG call to approve them.

Now, they would like to have the resource managers approve timesheets for the resources who report to them. So, I put the process on hold and I tried adding Timesheet Approve All to the RM group, but then the managers see the timesheets for all resources who've submitted a timesheet, not just their direct reports. What rights do I need to grant? I don't want to use instance rights if at all possible.

The idea is that RMs will see and be able to approve timesheets for their direct reports, and nobody else's.

[Ashok Kumar Modi]

Hi Paul,

I think you don't have to add Timesheet Approve - All access to RM group. I feel that you can add a manual step in your timesheet approval process to notify the resource manager of that timesheet only. This way only the resource manager of the resource who submitted the timesheet will be notified to approve the timesheet.

To do this you can add assignee using Object Role tab of the action and choosing "Resource Manager" as your assignee. This setting would look something like below:

Disclaimer: I have not tested this on my own, but I feel this should work. 

Please do share your findings of your tests.

Regards

-Ashok

[Paul Schofield]

Thanks for this but there is another process that runs on Mondays that emails the RMs with a list of their resources and timesheet dates that need to be approved.

At the moment RMs can see the list of timesheets for their resources but the Approve button isn't present, neither is the "My Rights" drop down. SO, I added the Approve All right. That enabled the button and drop down but it's a bit too blunt as all RMs' resources now appear, and the best we can do is filter by OBS, but it's a bit clunky.

Can this be done via OBS rights perhaps?

Thanks again,

Paul

[Liz Williamson]

Paul,

I believe you need a lower level of rights and not one right for a whole group.  As you said, if the group has the right, they will see all the timesheets.

You will either need OBS level rights if each manager has their own OBS, or instance rights where each approve has an instance right to approve their resources.  Instance level rights can get tedious to manage if you have a lot of change in the organization. 

------------------------------
Liz Williamson
Principal Support Engineer - Clarity
Broadcom
------------------------------

[Paul Schofield]

Thanks Liz.

I'll explore.

Paul

[Ming Cheung]

Hi Paul,

If you are on a current version on Clarity, you can now define security rights as part of a Resource blueprint as a business rule.

This was introduced in 16.3.1.  There are a couple of gotcha's to feature so please read up on it in the documentation from that release.  The largest gotcha is that the rule is only applied when the resource is changed in the UI.  You will need to run a script to add these rights to all managers once, then let the rule do it's thing.  Note that you can also have different blueprints for different categories of users

[Paul Schofield]

Hi there,

This looks interesting, and I will explore, but they're on 16.2.2 Classic.

Thanks for the response though!

Paul

[Luis Palacios]

Hi Paul, something we've done a couple of times is setup an OBS based on the manager structure, in some cases even setting the OBS via a process. To then use OBS rights to manage resources and/or timesheets, without having to go down to the instance based permissions

[Paul Schofield]

Hi there,

Yep it's looking like OBS rights are the only was this can be achieved.

Paul