As we continue to improve the experience for Apps Script developers, today we're announcing project history, a new interface for developers to view previously deployed script versions and compare versions to the current script version.
Developers can use project history to view the code of previously deployed script versions. The highlight changes can be used to quickly compare differences between their selected version and the current, or head, version, taking the guesswork out of determining what's changed. Anyone who has edit permission on an Apps Script project can access project history. To navigate to the project history page, open an Apps Script project and click Project History.
The project history page displays up to 200 previously deployed versions and the head version of the script.
To compare a version to the head version, turn on Highlight changes.
Additional improvements for script versions will be made in the coming weeks.
Who’s impacted
Developers
Why it’s important
Apps Script is a low-code development platform that makes it quick and easy to build business solutions that integrate, automate, and extend Google Workspace. With Apps Script, Google Workspace users can customize workflows, create automations, and build integrations that connect the applications they use every day.
Getting Started
Developers: Use our developer documentation to learn more about working with Apps Script and watch the video below to see project history in action:
Anyone who has edit permission on an Apps Script project can access project history. To navigate to the project history page, open an Apps Script project and click Project History.
Previously available in beta through our Developer Preview Program, the ability to read and write a user’s working location using the Calendar API is now generally available.
Reading a user’s working location helps better understand the flow and volume of people through physical campuses. Using this information, you can better adapt on-site resources and update other third-party surfaces, such as hot desk booking tools.
Writing a user’s working location makes it easier to update a user's working location in their calendar based on when and where they’ve booked a hot desk, or if they’ve scheduled a trip via a travel booking tool, and more.
Admins and Developers: For more information, see our developer documentation for reading and writing user's working location. Important Note: While all developers will be able to use the API, the working location feature is only available for eligible Workspace editions.
All developers can use the API, however the working location feature is only available for eligible Workspace editions:
Available to Google Workspace Business Standard, Business Plus, Enterprise Standard, Enterprise Plus, Education Fundamentals, Education Plus, Education Standard, the Teaching and Learning Upgrade and Nonprofits customers, as well as legacy G Suite Business customers
Not available to Google Workspace Essentials, Business Starter, Enterprise Essentials, Frontline, G Suite Basic customers
Recently, we introduced the ability for users to set working locations in Calendar that indicate where they’re working for specific portions of the day. Now, we’re adding the ability to programmatically read and write working locations for specific portions of the day. This update expands on the existing reading and writing functionality announced earlier this year.
This feature is available now for all eligible Google Workspace editions.
Availability
All developers can use the API, however the working location feature is only available for eligible Workspace editions:
Available to Google Workspace Business Standard, Business Plus, Enterprise Standard, Enterprise Plus, Education Fundamentals, Education Plus, Education Standard, the Teaching and Learning Upgrade and Nonprofits customers
Last year, we announced that developers could use the Google Chat API to programmatically create new spaces and add members to those spaces through the Google Workspace Developer Preview Program.
Today, those features are generally available for all Google Workspace developers, along with the ability to use Chat API to:
These features enable developers to build solutions that integrate into workflows and pull contextual data right into the conversation. Using the new API functionalities, you can set up new spaces that focus on a specific topic, team, or project. You can also use the new APIs to encourage collaboration and outreach with users in your organization. For example, LumApps, a leading intranet platform, enables you to start a direct message in Google Chat from its user directory. Those who are trying to find others based on job titles, roles, departments, and other attributes, can quickly start messaging each other.
Additional details
To ensure you are aware that a Chat application has performed an action on behalf of a user, Chat web and mobile apps will display the app name for system messages and Chat messages.
Getting started
Admins: Admins can use the API controls in Admin Console if they want to restrict access to Google Chat data.
Developers: Access the new Chat APIs through the Google Chat API.
Available now in beta through our Developer Preview Program, you can write a user’s working location using the Calendar API.
Using the API to write a Calendar user’s working location values can help you synchronize users' working location with third-party tools. You can easily update users’ working location based on:
When they book a hot desk via a hot desk booking tool
Schedule a trip via a travel booking tool
Reading of working locations is already available through the Developer Preview Program.
This feature is available now for all eligible Google Workspace editions.
Availability
All developers can use the API, however the working location feature is only available for eligible Workspace editions:
Available to Google Workspace Business Standard, Business Plus, Enterprise Standard, Enterprise Plus, Education Fundamentals, Education Plus, Education Standard, the Teaching and Learning Upgrade and Nonprofits customers
Available now in beta through our Developer Preview Program, you can read working location data using the Calendar API and get notified when those working locations change. Previously, we said this functionality would be available through a separate API. However, in order to provide a more streamlined experience, this functionality will be instead available in the Calendar API.
Using the API to read a Calendar user’s working location values can help you:
Analyze the flow and volume of people through physical campuses, helping you adapt on-site resources to the needs of your employees.
Share whereabouts across other internal or third-party surfaces, making it easier to enable tasks such as hot desk booking or schedule in-office or remote working days.
We anticipate write support for the API to become available in Q3 2023 — we’ll share an update here on the Workspace Updates Blog at that time.
While all developers will be able to use the API, the working location feature is only available for eligible Workspace editions:
Available to Google Workspace Business Standard, Business Plus, Enterprise Standard, Enterprise Plus, Education Fundamentals, Education Plus, Education Standard, the Teaching and Learning Upgrade and Nonprofits customers, as well as legacy G Suite Business customers
Not available to Google Workspace Essentials, Business Starter, Enterprise Essentials, Frontline, G Suite Basic customers
We’re improving the client-side security of Google Docs, Sheets, Slides, Forms, Sites, Jamboard, Drawings, and Drive with Trusted Types. This will provide an extra layer of protection around Document Object Model (DOM) APIs that are used by the apps listed above or third-party extensions.
This new enforcement mode will require third-party extensions to use typed objects instead of strings when assigning values to DOM APIs, and will begin rolling out on March 23, 2023. Once Trusted Types are fully enforced, the Trusted Types directive will be present in the Content Security Policy (CSP) header:
Who’s impacted
Developers (relying on any Chrome extensions that modify DOM APIs.)
Why it’s important
Trusted Types is a feature that further enhances our advanced data protection controls to keep users and data safe across more of the apps they use everyday.
Additional details
Screen readers, braille devices, and screen magnification will not change with Trusted Types. However, we recommend admins and developers check third party extensions for Trusted Types violations. Visit the Help Center to learn more about Accessibility for Google Docs, Sheets, Slides, & Drawings.
Getting started
Admins: There is no admin control for this feature.
Developers:
To make code Trusted Types compliant, signal to the browser that data being used within the context of these DOM APIs is trustworthy by creating a Trusted Type special object.
There are several ways to be Trusted Types compliant, such as removing the offending code, using a library, or creating a Trusted Types policy. To ensure a seamless experience for users, these techniques can be employed before Trusted Types enforcement is rolled out.
Within the Google Cloud Console, you can now view and manage all Google Workspace API activity. Here, you’ll find a centralized view of which APIs are currently running and their associated requests. You can also easily perform common actions such as:
Monitoring aggregated metrics for APIs, including traffic, errors, and latency.
Viewing and adjusting quotas as needed.
Managing API credentials.
Finding other available APIs, tutorials and documentation.
This unified experience will eliminate the need to search for APIs manually, making it easier to manage your existing projects and build out your API ecosystem with new integrations.
Getting started
Admins and Developers: From the navigation menu in the Google Cloud console, navigate to View all products > Other Google Products > Google Workspace. Visit the Help Center to learn more about enhancing Google Workspace Apps.
It’s now easier to configure and use Cloud Search search filters and facets with multiple enhancements to our existing functionalities. With this launch, you can use the Cloud Search Query API to configure new additional capabilities:
Faceting support for integer type fields, such as priority levels for support tickets or the number of pages in a document
Out of the box Faceting support for document size, document creation, and custom date fields
New default reserved operators for document size and created date fields
Simplified Query API response with filters being directly provided in the response
Expanding filter options creates a more user friendly search experience, making it easier and faster to narrow search results to the most relevant documents.
Getting started
Admins and developers: See our developer documentation for more information about using new facet enhancements
End users: There is no end user action required. You will automatically see new filter options once your admin has configured them
AppSheet is Google’s platform for building and deploying end-to-end apps and automation without writing code. As we continue to enhance and streamline app creation, we’re introducing a built-in structured database in public preview.
Within the database editor, you can set the same column types as in the AppSheet editor for your data.
Easily create and customize databases starting from AppSheet's My Apps page.
Who’s impacted
Admins, developers and end users
Why it’s important
AppSheet databases make it easy for you to organize and manage the data that power your apps directly inside AppSheet. See our Developer Blog for more information.
Additional Details
Note that during preview:
Access to AppSheet databases will be enabled by default for everyone. There will be no impact on existing apps. Users can connect a database to both new and existing AppSheet apps.
Databases will be limited to 10k rows per table, 20 tables per database and 20 databases per user. These limits may change when this feature becomes generally available.
Getting started
Admins and Developers: You can create a blank database from the My Apps page.
Visit the AppSheet Help Center for more information on AppSheet databases.