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 51: | Line 51: | ||
|- | |- | ||
| style="background:silver; color:arsenic" align="right"| '''Uses [[L Problem table]]: ''' | | style="background:silver; color:arsenic" align="right"| '''Uses [[L Problem table]]: ''' | ||
| {{#ifeq:DIC_app|Centralized data front end.accdb|{{{DIC_LProblem|not entered}}}|not relevant for this app}} | | {{#ifeq:{{{DIC_app}}}|Centralized data front end.accdb|{{{DIC_LProblem|not entered}}}|not relevant for this app}} | ||
|- | |- | ||
| style="background:silver; color:arsenic" align="right"| '''Status: ''' | | style="background:silver; color:arsenic" align="right"| '''Status: ''' | ||
Revision as of 15:15, 2021 July 15
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 relevant for this app |
| Status: | not entered |
| Implementation Date: | not entered |
| Backlogged: | true |