Isn't this a basic requirement for a purchase order system? Some people can raise them, others can approve them and people get notified as and when they've got something to do?
Choosing an approver for a PO should either be mandatory when creating it, or defined by configuration, ie. Mrs A approves POs raised by Mr B.
When Mr B raises a PO, Mrs A is notified. When Mrs A approves / declines the PO, Mr B is notified and everything moves along nicely.
Surprised to find that you're 3 years in to this suggestion with no apparent progress.
Ben Gladwyn
supported this idea
·
Isn't this a basic requirement for a purchase order system? Some people can raise them, others can approve them and people get notified as and when they've got something to do?
Choosing an approver for a PO should either be mandatory when creating it, or defined by configuration, ie. Mrs A approves POs raised by Mr B.
When Mr B raises a PO, Mrs A is notified. When Mrs A approves / declines the PO, Mr B is notified and everything moves along nicely.
Surprised to find that you're 3 years in to this suggestion with no apparent progress.