🆕 Actions! ⚡⚡⚡

I think it’s the way it is set up to work, which enables you to have multiple layouts for the same sheet.

This happened to me last satuday requiring me to rebuild 2 sets of 6 for a total of 12 windows and over 60 actions to rebuild.

Re-Using NAMED Actions

We can name custom action workflows, but they are not available afterwards from what I can tell. This means I have to recreate the same action workflows for every screen step by step.

IF we’re naming them, why not make them available as options on the Action Selection dropdown?

I’m sure this has been said elsewhere - it’s the #1 thing to add to this to make them more productive.

6 Likes

+1 :+1: This would be great.

So rather than have a button (for example) to trigger an action have the action trigger based upon the content of a cell or cells, especially those that are dynamic.

Example - Delete record after a certain number of days.

4 Likes

Exactly. Glide needs time based triggers.

4 Likes

Been working on a new concept app and this would be so helpful to achieve a seamless user experience.

Now I have to get the user to a) actually remember to go into the app (unlikely given they are “so busy”) and b) to then ‘do’ something to trigger the action.

I’m sure this will be on the glide roadmap for the future consideration :crossed_fingers:

Time based or cell content based so it becomes dynamic.

2 Likes

I guess the thing with time based triggers is that it would need to be a back end thing, yeah?
I mean… I’m not sure I can picture how a time-based trigger would work on a user device.

Ya, I guess it would need to leverage the system clock?

If you guys would like I can write you out a time based trigger. I use these currently in my apps. I can write a generic one that you guys can modify to fit your needs.

2 Likes

Rose, I built a script that does delete records after a certain timespan. Its in the Scripts, scripts, scripts! forum page I made a while back.

1 Like

Rose, when I asked a little over a month ago about this feature I was told by David that it was not in the pipeline.

1 Like

You mean like this?

But the point here is about having the ability to configure eventstate or time driven actions in Glide, and be able to avoid Apps Script triggers.

2 Likes

Thinking more about the types of actions you’d want to fire with time/eventstate based triggers. For example…

  • deleting and/or updating rows at a specific time of day, or after a specific period of time: rather than have this action fire on every individual user device, you’d want it to fire once on the back end, and then allow the change to sync to all users.
  • time and/or eventstate based notifications: again, seems to me something that should be initiated from the back end

Since we’re talking about it:

2 Likes

I know, but David said they don’t even have that as a thought for Glide so we are stuck with scripts. But we can make them more user friendly for the community through this process.

1 Like

Things to know about multi actions.

  1. The sequence matters
    Do this, then this, then that. matters alot.
    A wrong sequence may contradict or conflict or not work

  2. Although Multi actions are sequential, they execute so fast that they may not operate like they are sequential. So you have to configure delays in your sequence so the system wait for a process to end before it starts another. This is especially true of you are moving data from the google table to the glide table.

  3. Multiaction may convert your data
    When you add a type using the action the format of the data is not conveyef. So your numbers my transfer as text. So check your destination column for correct formatting.

  4. Filters are essential in every multi action
    Filters answers various conditions example
    If user is_ then run this dequence of actions. if not then show message_

If this row has column a = yes, then run. if not run sequence b.

  1. Zapier will turn off your sequence.
    If you edit or change zapier it will turn off your zapier action in glidr. Go back in your action and reselect the respective zapier after zap edits.

  2. Always use multiaction
    Even though you can use single action in glide it’s better to always use the multi action because Later you will realise you need to add 1 more action and prevents you from doing it all over again.

  3. Use multiactions to transfer large data from google sheets to glide.

For most of us who have used glide before there was the glide table. we have a lot of data inside Google tables. You can use the multi action to easily move a row from Google sheets and added in a glide table with the same columns quickly. You can move 1 row per second roughly. This will help your app operate faster with less dependence from Google sheets.

  1. Is multi actions with conditional column templates to expand buttons.

1 button could do 10 different things for 10 different people you just have to use filtering.

  1. Duplicate your multis
    Use the duplicate feature to save time and build complexity especially when you want something just slightly different.

  2. Use multi action to track users
    A button doesn’t have to do what it say it does. Sometimes the goal is to get users to push the button.

Example.
Creating a “Save” button could trigger an email to you, pop up a “saved” msg and go back. even tho the data was already saved.

Or

Creating a dual button that has log in and log out. will update a column to show current date and time. Log in will erase log out time and put now" in the log in column. Log out will erase log in time and put now in log out column. Then you can use visibility to give log in/out effect. So you see who’s logged in your app.

The biggest thing to remember is the timing of all the execution. Sometimes I have to add non related actions in order to use up the time needed to wait for another action to complete in order to make the needed action run effectively. Would be great for glides action set to have a delay function that we can wait for an action to execute. Especially that actions are sometimes interdependent of each other

7 Likes

Yes there must be a glitch in the condition configurations using “less then”… It assumes that it is a visibility condition for the button.

Hola @AjBruce,

Based on what you said. It seems that you have only on condition.

You need to have something like: if counter is less than do this, else show notification.

That way the button will always visible.

I hope this makes sense.

THIS! I do this now but only after having to rebuild and learning this lesson. Great post and tips @Lighted_Candle!

2 Likes

Agreed! I almost always use multi step actions now even if just a single action is needed because you never know when you might want to add onto it …tprevents the need to re-create the entire action. Especially when link to screens and forms are involved.

3 Likes