Tag Archives: Beta

Interoperability between Google Chat and other messaging platforms — powered by Mio

This announcement was made at Google Cloud Next ‘23. Visit the Workspace Blog to learn more about the next wave of AI innovation in Workspace. 


What’s changing 

If your organization uses a mixture of messaging tools, you can now use Mio to enable messaging interoperability between Google Chat and other platforms such as Slack and Teams. This is available now in beta, with general availability expected in early 2024. 




Who’s impacted 

Admins 


Why it matters 

We know that communication and collaboration happens over multiple channels and tools. This can cause missed messages, silos of communication, and a frustrating experience monitoring multiple chat tools. 


That’s why we’re partnering with Mio, a leading provider of collaborative interoperability solutions helping customers enhance their productivity by streamlining communication across multiple channels. You can leverage Mio to create a seamless experience between Chat and the various tools you need to get your work done. 


Getting started 



Availability 

Note: In order to leverage Mio’s interoperability capabilities, Mio licenses are required. 
  • Beta Availability: To request beta access, reach out to your account rep or submit this form to contact Mio
  • General Availability: Available to Google Workspace Business Starter, Business Standard, Business Plus, Essentials Starter, Enterprise Essentials, Enterprise Essentials Plus, Enterprise Standard, Enterprise Plus, Frontline Starter, Frontline Standard, and Nonprofits customers 

Resources 

Beta Channel Release for ChromeOS / ChromeOS Flex

Hello All,

The Beta channel has been updated to 116.0.5845.102 (Platform version: 15509.57.0) for most ChromeOS devices.

If you find new issues, please let us know one of the following ways:

Interested in switching channels? Find out how.


Google ChromeOS

Introducing eSignature for Google Docs and Google Drive: launching to open beta for Workspace Individual subscribers, launching to beta for Google Workspace customers

What’s changing 

In June 2022, we began alpha testing the ability to request and capture eSignatures in Google Docs. Based on the feedback we received, we’re ready to move this feature to the next level: 
  • eSignature is now available as an open beta for Google Workspace Individual subscribers — no additional sign-up is required to use the feature. 
  • eSignature will be available in beta for select Google Workspace customers — see the “Additional details” section below for more information.
eSignature in Google Drive

eSignature in Google Docs





Who’s impacted

Admins and end users


Why you’d use it

For solopreneurs and small businesses, keeping track of contracts, customer agreements, and other binding documents can be challenging. To help streamline this workflow, we’re natively integrating eSignature in Google Docs, allowing you to request and add Signatures to official contracts, directly in Google Docs. 

eSignature makes it easier to:
  • Quickly request signatures, see the status of pending signatures, and find completed contracts.
  • Sign an official contract right from Google Drive without having to switch apps or tabs.
  • Create a new copy of the contract for each request so that you can use your document as a template and initiate multiple eSignatures requests. 


Additional details

Later this year, we will introduce support for the following new eSignature capabilities:
  • Audit trail: all completed contracts will automatically contain an audit trail report.
  • Multi-signer: the ability to request a signature from more than one user.
  • Non-Gmail users: the ability to request an eSignature from non-Gmail users
  • Initiating eSignature on PDF: the ability to initiate an eSignature on PDF files stored in Drive

Beta availability for Google Workspace customers
Select Google Workspace editions (see the “Availability” section below) can apply to beta test eSignature using this form. This feature will be available as part of a larger beta, which includes access to new custom email layouts in Gmail. These new email layouts allow users to customize existing templates, reuse a custom layout in multiple email campaigns, or create a brand new layout from scratch. Once you sign up for the beta you will see the eSignature and new Gmail features in the coming weeks.


Getting started


Rollout pace

  • eSignature for Workspace Individual users
    • Gradual rollout (up to 15 days for feature visibility) starting on August 8, 2023
  • eSignature beta for Workspace customers:
    • We will be accepting beta applications and allowlisting customers over the next several weeks.

Availability

  • Available to Google Workspace individual subscribers
  • Eligible for beta: Google Workspace Business Standard, Business Plus, Enterprise Starter, Enterprise Standard, Enterprise Plus, Enterprise Essentials, Enterprise Essentials Plus, Education Plus, and Nonprofits customers


Resources


Beta Channel Release for ChromeOS / ChromeOS Flex

Hello All,

The Beta channel has been updated to 116.0.5845.52 (Platform version: 15509.37.0) for most ChromeOS devices.

If you find new issues, please let us know one of the following ways:

Interested in switching channels? Find out how.


Google ChromeOS

Import sensitive external files to Google Drive with client-side encryption using the Drive API, launching in beta

What’s changing 

For select Google Workspace editions, admins can import sensitive, encrypted files from third-party storage using Client-side encryption and the Google Drive API, preserving the confidentiality of your data. Eligible admins can apply for beta access using this form


