User interaction when editing records

VincentS

I have a form on which I let the user edit a record. When the user clicks "save" I am validating one of the fields. When that validation is true, I want to ask the user a question whether or not he accepts this change. If the user clicks yes, the change should be accepted. If then user clicks no, the change should be rolled back.

Now I tried many things to achieve this, but without successful result. Also, the user guide states that a transaction is commited in case you want to display a question. So it almost seems that what I want is not possible.

Could anyone confirm that or am I missing something?

aware_support

This is a rather strange interface. But anyway, you will have to store a copy of the original record before you start the operation and restore it if the user does not accept the change (you are right, Aware IM will commit the transaction when the question is asked)

An alternative is to do everything on a client in a custom form or in a custom button - you will need to use some Javascript for this.

VincentS

I don't really see how this is strange. What I want to achieve is that the user is warned for a certain change he makes and if he wants to accept that change or not. Originally I wanted that if the user chooses no, he will remain in that form. But given my previous post, that's not possible.

And regarding creating a copy of the original record: I thought about this too. But what if the user just closes the browser? Because of the question there is nothing to rollback.

How would you solve something like this?

aware_support

If a user makes a change and clicks Save he does want to accept the change - there's no point asking him about this. What you really want to do, probably, is to provide the "undo" functionality - and for this you do need to make a copy of the record, so that if the user clicks on "Undo" the previous values are restored. It's up to you how you want to do this - you can maintain undo records of one or more levels.

pbrad

Hi,

Without reviewing the pros and cons of doing what you are trying to do. Have you considered using a separate attribute and then when you have verified that the contents of that attribute are accepted, copy the contents of that attribute over to your primary attribute? That way you have total control over when the attribute is updated and what it is updated to.

Cheers,
Pete