# No Actions for Form Elements **URL:** \ **Category:** Ask for Help\ **Created:** [April 8, 2023, 1:27pm UTC](https://community.glideapps.com/t/no-actions-for-form-elements/60289 "2023-04-08T13:27:16Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![gannonatwork](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gannonatwork/32/91717_2.png) [@gannonatwork](https://community.glideapps.com/u/gannonatwork)\ **Post date:** [April 8, 2023, 1:27pm UTC](https://community.glideapps.com/t/no-actions-for-form-elements/60289/1 "2023-04-08T13:27:16Z")
Is there a reason why you can’t add actions to individual Form elements? Use case is I’m trying to create a decision-tree app that will route/navigate users through the app based on the answers to each question. For example, each question will be followed by a Yes and No checkbox and I need to add actions to each checkbox so I can route the users appropriately based on their answer. For example, user chooses “Yes” which would trigger a “Go to tab” action to route the user to the correct screen — choosing “No” would trigger a separate “Go to tab” action that takes user to a different page. ![Screenshot 2023-04-08 at 9.23.43 AM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/1/e/1e0288cf6682340bb448c70699bb2b2a1883c57d.jpeg) ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [April 9, 2023, 2:22am UTC](https://community.glideapps.com/t/no-actions-for-form-elements/60289/2 "2023-04-09T02:22:37Z")
I would not say it’s “no actions for form elements”, it’s “no actions for the checkbox element”. Regardless of where you add the checkbox, it would not allow you to add any actions. ---
**Author:** ![gannonatwork](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gannonatwork/32/91717_2.png) [@gannonatwork](https://community.glideapps.com/u/gannonatwork)\ **Post date:** [April 10, 2023, 10:18pm UTC](https://community.glideapps.com/t/no-actions-for-form-elements/60289/3 "2023-04-10T22:18:18Z")
Hi, @ThinhDinh. I appreciate the input. For me, none of the Form Elements shown below allow actions to be added; the only place actions can be added in Forms is to a Form Container. That’s what you’re seeing correct? Thx ![Screenshot 2023-04-10 at 6.13.59 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/f/d/fd5b5d1659df812a733b0c1a472cd13732622308.png) ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [April 10, 2023, 11:47pm UTC](https://community.glideapps.com/t/no-actions-for-form-elements/60289/4 "2023-04-10T23:47:21Z")
Yes that’s correct. I should have said “no entry components” to be clearer. My point is wherever you add them, you wouldn’t be able to add actions to it, not just forms. And vice versa, say for a collection that allows you to add actions anywhere, you should be able to add an action to it in a form environment. ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [April 10, 2023, 11:48pm UTC](https://community.glideapps.com/t/no-actions-for-form-elements/60289/5 "2023-04-10T23:48:20Z")
And yeah, it would be dope if we can add actions. I think the most requested one is for the choice component (say you choose a value and then we can do something more). ---
**Author:** ![gannonatwork](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gannonatwork/32/91717_2.png) [@gannonatwork](https://community.glideapps.com/u/gannonatwork)\ **Post date:** [April 11, 2023, 10:37am UTC](https://community.glideapps.com/t/no-actions-for-form-elements/60289/6 "2023-04-11T10:37:38Z")
Yeah, that would be great. I found we can add actions to choice component values inside a Form container but, of course, then that also add’s a Submit button to the layout. Weird that actions can be added to choice components inside a Form container but not the standard Container component. ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [April 11, 2023, 12:04pm UTC](https://community.glideapps.com/t/no-actions-for-form-elements/60289/7 "2023-04-11T12:04:31Z")
Umm… where do you see that you can add an action to a choice component in a form container??? ---
**Author:** ![gannonatwork](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gannonatwork/32/91717_2.png) [@gannonatwork](https://community.glideapps.com/u/gannonatwork)\ **Post date:** [April 11, 2023, 2:26pm UTC](https://community.glideapps.com/t/no-actions-for-form-elements/60289/8 "2023-04-11T14:26:12Z")
Hi, Jeff. While trying to figure out a workaround for my use case, I found that if I use a Choice component inside a Form container I can target the Choice component by customizing the after/submit action to send users to different tabs in the app based on the choice they made, as needed by my decision-tree app. But, like I mentioned above, it won’t solve the issue because I can’t change the default Form container’s button to say “Next” or something similar. :\ ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [April 11, 2023, 2:42pm UTC](https://community.glideapps.com/t/no-actions-for-form-elements/60289/9 "2023-04-11T14:42:28Z")
OK, so it’s the On Submit action on the form itself, not the choice component inside the form. So changing the choice will not trigger an action, but the submit button will. Just making sure I wasn’t missing some new feature. You wouldn’t necessarily have to use a form container. A choice component and a button component could essentially do the same thing. Let the user make their choice, then set a custom action on the button to do something based on that choice. The choice component could fill a user specific column and the button action would look at the value in that user specific column to determine what it should do. Plus you can name the button whatever you want and you don’t have to worry about it adding unnecessary rows every time you click on it. ---
**Author:** ![gannonatwork](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gannonatwork/32/91717_2.png) [@gannonatwork](https://community.glideapps.com/u/gannonatwork)\ **Post date:** [April 12, 2023, 9:50pm UTC](https://community.glideapps.com/t/no-actions-for-form-elements/60289/10 "2023-04-12T21:50:44Z")
Hi, Jeff. I appreciate the recommendation. I did build out a version doing that — using custom actions on each button (Yes/No) to navigate users based on their answer. However, what I’m trying to solve is if there is a discrete way to save progress for users without having them sign in. Most online form builders come with built-in functionality to enabled temporary browser caching — users can start a form, close the browser, return to the form using the same browser and pick up where they left off as long as they haven’t cleared their cache and it’s been less than 15 days. That’s why I experimented with the form route but Glide doesn’t yet allow for custom text on the submit action button and, from what I’ve been told, doesn’t have the temp browser cache functionality. If you have any other suggestions to accomplish my use case, I’m all ears and would appreciate any insight you may have. TIA if you haven’t anything to suggest and, as always, I appreciate your time. Thx!