Cross Check Engine: Difference between revisions
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
This are just some notes re how I might re-write how [[CCMDB.accdb]] runs the cross checks. | This are just some notes re how I might re-write how [[CCMDB.accdb]] runs the cross checks. See also [[Problems related to event timing of data consistency checks]] | ||
=== Definition/Data structure === | === Definition/Data structure === | ||
| Line 40: | Line 40: | ||
* Is complete vs incomplete the right way to think of this? A field may not be mandatory to enter early at all, but once it's triggered by a field edit, shouldn't it be correct? I suppose it might not be if a check looks at two fields... but that is also a different issue that would always crop up when checking based on fields. And it would mean a field triggered check doesn't even make sense for anything other than incomplete fields? So maybe there needs to be a "profile closing" trigger that checks incomplete records, and no field trigger at all? | * Is complete vs incomplete the right way to think of this? A field may not be mandatory to enter early at all, but once it's triggered by a field edit, shouldn't it be correct? I suppose it might not be if a check looks at two fields... but that is also a different issue that would always crop up when checking based on fields. And it would mean a field triggered check doesn't even make sense for anything other than incomplete fields? So maybe there needs to be a "profile closing" trigger that checks incomplete records, and no field trigger at all? | ||
{{Todo | |||
| who = Tina | |||
| todo_added = 2022-04-27 | |||
| todo_action = 2022-04-27 | |||
| question = _dev_CCMDB | |||
* implement better cross-check triggering }} | |||