Who’s impacted 

Admins 



Why it’s important 

Currently, client-side encryption allows for additional encryption by end users within Google Workspace. However, we know it’s critical for our customers and partners to import sensitive content into Google Drive on behalf of their users. With the launch of this beta functionality, admins will be able to easily bulk import files and keep them private with client-side encryption. 


Google Workspace already uses the latest cryptographic standards to encrypt all data at rest and in transit between our facilities. Client-side encryption helps strengthen the confidentiality of your data while helping to address a broad range of data sovereignty and compliance needs. Client-side encryption is already available for Google Drive, Google Docs, Sheets, and Slides, Google Meet, Google Calendar and Gmail. For more information, see our original announcement.


Getting started 

  • Admins: 
  • End users: There is no end user action required. 

Rollout pace 

  • We will be accepting beta applications and allowlisting customers over the next several weeks. 

Availability 

  • Available to Google Workspace Enterprise Plus, Education Standard, and Education Plus customers 

Resources 

What’s new in WindowManager 1.1.0-beta01

Posted by Jon Eckenrode, Technical Writer, Software Engineering blog header featuring Android logos

The 1.1.0-beta01 release of Jetpack WindowManager continues the library’s steady progress toward stable release of version 1.1.0. The beta adds an assortment of new features and capabilities, which are ready for testing and early adoption today!

We need your feedback so we can make WindowManager work best for you. Add the 1.1.0-beta01 dependency to your app, follow the migration steps below (if you’re already using a previous version of the library), and let us know what you think!

Activity embedding

androidx.window.embedding

Activity embedding enables you to optimize your multi-activity apps for large screens. The 1.1.0-beta01 release augments and refactors the APIs to provide greater versatility, capability, and control in managing task window splits. We started with experimental APIs in 1.0.0 and are promoting them ultimately to stable in 1.1.0.

tl;dr

Added a manifest setting so you can inform the system your app has implemented activity embedding. Refactored SplitController to be more focused on split properties; extracted split rule APIs to RuleController and activity embedding APIs to ActivityEmbeddingController. Added the SplitAttributes class to describe embedding splits. Added the EmbeddingAspectRatio class to set a minimum ratio for applying activity embedding rules. Changed pixels units to display-independent pixels (dp). Enabled customization of split layouts. Added a tag to rules so that developers can identify and manage specific rules.

What’s new

PROPERTY_ACTIVITY_EMBEDDING_SPLITS_ENABLED

  • Added as a boolean property of the <application> tag in the app manifest.

ActivityEmbeddingController

  • Added class for operations related to the Activity or ActivityStack classes.

  • Includes isActivityEmbedded() to replace the API in SplitController.

