We’ve redesigned the Integrated Development Environment (IDE) for Google Apps Script. The new IDE offers a more modern and simplified development experience which makes it quicker and easier to build solutions that make Google Workspace apps more useful for your organization.
Apps Script is a rapid application development platform that makes it fast and easy to create custom business solutions that integrate with Google Workspace and that increase the power of apps including Calendar, Docs, Drive, Gmail, Sheets, and Slides. With this launch, we’ve revamped the cloud-based IDE that helps you create, edit, and manage projects. The new IDE simplifies the experience of developing for Google Workspace and offers:
A state of the art code editor, which uses Monaco and that offers advanced autocomplete, auto-formatting, and more.
An enhanced troubleshooting experience by improving the debugger and adding real-time streaming logs.
Integration between the IDE and the Google Workspace Developer hub to provide a seamless, end-to-end experience to design, develop, deploy and manage Apps Script projects in one place.
Updated look and feel, with a user-friendly interface which is more similar to other Google Workspace apps that use the Material Design framework.
Admins and developers: This feature will be ON by default for all users. However, users can opt out to use the legacy IDE by clicking on “Use legacy editor” in the toolbar next to the Execution log button. Use our developer documentation to learn more about working with Apps Script.
Available to Google Workspace Essentials, Business Starter, Business Standard, Business Plus, Enterprise Essentials, Enterprise Standard, and Enterprise Plus, as well as G Suite Basic, Business, Education, Enterprise for Education, and Nonprofits customers
We recently launched Connected Sheets, which connects Google Sheets and BigQuery to help you analyze large datasets using familiar spreadsheet tools. We’re now adding support for macros and APIs to help you automate tasks, as well as providing mobile access. Specifically, you can now use Connected Sheets with:
Sheets mobile apps, to view Connected Sheets on Android and iOS.
Developers and end users
Why you’d use it
Sheets Macro recorder
You can use the macro recorder to record when to create, edit, delete, and refresh Connected Sheets objects. This generates macros which you can then directly run in Sheets to refresh the data. This can automate common tasks, saving time and reducing errors.
Apps Script and Sheets API
You can use these APIs to write scripts and applications that automate tasks. For example, you can automate CRUD functions for Connected Sheets objects, including sheets, formulas, pivot tables, and extracts. Additionally, you can use the APIs to refresh these objects, as well as to refresh charts.
Mobile app support
You can now view Connected Sheets on mobile devices. You can also copy and paste data from Connected Sheets using the mobile apps. At this stage, you can’t create, edit, or refresh data in Connected Sheets on mobile.
We’re changing how Apps Script manages Google Cloud Platform (GCP) projects. This will help IT Admins govern these projects and simplify how developers manage projects as well. New Apps Script GCP projects will now live in a new folder (“apps-script”) in the GCP resource hierarchy. This means that new Apps Script projects will be governed by organization policies defined for GCP projects by IT admins.
Admins, Apps Script developers, and end-users of Apps Script projects
Why you’d use it
Gives IT admins additional controls: This feature helps make Apps Script projects more secure by providing additional control and visibility over these projects to IT administrators. Admins who have not yet defined organization policies can now do so to control Apps Script projects. Admins who have already defined organization policies are now assured that those policies will also be applied to Apps Script projects.
Simplifies developer project management: Developers no longer need to visit the Cloud Console to enable Google APIs - simply enabling it in the Apps Script editor is now all that’s needed.
Removes ‘risky’ label for end users: End users of internally-created Apps Script projects will no longer see those projects labeled “risky” when they visit the Google Security Checkup tool at myaccount.google.com.
When an Apps Script project is created, a GCP project is also created and associated with it. This GCP project controls a range of configurations and settings, including API access, G Suite Marketplace API configuration for publishing add-ons, access to Stackdriver logs, and more.
Previously, these GCP Apps Script projects existed outside of the resource hierarchy. Now, new Apps Script projects will be parented by a new “apps-script” folder in the resource hierarchy, specifically at organization root > system-gsuite (new) > apps-script (new).
This means they will be governed by organization policies, which give you centralized and programmatic control over your organization's cloud resources. Policies that can be managed here include the ability to restrict domains that are allowed to be on the ACL for Cloud projects, specify restricted APIs that Cloud projects can access, and block GCP projects from creating new GCE instances.
You can already control the Apps Script projects that run in your organization using the G Suite API permissions settings located in the Admin console (at Security > API Permissions). Using these settings, you can block applications that request access to certain APIs—unless you’ve specifically whitelisted them. App Maker apps, add-ons, and scripts that request certain OAuth scopes (like Gmail, Calendar, Drive, etc.) are just some of the Apps Scripts projects that these settings control.
Now you can also control access to projects that request the following scopes:
Apps Script Runtime - Control access to projects that request certain high-risk scopes specific to Apps Script projects (e.g. UrlFetch, Container UI).
Apps Script API - Control access to any project (e.g. Apps Script, GCP, AWS, etc.) that requests scopes for Apps Script API (e.g. Manage Projects, Manage Deployments).
Apps Script lets you do more with Google, like create add-ons for Docs, develop custom functions for Sheets, and manage responses in Forms. Traditionally, G Suite admins have had little or no visibility into the extent of the Apps Script usage in their organizations. With this launch, however, admins will be able to view Apps Script metrics, including number of users and number of active projects, in the Aggregate reports section of the Admin console. Admins currently participating in the App Maker Early Adopter Program will see App Maker metrics listed as well.
Posted by Edward Jones, Software Engineer, Google Apps Script and Wesley Chun, Developer Advocate, Google Apps
Have you ever wanted a server API that modifies cells in a Google Sheet, to execute a Google Apps Script app from outside of Google Apps, or a way to use Apps Script as an API platform? Today, we’re excited to announce you can do all that and more with the Google Apps Script Execution API.
One of our launch partners, Pear Deck, used the new API to create an interactive presentation tool that connects students to teachers by converting slide decks into interactive experiences. Their app calls the Execution API to automatically generate a Google Doc customized for each student, so everyone gets a personalized set of notes from the presentation. Without the use of Apps Script, their app would be limited to using PDFs and other static file types. Check out the video below to see how it works.
Bruce McPherson, a Google Developer Expert (GDE) for Google Apps, says: “The Execution API is a great tool for enabling what I call ‘incremental transition’ from Microsoft Office (and VBA) to Apps (and Apps Script). A mature Office workflow may involve a number of processes currently orchestrated by VBA, with data in various formats and locations. It can be a challenge to move an entire workload in one step, especially an automated process with many moving parts. This new capability enables the migration of data and process in manageable chunks.” You can find some of Bruce’s sample migration code using the Execution API here.
The Google Apps Script Execution API is live and ready for you to use today. To get started, check out the developer documentation and quickstarts. We invite you to show us what you build with the Execution API!