• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Integration / Customization IPA/ProcessFlow

HR User Actions

 4 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Jill
Basic Member
Posts: 7
Basic Member
11/11/2008 8:10 PM
I'm having trouble using "HR User Actions" to route ProcessFlow workunits to supervisors.  The workunits never show up in the supervisor's in-basket.  I'm not sure if my problem is in my ProcessFlow "HR User Action" node itself or the User/Task/Work Category set-up.
 
The regular "User Actions" work great.  But -- since I want to use the employee/supervisor structure to route items -- I think I want to use the HR User Action node.
 
The recipient of my item is Company/New_Supervisor.  On the PF Admin forms, I set-up a user where task is "MGR", Work Category = "Supervisor", and Work Category Value = "00014751" where the company=1 and sup code = 4751.  (I've actually tried lots of different variations on recipient variables, tasks, and category values without luck)
 
Any idea what I'm missing?
Thanks,
Jill
David Williams
Veteran Member
Posts: 1127
Veteran Member
11/11/2008 8:19 PM
Check the Category Filter value on the WorkUnit to see what the system is defaulting to make sure the value is what you're expecting it to be.
David Williams
Jill
Basic Member
Posts: 7
Basic Member
11/11/2008 8:47 PM
Hello,

The category filter value for my workunit is what I would expect it to be. But, do HR User Actions use the category filter value? I know the regular User Action nodes use them. I *assumed* that the HR User Actions should go to recipients based on the variables chosen in ProcessFlow. (I can't find many examples on this stuff so I'm making a few guesses along the way!)

Thanks,
Jill
David Williams
Veteran Member
Posts: 1127
Veteran Member
11/11/2008 9:11 PM
Yes, the HR User Actions do use the Category Filter values. Can you send me screen shots of your WorkUnit and the User Category Definition you're using?

ConsultDavidW@gmail.com
David Williams
Jill
Basic Member
Posts: 7
Basic Member
11/12/2008 7:22 PM
Follow-up in case anyone else is interested...

Unlike "User Actions", "HR User Actions" don't use the Task/Filter/Work Category value set-up structure at all.

A HR User Action assigned to New_Supervisor does 2 things...1) finds the supervisor as assigned on HR11 and 2) looks in Security Administrator for a Resource Management ID assigned to that employee.

The first HR User Action called starts with the Category Value of the work unit (). The next HR User Action called in the ProcessFlow automatically goes up the HR chain.

The items show up in the Inbasket under the "User Level Work" not the "Task Level Work".

In concept, it seems pretty slick. But as David pointed out, this won't work too well if there are gaps in our HR reporting structure.

Thanks for you help David!