Skip to content

Release Validation Log

This document tracks test coverage, validation scenarios, and release checks for each release of Google Client for Salesforce. The goal is to ensure that all critical features, integrations, and edge cases are tested when creating a new version.

Release v2.1.0

Validation Suite Used

  • Full Validation Suite
  • Quick Regression Suite
  • Targeted Regression Suite

Release Changes

  • Change 1: The upgrade lands on an already configured org without disturbing it, and the Advanced screen is now split into four tabs.

    • Existing Google Drive, folder structure, and AI settings are unchanged after the upgrade.
    • Settings introduced in this release are empty, and the app behaves exactly as it did before.
    • Advanced opens on File Management, User Interface, AI Intelligence, and Safety & Customization, and each tab renders without errors.
    • [-] Org Cache is allocated to the GoogleCloudClient Platform Cache partition.

  • Change 2: Administrators choose which columns appear in File Explorer and in what order.

    • Columns can be selected and reordered in Advanced → User Interface, and the selection is saved.
    • Title stays first and cannot be removed, and no more than 7 columns can be selected.
    • A valid Google File Version field API name added as a custom column shows its values in the list.
    • An invalid field API name renders an empty column and the list still loads.
    • Restoring the default selection brings back the original columns.

  • Change 3: File Explorer loads long lists progressively, and search and sorting apply to every accessible file.

    • The first page renders without loading the whole list, and more rows are appended when scrolling to the bottom.
    • Scrolling to the end of a long list produces no repeated rows and no missing rows.
    • Searching by part of a file name finds files that had not been loaded yet.
    • Sorting by Title and by Last Modified Date stays correct across page boundaries.
    • Type, Size, Summary, and Access cannot be sorted.
    • The Owner column shows the real owner as a name, including for a file owned by a public group or a queue.

  • Change 4: View All and Edit All custom permissions give a support or compliance user visibility of every file.

    • With Google Client: View All Files assigned, a single All Files view replaces Owned and Shared, and files owned by other users are listed with View access.
    • Search and sorting work across that whole list.
    • With Google Client: Edit All Files assigned instead, access shows Edit and edit-level actions are available on a file owned by someone else.
    • An external user gains nothing from either permission.
    • Removing both assignments returns the user to Owned and Shared, and other users' files disappear again.

  • Change 5: Google Files are returned by Salesforce global search and open on the Google Client file details page.

    • A file is returned by global search and opens on the Google Client page rather than a standard record layout.
    • Standard record buttons and the highlights panel are not shown.
    • The same page opens when the file URL is entered directly.
    • A user without access to the file cannot open it by URL.
    • The Salesforce record name is shown in full on the file details page and in Linked Records, including for a record whose name is assembled from several fields, such as a Contact.

  • Change 6: One Google Drive folder is created per record, even when several files or several users arrive at once.

    • With Folder per Record configured, uploading several files at once to a record that has no folder yet creates exactly one folder, and every file of that upload is placed in it.
    • Two users uploading to the same new record at the same time do not create a second folder.
    • A record that already has duplicated folders receives every new file into the same one of them.
    • Attaching an existing file to a record with no folder yet creates the record folder under the configured upload folder, and not inside the folder the attached file already lived in.

  • Change 7: More than one upload folder can be configured, in priority order.

    • A second folder can be added under Folder Locations, and up to ten are accepted.
    • Uploads are placed in the first folder in the list, and the configured folder structure is created inside it.
    • After reordering, new uploads go to the newly promoted first folder.
    • Files already stored in another folder stay where they are and remain reachable from Salesforce.

  • Change 8: Direct Browser Upload sends large file content straight to Google Drive, and falls back safely when it cannot.

    • The setting is off after the upgrade, and large uploads behave exactly as before.
    • Test connection succeeds and leaves no file behind in Google Drive.
    • With the setting on, a file larger than 100 MB completes and lands in the configured folder, and a file under 2 MB is unaffected.
    • Folder structure, versioning, and preview behave the same as for a standard upload.
    • With the GoogleDriveDirectUpload CSP Trusted Site deactivated, the Uploader offers a retry through Salesforce on the file card, and accepting it completes the upload.
    • The same failure in the Attachments upload window offers the retry at the bottom of the window.
    • Turning the setting back off leaves large uploads working from the Uploader, Attachments, and File Explorer.
    • Logs tagged Google Client for Salesforce show the expected outcomes and no unexpected errors.

  • Change 9: Questions and answers are inspected before they leave and re-enter Salesforce.

    • Standard is the active mode when nothing was chosen, and the safety settings are disabled while File Intelligence is off.
    • A normal question about the document is answered.
    • An attempt to make the model ignore its instructions is refused with a readable message, and the preview keeps working.
    • A request to reveal the configuration or system prompt is refused.
    • With the mode set to Off, questions pass through without inspection.
    • An unknown class name in Custom AI Prompt Safety Guard Class falls back to the shipped protection rather than leaving questions unprotected.
    • Searching File Explorer for a word that appears in a file's summary but not in its name finds that file.

