IP Library Granted Patent US 11,615,376
Granted Patent B2
US 11,615,376 · App. 16/671,857 · Granted Mar 28, 2023

Techniques for managing functionality changes of an on-demand database system

Inventors: Eric D. Bezar (Oakland, CA); Sonali Agrawal (San Carlos, CA); Varadarajan Rajaram (San Francisco, CA); Walter Macklem (San Francisco, CA); Jill Blue Lin (San Francisco, CA); Sriram Gopalan (Foster City, CA); Sandip Ghosh (San Francisco, CA)
Assignee: salesforce.com, inc.
G06Q10/10G06F11/3672G06F16/21
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,615,376
App. No.
16/671,857
Granted
Mar 28, 2023
Kind
B2
Abstract

In accordance with embodiments, there are provided techniques for managing functionality changes of a database platform of a service provider. The techniques facilitate implementing changes to the database platform while minimizing work flow reductions to users of the database platform. To that end, one embodiment of the present invention delays implementation of the changes for a duration of time to provide users of the database platform an opportunity to adjust behavioral interaction with the database platform. In accordance with another embodiment of the present invention, users may implement the functional changes to determine any adverse impact on work flow, before the functional changes become permanent. In another embodiment, the users may be afforded an opportunity to selectively enable and disable the functionality changes before the duration of time expires.

Claims (48)

1. A method comprising:

identifying functional changes to be made to a database platform of a service provider by or on behalf of the service provider, wherein the database platform supports a plurality of tenants;

identifying a tenant-specific production environment, within the database platform, impacted by the functional changes, the tenant-specific production environment being associated with one of the plurality of tenants supported by the database platform; and

responsive to identifying the tenant-specific production environment impacted by the functional changes, providing users of the associated tenant an opportunity to assess an effect of the functional changes on the tenant-specific production environment prior to the functional changes being installed in the tenant-specific production environment by:

copying tenant-specific business logic, functional changes and at least a portion of the tenant-specific production environment impacted by the functional changes to a tenant-specific test and development environment of the tenant;

and

notifying at least one of the users regarding the functional changes, including providing information regarding the functional changes and information regarding a point in time at which the functional changes will be deployed to the tenant-specific production environment;

prior to the point in time at which the functional changes will be deployed to the tenant-specific production environment, testing the functional changes within the tenant-specific test and development environment;

and

on or after the point in time at which the functional changes will be deployed to the tenant-specific production environment, deploying the functional changes to the tenant-specific production environment.

2. The method of claim 1 , wherein the tenant-specific production environment is impacted by the functional changes as a result of the tenant specific business logic customizing functionality of a database of the database platform.

3. The method of claim 2 , wherein the tenant-specific business logic includes configuration information and customization information specified by the tenant and wherein the tenant-specific production environment provides customized functionality of one or more of: third party applications of the tenant or the database to the users based on the tenant-specific business logic.

4. The method of claim 2 , wherein the tenant-specific business logic includes third party applications.

5. The method of claim 1 , wherein said notifying comprises providing the information regarding the functional changes and the information regarding the point in time at which the functional changes will be deployed via a graphical interface of a user system.

6. The method of claim 5 , wherein the graphical interface is displayed responsive to a user accessing the database platform.

7. The method of claim 5 , wherein said notifying is in a form of a critical update console included in a set-up page or a configuration page of the graphical interface.

8. The method of claim 5 , further comprising providing via the graphical interface an option for the tenant to indicate to the service provider that deployment of the functional changes need not be delayed.

9. The method of claim 5 , further comprising providing via the graphical interface concurrent with access by a user to the tenant-specific production environment and the tenant-specific test and development environment.

10. A non-transitory computer-readable medium having stored thereon instructions that, when executed by one or more processors of a database platform of a service provider, cause the one or more processors to:

identify functional changes to be made to the database platform by or on behalf of the service provider, wherein the database platform supports a plurality of tenants;

identify a tenant-specific production environment, within the database platform, impacted by the functional changes, the tenant-specific production environment being associated with one of the plurality of tenants supported by the database platform; and

