Cross Check Engine: Difference between revisions

Line 34:

=== ~~other~~ thoughts ===

=== Other thoughts ===

* Wiki pages contain the info; drawing from there is too slow, though

* Would it be best to store the query as text rather than as query? It would facilitate dumping the actual query to the wiki, if we wanted to do that. It would also facilitate text manipulation of the query... but harder to work with since one can't just use the query builder. And yet, easier to work with since one can actually annotate the query with comments.

* 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.

* 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?

@@ Line 34: / Line 34: @@
-=== other thoughts ===
+=== Other thoughts ===
 * Wiki pages contain the info; drawing from there is too slow, though
 * Would it be best to store the query as text rather than as query? It would facilitate dumping the actual query to the wiki, if we wanted to do that. It would also facilitate text manipulation of the query... but harder to work with since one can't just use the query builder. And yet, easier to work with since one can actually annotate the query with comments.
-* 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.
+* 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?