> I have some Claims that need to be entered, but when they are "closed"
> it saves the data from other related tables into the Claim (this could
> get messy), so that if the Customer, Registration, or Dealer information
> is changed at a later date it will remain the same as when the Claim was
> closed.
Michael,

I completely understand your dilemma. I spent quite a bit of time on a 
claims application myself. I can tell you that your statement, "This 
could get messy." is certainly true. Unfortunately, I don't know any way 
around it not being "messy." I don't know of any plugins or such that 
would help here, but maybe there are some.

The approach I took was to treat models related to the claim as 
"templates" for filling in the claim records. In my case this system was 
for the trucking industry. So I had to deal with information about truck 
drivers, claimants, insurance companies, etc.

My system would capture a "snapshot" of a driver (for example) and copy 
that data to a separate table that was then related to the claim. Then I 
provided a way for the user to update the driver's data in the claim to 
the latest version in the original driver record, but only if the claim 
was open. Once closed the update feature was no longer available.

I realize this is not ideal, but the alternative wasn't much better. I 
suppose I could have done the update automatically on save depending on 
the state of the claim. But, I chose instead to allow the user to update 
at their own discretion.

In my case some of the data needed to be captured (and frozen) based on 
the date of loss. We needed to know the driver attached to an order on 
the date of loss. So even if the order was assigned a new driver we 
still needed to capture the original driver's information that was 
involved in the claim. Which meant that is data had to be frozen when 
the claim was created, not when it was finally closed.

-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to