RuleController

  • Added class for operations related to the EmbeddingRule class and subclasses.
  • Includes the following APIs to replace APIs in SplitController:
    • addRule() — Adds a rule or updates the rule that has the same tag.
    • removeRule() — Removes a rule from the collection of registered rules.
    • setRules() — Establishes a collection of rules.
    • clearRules() — Removes all registered rules.
    • parseRules() — Parses rules from XML rule definitions.

          SplitAttributes

          • Added class to define the split layout.

          EmbeddingAspectRatio

          • Added class to define enum-like behavior constants related to display aspect ratio. Lets you specify when splits are enabled based on the parent window’s aspect ratio.

          See SplitRule for properties that use the constants.


          What’s changed

          EmbeddingRule

          • Added tag field for identification of split rules.

          SplitController
          • Refactored APIs to the following modules:
            • ActivityEmbeddingController
              • Moved isActivityEmbedded() to ActivityEmbeddingController.
            • RuleController
              • Removed the following APIs and replaced their functionality with RuleController APIs:
                • clearRegisteredRules()
                • getSplitRules()
                • initialize()
                • registerRule()
                • unregisterRule()
            • Deprecated isSplitSupported() method and replaced with splitSupportStatus property to provide more detailed information about why the split feature is not available.

            • The getInstance() method now has a Context parameter.

                    Note: The getInstance() methods of ActivityEmbeddingController and RuleController also have a Context parameter.
                    • Added SplitAttributes calculator functions to customize split layouts:
                      • setSplitAttributesCalculator()
                      • clearSplitAttributesCalculator()
                      • isSplitAttributesCalculatorSupported() to check whether the SplitAttributesCalculator APIs are supported on the device.

                    • Defined SplitSupportStatus nested class to provide state constants for the splitSupportStatus property. Enables you to modify app behavior based on whether activity embedding splits are supported in the current app environment.

                    SplitRule

                    • Added defaultSplitAttributes property which defines the default layout of a split; replaces splitRatio and layoutDirection.
                    • Added translation of the XML properties splitRatio and splitLayoutDirection to defaultSplitAttributes.
                    • Changed minimum dimension definitions to use density-independent pixels (dp) instead of pixels.
                      • Changed minWidth to minWidthDp with default value 600dp.
                      • Changed minSmallestWidth to minSmallestWidthDp with default value 600dp.
                      • Added minHeightDp property with default value 600dp.
                    • Added maxAspectRatioInHorizontal with default value ALWAYS_ALLOW.
                    • Added maxAspectRatioInPortrait with default value 1.4.
                    • Defined FinishBehavior nested class to replace finish behavior constants.
                    • Applied the property changes to the Builder nested class of SplitPairRule and SplitPlaceholderRule.

                        SplitInfo

                        • Replaced getSplitRatio() with getSplitAttributes() to provide additional split-related information.

                        Window layout

                        androidx.window.layout

                        The window layout library lets you determine features of app display windows. With the 1.1.0-beta01 release, you can now work in contexts other than just activities.

                        What’s changed

                        WindowInfoTracker

                        • Added non-activity UI context support in experimental.

                        WindowMetricsCalculator

                        • Added non-activity UI context support.

                        Migration steps

                        Take the next step and upgrade your app from a previous alpha version. And please let us know how we can further facilitate the upgrade process.

                        PROPERTY_ACTIVITY_EMBEDDING_SPLITS_ENABLED
                        • To enable activity embedding, apps must add the property to the <application> tag in the app manifest: 

                        < property android:name="android.window.PROPERTY_ACTIVITY_EMBEDDING_SPLITS_ENABLED" android:value="true" />

                        When the property is set to true, the system can optimize split behavior for the app early.


                        SplitInfo

                        • Check if the current split is stacked:

                        SplitInfo.splitAttributes.splitType is SplitAttributes.SplitType.ExpandContainersSplitType

                        • Check the current ratio:

                        if (SplitInfo.splitAttributes.splitType is SplitAttributes.SplitType.RatioSplitType) { val ratio = splitInfo.splitAttributes.splitType.ratio } else { // Ratio is meaningless for other types. }
                         

                        SplitController

                        • SplitController.getInstance()

                        changes to

                            SplitController.getInstance(Context)

                        • SplitController.initialize(Context, @ResId int)

                        changes to:

                        RuleController.getInstance(Context) .setRules(RuleController.parse(Context, @ResId int)) 
                        • SplitController.getInstance().isActivityEmbedded(Activity)
                        changes to:

                        ActivityEmbeddingController.getInstance(Context) .isActivityEmbedded(Activity)

                        • SplitController.getInstance().registerRule(rule)
                                  changes to:
                        RuleController.getInstance(Context).addRule(rule)

                        • SplitController.getInstance().unregisterRule(rule)

                        changes to:
                        RuleController.getInstance(Context).removeRule(rule)
                        • SplitController.getInstance().clearRegisteredRules()

                        changes to:
                        RuleController.getInstance(Context).clearRules()
                        • SplitController.getInstance().getSplitRules()

                        changes to:

                            RuleController.getInstance(Context).getRules() 


                        SplitRule

                        • Change minWidth to minWidthDp and minSmallestWidth to minSmallestWidthDp
                        • minWidthDp and minSmallestWidthDp now use dp units instead of pixels

                        Apps can use the following call:

                        TypedValue.applyDimension( COMPLEX_UNIT_DIP, minWidthInPixels, resources.displayMetrics )

                        or simply divide minWithInPixels by displayMetrics#density.  


                        SplitPairRule.Builder

                        • SplitPairRule.Builder( filters, minWidth, minSmallestWidth )

                        changes to:

                        SplitPairRule.Builder(filters) // Optional if minWidthInDp argument is 600. .setMinWidthDp(minWidthInDp) // Optional if minSmallestWidthInDp argument is 600. .setMinSmallestWidthDp(minSmallestWidthInDp)

                        • setLayoutDirection(layoutDirection) and setSplitRatio(ratio)

                        change to:

                        setDefaultSplitAttributes(SplitAttributes.Builder() .setLayoutDirection(layoutDirection) .setSplitType(SplitAttributes.SplitType.ratio(ratio)) .build() )

                        • setFinishPrimaryWithSecondary and setFinishSecondaryWithPrimary take the FinishBehavior enum-like constants.

                        See SplitRule migrations for details.

                        • Use:
                        setMaxAspectRatioInPortrait( EmbeddingAspectRatio.ALWAYS_ALLOW )
                        to show splits on portrait devices.

                        SplitPlaceholder.Builder

                        • Has only filters and placeholderIntent parameters; other properties move to setters.
                        See SplitPairRule.Builder migrations for details.  
                        • setFinishPrimaryWithPlaceholder takes the FinishBehavior enum-like constants.
                        See finish behavior migrations for details.

                        • setLayoutDirection(layoutDirection) and setSplitRatio(ratio)

                        change to 

                        setDefaultSplitAttributes(SplitAttributes.Builder() .setLayoutDirection(layoutDirection) .setSplitType(SplitAttributes.SplitType.ratio(ratio)) .build() )

                        See layout direction migrations for details.

                        • Use:

                        setMaxAspectRatioInPortrait( EmbeddingAspectRatio.ALWAYS_ALLOW )

                        to show splits on portrait devices.

                         
                        Finish behavior

                        Finish behavior constants must be migrated to FinishBehavior enum-like class constants:

                        • FINISH_NEVER changes to FinishBehavior.NEVER
                        • FINISH_ALWAYS changes to FinishBehavior.ALWAYS
                        • FINISH_ADJACENT changes to FinishBehavior.ADJACENT

                        Layout direction

                        Layout direction must be migrated to SplitAttributes.LayoutDirection:

                        • ltr changes to SplitAttributes.LayoutDirection.LEFT_TO_RIGHT
                        • rtl changes to SplitAttributes.LayoutDirection.RIGHT_TO_LEFT
                        • locale changes to SplitAttributes.LayoutDirection.LOCALE
                        • splitRatio migrates to SplitAttributes.SplitType.ratio(splitRatio)


                        Get started 

                        To get started with WindowManager, add the Google Maven repository to your app’s settings.gradle or project-level build.gradle file: 


                        dependencyResolutionManagement {

                            repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)

                            repositories {

                                google()

                            }

                        }

                         Then add the 1.1.0-beta01 dependency to your app’s module-level build.gradle file: 


                        dependencies {

                            implementation 'androidx.window:window:1.1.0-beta01'

                            . . .

                        }

                         Happy coding!

                        Launching in beta: manage working locations with the Calendar API

                        What’s changing

                        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.

                        Getting started


                        Admins and Developers: 

                        Admins: 

                        Availability

                        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 

                        Resources


                        Beta Channel Update for ChromeOS and Flex

                        The Beta channel is being updated to ChromeOS version: 15359.15.0 and Browser version: 112.0.5615.18 for some devices. This build contains a number of bug fixes and security updates and will be rolled out over the next couple days.

                        If you find new issues, please let us know one of the following ways

                        1. File a bug
                        2. Visit our ChromeOS communities
                          1. General: Chromebook Help Community
                          2. Beta Specific: ChromeOS Beta Help Community
                        3. Report an issue or send feedback on Chrome

                        Interested in switching channels? Find out how.


                        Google ChromeOS.

                        Beta Channel Update for ChromeOS and Flex

                        The Beta channel is being updated to ChromeOS version: 15359.15.0 and Browser version: 112.0.5615.18 for some devices. This build contains a number of bug fixes and security updates and will be rolled out over the next couple days.

                        If you find new issues, please let us know one of the following ways

                        1. File a bug
                        2. Visit our ChromeOS communities
                          1. General: Chromebook Help Community
                          2. Beta Specific: ChromeOS Beta Help Community
                        3. Report an issue or send feedback on Chrome

                        Interested in switching channels? Find out how.


                        Google ChromeOS.

                        Client-side encryption for Gmail available in beta

                        What’s changing

                        We’re expanding customer access to client-side encryption in Gmail on the web. Google Workspace Enterprise Plus, Education Plus, and Education Standard customers are eligible to apply for the beta until January 20th, 2022.

                        Using client-side encryption in Gmail ensures sensitive data in the email body and attachments are indecipherable to Google servers. Customers retain control over encryption keys and the identity service to access those keys.


                        Who’s impacted
                        Admins and end users



                        Why it’s important

                        Google Workspace already uses the latest cryptographic standards to encrypt all data at rest and in transit between our facilities. Client-side encryption helps strengthen the confidentiality of your data while helping to address a broad range of data sovereignty and compliance needs. 

                        Client-side encryption is already available for Google Drive, Google Docs, Sheets, and Slides, Google Meet, and Google Calendar (beta).


                        Getting started


                        • Admins: 
                          • Eligible Workspace customers can apply for the beta after completing a few steps to prepare your account.
                          • This feature will be OFF by default and can be enabled at the domain, OU, and Group levels (Admin console > Security > Access and data control > Client-side encryption). Visit the Help Center to learn more about client side encryption

                        • End users: To add client-side encryption to any message, click the lock icon and select additional encryption, and compose your message and add attachments as normal. Visit the Help Center to learn more about using Client-side encryption for Gmail.





                        Rollout

                        We will be accepting beta applications and allowlisting customers over the next several weeks.


                        Availability

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

                        Resources