If your users can be more specific (perhaps giving you a SMALL list of fields from which to trigger a Save - and not just "Everything"), you can create a small customization to do an otrans.update() when the focus() status of these key fields changes.
Personally, I don't recommended it. I'd instead I'd only invoke a background save (otrans.update()) if the values in any of these key fields have changed.
Rob Brown.
Personally, I don't recommended it. I'd instead I'd only invoke a background save (otrans.update()) if the values in any of these key fields have changed.
Rob Brown.
--- On Mon, 7/21/08, bpbuechler <pbuechler@...> wrote:
From: bpbuechler <pbuechler@...>
Subject: [Vantage] Job Entry-Job Details-Operations-Details
To: vantage@yahoogroups.com
Date: Monday, July 21, 2008, 9:41 AM
My Job Engineers are telling me that sometime back on 8.0 they would
tab off a field (specifically Job Entry-Job Details-Operations-
Details tab) and Vantage would Auto-Save changes. Now, they are
tabbing off fields and it does not auto-save and it frustrates them
because they never know if the changes made are saved.
I came up with two recommendations:
1. Click Save - which in most cases it does not give you any
indication it has saved (bottom left of screen = READY)
2. Click on the tree (anything different than the current
operation) - which does give indication it is SAVING DATA...
Obviously they do not like either option.
Two questions for the group:
1. Did Vantage used to auto-save when tabbing from field to field in
Job Entry-Job Details-Operations- Details?
2. Can I customize to Auto-Save when you tab off of certain fields
or sections?
TIA
Patty Buechler