Query check tmp generate allowed: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m not retired after all, it's used for more than overstay
m no longer used for overstay
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{Data Integrity Check
{{Data Integrity Check
|DIC_summary=check that [[:Category:Project|tmp]] project/item combo exists for this location in [[Overstay]]
|DIC_summary=check that [[:Category:Project|tmp]] project/item combo exists for this location for a project
|DIC_related_concepts=Overstay; Overstay Predictor Project
|DIC_related_concepts=Overstay; Overstay Predictor Project
|DIC_firmness=hard check
|DIC_firmness=hard check
Line 14: Line 14:
{{Related Articles}}
{{Related Articles}}


[[Category:OverstayProject]]
[[Category:Tmp check‎‎‎]]
[[Category:Tmp check‎‎‎]]

Latest revision as of 10:40, 9 April 2020

Data Integrity Checks
Summary: check that tmp project/item combo exists for this location for a project
Related: Overstay, Overstay Predictor Project
Firmness: hard check
Timing: always
App: CCMDB.accdb
Coding: query check tmp generate allowed, Sub GenerUpdate_tmp_entry
Uses L Problem table: not relevant for this app
Status: implemented
Implementation Date: date change was rolled out / first applied
Backlogged: No
  • Cargo


  • SMW


  • Categories:  
  • form:

In spite of the name, this function is not a check funtion. It is called by Sub GenerUpdate_tmp_entry which is used by the overstay project to generate colour entries in tmp.

Related articles

Related articles: