Kace - Purchase order process
Hi,
Have some problems to configure our purchase order process. If anyone has a how-to or tips that would be great. Will describe our set-up but the main problem is to get the approvals to work for the different steps.
Scenario:
1. user need x equipment
2. signs on to kace and servicedesk and order the x equipment via? process or ticket or?
3. which shall start the process that I cant get to work
4. the user shall chose (his or hers boss) one of a handful of managers that are allowed to approve this first step
5. after first approval it shall in the next step move on to our Management Director for the final approval
6. IT department then order the x equipment
Hope this workflow makes sense.
Any tips or ideas how to get this to work?
Best Regards
christian
Have some problems to configure our purchase order process. If anyone has a how-to or tips that would be great. Will describe our set-up but the main problem is to get the approvals to work for the different steps.
Scenario:
1. user need x equipment
2. signs on to kace and servicedesk and order the x equipment via? process or ticket or?
3. which shall start the process that I cant get to work
4. the user shall chose (his or hers boss) one of a handful of managers that are allowed to approve this first step
5. after first approval it shall in the next step move on to our Management Director for the final approval
6. IT department then order the x equipment
Hope this workflow makes sense.
Any tips or ideas how to get this to work?
Best Regards
christian
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
nshah
12 years ago
Hi Christian,
Scenario:
1. user need x equipment
theis can open a single ticket in the KBOX
2. signs on to kace and servicedesk and order the x equipment via? process or ticket or?
Currently there isn't a way for a ticket to trigger a process, they would have to trigger a process on their own. If it is just an equipment request, I don't think you need to have more then one ticket.
3. which shall start the process that I cant get to work
I don't think a process is needed but again if you wanted to you could create a process that has 3 child tickets. One for the 1st approver, one for the 2nd and then the IT ticket. The hard part would be to select the 1st and 2nd as approvers. KACE is working on allowing multiple approvers which would help your process out.
4. the user shall chose (his or hers boss) one of a handful of managers that are allowed to approve this first step
Right now there can only be one approver so once they approve it, you have two choices you can do.
1. The 1st approver had to say yes to the purchase and SAVE. Then manually select the next approver.
2. You can create a ticket rule that automatics if the 1st manager is USER 1 then send it to approver 2 if USER 1 OK's the purchase. If they say no then another rule would close all the other tickets as there is no need to go to the second approver or IT. There are a lot of different ways you could do the automation but it would require that you write custom SQL statements and update queries.
Scenario:
1. user need x equipment
theis can open a single ticket in the KBOX
2. signs on to kace and servicedesk and order the x equipment via? process or ticket or?
Currently there isn't a way for a ticket to trigger a process, they would have to trigger a process on their own. If it is just an equipment request, I don't think you need to have more then one ticket.
3. which shall start the process that I cant get to work
I don't think a process is needed but again if you wanted to you could create a process that has 3 child tickets. One for the 1st approver, one for the 2nd and then the IT ticket. The hard part would be to select the 1st and 2nd as approvers. KACE is working on allowing multiple approvers which would help your process out.
4. the user shall chose (his or hers boss) one of a handful of managers that are allowed to approve this first step
Right now there can only be one approver so once they approve it, you have two choices you can do.
1. The 1st approver had to say yes to the purchase and SAVE. Then manually select the next approver.
2. You can create a ticket rule that automatics if the 1st manager is USER 1 then send it to approver 2 if USER 1 OK's the purchase. If they say no then another rule would close all the other tickets as there is no need to go to the second approver or IT. There are a lot of different ways you could do the automation but it would require that you write custom SQL statements and update queries.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
