Chain of Approver -Timesheets

[/pd]

I remember a long time ago, that Dale had posted a good hack 0n creating a
chain for mulitple timesheet approvers. I pulled that thread up and some
research. The problem that I am having is at times the Chain of approvers is
not liner, based on the resource, the next in line maybe either one or the
other (PM)

Link to Dales process [
http://msdn.microsoft.com/newsgroup...&p=1&tid=af934d7a-1e82-4f54-a636-db81993ef687]

the scenario looks like this

TeamMember => PoolManager=> Product Manger(A) => SeniorMngr

Now at times the TeamMember can work on two seperate Projects and then the
pool manager needs to actually route the Timesheet to ProductManager(A) and
then to another productManager(B), who then routes it SeniorMngr.

Question, using Dale's process, is it possible for

a) PoolManager create more then one appoval route ?
b) ProductManger(A) to route to ProductManger(B) for review

end state of approval will always be srMngr

any suggestions ??

 

[Dale Howard [MVP]]

/pd --

I don't really think Project Server 2007 offers the flexibility you need
with the chain of approvers. The chain is pretty much "hard wired" to send
the Timesheet to a manager, who approves and sends to another manager, who
approves and sends it to the final manager. I don't think there is any way
to change the approvers "on the fly" so to speak. Sorry, but I hope this
helps.

 

[/pd]

Thanks Dale.. then we'll need to just hardwire the route.. too bad for the
product(b) manager -

/pd --

I don't really think Project Server 2007 offers the flexibility you need
with the chain of approvers. The chain is pretty much "hard wired" to send
the Timesheet to a manager, who approves and sends to another manager, who
approves and sends it to the final manager. I don't think there is any way
to change the approvers "on the fly" so to speak. Sorry, but I hope this
helps.

I remember a long time ago, that Dale had posted a good hack 0n creating a
chain for mulitple timesheet approvers. I pulled that thread up and some
research. The problem that I am having is at times the Chain of approvers
is
not liner, based on the resource, the next in line maybe either one or the
other (PM)

Link to Dales process [
http://msdn.microsoft.com/newsgroup...&p=1&tid=af934d7a-1e82-4f54-a636-db81993ef687]

the scenario looks like this

TeamMember => PoolManager=> Product Manger(A) => SeniorMngr

Now at times the TeamMember can work on two seperate Projects and then the
pool manager needs to actually route the Timesheet to ProductManager(A)
and
then to another productManager(B), who then routes it SeniorMngr.

Question, using Dale's process, is it possible for

a) PoolManager create more then one appoval route ?
b) ProductManger(A) to route to ProductManger(B) for review

end state of approval will always be srMngr

any suggestions ??