IP Library Granted Patent US 10,146,510
Granted Patent B2
US 10,146,510 · App. 13/933,776 · Granted Dec 4, 2018

Custom metametadata with packagable records

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 10,146,510
App. No.
13/933,776
Granted
Dec 4, 2018
Kind
B2
Abstract

Techniques for providing custom metadata in a multi-tenant database environment in which hardware and software of the multi-tenant database system is shared by one or more organizations, each having one or more corresponding users. Each of the organizations has associated organization data and organization metadata. Activating procedural code is triggered in response to a trigger event determined by a platform interface. The procedural code is to query the organization metadata provided by the associated organization through a metadata interface provided by a platform developer. The platform interface is provided by the platform developer and the procedural code utilizes compile time dependencies to generate custom metametadata to be maintained by the platform developer and to be provided to the organizational metadata, which is to be maintained by the corresponding organization. The organization data owned by the organization is written to with the procedural code in response to results of the query.

Claims (33)

1. A method for utilizing metametadata, the metametadata comprising custom metadata about metadata in a multitenant database environment provided via a platform in which hardware and software of the multi-tenant database system is shared by two or more organizations, each having one or more corresponding users, wherein each of the two or more organizations has associated organization data and organization metadata and organization metametadata, the method comprising:

coupling a trigger to procedural code using the metadata, wherein the trigger does not specify an entity at compile time;

triggering, in response to a trigger event determined by a standard platform interface, the procedural code to query the organization metadata provided by the associated organization through a metadata interface provided by a platform developer, wherein the standard platform interface is provided by the platform developer and the procedural code utilizes one or more compile time dependencies to generate custom metametadata, which is to be maintained by the platform developer;

generating the metametadata utilizing a declarative feature to determine the form the metametadata takes for a corresponding tenant within the multi-tenant database, wherein one or more tenants in the multitenant environment generate custom records of an object provided by the platform developer and the metametadata is utilized to provide functionality to the tenant; and

writing to the organization data owned by the organization using the custom records with the procedural code.

2. The method of claim 1 , wherein the procedural code is provided by a platform developer.

3. The method of claim 1 , wherein the trigger event comprises receiving user input.

4. The method of claim 1 , wherein the trigger event comprises insertion of data.

5. The method of claim 1 , wherein the procedural code comprises a portion of a time-based workflow.

6. The method of claim 1 , wherein the procedural code comprises an inbound service call.

7. The method of claim 1 , wherein writing the data comprises one or more of a user interface (UI) modification, a message trigger, and a message integration.

8. An article of manufacture comprising a non-transitory computer-readable medium having instructions to cause one or more processors to provide metametadata, the metametadata comprising custom metadata about metadata in a multi-tenant database environment in which hardware and software of the multi-tenant database system is shared by two or more organizations, each having one or more corresponding users, wherein the custom metadata comprises data about metadata and each of the two or more organizations has associated organization data and organization metadata and organization metametadata, the instructions to:

couple a trigger to procedural code using the metadata, wherein the trigger does not specify an entity at compile time;

trigger, in response to a trigger event determined by a standard platform interface, procedural code to query the organization metadata provided by the associated organization through a metadata interface provided by a platform developer, wherein the standard platform interface is provided by the platform developer and the procedural code utilizes one or more compile time dependencies to generate custom metametadata, which is to be maintained by the platform developer;

generate the metametadata utilizing a declarative feature to determine the form the metametadata takes for a corresponding tenant within the multi-tenant database, wherein one or more tenants in the multitenant environment generate custom records of an object provided by the platform developer and the metametadata is utilized to provide functionality to the tenant; and

write to the organization data owned by the organization using the custom records with the procedural code.

9. The article of manufacture of claim 8 wherein the procedural code is provided by a platform developer.

10. The article of manufacture of claim 8 , wherein the trigger event comprises receiving user input.

11. The article of manufacture of claim 8 , wherein the trigger event comprises insertion of data.

12. The article of manufacture of claim 8 , wherein the procedural code comprises a portion of a time-based workflow.

13. The article of manufacture of claim 8 , wherein the procedural code comprises an inbound service call.

14. The article of manufacture of claim 8 , wherein writing the data comprises one or more of a user interface (UI) modification, a message trigger, and a message integration.

15. A system comprising one or more computing devices to provide a multi-tenant database environment in which hardware and software of the multi-tenant database system is shared by two or more organizations, each having one or more corresponding users, wherein the functions to utilize metametadata, the metametadata comprising custom metadata comprises data about metadata and each of the two or more organizations has associated organization data and organization metadata and organization metametadata, and the hardware components of the system

couple a trigger to procedural code using the metadata, wherein the trigger does not specify an entity at compile time;

trigger, in response to a trigger event determined by a standard platform interface, procedural code to query the organization metadata provided by the associated organization through a metadata interface provided by a platform developer, wherein the standard platform interface is provided by the platform developer and the procedural code utilizes one or more compile time dependencies to generate custom metametadata, which is to be maintained by the platform developer;

generate the metametadata utilizing a declarative feature to determine the form the metametadata takes for a corresponding tenant within the multi-tenant database, wherein one or more tenants in the multitenant environment generate custom records of an object provided by the platform developer and the metametadata is utilized to provide functionality to the tenant; and

write to the organization data owned by the organization using the custom records with the procedural code.

16. The system of claim 15 , wherein the procedural code is provided by a platform developer.

17. The system of claim 15 , wherein the trigger event comprises receiving user input.

18. The system of claim 15 , wherein the trigger event comprises insertion of data.

19. The system of claim 15 , wherein the procedural code comprises a portion of a time-based workflow.

20. The system of claim 15 , wherein the procedural code comprises an inbound service call.

21. The system of claim 15 , wherein writing the data comprises one or more of a user interface (UI) modification, a message trigger, and a message integration.

Assignments (2)
CHANGE OF NAME Recorded Oct 25, 2024
From: SALESFORCE.COM, INC.
To: SALESFORCE, INC.
Reel/Frame 069268/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 17, 2014
From: ROY-FADERMAN, AVROM
To: SALESFORCE.COM, INC.
Reel/Frame 031994/0647 →