responsive to identifying the tenant-specific production environment impacted by the functional changes, provide users of the associated tenant an opportunity to assess an effect of the functional changes on the tenant-specific production environment prior to the functional changes being installed in the tenant-specific production environment by:

copying tenant-specific business logic, functional changes and at least a portion of the tenant-specific production environment impacted by the functional changes to a tenant-specific test and development environment of the tenant; and

notifying at least one of the users regarding the functional changes, including providing information regarding the functional changes and information regarding a point in time at which the functional changes will be deployed to the tenant-specific production environment;

prior to the point in time at which the functional changes will be deployed to the tenant-specific production environment, test the functional changes within the tenant-specific test and development environment;

and

on or after the point in time at which the functional changes will be deployed to the tenant-specific production environment, deploy the functional changes to the tenant-specific production environment.

11. The non-transitory computer-readable medium of claim 10 , wherein the tenant-specific production environment is impacted by the functional changes as a result of the tenant specific business logic customizing functionality of a database of the database platform.

12. The non-transitory computer-readable medium of claim 11 , wherein the tenant-specific business logic includes configuration information and customization information specified by the tenant and wherein the tenant-specific production environment provides customized functionality of one or more of third party applications of the tenant or the database to the users based on the tenant-specific business logic.

13. The non-transitory computer-readable medium of claim 11 , wherein the tenant-specific business logic includes third party applications.

14. The non-transitory computer-readable medium of claim 10 , wherein said notifying comprises providing the information regarding the functional changes and the information regarding the point in time at which the functional changes will be deployed via a graphical interface of a user system.

15. The non-transitory computer-readable medium of claim 14 , wherein the graphical interface is displayed responsive to a user accessing the database platform.

16. The non-transitory computer-readable medium of claim 14 , wherein said notifying is in a form of a critical update console included in a set-up page or a configuration page of the graphical interface.

17. The non-transitory computer-readable medium of claim 14 , wherein the instructions further cause the one or more processors to provide via the graphical interface an option for the tenant to indicate to the service provider that deployment of the functional changes need not be delayed.

18. The non-transitory computer-readable medium of claim of claim 14 , wherein the instructions further cause the one or more processors to provide via the graphical interface concurrent with access by a user to the tenant-specific production environment and the tenant-specific test and development environment.

19. A system, comprising:

one or more processors; and

a memory, the processors configurable to:

identify functional changes to be made to the database platform by or on behalf of the service provider, wherein the database platform supports a plurality of tenants;

identify a tenant-specific production environment, within the database platform, impacted by the functional changes, the tenant-specific production environment being associated with one of the plurality of tenants supported by the database platform; and

responsive to identifying the tenant-specific production environment impacted by the functional changes, provide users of the associated tenant an opportunity to assess an effect of the functional changes on the tenant-specific production environment prior to the functional changes being installed in the tenant-specific production environment by:

copying tenant-specific business logic, functional changes and at least a portion of the tenant-specific production environment impacted by the functional changes to a tenant-specific test and development environment of the tenant; and

notifying at least one of the users regarding the functional changes, including providing information regarding the functional changes and information regarding a point in time at which the functional changes will be deployed to the tenant-specific production environment;

prior to the point in time at which the functional changes will be deployed to the tenant-specific production environment, test the functional changes within the tenant-specific test and development environment;

and

on or after the point in time at which the functional changes will be deployed to the tenant-specific production environment, deploy the functional changes to the tenant-specific production environment.

20. The system of claim 19 , the processors further configurable to:

facilitate testing the functional changes within the tenant-specific test and development environment of the tenant.

Assignments (2)
CHANGE OF NAME Recorded Dec 18, 2024
From: SALESFORCE.COM, INC.
To: SALESFORCE, INC.
Reel/Frame 069717/0452 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 25, 2020
From: BEZAR, ERIC D.; AGRAWAL, SONALI; RAJARAM, VARADARAJAN; MACKLEM, WALTER; LIN, JILL BLUE; GOPALAN, SRIRAM; GHOSH, SANDIP
To: SALESFORCE.COM, INC.
Reel/Frame 051925/0596 →
Continuity (2)
Continuation 12569603 · Sep 29, 2009
Related Publication 20200065764A1 · Feb 27, 2020