|
Estimating Workflow |
|
|
Written by Brent Martin
|
|
Tuesday, 22 January 2008 |
|
A friend of mine was working on a staffing model for an AP implementation and needed to know what kind of resources would be required for workflow. Could a functional person configure AP workflow, do you need a technical person and if so why. What I told him is below. How did I do?
|
|
Last Updated ( Thursday, 12 June 2008 )
|
|
|
Using Trees to Route Workflow |
|
|
Written by Brent Martin
|
|
Monday, 07 May 2007 |
I’m currently working on two workflows. The first one is Journal line approval, and the other is AR Pending Item approval. Each approval needs to go to the submitter’s “supervisor” until it gets to someone who’s authorized to approve at that level.
I had planned to use the ROLEUSER_SUPR field on PS_ROLEXLATOPR. It’s an easy solution with a delivered role query called _ROLE__SUPERVISOR_BY_OPRID. Then I discovered that the receivables department has one person who approves all Journals, so a “supervisor” for GL workflow will be different than a “supervisor” for AR workflow. At that point I couldn’t use the same ROLEUSER_SUPR field for both anymore, and I needed a new solution.
The obvious choice would have been to use Route Control Profiles. And that’s not a bad solution. But at this client, they want a workflow administrator to be able to maintain this hierarchy, and the workflow administrator won’t have access to the “Roles” page in the User Profile component in order to assign route control profiles.
Then the GL functional guy came up with a good idea (yes they can be helpful on occasion). Why not build a tree to represent the approval hierarchy?
|
|
Last Updated ( Thursday, 10 May 2007 )
|
|
|