Boring Changes

  • Version number assigned to all hard-coded labels
  • Version ID is assigned to all installation guides.

Smoke Checks

  • Internal user (Core Cloud) can open Lightning record pages containing Google Client components without errors
  • External user (Experience Cloud) can open Experience Cloud pages containing Google Client components without errors
  • Admin can open Google Client app and browse configuration tabs without errors

Suite Execution (only for Full or Quick)

  • Suite execution completed successfully. No critical defects were identified that would block creating a new version.

Notes

  • On certain Experience Cloud sites, modal actions such as Share and Download As are displayed beneath the preview window, making them inaccessible. A bug will be created to address this issue.
  • Platform Cache is not allocated automatically when installing or upgrading the package. This remains a known issue listed on the Help page. Unfortunately, there is nothing we can do to address it as part of the unlocked package, so allocating Platform Cache remains a manual step. Note: Even without Platform Cache, most functionality continues to work as expected, except for the View All button in the Attachments component.
Release v2.0.0

Validation Suite Used

  • Full Validation Suite
  • Quick Regression Suite
  • Targeted Regression Suite

Release Changes

  • Change 1: When an existing Google Client file is attached to another Salesforce record and Folder Structure includes a record folder, Google Client creates a Google Drive shortcut in the resolved folder for the newly linked record.

    • With no folder structure configured, attaching an existing file does not create a record shortcut.
    • With Folder per User configured, attaching an existing file does not create a record shortcut.
    • With Folder per Record configured, attaching an existing file creates a shortcut in the resolved record folder.
    • With Folder per User → Record configured, attaching an existing file creates a shortcut in the resolved nested record folder.
    • With Folder per Record → User configured, attaching an existing file creates a shortcut in the resolved nested user folder.
    • Google Docs / Workspace conversion works correctly together with folder structure chaining.

  • Change 2: Preview modal supports Download as... for previewable files and hides the action for non-previewable files.

    • Download as... is available for PDF files.
    • Download as... is available for document files.
    • Download as... is available for image files.
    • Download as... is not visible for non-previewable files.

  • Change 3: Google Client stores AI-generated document summaries in Salesforce and displays them on hover and in the preview sidebar.

    • Document summary is generated and stored in Salesforce when Gemini is configured.
    • Document summary is generated and stored in Salesforce when Agent Platform / Vertex is configured.
    • Summary appears on hover where supported.
    • Summary appears in the preview sidebar.
    • When no AI provider is configured, preview opens without broken or empty AI summary UI.

  • Change 4: Preview modal supports file Q&A when Gemini or Agent Platform / Vertex is configured and Q&A / analysis is enabled.

    • With Gemini configured and Q&A / analysis enabled, user can ask questions about the file.
    • With Agent Platform / Vertex configured and Q&A / analysis enabled, user can ask questions about the file.
    • Answers are related to the currently opened file.
    • With Q&A / analysis disabled, Q&A is not available even when Gemini is configured.
    • With Q&A / analysis disabled, Q&A is not available even when Agent Platform / Vertex is configured.
    • Q&A respects configured prompts and token limits.

  • Change 5: Admin configuration supports AI prompts and token limits for summaries and file questions.

    • Admin can save the summary prompt.
    • Admin can save the question-answering prompt.
    • Admin can save token limits.
    • Saved summary prompt is used when generating summaries.
    • Saved question-answering prompt is used when answering file questions.
    • Existing Google Drive functionality continues to work after AI configuration changes.

  • Change 6: Existing Google files can be attached to multiple Salesforce records, and the File Record Details page shows linked Salesforce records.

    • User can attach an existing owned Google file to another Salesforce record.
    • User can attach the same existing Google file to multiple Salesforce records.
    • Files not owned by the current user are not available for selection.
    • The same Google Client file appears on all linked Salesforce records.
    • File Record Details page shows all linked Salesforce records the current user is allowed to see.
    • Attaching the same existing file to multiple records creates correct Salesforce associations and does not incorrectly duplicate the main Google Client file record.
    • Deleting a Google Client file removes all related record associations.
    • Security layer resolves access correctly when a file is linked to multiple records.

  • Change 7: Large image files can be previewed without relying only on Google Workspace preview generation.

    • Large image preview works from the Attachments component.
    • Large image preview works from the Uploader component.
    • Large image preview works from the View All page.
    • Large image preview works from File Explorer where applicable.
    • Large image preview works when Google Workspace preview generation is unavailable or unreliable.
    • Existing PDF, CSV, document, and regular image previews continue to work.

  • Change 8: File version handling continues to work correctly after the file/version refactoring.

    • latestVersion is set correctly after uploading a new file.
    • latestVersion is set correctly after replacing a file.
    • latestVersion is set correctly after attaching an existing file.
    • latestVersion is set correctly after uploading a new version.

