Universal Worklist - TS20000166 (purchase order release) and SWFVISU

[Mike Pokraka]

On Tue, June 14, 2011 11:28 am, Kjetil Kilhavn wrote:
> I'd have to check the authorization before doing the actual approval, as a
> manager who technically could forward a work item to a subordinate without
> sufficient authorization should not succeed in making that subordinate
> approve
> the purchase.
>
Not if you set the authorisations at task level and restrict forwarding to
possible agents or disallow it altogether. Substitution is still a
possibility, but from a legal/audit point of view this form of delegation
of responsibility is fine. But then in my experience many managers find it
easier to give people their passwords than all this complicated
forwarditution nonsense.

> So, improved security can be obtained, the direct approval button will be
> there, but at the cost of development (and maintenance) in order to handle
> locking problems, prevent approval by unauthorized agents etc.

With task-based auths the only development needed is dynamic tasks. But
you can take it as far as you like, I've built solutions where e.g. the
tasks are configured by a table (i.e. release code/amount ==> Task
TS9....) and forwarding disallowed.

>
> Thanks for the tip - and for the additional explanation for those of us
> who
> are a little slow sometimes :)

Happens to all of us :)