SDP 7.0.0 Build 7018 Open Issues
The following list of issues are open with SDP 7.0.0 build 7018. Some of these issues I have been reporting since build 7009. Are there "SDP" fix numbers associated with any of these problems that I may use to track against the patch readme files?
NEWLY REPORTED (but not new in 7018):
1.) When a request is split from a parent request that is past due with respect to the SLA's defined, the priority of the newly-split request is not re-evaluated for SLA purposes causing reporting to incorrectly show this request as not meeting SLA when it may actually not be past due.
2.) When a request is submitted via e-mail and the requester is subsequently changed, assets may not be changed using the pop-up screen view, only the drop down list view will work.
3.) In the edit request screen, the system will not save changes to the asset associated with the request.
PREVIOUSLY REPORTED:
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 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.
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.) Active Directory scheduled import fails when non-existent OU is encountered.
Thanks!
Kirk.
NEWLY REPORTED (but not new in 7018):
1.) When a request is split from a parent request that is past due with respect to the SLA's defined, the priority of the newly-split request is not re-evaluated for SLA purposes causing reporting to incorrectly show this request as not meeting SLA when it may actually not be past due.
2.) When a request is submitted via e-mail and the requester is subsequently changed, assets may not be changed using the pop-up screen view, only the drop down list view will work.
3.) In the edit request screen, the system will not save changes to the asset associated with the request.
PREVIOUSLY REPORTED:
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 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.
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.) Active Directory scheduled import fails when non-existent OU is encountered.
Thanks!
Kirk.