Boring Changes

  • Version number assigned to all hard-coded labels
  • Version ID is assigned to all installation guides.

Smoke Checks

  • Internal user (Core Cloud) can open Lightning record pages containing Google Client components without errors
  • External user (Experience Cloud) can open Experience Cloud pages containing Google Client components without errors
  • Admin can open Google Client app and browse configuration tabs without errors

Suite Execution (only for Full or Quick)

  • Suite execution completed successfully. No critical defects were identified that would block creating a new version.

Notes

  • During testing, I identified an issue where, when the share type for a link was set to “None”, the file disappeared from the list completely for everyone: the owner and explicitly shared users. None of them could see it. The only way to access it was through File Explorer, but even there, when opening the “Share” modal window, the record was not displayed. This problem was fixed as I continued testing, and everything looks good now.
  • A few security layer changes were made because files were not being displayed correctly for the appropriate users. After the fixes, everything looks good.
  • One small defect was found: when the Uploader component has reached the maximum number of allowed files, adding existing files does not respect this limit. As a result, users can attach more existing files than allowed. A defect will be created for this and included in a future release.
Hotfix v1.3.2

Validation Suite Used

  • Full Validation Suite
  • Quick Regression Suite
  • Targeted Regression Suite

Release Changes

  • Fixed 1: When Google Client is configured to use a dedicated folder per record, uploading multiple files to a record that does not yet have any Google files creates multiple Google Drive folders for the same record. This issue appears to happen only when multiple files are uploaded at once and the record does not already have a resolved folder. After the first upload is completed, subsequent uploads to the same record are stored in a single folder as expected. For reference: https://github.com/sandriiy/salesforce-google-client/issues/68

Boring Changes

  • Version number assigned to all hard-coded labels
  • Version ID is assigned to all installation guides.

Smoke Checks

  • Internal user (Core Cloud) can open Lightning record pages containing Google Client components without errors
  • External user (Experience Cloud) can open Experience Cloud pages containing Google Client components without errors
  • Admin can open Google Client app and browse configuration tabs without errors

Specific Checks

  • With Folder Structure not configured at all, a regular user uploaded single, multiple, small, and large files from Attachments, Uploader, and File Explorer without any issues. Uploaded files stayed in the root Google Drive folder, and no sub-folder was created.
  • After admin changed Folder Structure to Folder per User, a regular user uploaded files from all three places without any issues. Uploaded files were placed in that user’s own folder.
  • With Folder per User configured, a regular user shared files with another internal user using both Viewer and Collaborator access. The second user was able to access those files, and when he uploaded his own file, it was placed in his own separate user folder.
  • After admin changed Folder Structure to Folder per Record, a regular user uploaded files from all three places without any issues. Files uploaded to records were placed in the folder created for the related record. The user tested several Account records, and only one folder was created per record.
  • Another internal user uploaded files to a record where the folder had already been created by the first user. New files were placed in the same existing record folder, and no duplicate folder was created.
  • After admin changed Folder Structure to Folder per Record → Folder per User, a regular user uploaded files from all three places without any issues. Files were placed inside the related record folder, under a sub-folder created for that user.
  • After admin changed Folder Structure to Folder per User → Folder per Record, a regular user uploaded files from all three places without any issues. Files were placed inside the user folder, under sub-folders created for each related record.
  • A user shared several files with an external user. The external user was able to see those files. After more single and multiple files were uploaded, all new files were placed in the already existing folder.

