WorryFree Computers   »   [go: up one dir, main page]

What’s changing 
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. 



Rollout pace 
  • This feature is available now for all users. 

Availability 
  • Available to Google Workspace Enterprise Plus customers, as well as those with an AppSheet license. 

Resources 
Labels: , ,

[Update] What’s changing 
Coming soon to beta, the Calendar User Availability API will be used to programmatically access the working location feature in Google Calendar. You can gain access to the beta through the Google Workspace Developer Preview Program. 


You can preview the API documentation now to prepare in advance and share your initial feedback as we move closer to beta.




Who’s impacted 
Admins and developers 


Why you’d use it 
The working location feature is an easy way for users to share where they’ll be working for any given day or period of time. Up until now, only end users could create these calendar entries. Now, this information can be read and written using an API to manage and accommodate the needs of your employees. 


Customers rely on other applications to set their location context, such as booking a desk with hot desk booking tools or requesting and setting “work from home” days in HR management tools. This creates duplicative work for end users. With the API, a user’s working location can be programmatically set or accessed directly from the user’s calendar to any other third-party application. 


Additionally, by surfacing working location context into other systems and tools like internal team directories, customers can optimize the flow of people in their physical office locations. Or you can use the API to prepare for the demand of dining services, conference rooms, and more, based on this data. 


Getting started 

Availability 
While all developers will be able to use the API, apps created using the API are only accessible to those on 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 

Resources
Labels: , , , ,

What’s changing 
We’re introducing Suggest Filters for Cloud Search. Using the Cloud Search Query API, admins can specify a filter condition that will be pre-applied to keyword suggestions as user types a query. This will surface more relevant suggestions, helping reduce the time users spend searching. 



Who’s impacted 
Admins, developers and end users 



Why it’s important 
With suggestion filters, admins can configure suggestions based on the use cases for a given search application, reducing irrelevant suggestions. For example, admins can add a suggestion such as a country, which will surface suggestions based on documents that align the filters. 


Getting started 
  • Admins: See our developer documentation here and here for more information about creating a suggestion filter.
  • End users: There is no end user action required, you will automatically see relevant suggested filters as you type a query. 

Rollout pace 
  • This feature is available now for all users. 

Availability 
  • Available to Google Cloud Search Customers 

Resources 
Labels: , , ,

New updates 

There are no new updates to share this week. Please see below for a recap of published announcements. 


Previous announcements


The announcements below were published on the Workspace Updates blog earlier this week. Please refer to the original blog posts for complete details.



Migrate your classic Google Sites before December 1, 2022 
We’re extending the previously announced timeline to give Google Workspace customers more time to migrate from classic Google Sites to new Google Sites: 
  • Starting December 1, 2022 (previously June 1, 2022), you will no longer be able to edit any remaining classic Sites in your domain. 
  • Starting January 1, 2023 (previously July 1, 2022), Classic Sites will no longer be viewable unless they are converted to new Google Sites. 
Learn more here and here. 


New and updated third-party DevOps integrations for Google Chat, including PagerDuty 
There are now a variety of additional DevOps integrations that allow you to act on common workflows directly in Google Chat. | Learn more. 


Export log data in near-real time to BigQuery
Exported log data streams are now in near-real time (under 10 minutes), improving upon the previous process which returned log data that could be up to three days old. | Learn more here and here. 


AppSheet Enterprise Standard and Enterprise Plus available as add-ons to Google Workspace editions
Google Workspace customers can now purchase AppSheet Enterprise Standard and Enterprise Plus as add-ons by contacting their Google Cloud sales representative or through the Google Workspace Partner network. | Learn more. 


Use Connected Sheets with VPC-SC protected data, improved Cloud Audit Logs for Connected Sheets events 
BigQuery datasets that are behind a perimeter created by VPC Service Controls can now be accessed using Connected Sheets. We’ve also made improvements to the Connected Sheets logging in the Cloud Audit Logs. | Learn more. 


