Purchase limitations
I was in a demo today running the PO element of ServiceDesk past our purchasing manager to see if it would meet her requirements. The module strikes me as a little bare-bones and certainly lacking in some areas, and rather an odd module for an IT Helpdesk product.
Anyway, she registered the following limitations:
What plans (if any) are there to develop this area of the program?
Anyway, she registered the following limitations:
-
*Requestors cannot raise POs which means additional technician licenses, which is quite an expense for departmental managers or the like to click Add a few times.
*No ability to enforce who can approve what according to cost.
*History doesn't track changes to quantity (and possibly item changes?)
Signing authority field doesn't link into your requestors or technicians and isn't enforced in any way, it's effectively meaningless.
*No system to auto-generate PO numbers.
*Doesn't support multiple levels of sign-off, for example (in our business) a PO being signed off by both approver and purchasing, and I know some places require multiple sign-offs for large spending.
*No way to link POs to business cases for tracking purposes. While Remarks can be used for this, it really needs a dedicated field or the ability to attach files.
*Unable to make fields mandatory.
*No customisation of template to account for things like the business case field.
What plans (if any) are there to develop this area of the program?