So i am looking for recommendations on how to document vendors that support our applications.
Our basic use for the system is ticketing system for our internal users.
Within the CMDB i would like to document the vendor, its points of contact, our service contract with them ( as well as start / end date) and then relate any other documentation to them.
Two examples would be office 365 and our managed print vendor.
For office 365 that of course would be the app name
Vendor would be two parts, first our reseller and then also Microsoft.
For the managed print i would just used that as the name
vendor would be who we are contracted with
Then a way to create contracts for them and link any other documents to them. Also for say the managed print i would like to link the printer objects to them as well. we have some printers that are off contract so i could separate them.
Not sure if i should create these vendors as their own organization. I figure im somehow using a provider contract. Looking for recommendations on this on how others have set this up.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So i download your extension to my test build and loaded it into the extensions folder, rebooted as well for good measure but im not really seeing anything different.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So I didn't install it right. New to Linux (using ubuntu), working now at a non profit so working on learning Linux to cut down on windows incensing where i can.
I installed it to the extension folder but the added step to take ownership and give write permission to the config file in the production folder was missed and then of course re running the setup which does the install and then fixes the permissions on the folder were missed.
Now that that is corrected I see the changes.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So i am looking for recommendations on how to document vendors that support our applications.
Our basic use for the system is ticketing system for our internal users.
Within the CMDB i would like to document the vendor, its points of contact, our service contract with them ( as well as start / end date) and then relate any other documentation to them.
Two examples would be office 365 and our managed print vendor.
For office 365 that of course would be the app name
Vendor would be two parts, first our reseller and then also Microsoft.
For the managed print i would just used that as the name
vendor would be who we are contracted with
Then a way to create contracts for them and link any other documents to them. Also for say the managed print i would like to link the printer objects to them as well. we have some printers that are off contract so i could separate them.
Not sure if i should create these vendors as their own organization. I figure im somehow using a provider contract. Looking for recommendations on this on how others have set this up.
Keep in mind that you could also extend some classes, so you can have both vendor and reseller.
This was an alternative approach to documenting licenses etc: https://github.com/jbostoen/itop-jb-software-mgmt
So i download your extension to my test build and loaded it into the extensions folder, rebooted as well for good measure but im not really seeing anything different.
Hm, either you didn't install it properly; or you're overlooking it. It re-uses the same icons, descriptions and adds a "License" class as well.
The fields and links are quite different. It's just an example of course.
You can always customize the datamodel to suit your own needs :)
Last edit: Jeffrey Bostoen 2023-10-21
So I didn't install it right. New to Linux (using ubuntu), working now at a non profit so working on learning Linux to cut down on windows incensing where i can.
I installed it to the extension folder but the added step to take ownership and give write permission to the config file in the production folder was missed and then of course re running the setup which does the install and then fixes the permissions on the folder were missed.
Now that that is corrected I see the changes.