As of today, webhook automation API calls will start originating from a dynamic list of IP addresses. If you depend on the stability of the IP addresses for access control security, you can request static IP addresses by contacting AppSheet through your usual channels or through AppSheet Support.
Bug fixes
Item
Description
Bug
For the desktop UI (preview), clicking a pin in a Map inline view now behaves the same as in the mobile UI.
Rollout changes
Item
Description
Bug
For Desktop UI (preview), fixed inconsistent expression results in Desktop forms. Certain expressions were producing different results in Desktop mode, specifically those that involve searches (e.g. SELECT() or LOOKUP()) over the same table currently being edited in the form. With Desktop mode off, the pending changes in the unsaved form are not included in the result. With Desktop mode on, they were being included. After this change, they will again be omitted from the result.
New: Deployed to 100% of free users. Previous: Deployed to 75% of free users.
Update: As part of this rollout, there is a fix for INPUT() modal form not showing changed values. The value would appear to revert to its initial state after focus leaves the input. This issue has been fixed.
Preview announcements
Preview feature releases enable you to try out new app features that are not yet fully supported. See Product launch stages.
No new preview features were released today.
What’s currently available in Preview?
The following tables summarize the preview features that are currently available.
Item
Description
Feature
AppSheet databases (Preview)
The new AppSheet database feature is now in preview release. An AppSheet database is a first-party, native data source for organizing and managing data powering AppSheet apps. An AppSheet database provides an easy and efficient way to build data models for any AppSheet app without needing to use an external data source solution such as cloud-based spreadsheets or databases.
Navigation improvements in AppSheet app editor (Preview)
The app editor includes navigation improvements, currently in preview, to facilitate the configuration of specific features. For example, the new Settings section in the left navigation gathers together all app-wide settings and makes it more intuitive for all app creators to find these types of settings.
Additional usability improvements in AppSheet app editor (Preview)
The app editor includes navigation and app setting improvements, currently in preview, to facilitate the configuration of specific features. The navigation improvements now include a secondary navigation panel that lets you quickly scan all of your components. In addition, there are more direct links in your View component to the table, column, or action that you want to check or edit. Finally, error and warning messages are more prominently displayed in the app.
The new desktop design, currently in preview, is optimized for desktop browsers, presenting a more complete view of information with a consistent organization and structure. The new desktop design lets users navigate their apps more easily and access information in context, and provides an efficient way to edit existing records without losing context. The legacy desktop design, enabled by default, provides an experience similar to the mobile and tablet device.
The following features require opt-in to the AppSheet preview program. The AppSheet Preview program lets app creators try out new app features that are not yet fully supported.
Item
Description
Feature
Chat apps with AppSheet (Preview)
Create and publish Chat apps using AppSheet. Chat apps are web applications or services that run in Google Chat. By creating a Chat app with AppSheet, you enable users to interact directly with your app in Google Chat rather than clicking out to view the AppSheet app in a separate window.
New coming feature of Chat app, people never gonna use as there is no fixed use cases.
Once we got this new policy, we will ban straightaway. This will help us to deal with quetions from those who test the new (not-working) new feature. I know such a new feature is designed for 1 % of global appsheet user ( not sure who they are, but as far as Santiago claims there is someone who love such, but i leave them alone).
In the meantime, we banned new AppSheet database and other features, as we know it disturb us , and never help the end users.
It is pretty much problematic works.. with us. Once new feature is delivered by the google, we ask our client to ban them, if they wish to stay away from the possible problem.
When it comes to Google announces the new features will be delivering to the users , then good sign. We need to watch out. Even for the existing apps,as it will most likely be broken.
I dont have much of statical analysys but on my feeling, this is highly like to happen… sadly.
So, I m checking daily the new announcement daily (not daily sometime) thrown by Google team. Then once I found out the new featues, then, I naturally ask question how to BAN the new upcoming features.
Im telling to my ones, please do not take a poisnous apples, even though you are offered to bite.
Probably (as im silly), 100% of readers on your write will not understand what you mean… If not you, but i someone else reading this, could you interpret for me?
Yeah, i provided the feedback privaly (free, no charge on google), but this is not tellling me what is the issue, and how the issue is solved. Please dont care, probably it is because of my lack in English ability.
Long one, but the 100% of appsheet users is expecting the new desktop ux, without LOSING he existing functionality.
It is HIGHLY possible for Google to declare the GA while the currently availabe functionalties will not be available on new UX.
Then, could you please tell us the contact details to claim over SLA agreement, as Google is breaching such a basic contract with us (existing functionalities not work… then we asked why. Then Googe admid it wont work) … I m eager that new UX to come. But if any single existing funtionalities not gonna work. Then all the community member need to declare the breach of the contract against SLA. A Google could not manage to ensure the apps.
I dont want to get this story to happen but to get prepared ourself, we asked the suport desk to tell us to lodge (register) our possible (most like to happen) claim to calll for the “Against SLA”. Then they immidicatly not “responsible”. No anser , not reaction, no explanation. Annoy with us will contines, before Google kills appsheet sadly.
if anyone are supporing with us, who wish to claim over Google who are not performing our basing SLA under the licencing contract, please let me know. We will team up..
I m ready to take a legal proceeding, even personnely, as the current repeated outage and downtime, and the un-reported signficantly impacting bugs are never gonne being shared by the Google. And worse enough they are never being fixed. Fraud fault.
I sincerely agree with everything you just posted in this thread @Koichi_Tsuji ,
However, as someone who is coming from App Maker, almost everyday I ponder the question what If we were to live that fate again, and it is a scary scenario because I’ve reached far more users and build far more apps now with Appsheet than I did with AppMaker, in a shorter period time. I wouldn’t want to lose all that work (again), and Google has demonstrated they have the coldness to kill projects without hesitation, if they think it is of no longer need/ use.
So I would like to take the time in this thread to also mention that I deeply appreciate the progress that the current AppSheet team has done, and of course all the work that Parveen, Santiago and the OG Appsheet team did to create such an agile yet powerful tool to empower non programmers.
I do use Chat Apps (a lot), I think Desktop UI was a huge step up for desktop users, and I’m willing to give Databases a chance as long as it truly improves performance and if it ever allows 100K+ rows.
I also agree with most of the claims in the community, which usually come from the same set of members, In the way of how things are prioritized or the pace at which projects are evolving. But I’m far from thinking that everything is heading in the wrong direction, quite opposite I’m very hopeful on Appsheet’s future, as long as they don’t start killing already established features, as some Google divisions are known of doing, and I feel like this is the overall fear in the negative post I have been seeing lately in my feed.
So a little bit playing both sides, or maybe leaning more towards one, but this is my humble opinion, let’s just not make it seem like every single thing is wrong, but keep pushing the team in the desired direction so that this product keeps getting better in the most efficient way possible without Google feeling like it is completely heading in the wrong direction and starts “sunseting” it, as they like to call it.
@lizlynch please elaborate more on the dynamic list of IP addresses. Specifically on how to configure the Google Cloud firewall to accept webhooks from Appsheet if the IPs are dynamic.
You can request static IP addresses if you depend on the stability of the IP addresses for access control security. Reach out to AppSheet using the usual channels or by contacting AppSheet Support.
I’ll make this more clear in the release note above.
This support article lists the IP addresses where “most” AppSheet’s egress traffic is coming from. This was made to make sure you could specify the firewall rules for the Databases and other data sources when needed.
To accommodate Automation Webhook (Api calls) larger adoption, we decided to use a dynamic list of IP addresses for egress. We can’t guarantee the stability of this list.
In case you require such stability, please follow the instruction mentioned by @lizlynch so that we could allow-list apps for a specific app owner to use the static list mentioned above.
The AppSheet support team just emailed me that you have rolled back the dynamic IP proxy, is this information accurate? If so, shouldn’t you officially mention this in one of your release notes ?
Thanks for reaching out. It was only temporarily rolled back a while ago, but it’s currently rolled out 100% to all.
I asked them to reach out to you because of the last reported issue. You have filed for an exception and all the apps that you are authoring should sending traffic through the list of static IPs.
Please let the support know in case this is not what you are experiencing now.
