Cloud Spreadsheet Add-In Custom Functions for Tenant Data Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing cloud platform office add-ins face limitations in accessing customer-specific data due to API requirements that restrict custom functions to be defined in a public landing page, preventing seamless integration and data access.
Innovation Solution
Implementing custom functions with pseudo implementations in the public landing page and full implementations in a private web application, allowing seamless integration and access to customer-specific data after authentication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If custom functions are defined in a public landing page as required by API, then add-in can be loaded automatically without explicit user installation, but the add-in cannot access customer-specific cloud platform data
Solution Approach 1:
The patent segments the add-in implementation into two distinct parts: a public landing page containing function declarations and a private web application containing data access logic. This segmentation allows the public portion to be freely accessible for automatic loading while the private portion maintains secure customer-specific data access capabilities.
Solution Approach 2:
The patent introduces an intermediary authentication mechanism that bridges the public landing page and private web application. The authentication system acts as a mediator, verifying user credentials and enabling seamless transition from the public interface to the private data access layer without requiring explicit installation.
2Adaptability or versatility
If add-in is locally installed on user computers, then custom functions can access customer data, but users must manually download and reinstall to get latest functionality
Solution Approach 1:
The patent implements a dynamic loading architecture where the add-in functionality is delivered on-demand through cloud-based web applications rather than static local installations. The spreadsheet application dynamically loads the latest version of the private web application whenever needed, ensuring users always access current functionality without manual reinstallation.
Solution Approach 2:
The patent performs preliminary authentication and setup actions through the public landing page before accessing the private application. This preliminary action establishes user credentials and permissions in advance, enabling seamless subsequent access to the latest functionality without requiring users to reinstall or reconfigure anything.
3Productivity
If custom functions are implemented in public landing page only, then add-in can be updated on demand, but cannot retrieve customer-specific cloud platform data
Solution Approach 1:
The patent segments functionality into public declarations and private implementations, allowing the public portion to be updated on-demand while the private portion maintains data access capabilities.
Solution Approach 2:
The authentication system serves as an intermediary that enables the public landing page to access the private web application's data retrieval capabilities without compromising security or requiring local installation.
Data Source
AI summary
The present disclosure involves systems, software, and computer implemented methods for enabling custom formulas in a cloud platform office add-in. An example method includes automatically loading a public landing page of a cloud platform add-in of a spreadsheet application. The public landing page includes a declaration and a first implementation of at least one custom function. Login credentials for a customer tenant of the cloud platform are obtained. A redirect is performed to a private web application for the customer tenant. The private web application includes, for each custom function, a second implementation that is configured to retrieve customer-specific cloud platform data of the customer tenant. Each first implementation of a custom function is replaced with the second implementation of the custom function. In response to a user request in the spreadsheet application to use a first custom function, the second implementation of the custom function is invoked.