Skip to content
← General

I suggest you ...

General

Categories

(thinking…)

Field change event

The Memento Database could have events for field change, allowing to script for another data (previous entries, another database, etc) and fill another editable field. This is not a calculated field but allowing to pre fill some field or fields of the new entry just to quickly fill in the form.
The event could be triggered to any field change and let the coder to handle what field triggered and what to do.

13 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Keiji shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Anonymous commented  ·   ·  Report

    I fully agree with Mr. Tony G. He has very clearly escribe where field level trigger will be useful. I will also find them useful for my work.

  • Bill Crews commented  ·   ·  Report

    Assuming I understand correctly what is proposed...

    It would be WAY helpful to simply state that what is desired/proposed is a scripted event, perhaps called something other than "trigger", that fires WITHIN THE PROCESSING OF AN ENTRY EDIT CARD PRIOR TO THE USER PRESSING THE CHECKMARK, SUCH AS WHEN FOCUS IS MOVED FROM A FIELD THAT HAS CHANGED SINCE FOCUS WENT TO THAT FIELD.

    Why not be clear about what is proposed?

    Yes, I agree with this proposal. Perhaps, along with it, each field that has changed since opening the card could have an Entry object property, perhaps called "changed", as well. It would help any fired script to detect multi-field changes. Also, assuming these intra-card events would have phases, then Losing focus, Saving entry, and Canceling entry might be reasonable phases for these events.

    If my assumption after reading the UserVoice proposal is incorrect, then please forgive me once again, and since reasonable people don't get it, please clarify the submitted proposal.

  • Tony G commented  ·   ·  Report

    Adding a vote to this. With all of the JavaScript enhancements, this seems like the next obvious step. As a developer I feel severely limited with only having page level events rather than being able to respond to field changes. Common usage:
    - Hide other fields based on the value of a changed field. Example: Disable or hide a prompt for something like "favorite programming language" if the user unchecked "are you a programmer".
    - Change a list to not include meat products if the user checks "Vegetarian". (Link a list to a
    - Google search for terms related to whatever is entered into a field.
    - Check to see if an entered date conflicts with another date.

    It should go without saying that we can do this with all GUI tools. It would be great to see Memento graduate to this next level.