Notes

  • As part of this hotfix, I also fixed an issue where files uploaded from the File Explorer component, which means without a record ID, could still trigger the asynchronous Google Drive folder-structure job to create a User folder, even when the User folder option was not enabled in the "Google Client" settings. Since this behavior does not seem to match the expected configuration, the job now respects the folder-structure settings. If the User folder is not selected, it will not be created.
Hotfix v1.3.1

Validation Suite Used

  • Full Validation Suite
  • Quick Regression Suite
  • Targeted Regression Suite

Release Changes

  • Fixed 1: Create a new organization where Experience Cloud is fully disabled under Digital Experiences → Settings. Upload a new file and verify that it can be shared without errors.
  • Fixed 2: Create a new user with the Salesforce license and Standard User profile, then assign the Google Cloud Client Admin permission set. Open the Google Client application and verify that the user can access the Analytics tab and view the dashboard inside it.

Boring Changes

  • Version number assigned to all hard-coded labels
  • Version ID is assigned to all installation guides.

Smoke Checks

  • Internal user (Core Cloud) can open Lightning record pages containing Google Client components without errors
  • External user (Experience Cloud) can open Experience Cloud pages containing Google Client components without errors
  • Admin can open Google Client app and browse configuration tabs without errors

Notes

  • When promoting a new package version, if the installation fails, unassign the Google Cloud Client Admin permission set from all users, then try the installation again.
Release v1.3.0

Validation Suite Used

  • Full Validation Suite
  • Quick Regression Suite
  • Targeted Regression Suite

Release Changes

  • Change 1: Verified the new Gemini & Agent Platform configuration (picklist option) in the Google Client app: confirmed both tabs are present and functional: Gemini API for Developers and Gemini Agent Platform (ex-Vertex AI). For each tab, confirmed all required integration fields are present and can be saved and validated successfully. Confirmed the app is visible only to users with the Google Cloud Client Admin permission and is not accessible to users without it.
  • Change 2: Verified that a Collaborator (non-owner) can successfully upload a new version and share a file: confirmed both actions complete without access errors for internal users and Experience Cloud external users.
  • Change 3: Verified large file preview for PDF files: confirmed that the large PDF opens in the preview modal successfully, and that the setting previously labeled "Default Big File Size" is now labeled "Maximum Preview File Size" across all configuration areas. Verified the behavior is consistent across all Google Client components.
  • Change 4: Verified that non-admin users (without System Administrator profile or View All Data permission) can open "Edit File Details" from the file preview without errors: confirmed the action completes successfully for both internal and Experience Cloud external users.
  • Change 5: Verified the actions dropdown in the file preview header on an LWR Experience Cloud site: confirmed menu items are readable and the dropdown does not render with black text on a black background for external users.
  • Change 6: Verified CSV file preview: confirmed that a CSV file opens in the preview modal and displays its content in a readable format. Confirmed that Download and other existing file actions continue to work for CSV files as they do for other supported file types.
  • Change 7: Verified Nebula Logger improvements: confirmed that Command classes produce logs with relevant transaction context (record ID, input parameters, received data) and that all logs include the DEFAULT_LOGGER_TAG. Confirmed the service layer saves the accumulated log when an exception occurs. Verified the new "Google Client: Analytics" Lightning tab is accessible and loads without errors, and that the "Logger Admin Dashboard" in the "Google Client: Analytics" folder displays log data filtered to this client.

Boring Changes

  • Version number assigned to all hard-coded labels
  • Version ID is assigned to all installation guides.

Smoke Checks

  • Internal user (Core Cloud) can open Lightning record pages containing Google Client components without errors
  • External user (Experience Cloud) can open Experience Cloud pages containing Google Client components without errors
  • Admin can open Google Client app and browse configuration tabs without errors

Suite Execution (only for Full or Quick)

  • Suite execution completed successfully. No critical defects were identified that would block creating a new version.

