I am currently evaluating SF as a framework for our migration to .NET
I have played extensively with several other products over the past 6 months or so, and I was suprised when I did stumble onto SF that I hadn't come across it before.
At first glance, it seems to me it should at least be holding as prominent a position as other tools such as IB,ES...

Anyway, I want to evaluate SF's capacity to adapt to some less than typical scenario's and I'd appreciate a heads-up from anyone who's willing.

Lets suppose I have a BO called IncidentBO, and I have it hooked up to an SF Maintenance Form.
I want to allow the user to Add a New or Edit an exisiting Incident.

However, when the user saves an Edited Incident, I want to leave the original row untouched and add a new row, which has the new details.
I already have a PK structure that supports this.
What I would like an insight into is where to hook the logic I would use and how to turn the updated BO into a new BO instance so it gets inserted.

I think the answer to this will also give me an insight into some other questions I have.

Cheers

Geoff