Custom action when edit screen (form) is cancelled (ON CANCEL)

[rayo]

currently we can add a custom action ON SUBMIT of Edit Form.

would be great if we could also add a custom action ON CANCEL of the form.

can be very useful to restore default conditions if form was triggered from a button with other set columns changes made.
ex. in my apps, edit screens are sometimes triggered from buttons with visibility Boolean conditions to view certain edit parts depending on where or who is accessing the edit screen from.
(A store can edit an item details. A driver can edit the shipping details of that item) etc…

it can also be useful to track time spent on a form by a user.

[Uzo]

that’s why its better to always create your own form… so you have a full control

[rayo]

how do you usually create your own forms? the new screen action doesn’t really create a form feeling, no cancel / submit … etc.

[kyleheney]

How do I create a custom form?

I’m just dropping this here so I have something to refer people to when they ask. This is a simple concept app (copyable), that demonstrates the following techniques: Building custom forms for adding and editing list items (as an alternative to the native forms provided by Glide) Preventing duplicate new entries using User Specific Columns and Relations Enforcing mandatory input items The use of visibility conditions and user specific booleans to control user flow There is nothing particula…

[escott]

Just to clarify, because I’m just getting started with Glide: when viewing a list of items on a form, I can choose the action “Show Edit Screen” to edit the selected item. But your advice is never to use that option, but rather to create a form and jump over to that, is that right?

I have a different problem but it might have the same solution. Thanks.

[Uzo]

to be clear, I use the words “is better” not “never”
the idea of creating custom forms or editing screens applies to situations when you need all App functionalities when entering or editing data… for instance: if you need to compute entered data before saving, to check or show some restrictions… also you can use relations to entered data, and my favorite… you can apply CSS codes.
to create a custom form or edit screen, have an action in button, image, or list that will open a new screen… now you add all the entry elements that you need, for each entry, create a USC column to collect that data…
when the user is done editing/entering simply create the compound action to add a new row (for form), or set columns (for editing) then, clear USC columns (optional if you don’t want users to have their data there when they come back again), show notification, and go back…

[escott]

Got it. Thanks! That’s useful.