Notes

  • There is a scenario where, if an external user creates a file and an internal user tries to share it with someone else or make other changes, it causes an error ("INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY"). This scenario does not violate the visibility or security layer, so it is not considered a problem at this time.
  • The GoogleClientConfig__mdt record (GoogleClient) was removed from the package in this release. In previous versions, the package shipped a pre-built record that Salesforce re-deployed on every upgrade as a full overwrite, silently wiping any values configured by the subscriber (certificate name, service account email, API keys, etc.). Removing it from the package prevents this data loss permanently. As a side effect, customers upgrading from a previous version may see a deprecation warning on the record in Setup — this is expected, harmless, and requires no action. See Known Issues for details.
Release v1.2.0

Validation Suite Used

  • Full Validation Suite
  • Quick Regression Suite
  • Targeted Regression Suite

Release Changes

  • Change 1: Verified the Google Client lightning app is in a healthy working state: user can authorize successfully, admin/developer settings load correctly, and updated metadata values save as expected, including Main Upload Folder ID, Folder Structure selection, and the Organizational Domain value in the Advanced section.
  • Change 2: Verified Folder Structure behavior in Google Client across supported structures (Main Upload Folder only, User, User → Record, Record → User, Record): for each structure, uploading a file creates the expected folder(s) under the Main Upload Folder and places the file in the correct location. Tested using one standard object and one custom object to confirm consistency.
  • Change 3: Verified the Organizational Domain field behavior in the Public Link flow: when an Organizational Domain is configured, the Public Link window displays a new checkbox that controls link scope (unchecked = domain-restricted link, checked = global link). Confirmed the user still has the ability to create a global public link, while the default behavior is domain-restricted.
  • Change 4: Verified the new Share Type option in the Share modal: from the Preview window, clicked Share (at the top), selected the record the file is attached to, and confirmed the Share Type picklist includes a new value "None". When "None" is selected, confirmed record-based access does not grant visibility to the file and only explicitly shared users can see it. Validated by explicitly sharing the file to another user, logging in as that user, and confirming behavior for both internal and external users.
  • Change 5: Verified collaborator limitations messaging in the Share modal: shared a file to another user as Collaborator, then opened the Share modal (via Preview) as that collaborator and confirmed a new informational message appears indicating the user has collaborator access, some sharing actions may be limited, and the user should contact the file owner (visible in the list) if changes cannot be applied.
  • Change 6: Verified File Explorer tab behavior for internal users with Google Client user permissions: confirmed a "File Explorer" tab appears in the top-left navigation and opens in a new tab with two left-sidebar items (Owned by Me, Shared with Me). Confirmed "Owned by Me" lists all files uploaded by the current user and includes a datatable indicator showing whether each file is attached to a record; validated the indicator by removing the record link via the Share modal (without deleting the file) and confirming the UI reflects the correct attached/not-attached state. Confirmed the user can upload a new file directly from File Explorer (no file type/size restrictions enforced by the UI), and that the upload completes successfully without linking the file to any record. Confirmed Preview actions work end-to-end for owned files (Share, Public Link, Rename, Edit, Download, Upload New Version). Confirmed "Shared with Me" lists files shared to the current user; validated by logging in as another user, uploading a file to a record, sharing it to the target user, then logging in as the target user and confirming it appears. Confirmed permission levels are reflected correctly in the UI (Viewer = read-only, Collaborator = edit access), and confirmed Owned files always remain editable for the owner.
  • Change 7: Verified Experience Cloud behavior on record detail pages: configured required custom pages, added the Attachments component to the record detail page, uploaded a file, clicked "View All", and confirmed the opened page/component shows the correct object label (e.g., "Account") and the record name in the top-left header area.

Boring Changes

  • Version number assigned to all hard-coded labels
  • Version ID is assigned to all installation guides.

Smoke Checks

  • Internal user (Core Cloud) can open Lightning record pages containing Google Client components without errors
  • External user (Experience Cloud) can open Experience Cloud pages containing Google Client components without errors
  • Admin can open Google Client app and browse configuration tabs without errors

Suite Execution (only for Full or Quick)

  • Suite execution completed successfully. No critical defects were identified that would block creating a new version. For detailed coverage, see the Validation Suites tab to review exactly what was tested.

Notes

  • The System Administrator has access to functionality even if the "Google Cloud Client User" permission set is not assigned to the user.
  • A new bug related to UI/UX file preview has been created, see here
  • A new bug related to the "Edit File Details" window (from preview) has been created, see here
  • A new bug related to the security layer has been created, see here