New banners in Google Chat protect against malicious links 
In Google Chat, you can now see banners warning against potential phishing and malware messages coming from users with personal Google Accounts to help protect users against malicious actors, keeping data safe. | Learn more. 


For a recap of announcements in the past six months, check out What’s new in Google Workspace (recent releases).
Labels: , , , , , ,

What’s changing

Using the Google Chat API, you can now programmatically create new Spaces and add members to those Spaces. This functionality is available in preview – developers can apply for access through our Google Workspace Developer Preview Program.

Google Workspace administrators can also use the API controls in Admin Console if they would also like to restrict access to Google Chat data.


Who’s impacted

Admins and Developers

Why you’d use it 

While it’s easy to create new Spaces and add members directly in Google Chat, there are cases where Spaces can be filled with many topics and side conversations, making it difficult to keep track of important information. Using the new API functionality, you can set up new spaces that focus on a specific topic, team, or project. For example, an on-call app can automatically create a space when an outage has been detected.

Getting started


Availability

  • Available to all Google Workspace customers, as well as legacy G Suite Basic and Business customers


Labels: , , ,

Quick Summary 
We’re improving search rankings in Cloud Search by taking into account document popularity. This means documents that have been clicked on by a large number of users will be prioritized in the overall search rankings. By surfacing popular and useful documents that match a user’s query, this feature will help reduce the effort and time required to find relevant documents. 


Getting started 
  • Admins: The feature is available by default. Use this guide to learn more about the use of Document Popularity in Cloud Search ranking. Note: You need to use the default redirect URLs for search results when using Cloud Search Query API for this feature to work.
  • End Users: No effort needed.

Rollout pace 

Availability 
  • Available to all Google Cloud Search customers 
  • Available to Google Workspace Business Plus, Enterprise Standard, Enterprise Plus, and Education Plus customers 
  • Not available to Google Workspace Essentials, Business Starter, Business Standard, Enterprise Essentials, Education Fundamentals, Frontline, and Nonprofits, as well as G Suite Basic and Business customers 

Resources 
Labels: , , ,

Quick summary 
Google Workspace developers can now create Google Workspace add-ons that attach files to a Google Calendar event from any third-party service. This feature enables developers to create add-ons that support attachments from a wide range of sources beyond Google Drive, such as digital whiteboard, content creation, or file management tools. 


Users who have the relevant add-ons installed will be able to attach files from these sources to a Calendar event, and attendees can view the event with the attachment on the web or on mobile.



Attach files from a third-party service to a Calendar event


After attaching files in Calendar on the web, users can view the event with the attachment on the web or on mobile. 


Getting started 

Rollout pace 
  • This feature is available now for all developers and users. 

Availability 
  • Available to all Google Workspace customers, as well as legacy G Suite Basic and Business customers 

Resources 
Labels: , , , , ,

What’s changing

The Google Forms API provides programmatic access for managing Google Forms and acting on responses— empowering developers to build powerful integrations on top of Forms.

Who’s impacted 

Admins and developers

Why you’d use it 

The Google Forms API provides programmatic access to manage Forms and receive responses, supporting the development of a variety of powerful integrations. For example, you can use the API to develop real-time dashboards or data visualizations; trigger business workflows incorporating project management, CRM, or LMS tools; or auto-generate forms from question banks or other data sets. 

The API is useful for a variety of tasks such as:

  • Creating and modifying forms or quizzes
  • Retrieving form responses or quiz grades
  • Reading form content and metadata
  • Receiving push notifications for form or quiz responses or form structure updates 


Getting started



Rollout pace
Integration availability for end users
  • This feature is available now for all users.

Availability

  • Available to all Google Workspace customers, as well as legacy G Suite Basic and Business customers and users with personal Google Accounts

Resources

Labels: , , , ,

What’s changing 

At Google Cloud Next 2021, we announced the Google Forms API Beta, which provides programmatic access for managing Google Forms and acting on responses— empowering developers to build powerful integrations on top of Forms. 

