Hi,
I would like to get a steer on what a best practice solution would look like for the following use case. I am looking to minimise technical debt where possible and provide a solution which meets good architectural design principles.
When raising a change against CIs, a quality gate is needed which prevents the user from raising changes where any of the affected CIs is missing data defined in the CMDB Health recommended fields for that class. If CI information is missing on any of the selected CIs, then the user should be prompted to update the CI(s) by means of a link which appears in a pop-up box. If they own the CI, they should be able to populate the missing data without too much delay. If they don't own the CI, a notification should be sent to the CI owner asking them to populate the data as someone is trying to raise a change against it.
Above is a high level summary. I'm looking for ideas or suggestions as to how this can be best implemented. A few reasons I've posted in here are as follows : I'm not too sure whether a flag would be appropriate on the change or individual CIs, and how that would be maintained ie. through a daily job. We would need the CI to be usable on a change immediately after the data has been corrected, so a flag on the change may be better and then lookup each CI. I'm wondering how much load time it would add to a change if this check was added to lookup each CI and check against its list of recommended fields in CMDB health. Hope the logic makes sense. Would welcome any suggestions.
Thanks.
