Prev
Next
Forums Integration / Customization IPA/ProcessFlow

WF12 Tasks as ROLEs

 2 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Carrie Busbee
Basic Member
Posts: 10
Basic Member
1/28/2009 2:01 AM
     Has anyone approached the WF12 Tasks as a Role instead of Task in the Workflow? we are debating whether to create a "Promotion Action Approver" task and a "Termination Action Approver" task and assign it to each HR Rep - or just create an "HR Rep Approver" task that can be used in many work flows.  THe goal is to cut down on WF12 administration and restrict workflow requirements to certain "standards".

    Has anyone else used the WF12 Tasks as Roles?
    David Williams
    Veteran Member
    Posts: 1127
    Veteran Member
    1/28/2009 6:31 AM
      I have had clients add multiple Tasks when Lawson’s standard ones didn’t fit their structure but not like this. I wouldn’t recommend, as you seem to be suggesting, Tasks for each Personnel Action. The “HR Rep Approver” Task would be the best approach.

      You can use the UserAction node’s Work Title to reflect the Personnel Action being approved as a way to distinguish them within the one Inbasket Task.
      David Williams
      Gary Davies
      Veteran Member
      Posts: 248
      Veteran Member
      3/9/2009 10:07 AM

        The only other suggestion I would make is you could set up an employee group of the valid users for the action, in the inbasket display you could display a message that they are not assigned to take the action, and in the flow when the approve action is taken check to see if they are in the employee group and if not reroute back to the User Action.