Method and system for recursive plug-in application recipe generation

Patent metadata

Field	Value
Publication number	US-10521245-B2
Application number	US-201715794994-A
Country	US
Kind code	B2
Filing date	Oct 26, 2017
Priority date	Dec 18, 2016
Publication date	Dec 31, 2019
Grant date	Dec 31, 2019

Abstract

Techniques for recursively generating a plug-in application recipe (PIAR) are disclosed. A PIAR management application manages a particular PIAR in an active state. The PIAR management application manages PIAR specifications, each identifying a trigger and an action. The action is conditional on the trigger. The particular PIAR includes a particular trigger and a particular action. The particular action includes a child PIAR specification that defines, for a child PIAR, a second trigger and a second action to be executed when the second trigger is satisfied. In response to detecting that the particular trigger is satisfied, the PIAR management application creates the child PIAR. The PIAR management application monitors the second trigger concurrently with the particular trigger, which the PIAR management application did not do before creating the child PIAR.

First claim

The invention claimed is:

1. A non-transitory computer readable medium comprising instructions which, when executed by one or more hardware processors, causes performance of operations comprising:
managing, by a plug-in application recipe (PIAR) management application, a particular PIAR in an active state, wherein the PIAR management application manages PIAR specifications, each PIAR specification identifying
(a) a trigger for which one or more trigger variables, values of which are necessary to evaluate the trigger on an ongoing basis, are exposed by a first plug-in application to the PIAR management application, wherein an instance of evaluating the trigger comprises determining whether a condition is satisfied based at least in part on one or more values of the one or more trigger variables, and
(b) an action for which a second plug-in application exposes an interface to the PIAR management application for causing the second plug-in application to carry out the action, wherein an instance of evaluating the action comprises carrying out the action based on one or more values of one or more input variables that are input to the action in the PIAR specification,
wherein the PIAR management application makes the action conditional on the trigger on an ongoing basis,
wherein the particular PIAR comprises a particular trigger and a particular action,
wherein the particular action comprises a child PIAR specification that defines, for a child PIAR, a second trigger and a second action to be executed when the second trigger is satisfied;

detecting, by the PIAR management application that the particular trigger is satisfied; and
in response to detecting that the particular trigger is satisfied, creating the child PIAR, wherein the PIAR management application monitors the second trigger concurrently with the particular trigger, wherein the PIAR management application did not monitor the second trigger before creating the child PIAR.

2. The medium of claim 1 , wherein the operations further comprise, prior to detecting that the particular trigger is satisfied:
receiving, by the PIAR management application via a graphical user interface provided by the PIAR management application, an initial PIAR specification defining (a) the particular trigger and (b) the particular action; and
configuring, by the PIAR management application, a monitoring operation to detect one or more conditions based on the particular trigger from the initial PIAR specification.

3. The medium of claim 2 , wherein configuring the monitoring operation comprises configuring, based at least in part on a first interface exposed by the first plug-in application, a service to monitor the first plug-in application to determine whether the first plug-in application performs an operation corresponding to the particular trigger.

4. The medium of any claim 1 , wherein the first plug-in application and the second plug-in application operate independently of each other and independently of the PIAR management application.

5. The medium of claim 1 , wherein the operations further comprise, prior to detecting that the particular trigger is satisfied:
linking the first plug-in application to the PIAR management application based at least in part on authentication credentials received via a graphical user interface provided by the PIAR management application, wherein the authentication credentials are associated with a particular user account of a plurality of user accounts managed by the first plug-in application.

6. The medium of claim 5 , wherein the linking comprises storing the authentication credentials for use in polling the first plug-in application for data.

7. The medium of claim 5 , wherein the linking comprises establishing a secure reusable data pipe for receiving data from the first plug-in application.

8. The medium of claim 1 , wherein creating the child PIAR comprises:
using, by the PIAR management application, a representational state transfer (REST) Application Programming Interface (API) to create the child PIAR in accordance with the child PIAR specification.

9. The medium of claim 1 , wherein the operations further comprise, prior to detecting that the particular trigger is satisfied:
receiving, via a graphical user interface provided by the PIAR management application, a native PIAR specification for creating the child PIAR, wherein the native PIAR specification is stored, in a PIAR repository, as the child PIAR and is executable as the child PIAR by the PIAR management system.

10. The medium of claim 1 , wherein the operations further comprise, prior to detecting that the particular trigger is satisfied:
receiving, by a graphical user interface provided by the PIAR management application, a native title of the child PIAR, wherein the child PIAR is stored, in a PIAR repository, using the native title.

11. The medium of claim 1 , wherein the operations further comprise, prior to detecting that the particular trigger is satisfied:
receiving, by a graphical user interface provided by the PIAR management application, a selection to automatically generate a title of the child PIAR, wherein creating the child PIAR comprises storing the child PIAR using a title automatically generated based at least in part on the second trigger and/or the second action.

12. The medium of claim 1 , wherein the operations further comprise, prior to detecting that the particular trigger is satisfied:
receiving, by a graphical user interface provided by the PIAR management application, PIAR trigger metadata that indicates, for the child PIAR: a PIAR trigger application from which data is needed to satisfy the second trigger, a trigger type of one or more trigger types available for the PIAR application, and/or condition metadata for determining whether or not the second trigger is satisfied.

13. The medium of claim 1 , wherein the operations further comprise, prior to detecting that the particular trigger is satisfied:
receiving, by a graphical user interface provided by the PIAR management application, PIAR action metadata that indicates, for the child PIAR: a PIAR action application on which the second action is to be performed, an action type of one or more action types available for the PIAR application, and/or content metadata for enriching the second action.

14. The medium of claim 1 , wherein the operations further comprise, prior to detecting that the particular trigger is satisfied:
receiving, by a graphical user interface provided by the PIAR management application, a selection of one or more PIAR templates to be used by the PIAR management application to create the child PIAR, wherein the one or more PIAR templates populate at least part of a PIAR name, the second trigger, and/or the second action, and allow at least partial modification to at least part of the PIAR name, the second trigger, and/or the second action.

15. The medium of claim 1 , wherein the PIAR management application stores PIAR specifications in a PIAR repository that is accessible via a particular authenticated account of the PIAR management application.

16. The medium of claim 1 , wherein the second action comprises another child PIAR specification that defines, for the other child PIAR, a third trigger and a third action to be executed when the third trigger is satisfied, and wherein the operations further comprise:
detecting that the second trigger is satisfied; and
in response to detecting that the second trigger is satisfied: creating the other child PIAR.

17. The medium of claim 1 , wherein the child PIAR is associated with a s

Assignees

• Oracle Int Corp

Inventors

• Chan Victor
• Dwivedi Udom
• Sutton Eric

Classifications

• G06F9/44526 Primary

  Plug-ins; Add-ons · CPC title

• G06F21/31

  User authentication · CPC title

• G06F9/451

  Execution arrangements for user interfaces · CPC title

• G06F3/0484

  for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range · CPC title