Duplicate Entries for One Software
Good Morning,
In your process for purchasing software, it is required that the software already be in the system because you have to select a related version of the software. So we've been going into the system, adding the software by hand, and then adding it into a PO for purchase.
Here is the problem. The software may be called one thing on the PO, but when a scan picks it up, it comes up as something else. For instance, Scrutinizer on an official PO is called simply "Scrutinizer." However, when it's scanned, it comes up as "Scrutinizer NetFlow & sFlow Analyzer." I'm not sure how many pieces of software have this issue, but I'm sure it's an extensive list. This creates a very big problem.
We now have two instances of this software in our system - One is the one that was automatically generated when a system scan found it, the other is the one that was manually put in so that we could order the software. We have the PO attached to one that is considered "Over Licensed" because it doesn't see an installation, and we have one that is Over Licensed because it doesn't see that we HAVE a license for it. I could just delete the one with the PO and manually put the license into the other one, but then I've lost that connection to the PO and we've completely lost the purpose of having a PO system attached to asset tracking.
This process is so broken, it hurts. There are only a couple of work arounds that I can see (because there's no "Merge" function or anything). First is the one above where we lose the connection to the PO, and that is not an option. The second is we would have to have the software installed and scanned before putting it into a PO. This is equally unacceptable as, again, the PO system becomes useless. Third is to hold off on "receiving" the purchase when it comes in, give IT a chance to install and scan the software, then, once the software is in the system, go back into the PO, change the names of what was ordered.... needless to say this option is unacceptable as well.
I'm hoping that other people have also had this issue and that it will get fixed soon. I wasn't able to find anything in the forums when doing a generic search. Thank you for your time.
~James Murphy
ServiceDesk 7.6.0 Build 7604
In your process for purchasing software, it is required that the software already be in the system because you have to select a related version of the software. So we've been going into the system, adding the software by hand, and then adding it into a PO for purchase.
Here is the problem. The software may be called one thing on the PO, but when a scan picks it up, it comes up as something else. For instance, Scrutinizer on an official PO is called simply "Scrutinizer." However, when it's scanned, it comes up as "Scrutinizer NetFlow & sFlow Analyzer." I'm not sure how many pieces of software have this issue, but I'm sure it's an extensive list. This creates a very big problem.
We now have two instances of this software in our system - One is the one that was automatically generated when a system scan found it, the other is the one that was manually put in so that we could order the software. We have the PO attached to one that is considered "Over Licensed" because it doesn't see an installation, and we have one that is Over Licensed because it doesn't see that we HAVE a license for it. I could just delete the one with the PO and manually put the license into the other one, but then I've lost that connection to the PO and we've completely lost the purpose of having a PO system attached to asset tracking.
This process is so broken, it hurts. There are only a couple of work arounds that I can see (because there's no "Merge" function or anything). First is the one above where we lose the connection to the PO, and that is not an option. The second is we would have to have the software installed and scanned before putting it into a PO. This is equally unacceptable as, again, the PO system becomes useless. Third is to hold off on "receiving" the purchase when it comes in, give IT a chance to install and scan the software, then, once the software is in the system, go back into the PO, change the names of what was ordered.... needless to say this option is unacceptable as well.
I'm hoping that other people have also had this issue and that it will get fixed soon. I wasn't able to find anything in the forums when doing a generic search. Thank you for your time.
~James Murphy
ServiceDesk 7.6.0 Build 7604