SDP 7.0.0 Build 7014 open issues
The following list of issues are open with SDP 7.0.0 build 7014. 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.
2.) When updating the requester in a request, if you leave the asset unchanged the update button will not function. The asset should become blank when a new requester is selected.
3.) 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.
4.) AD scheduled import does not work. It updates task_input indicating that it finished in 1 second and does not update user records.
5.) When you update the schedule frequency for importing from AD and hit the 'Save Schedule' button, the system updates the SCHEDULED_TIME in TASK_INPUT for the SCHEDULE_ID matching ADSynchronizationSchedule in SCHEDULE. When you press the 'Save Schedule' button and the SCHEDULED_TIME becomes NOW+FREQUENCY. So if you set the frequency to one (1), you would see that the schedule should fire 24 hours from when you updated the schedule. Further, this means that if you keep updating the schedule, the event will never fire as it will always be pushed further into the future. I would propose that this behavior change to be EXECUTION_TIME_FINISHED+FREQUENCY. This would produce a much more logical outcome.
6.) 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.
7.) The additional fields defined against the asset/resource records will not display correctly for a record that had a type of desktop or laptop that was imported from SDP 6. The data is still present in the system, but is unavailable in most of the user interface.
8.) 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.
9.) The query data model does not list the names of the tables where the user defined fields are stored for any type of record. This is not limited to assets/resources/workstations.
10.) The Warranty Expiry field for the Resource table is not accessible through the user interface. You must use a query to pull this from the database. It should be available, or the data should be migrated to an available field. The current migration procedure from 6 to 7 causes this field to effectively become invisible.
Adventnet, please comment and resolve:
1.) There is no way to delete an asset connection relationship.
2.) When updating the requester in a request, if you leave the asset unchanged the update button will not function. The asset should become blank when a new requester is selected.
3.) 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.
4.) AD scheduled import does not work. It updates task_input indicating that it finished in 1 second and does not update user records.
5.) When you update the schedule frequency for importing from AD and hit the 'Save Schedule' button, the system updates the SCHEDULED_TIME in TASK_INPUT for the SCHEDULE_ID matching ADSynchronizationSchedule in SCHEDULE. When you press the 'Save Schedule' button and the SCHEDULED_TIME becomes NOW+FREQUENCY. So if you set the frequency to one (1), you would see that the schedule should fire 24 hours from when you updated the schedule. Further, this means that if you keep updating the schedule, the event will never fire as it will always be pushed further into the future. I would propose that this behavior change to be EXECUTION_TIME_FINISHED+FREQUENCY. This would produce a much more logical outcome.
6.) 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.
7.) The additional fields defined against the asset/resource records will not display correctly for a record that had a type of desktop or laptop that was imported from SDP 6. The data is still present in the system, but is unavailable in most of the user interface.
8.) 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.
9.) The query data model does not list the names of the tables where the user defined fields are stored for any type of record. This is not limited to assets/resources/workstations.
10.) The Warranty Expiry field for the Resource table is not accessible through the user interface. You must use a query to pull this from the database. It should be available, or the data should be migrated to an available field. The current migration procedure from 6 to 7 causes this field to effectively become invisible.