Template:Data Integrity Check: Difference between revisions

Revision as of 08:47, 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.

This template defines the table "DataIntegrityChecks". View table.

@@ Line 20: / Line 20: @@
 |Firmness=text
 |L_Problem=boolean
+|Backlogged=boolean
 }}
@@ Line 50: / Line 51: @@
 |-
 | style="background:silver; color:arsenic" align="right"| '''Uses [[L Problem table]]: '''
-| {{{DIC_LProblem|not entered}}}
+| {{#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: '''
@@ Line 57: / Line 58: @@
 | style="background:silver; color:arsenic" align="right"| '''Implementation Date: '''
 | {{{DIC_implementation_date |not entered}}}
+|-
+| style="background:silver; color:arsenic" align="right"| '''Backlogged: '''
+| {{{DIC_backlogged|true}}} <!-- default to true if not entered -->
 |} </div> <includeonly><div style="display: none;">
@@ Line 71: / Line 75: @@
 |Firmness={{{DIC_firmness |not entered}}}
 |L_Problem={{{DIC_LProblem|false}}}
+|Backlogged={{{DIC_backlogged|true}}}
 }}