Hello apologies if this has been covered but I want to look ahead to what the collection of tools will look like for appsheets logic. How will the current actions/buttons be rolled into the Automation section? Or will they somehow remain separate?
Thank you
It seems that the new Automation panel is essentially a re-work of the workflow/report panels.
Iโve noticed that any processes I create are enacted like a workflow would be;
Not like a button: where when I press it, the change is seen immediately. It seems that if you want THAT sort of behavior, youโre still gonna be doing everything with actions.
Ok cool good to know, very exciting stuff all around!
It would be nice to hear from someone on the AppSheet team about this.
For instance: hereโs a process Iโve built into an app that I would love to be able to automate a different way.
Asking too much
@MultiTech_Visions Automation is a set of capabilities that are focussed on data (non UI) aspects and execute in background. For eg: a bot can be configured to either run on a schedule (eg: every day at Noon) or on a data change event (eg: a new row added to a sheet). A bot has an event (& some filtering condition) and a process (a sequence of steps).
Looked at your video, thanks for sharing that. Navigating to another view, performing an update etc makes total sense in an app centric use case. For automation centric use cases its all about reacting to data change events or run on a schedule so having an app view is not relevant.
If you do however want to execute a set of data change actions from an app view by clicking on a button you can do that with automation as follow:
When you go to the app view and click on the action (added in step 7), it should execute the process - which will execute all the data change actions in sequence.
Hope this helps.
Thatโs actually my exact use-case.
The users need the results of the data change immediately - they canโt wait for a sync to happen.
Iโm not trying to navigate away from where the user was looking, the button they pressed initiated a series of actions that created both child and grand-child records.
Iโve attempted something similar to what youโve described:
I believe what you are looking for is an โauto-refreshโ of the app view. There are no current plans for this feature.
So Actions as a concept will stay (we may move them from where they are placed today i.e โBehaviorโ section). Actions of type โData:โ are the only ones that are relevant as โTasksโ from a step in the process. Actions of type โExternalโ, the relevant ones are already available as โTasksโ that can be configured and accessed from a step in the process. I have attached screen shots to provide examples. Let me know if there are additional questions. @Ethan_U
Hope this helps
User | Count |
---|---|
27 | |
26 | |
22 | |
21 | |
21 |