Have Geek Brain

Saving partial data entry

Scenario: Users enter complex data (WPF frontend) and save the data with some OR-mapper in SQLServer. I am using OpenAccess from Telerik.

But now think about the following situation: one almost finished work on some use case, but now some information is missing. because the data he entered does not comply with all business rules (required fields may be empty), he cannot save his work.

But, unfortunately, he also cannot get the missing information. So what can he do. Discard all work, bad idea, just do nothing and wait, no good idea.

Now my idea has come up. It would be helpful if the user can "park" their unsolved problem and start working on some other use case. And after he has parked his work, he can shut down the system and try to solve it another day. (And by the way, it can continue working on another system)

But where to serialize? The business object is not serializable because it contains some identity information from the ORM. Introducing some intermediate objects explodes assignment operations. User interface?

Maybe someone knows an existing solution or had some good ideas.

0


a source to share


2 answers


use the status field to keep track of whether it meets all the rules or not. allow it to be saved regardless of the rules, but mark it as such. when valid, change the flag. just let other users see / work with valid items.



+1


a source


How about a Memento template? Take all the serializable data and put it in another class, then serialize and store it in the database. When needed again, deserialize to a memory class, then populate the original object.



0


a source






More articles:


All Articles