I’m trying to figure out how to trigger a workflow when adding a new row to a table, or when a value changes. I can’t find where I can select such a trigger.
Can someone direct me? Is that available in the maker plan?
Take a look at this:
If you don’t have to do any complicated flows, you can have an on-submit action when adding a new row to a table via a form.
When a value changes, depends on how it’s changed, if it’s through an action, you can add more steps to the custom action that triggers the change.
If not, can you describe how the value changes?
Perhaps I’m doing something non-Glide in my approach, but here is a summary of my current problem.
I have an INPUT FORM on a screen (that unrelatedly takes a good 5 to 8 seconds to load) that populates a table I called SELECT & GO and on submit displays the DETAIL SCREEN.
On the detail screen are two DISPLAY TABLE components that display data from from two derived glide tables that I use to create the displayed information. The derived tables use information from the last line of SELECT & GO (the submitted information) and data from a STATIC DATA TABLE which is 30 columns by 20500 rows. There are some relations for lookup. some single value columns, a few if-then-elses. I don’t think it’s that complicated, but perhaps my perspective isn’t right.
The issue is: The DETAIL SCREEN loads almost immediately. The DERIVED TABLES and DISPLAY TABLES take 5 to 10 seconds to refresh. For 5 to 10 seconds, the screen is showing the old/incorrect data.
I’m looking for a way to either eliminate the delay or use some clever gliding to either clear the tables so they don’t show the old data, or hide the tables until the refresh is completed or any other suggestion you gurus think might help.
thanks in advance
One of piece of information, perhaps it will help. The DETAIL SCREEN contains a button block that allows the user to change data in SELECT & GO.
When they change the values in SELECT & GO, the propagation to the DETAIL SCREEN TABLEs is immediate. I think this indicates that the calculation of the tables is not the issue. The delay only occurs on the initial display of the DETAIL SCREEN after selection SUBMIT.
Hope that helps.
How are you constructing those derived tables?