Checkboxes for Certifications

[John Flack]

I'm not sure that this is specifically an ADF methodology question.  It may be just a general application development methodology question.

I am developing a form for people to fill out to request something (doesn't matter what).
One of the requirements for the form is that they must check some boxes to certify that they do or will meet some requirements to have their request fulfilled. Like:
"Do you certify that if you get this unnamed thing, you will use it only for the purposes intended, and not to commit a crime?"
And the user MUST check the box for "yes", or the request will not be submitted.

The question: Since the rest of the data from the form doesn't get into the database unless ALL the checkboxes are checked, should we even represent these checkboxes as fields in the database?  In ADF terms, should these all be transient attributes of the VO, with rules saying that they must all be set to TRUE on insert?  It just seems a bit wasteful to have a bunch of database columns where every record will have the same value (probably "Y").

[Darrel Chia]

I would likely build a validator that checks that the checkbox is enabled, and not build anything onto the VO itself at all.

--
--
You received this message because you are subscribed to the ADF Enterprise Methodology Group (http://groups.google.com/group/adf-methodology). To unsubscribe send email to adf-methodolo...@googlegroups.com
 
All content to the ADF EMG lies under the Creative Commons Attribution 3.0 Unported License (http://creativecommons.org/licenses/by/3.0/). Any content sourced must be attributed back to the ADF EMG with a link to the Google Group (http://groups.google.com/group/adf-methodology).

---
You received this message because you are subscribed to the Google Groups "ADF Enterprise Methodology Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to adf-methodolo...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Eric van Mourik]

It depends....

At first sight there seems to be no reason to persist the values. So if you rely on the logic of your (ADF) application, transient attributes (or even bean-based values) will do the job.

However, storing the values in the database (and implementing corresponding constraints) might increase the robustness and reusability of your solution. Other reasons to store the "senseless" values in the database might come from non-technical origins: governance, auditing, tracebility, etc.

But if none of these apply to your situation, keeping things "transient" might be okay.

Regards,

Eric

   

--

--
You received this message because you are subscribed to the ADF Enterprise Methodology Group (http://groups.google.com/group/adf-methodology). To unsubscribe send email to adf-methodolo...@googlegroups.com
 
All content to the ADF EMG lies under the Creative Commons Attribution 3.0 Unported License (http://creativecommons.org/licenses/by/3.0/). Any content sourced must be attributed back to the ADF EMG with a link to the Google Group (http://groups.google.com/group/adf-methodology).

---
You received this message because you are subscribed to the Google Groups "ADF Enterprise Methodology Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to adf-methodolo...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

______________________________________________________
Eric van Mourik  | Senior Consultant | Darwin IT-Professionals          
email: eric.va...@darwin-it.nl | telefoon: 06-27654726
Beeklaan 444 | 2562 BK Den Haag | KVK: 27283780
weblog: darwin-it.blogspot.com | website: www.darwin-it.nl

[Sten Vesterli]

Agree with Eric that you want to store this for compliance purposes. 

A record that stores Yes, Yes, Yes and a timestamp is easy to understand for any auditor, whereas if you don't store it, you'll have to explain the business logic that prevents it from being stored to the auditor.

[John Flack]

You are right - I'm adding the fields to the database.