Edit Data Integrity Check: Query s tmp project item consistent

Are you logged on?

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: CCMDB_legit.

Summary (what is the check, one-liner):
links to related pages:
Firmness (is this a warning only (soft check) or will it stop sending (hard check) - applicable only in CCMDB.accdb app):	None/unknown hard check soft check
Timing (does this query run for all records or only complete ones):	None/unknown complete always
Name of the function or query this is implemented as:	[[Function TmpChecker]], query ''s_tmp_project_item_consistent''
Implementation date:
Implementation Status:
L_Problem (are false positive special cases addressed in table L_Problems - applicable only in CFE):	None/unknown Yes No
App:
Backlogged (is this query cleaned up to date or backlogged? Applicable only in CFE):

Free text:

{{DISPLAYTITLE:query s_tmp_project_item_consistent}} approximate implementation date; this would have been implemented when we first went to the tmp coding we do now. == Log == * 2022-07-12 - added the "and active" criterion; then reverted the change == Related articles == {{Related Articles}} [[Category:Tmp Project Infrastructure]] [[Category:Tmp check]]

Explain your edit, if you think it needs explanation (e.g. "as discussed with ...", or "content moved to ...", or "duplicate content, see ..."):

This is a minor edit

Watch this page

Cancel