Template:Data Integrity Check: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 67: | Line 67: | ||
|App={{{DIC_app|not entered}}} | |App={{{DIC_app|not entered}}} | ||
|Timing= {{{DIC_timing |always}}} | |Timing= {{{DIC_timing |always}}} | ||
|ImplementationDate={{{DIC_implementation_date|}} | |ImplementationDate={{{DIC_implementation_date|}}} | ||
|Coding={{{DIC_coding |not entered}}} | |Coding={{{DIC_coding |not entered}}} | ||
|Firmness={{{DIC_firmness |not entered}}} | |Firmness={{{DIC_firmness |not entered}}} | ||
Revision as of 09:33, 2019 June 20
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.
| Data Integrity Checks | |
| Summary: | not entered |
| Related: | |
| Firmness: | not entered |
| Timing: | always |
| App: | not entered |
| Coding: | not entered |
| Uses L Problem table: | not entered |
| Status: | not entered |
| Implementation Date: | not entered |