The Google Forms API is now rolling out as an Open Beta which means developers who are part of our Early Adopter Program can make their integrations available to the public. We’ll no longer require individual end-user accounts to be allowlisted. Developers should keep in mind, however, that their integrations are in Beta. 

Developers can apply to join our Early Adopter Program and begin developing using the Google Forms API by filling out this form. 

See below for more information. 

Who’s impacted 

Admins and developers 

Why you’d use it 

The Google Forms API provides programmatic access to manage Forms and receive responses, supporting the development of a variety of powerful integrations. For example, the API could be utilized to develop real-time dashboards or data visualizations, trigger business workflows incorporating project management, CRM, or LMS tools, or auto-generate forms from question banks or other data sets. 

The API is useful for a variety of tasks such as: 

  • Creating and modifying forms or quizzes 
  • Retrieving form responses or quiz grades 
  • Reading form content and metadata 
  • Receiving push notifications for form or quiz responses and updates 



Getting started 

Rollout pace 

Integration availability for end users 

Availability 

Resources 

Labels: , , ,

What’s changing 

Earlier this year, we announced the beta for Google Workspace Client-side encryption, specifically for Google Drive, Docs, Sheets, and Slides, with support for all file types in Drive including Office files, PDFs, and more. 

We’re now expanding the beta to include desktop data for Google Meet and Google Drive. Additionally, key access service APIs are now publicly available for anyone to use. 

Encryption notice in Meet

Encryption notice in Meet

Lastly, we are adding two new Key access service partners (Fortanix, Stormshield) for customers looking for a dedicated partner that integrates with the key access service APIs. Previously, we had announced key service partnerships with Flowcrypt, FutureX, Thales and Virtru. 

The beta is available to Google Workspace Enterprise Plus and Google Workspace Education Plus customers—eligible customers can now apply for the beta here. Important note: Customers who are already participating in the beta will have to reapply for access to the Google Meet and functionality, but you will be able to reuse your key service configuration. 

Who’s impacted 

Admins and developers 

Why it’s important 

Google Workspace already uses the latest cryptographic standards to encrypt all data at rest and in transit between our facilities. With Client-side encryption, we’re taking this a step further by giving customers direct control of encryption keys and the identity provider used to access those keys. This can help you strengthen the confidentiality of your data while helping to address a broad range of data sovereignty and compliance needs. 

When using Client-side encryption, customer data is indecipherable to Google. Customers can create a fundamentally stronger privacy posture to comply with regulations like ITAR and CJIS or simply to better protect the privacy of their confidential data 

Read our announcement post to learn more about this beta and our plans for Client-side encryption across Google Workspace. 

Additional details 

If you are looking to choose a key service access partner, Flowcrypt, Fortanix, Futurex, Stormshield, Thales, and Virtru have built tools in accordance with Google’s specifications and provide both key management and access control capabilities. Your partner of choice holds the key to decode encrypted Google Workspace files, and Google cannot access or decipher these files without this key. 

If you prefer to build or integrate your own in-house key services, we have published the key access service API specifications that can be used with Client-side encryption. 

Getting started 

Availability 

  • Available to Enterprise Plus and Education Plus customers 
  • Not available to Google Workspace Essentials, Business Starter, Business Standard, Business Plus, Enterprise Essentials, Enterprise Standard, Education Fundamentals, Frontline, and Nonprofits, as well as G Suite Basic and Business customers. 

Resources 

Labels: , , , , ,

What’s changing 

You can now send an email archive of Google Chat messages to a 3rd party archiving solution. 

For users that have archiving of Chat messages enabled, the 3rd party archiving solution will be able to receive email archives containing 1:1 conversations and conversations in rooms and groups. Content within the Chat message is also archived, such as reactions, Drive links, and file attachments. 

Who’s impacted

Admins and developers

Why it’s important

If you’re required to archive Chat messages for compliance purposes, or are already using a 3rd party archiving solution, you’ll now be able to integrate Google Chat with these 3rd-party partners. 

