We would like to create a process (or job) to automatically approve Clarity timesheets. Any suggestions how to do this?
Check this -
Thanks to Jeanne from CA!. This has been a learning experience. The process wouldn't run because our BG services were down in our DEV environment.
Started BG service and Process is working.
Thanks to all who replied with suggestions!
That should not be so complicate.
You can create a condition than when TS is 40 or more hours gets auto-approved.
See screenshot with condition.
then in next step, you create a system action which sets status to "approved".
But you need to think what to do when it's less than 40h. Do they get rejected, etc... .. further steps, who gets notified, etc...
Thank you for the links. I found both of these during my research however more assistance is needed. We are a small team. Most of my training so far is OJT, no formal CA training yet. We are running V13.1
and want to auto approve all timesheets where hours are 40 or more. I have reviewed the workflow for the Project Manager Approval process but have not been successful in creating an automated process.
Any additional help is appreciated.
If you have access to the GUC sandbox, you can take a look at the "Conditional Automatic Approval" process as an example.
I've attached the screenshot from a simple timesheet aotu-approve process for your reference (with the condition you look for) that I created on the GUC sandbox
Hope this would help !
Happy Friday and have a nice weekend
Also, check this -
Setting Timesheet Status with SQL
Thank you for the screen shots! The process we created is very similar, see attachment. We validated and activated however when we test, the process is never initiated.
Your users will need to have the relevant access-right to "start" the process.
Perhaps you have missed that?
Our basic user group has access to "start" the process.
Ok well there could be many horrible reasons why a process would not start - do any other processes run on your system? If not, then your "process engine" might not be set up correctly (or might not be running);
You would go into the admin menu to debug the "process engine" - there is a "Process Engines" option in the menu (which your admin user needs a specific right to see) - then you can look at the "Events" tab within that to see if the app is "sending messages" to the Process Engine (which wouldn't happen if the user did not have that "Start" access right) and also whether the messages are being received (and then processed) by the "Process Engine" - if the engine has fallen over you would see a lot of stacked up messages. Debugging all this if something has gone wrong technically can be a nasty job though.
If other processes do run OK, then its reasonable to assume that there is just a problem with your new process though, and I have not looked in any detail at your screen shots so I will not comment on that just now.
David, thank you for your help. We have not successfully run a process in this environment so my suspicion has been something
in the set-up. Based on your reply, I believe our problem is in the Process Engine and how it was configured.
As I mentioned earlier we are a small team with limited experience. Unless there are other recommendations I will probably open
a case with CA help desk.
Can you check the process engine status ?
What do you see in the logs when the Timesheet status is Submitted ?