Is anyone using the K1 to enter and track PO information? If so, how are you doing it? We are considering abandoning our current ticketing system in lieu of the Kace service desk. We currently enter POs and print them out from our old system. Not seeing how I could print out a PO form. Only thing I can think of is attaching one to an asset but that means manually filling in the form, printing it out, then attaching it. Let me know what you may be doing out there in your own environments...
0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity


We have a queue configured for purchasing. As part of the configuration I created an asset called "Purchased Assets" and those can be selected when our purchaser makes purchases. Custom rules pull in data from the asset such as price and enters those in the ticket. Each individual purchased item is a child on a parent ticket. This makes the ticket view a little complicated because the parent ticket includes the fields for the individually purchased items.

When a user enters a purchase request we supply what needs to be purchased in the comment and set the required fields. The purchaser then creates child tickets for each purchase. When items are received our receiving folks update the child ticket's status to indicate that to the requestor. 

Another thing I did was create a custom rule that adds the ticket number to a field in the Purchased Items asset so you can look at a purchased item and find on which tickets that item has been purchased. 

One thing we can't do with this system is generate an actual printed purchase order but our institution has a separate system tied to our central accounting system (Banner) that provides that functionality. Where an actual PO is required our purchaser generates it in that system and can attach it to the ticket. She also attaches any paperwork from vendors to tickets so it is easy to go back and reference in the future.

Answered 04/08/2015 by: chucksteel
Red Belt

  • LOL I hope that's your work number and not your cellphone on the screenshot.
    • Yes, that was my work number. Thanks.
Please log in to comment