Custom metadata in loosely coupled triggers

• US 9,977,814 B2
• Filed: 05/27/2015
• Issued: 05/22/2018
• Est. Priority Date: 11/04/2011
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Roy-Faderman, Avrom Irwin
• Primary Examiner(s): Gortayo, Dangelino N
• Application Number:
  US14/722,825
• Publication Number:
  US 20150317350A1
• Time in Patent Office: 1,091 Days
• Field of Search: 707702, 707609, 707760, 707770, 707694, 707713, 707756, 707784
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/2291 User-Defined Types; Storage management thereof
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/24565 Triggers; Constraints
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]

Abstract

A database system that supports associating a custom metadata type with loosely coupled triggers may be implemented to include instructions to receive a definition of a custom metadata type, the definition comprising at least one relationship field associated with a triggerable database object. The database system may also include instructions to associate the definition of the custom metadata type with a loosely-coupled trigger, and to cause the loosely-coupled trigger to execute based on generating a custom metadata record of the custom metadata type. The custom metadata record including a triggerable database object value for the relationship field.

Claims

1. A method for using a custom metadata type with loosely coupled triggers, the method

comprising:

receiving, by a database system, a definition of custom metadata type, the definition comprising at least one relationship field associated with a triggerable database object;

associating, by the database system, the definition of the custom metadata type with a loosely-coupled trigger; and

causing, by the database system, the loosely-coupled trigger to execute based on generating a custom metadata record of the custom metadata type, the custom metadata record being generated after the loosely-coupled trigger is compiled and including a triggerable database object value for the relationship field.

2. The method of claim 1, wherein said associating the definition of the custom metadata type with a loosely-coupled trigger occurs before the loosely coupled trigger is compiled.

3. The method of claim 2, wherein the custom metadata record is generated after the loosely coupled trigger has been compiled.

4. The method of claim 3, wherein the generation of the custom metadata record causes the loosely coupled trigger to associate with the triggerable database object indicated by the triggerable database object value of the relationship field.

5. The method of claim 4, wherein the loosely coupled trigger is caused to execute based on an update to the triggerable database object identified in the triggerable database object value.

6. The method of claim 5, further comprising:

determining, by the database system, whether the triggerable database object is associated with the custom metadata record, and if so, identifying the loosely coupled trigger associated with the custom metadata record.

7. The method of claim 6, wherein the update to the triggerable database object comprises one of creating a record, modifying a record, and deleting a record.

8. The method of claim 1, wherein the definition of the custom metadata type is provided by a developer, and wherein the custom metadata record is stored by the database system.

9. An apparatus for custom metadata with loosely coupled triggers, the apparatus comprising:

one or more processors; and

a non-transitory computer readable medium storing a plurality of instructions, which when executed, cause the one or more processors to;

receive, by a database system, a definition of custom metadata type, the definition comprising at least one relationship field associated with a triggerable database object;

associate, by the database system, the definition of the custom metadata type with a loosely-coupled trigger; and

cause, by the database system, the loosely-coupled trigger to execute based on generating a custom metadata record of the custom metadata type, the custom metadata record being generated after the loosely-coupled trigger is compiled and including a triggerable database object value for the relationship field.

10. The apparatus of claim 9, wherein the definition of the custom metadata type is associated with a loosely-coupled trigger before the loosely coupled trigger is compiled.

11. The apparatus of claim 10, wherein the custom metadata record is generated after the loosely coupled trigger has been compiled.

12. The apparatus of claim 11, wherein the generation of the custom metadata record causes the loosely coupled trigger to associate with the triggerable database object indicated by the triggerable database object value of the relationship field.

13. The apparatus of claim 12, wherein the loosely coupled trigger is caused to execute based on an update to the triggerable database object identified in the triggerable database object value.

14. The apparatus of claim 13, further comprising:

determine, by the database system, whether the triggerable database object is associated with the custom metadata record, and if so, identify the loosely coupled trigger associated with the custom metadata record.

15. A computer program product comprising computer-readable program code to be executed by one or more processors when retrieved from a non-transitory computer-readable medium, the program code including instructions to:

receive, by a database system, a definition of custom metadata type, the definition comprising at least one relationship field associated with a triggerable database object;

associate, by the database system, the definition of the custom metadata type with a loosely-coupled; and

cause, by the database system, the loosely-coupled trigger to execute based on generating a custom metadata record of the custom metadata type, the custom metadata record being generated after the loosely-coupled trigger is compiled and including a triggerable database object value for the relationship field.

16. The computer program product of claim 15, wherein the definition of the custom metadata type is associated with a loosely-coupled trigger before the loosely coupled trigger is compiled.

17. The computer program product of claim 16, wherein the custom metadata record is generated after the loosely coupled trigger has been compiled.

18. The computer program product of claim 17, wherein the generation of the custom metadata record causes the loosely coupled trigger to associate with the triggerable database object indicated by the triggerable database object value of the relationship field.

19. The computer program product of claim 18, wherein the loosely coupled trigger is caused to execute based on an update to the triggerable database object identified in the triggerable database object value.

20. The computer program product of claim 19, wherein the program code includes further instructions to:

determine, by the database system, whether the triggerable database object is associated with the custom metadata record, and if so, identify the loosely coupled trigger associated with the custom metadata record.