CiviCRM Community Forums (archive)

I dont think there is any easy way of doing this

one potential solution if you are using drupal is:

a. use webform + custom code (for setting defaults / validation / check civi db etc?) to collect the data and store it in webform fields

b. use webform + webform_civicrm + custom code for the approval and store in civi

the other option is to introduce the concept of "is_approved" but that might require quite a few changes across the code base (similar to is_deleted) and it works only across contact creation not contact updates

alternatively you can use logging to "roll back" changes if they are not approved

lobo

A possible solution that I have come up with is to:

Add an additional column to log_tables with an integer value to indicate the tuple's version. Unfortunately since the record would be in the log_table, the data in actual database could be incorrect until it is reviewed.

0 - Previous accepted value
1 - Current accepted value
2 - Pending Review
3 - Rejected

An custom report could show all pending changes. The user would be able to select a record and determine if the change was valid. If not, the previous version is copied and in both cases, the integer value is adjusted.

I think this may be the easiest way to implement feature. Generally the data is not accessed or used frequently, so minimal up keep would be required. There are only certain times during the year in which the database undergoes heavy use and as such, would be monitored more frequently.

I thought about implementing this type of feature to the main database, but figured it would be much more of an effort due to:
   Any update would have to be treated as an insert.
   Makes log tables redundant.
   Could be issues with primary/foreign keys.
   WHERE clauses would have to distinguish between current and previous versions when displaying data.