Getting started 

Turning on third party archiving setting



End users: 

  • There is no end user setting for this feature. 

Rollout pace 

  • This feature is available now for all users.

Availability 

  • Available to Google Workspace Enterprise Standard, Enterprise Plus, Education Fundamentals, Education Plus customers 
  • Not available to Google Workspace Essentials, Business Starter, Business Standard, Business Plus, Enterprise Essentials, Frontline, and Nonprofits, as well as G Suite Basic and Business customers 

Resources 

Labels: , , ,

What’s changing 
There has been a change to how the Google Calendar API manages usage. Previously, Calendar API queries were monitored and limited daily. These queries are now monitored and limited on a per-minute basis. 

See below for more information. 


Who’s impacted 
Admins and developers 



Why it’s important 
This change introduces better behavior when a quota is exceeded, as requests will be rate-limited until the quota is available rather than falling all requests for the rest of the day. Additionally, this will help developers identify issues around quota enforcements faster. 

More information regarding your usage and quota limits can be found in the Google API console. 



Additional details 
To ensure you’re working efficiently with your quota, we recommend: 
  • Using push notifications instead of polling. 
  • Randomized timing to ensure user requests are spread out evenly, rather than bursts of requests. 
  • Using incremental synchronization with sync tokens for all collections instead of repeatedly retrieving all the entries. 
  • Increasing page size to retrieve more data at once by using the max results parameter. 
  • Updating events when they change to avoid recreating all the events on every sync. 
  • Using exponential backoff for error retries to make rate-limiting work properly. 


Getting started 
  • Admins and Developers: Use this guide to learn more about how to view your API usage and limits.
  • End users: There is no end user impact for this feature. 

Availability 
  • Available to all Google Workspace customers, as well as G Suite Basic and Business customers 

Resources 
Labels: , , ,

Update

[May 26, 2021]: We’ve updated the “Additional details” section of this post with more information on Google Docs accessibility features and support. Please see below for more information.

What’s changing 
We’re updating the way Google Docs renders documents. Over the course of the next several months, we’ll be migrating the underlying technical implementation of Docs from the current HTML-based rendering approach to a canvas-based approach to improve performance and improve consistency in how content appears across different platforms. 


We don’t expect this change to impact the functionality of the features in Docs. However, this may impact some Chrome extensions, where they may no longer work as intended. 


Who’s impacted 
Admins and developers 


Why it’s important 
Some Chrome extensions rely on the way the backend of a Google Doc is structured or specific bits of HTML to function properly. By moving away from HTML-based rendering to a canvas-based rendering, some Chrome extensions may not function as intended on docs.google.com and may need to be updated. 


Admins should review the current extensions deployed in their organization. See this file for an example of a Google Doc using canvas-based rendering and to test out your extensions.


If you are building your own integrations with Google Docs, we recommend using Google Workspace Add-ons framework, which uses the supported Workspace APIs and integration points. This will help ensure there will be less work in the future to support periodic UI implementation changes to Docs. 


If your company has developed a private Chrome Extension that you believe will be impacted and you are unable to migrate to the Google Workspace Add-ons framework, you can submit this form to provide feedback and notify our team. 

Additional details
Compatibility for supported assistive technologies such as screen readers, braille devices, and screen magnification features, will not be impacted by the canvas-based rendering change. We will continue to ensure assistive technology is supported, and work on additional accessibility improvements enabled by canvas-based rendering.

Getting started 
  • Admins and developers: 
    • To see an example of a Google Doc using canvas-based rendering, please see this example file. We strongly recommend reviewing the current extensions used in Google Docs that are deployed within your organization.
    • To ensure any Chrome extensions you build in-house continue to work as intended, we recommend migrating them to the Google Workspace Add-ons framework. 
  • End users: No action required. 


Rollout pace 
  • Google Docs will be migrating slowly from HTML to canvas based rendering over the course of the next several months. 


Resources 
Labels: , , , ,

