Difference between revisions of "FAQ:Status and CMDB Status not updating through Staging"
(Created page with "The reason that CI Status levels currently shouldn't be updated through the CMDB Staging area is that this would completely bypass any application functionality relating to th...") |
|||
| Line 1: | Line 1: | ||
| − | The reason that CI Status levels currently shouldn't be updated through the CMDB Staging area is that this would completely bypass any application functionality relating to the alteration of this field. Hence altering the status via an import could lead to unexpected data content and potentially the absence of notifications as a minimum. | + | The reason that CI Status levels currently shouldn't be updated through the CMDB Staging area is that this would completely bypass any application functionality relating to the alteration of this field. |
| + | Hence altering the status via an import could lead to unexpected data content and potentially the absence of notifications as a minimum. | ||
| − | If required this should be raised as an enhancement for your particular version. We would suggest that the enhancement would be to include functionality in the CMDB Staging area which would allow bulk update of the CI Status for selected CIs. The enhancement would then need to invoke the existing functionality in the application relating to this change in CI Status. This route would also cater for scenarios in which the CI Status is not imported so it should be of benefit to more implementations. | + | If required this should be raised as an enhancement for your particular version. We would suggest that the enhancement would be to include functionality in the CMDB Staging area which would allow bulk |
| + | update of the CI Status for selected CIs. The enhancement would then need to invoke the existing functionality in the application relating to this change in CI Status. This route would also cater for | ||
| + | scenarios in which the CI Status is not imported so it should be of benefit to more implementations. | ||
Revision as of 15:39, 22 June 2018
The reason that CI Status levels currently shouldn't be updated through the CMDB Staging area is that this would completely bypass any application functionality relating to the alteration of this field. Hence altering the status via an import could lead to unexpected data content and potentially the absence of notifications as a minimum.
If required this should be raised as an enhancement for your particular version. We would suggest that the enhancement would be to include functionality in the CMDB Staging area which would allow bulk update of the CI Status for selected CIs. The enhancement would then need to invoke the existing functionality in the application relating to this change in CI Status. This route would also cater for scenarios in which the CI Status is not imported so it should be of benefit to more implementations.