Template:Data Integrity Check: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) No edit summary |
Ttenbergen (talk | contribs) No edit summary |
||
| Line 79: | Line 79: | ||
|Coding={{{DIC_coding |not entered}}} | |Coding={{{DIC_coding |not entered}}} | ||
|Firmness={{{DIC_firmness |not entered}}} | |Firmness={{{DIC_firmness |not entered}}} | ||
| | |L_Problem={{#if:{{{DIC_LProblem|}}}|{{{DIC_LProblem}}}|false}} | ||
|L_Problem_TS={{{DIC_LProblem}}} | |L_Problem_TS={{{DIC_LProblem}}} | ||
|Backlogged={{{DIC_backlogged|true}}} | |Backlogged={{{DIC_backlogged|true}}} | ||
Latest revision as of 23:08, 22 July 2025
This template manages information related to Data Integrity Checks. the template call is usually managed by Form:Data Integrity Check.
To use:
{{Data Integrity Check}}
and then use form
- if ready to implement, the template should also put the check on the Requested Changes Page. Now there is a tricky thing! Means we actually need to template requested changes in the first place. And if we go there, should a requested change turn into a log entry? It all becomes really disjointed but also powerful.
Cargo declaration
This template defines the table "DataIntegrityChecks". View table.
actual template code
| Data Integrity Checks | |
| Summary: | not entered |
| Related: | |
| Firmness: | not entered |
| Timing: | always |
| App: | not entered |
| Coding: | not entered |
| Uses L Problem table: | not relevant for this app |
| Status: | not entered |
| Implementation Date: | not entered |
| Backlogged: | true |