What’s changing 
We’re launching a new way to create Google Workspace Add-ons. With alternative runtimes, developers can write Add-ons in any language and on any infrastructure, and then publish them to the Google Workspace Marketplace. Alternate runtimes was previously available in beta. 


Who’s impacted 
Admins and developers 

Why it’s important 
Google Workspace Add-ons allow you to use third-party applications within Google Workspace. These integrations between Google Workspace and other productivity applications allow work to happen more seamlessly across platforms, helping you get work done faster without switching from one app to another. 

Previously, developers had to write Add-ons in Apps Script. With this launch, developers can write them in whatever language, and on whatever infrastructure, they want. This change enables developers to use the tools and systems they’re used to, making it quicker and easier to create and publish high-quality Add-ons. 

Getting started 

Rollout pace 
  • This feature is available now for all users. 

Availability 
  • Available to all Google Workspace customers, as well as G Suite Basic and Business customers  

Resources 
Labels: , ,

Quick launch summary We’re launching a Postmaster Tools API, allowing programmatic access to the email data found in the Postmaster Tools user interface. You can use the API to gather metrics on bulk emails sent to Gmail users—such as delivery errors, spam reports, feedback loop performance, and more. You can also import or merge the data into other systems and diagnose issues with email delivery.


Getting started
  • Admins: There is no admin control for this feature. 
  • End users: Registered domain owners can use this API to programmatically extract their domain’s data into their systems. Check out the Developers Guide to learn more about the using the Postmaster Tools API.
Rollout pace
Availability
  • 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

Labels: , , ,

What’s changing Due to low usage, Google App Maker will be turned down gradually over the course of 2020 and officially shut down on January 19, 2021. Prior to the shutdown, you’ll need to review App Maker usage in your domain and take any necessary action.

See the Additional details section below for a timeline of the shutdown and alternatives you can deploy in your organization.

Who’s impacted Admins, end users, and developers

Why it’s important As soon as possible, review your organization’s App Maker applications. App creators should review the uses cases listed in the Additional details section below and take action as necessary by the dates listed in the turndown schedule.

Additional details Turndown schedule
App Maker will be disabled gradually according to the schedule below:
  • Today, existing apps continue to work. Though App Maker is no longer under active development, the service will continue to be maintained.
  • Starting April 15, 2020, you will no longer be able to create new App Maker apps. You will still be able to edit and deploy existing apps.
  • Starting January 19, 2021, existing App Maker apps will stop working and you will no longer have access to them. App maker data stored in Cloud SQL will remain unchanged and continue to follow the policies established by your Google Cloud Platform (GCP) account.

Alternative solutions
Due to the specific source code used for App Maker, you can’t directly migrate your apps to another platform. Depending on your use case, we recommend the following:
  • If you use App Maker to automate business processes: Use AppSheet, a new addition to our application development portfolio that has capabilities similar to App Maker. App Maker data is stored in Cloud SQL, and App Sheet supports Cloud SQL databases. This allows you to build an application on the existing database tied to your App Maker app.
  • If you use App Maker to develop apps: Use App Engine to build and deploy applications on a fully managed platform. App Maker data is stored in Cloud SQL, allowing you to build an App Engine application on the existing Cloud SQL database tied to your App Maker app.
  • If you use App Maker for data collection: Use Google Forms, which has many new features that were not available when App Maker launched. 
Deleting apps
If you no longer use apps created with App Maker, please follow these steps to fully delete each app:
Data retention
Your App Maker data belongs to your organization. App Maker user data is stored in CloudSQL and will continue to be retained according to the policies established by your GCP account. Data composing the App Maker app itself can be exported from within the App Maker editor until January 19, 2021.

Getting started 
Admins: We recently emailed the primary admin in your domain and provided a CSV file with a list of the App Maker apps being used in your organization. This list includes the application name, creator name, and last modified date for each app. It also contains a link to your Admin console with application-specific usage stats and project information.
Notify app creators in your domain as necessary of the upcoming shutdown and alternative solutions.
Labels: , , , ,

