Open Issues with SDP 7.0.0 build 7017
Support, please respond.
The following list of issues are open with SDP 7.0.0 build 7017. Some of these issues I have been reporting since build 7009. I have not received specific feedback on any of these issues.
Adventnet, please comment and resolve:
1.) There is no way to delete an asset connection relationship other than replacing it. This greatly limits the usefulness of this feature. For example, a relationship between a computer and a printer cannot be deleted, only replaced with a new relationship.
2.) When an asset is associated to a requester, a new request for that requester will always default to having an asset. This behavior should be controllable.
3.) The terms asset and resource are used inconsistently. The additional fields function on the Admin tab uses the term Assets. The Asset tab in the system refers to the same records as Resources. There are many locations where either term is used to mean the same thing. Please make the system consistent in its use of terminology.
4.) The GUI report builder functions do not allow you to access the additional fields you have defined in the admin tab for asset/resource records. This must be performed in the query builder.
5.) The query data model does not list the names of the fields in the tables where the user defined fields are stored for any type of record. This is not limited to assets/resources/workstations.
6.) Has the Active Directory import function been repaired in this build?
7.) When a new request is submitted via e-mail, the system will automatically add an asset for the user submitting the request. This should not occur or should be configurable.
Thanks!
Kirk.
The following list of issues are open with SDP 7.0.0 build 7017. Some of these issues I have been reporting since build 7009. I have not received specific feedback on any of these issues.
Adventnet, please comment and resolve:
1.) There is no way to delete an asset connection relationship other than replacing it. This greatly limits the usefulness of this feature. For example, a relationship between a computer and a printer cannot be deleted, only replaced with a new relationship.
2.) When an asset is associated to a requester, a new request for that requester will always default to having an asset. This behavior should be controllable.
3.) The terms asset and resource are used inconsistently. The additional fields function on the Admin tab uses the term Assets. The Asset tab in the system refers to the same records as Resources. There are many locations where either term is used to mean the same thing. Please make the system consistent in its use of terminology.
4.) The GUI report builder functions do not allow you to access the additional fields you have defined in the admin tab for asset/resource records. This must be performed in the query builder.
5.) The query data model does not list the names of the fields in the tables where the user defined fields are stored for any type of record. This is not limited to assets/resources/workstations.
6.) Has the Active Directory import function been repaired in this build?
7.) When a new request is submitted via e-mail, the system will automatically add an asset for the user submitting the request. This should not occur or should be configurable.
Thanks!
Kirk.
Topic Participants
kpatten
ServiceDesk Plus
Bradley Munsen
greeneje
Andy.Fox