1 of 1 people found this helpful
There certainly is a way to do this.
You need to have an "edit mode" in your solution. This mode is a purposefully-chosen mode by the user. It opens up the record so that it is locked from others trying to edit it, and it allows the user to commit or revert the changes made through a dialog box.
Is this what you're looking for? We can get specific if this is the right path.
Not exactly but that will be great for my other question! Is it possible to lock records to prevent accidental changes?
I would like an "edit mode" button to lock an unlock record.
As for this question, we are looking to receive an confirmation window to any changes made to an existing information while in "edit mode".
There is a new function that allows you to get the modified fields.:
It can be used during an EditMode to show which changes have been made. You can then display this list or store it somewhere.
This afternoon, if others haven't answered this for you, I'll put together a little demo file that shows this in action.
The client wants to be able to ask for a confirmation before committing the record so that Get function will be too far in the process.
I think my client will be happy with that solution, thanks!
We have a very intelligent but over-enthusiastic volunteer with quick fingers on her Surface tablet. I have set up her own WebDirect layouts and have the edit confirmation required, but the default it Confirm, so she is just one more click away from havoc.
I'd like to also have a conscious EDIT mode required before she changes anything, followed by the layout-specific confirmation. So as I understand it, you had more suggestions, Jeremy, about setting up an Edit mode.
I'd envisioned a button to start the Edit process, or perhaps if a change was made, an immediate dialog asking whether a record edit was intended.
An Edit mode requires the user to specifically press an "Edit" button and be taken to another layout (or to a popover) where the fields are there and open for data entry. During this "Edit" script, the record is opened.
This locks the record, allowing only this person to use it.
By the way, you'd want to check to see if the record can be opened; if not, you'd have to build in logic to say "Sorry, this record is being used by someone else" and close the layout or popover. The link above talks about this.
On this layout are the fields that the user can type into. All the while the record is opened. Any changes that are entered into fields are NOT saved to the database until the record is explicitly committed thru a button called "Commit" (or whatever you want) using the Commit Records script step. The changes can be reverted by a "Cancel" button that uses the Revert Record/Request script step. This discards any changes that were made.
That's how I'd approach it.
Another note: Actions such as going to another record or layout while editing a record will commit the record. You can prevent this by making the window/popover modal, disallowing a user to do something else until they specifically hit one of your buttons.
I'll see if I have a demo on this laying around my computer.