What's changing

With the new Docs API, there are more ways to build services that better support your business and improve your workflows. For documents that require consistency, collaboration, and accuracy — like invoices, proposals, contracts, and reports — the API will help automate common word processing tasks with the real-time editing and collaboration of Docs.

Who’s impacted 
Developers 

Why you’d use it 
Some ways you could use this API are: 
  • Create documents automatically 
    •  Use the Docs API to automate document creation, like creating all of the blank invoices you need for a particular quarter with a single click. Documents that require a template, like legal documents or contracts, can be automated based on user input and monitored with the API as well. 
  • Manage workflows 
    • Use the Docs API to add user or system-provided data to a document at various stages of a process. Programmatic edits to the same document over time, or to multiple documents at once, can simplify your workflows. 
  • Sync with your content management systems 
    •  From internal wikis to blog content, you can import and export document details seamlessly between Google Docs your employees are editing and your content management systems. For example, publishing platforms can now allow their customers to compose and collaborate in Docs to drive content to their sites. 
How to get started 
For more information and how to get started, see the Docs API developer site. 

Additional details 

The Docs API will round out a complete set of APIs across all G Suite editor applications along with the Sheets API and the Slides API. 

Helpful links Availability 
G Suite editions 
Available immediately to all G Suite editions. 

On/off by default? 
The API is available and accessible by default to all G Suite users.

Stay up to date with G Suite launches
Labels: , , , , ,

Businesses using Google Mobile Management and other Enterprise Mobility Management (EMM) providers can publish Android apps customized for their workplace directly to their managed Google Play store, where their employees can easily access and install them. In some cases, these customers have set up multiple “organizations” within their domain (e.g. to serve different regions, for testing purposes, etc.), each of which needs access to the custom app. To meet this need, we recently made it possible to publish a single private app to up to 20 organizations. This has several advantages:
  1. Developers can publish apps to domains other than their own (including developers with personal @gmail.com accounts).
  2. Developers no longer need to be admins of the organizations they’re publishing to.
  3. Businesses can more easily delegate app publishing to third-party developers.
  4. Private app publishing remains secure, because the developer must have the target organization’s Organization ID and an admin must approve any apps targeted to their organization.


For more information, please see the Help Center.

Launch Details
Release track:
Available to both Rapid Release and Scheduled Release

Editions:
Available to all G Suite editions

Impact:
All end users

Action:
Change management suggested/FYI

More Information
Help Center: Publish private apps


Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates
Labels: , , , ,

(Cross posted from the Apps Developer Blog)

Posted by Pierce Vollucci, Associate Product Manager, Gmail and Steve Bazyl, Developer Programs Engineer, Google Apps

When you send emails, your recipients might read them on a computer, tablet, or phone—or more likely, all three. However your message might look different on all these devices. Later this month, you’ll be able to use CSS media queries with Gmail and Inbox by Gmail to ensure that your message is formatted the way you intended, whether it's viewed on a computer, a phone in portrait mode, or a tablet in landscape mode. You’ll be able to change styles based on width, rotation, and resolution, allowing for more responsive formatting to optimize your email for every device.

Example of an email before and after responsive design

In discussions with email designers, these supported CSS rules were identified as the most useful media queries to support responsive design. This is just one part of an overall effort to expand CSS support in Gmail and to give email designers more control over how their messages are rendered. For example, the CSS below applies the color red when the screen width exceeds 500px. 
@media screen and (min-width: 500px) {
  .colored {
    color:red;
  }
}
You can find the full list of supported CSS rules in the developer documentation. We hope this reference helps you create more feature-rich, responsive email for users. Happy formatting!


Launch Details
Release track:
Launching to both Rapid release and Scheduled release after September 29, 2016

Rollout pace:
Gradual rollout (more than 3 days for feature visibility)

Impact:
All end-users

Action:
Change management suggested

More Information
Gmail Blog (for end-users)
Labels: , ,