PATENT CLAIM ANALYSIS

Application Number: 15994346
Application Type: Utility
Filing Date: 2018-05
Publication Date: 2019-01
Patent Classification: ["719", "328000"]

Abstract:
Techniques for managing a plug-in application recipe (“PIAR”) are disclosed. A mapping between (a) a user-selected field, selected via a PIAR creation interface, and (b) a third-party application field, exposed by an application programming interface (“API”) of a third-party application, is stored. The third-party application field is associated with a trigger or action of a PIAR. Managing the PIAR in an active state involves periodically receiving and checking data from the third-party application field against a PIAR condition. During or after managing the PIAR in the active state, information is stored to update the mapping to a different mapping. The different mapping maps the user-selected field to a different third-party application field. Without modifying the PIAR, managing the PIAR in the active state then involves periodically receiving and checking data from the different third-party application field against the PIAR condition.

Claim (Index 1):
A non-transitory computer readable medium comprising instructions which, when executed by one or more hardware processors, causes performance of operations comprising:\n storing a first mapping between:\n a set of user-exposed fields selectable via a plug-in application recipe (\u201cPIAR\u201d) creation interface associated with a PIAR management engine, and \n another set of fields exposed by an Application Programming Interface (API) of a third-party application, \n wherein the PIAR management engine manages PIAR definitions, each PIAR definition identifying\n (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 a PIAR management engine, 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 \n (b) an action for which a second plug-in application exposes an interface to the PIAR management engine 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 definition, \n wherein the PIAR management engine makes the action conditional on the trigger on an ongoing basis, and \n wherein the PIAR definition comprises a particular trigger and a particular action; \n receiving, via one or more PIAR creation interfaces, a plurality of PAIR definitions based at least on a user-selected field of the set of user-exposed fields; wherein the user-selected field is mapped, in the first mapping, to a first third-party application field exposed by the API of the third-party application, wherein the first third-party application field is associated with the particular trigger or the particular action; managing a particular PIAR in an active state, wherein the particular PIAR corresponds to a PIAR definition of the plurality of PIAR definitions, and wherein managing the particular PIAR comprises periodically receiving and checking, against a condition of the particular PIAR, data from the first third-party application field as provided by the third-party application via the API; during or after managing the particular PIAR in the active state, storing information comprising an update from the first mapping to a second mapping, wherein the second mapping maps the user-selected field to a second third-party application field, wherein the second third-party application field differs from the first third-party application field; without modifying the particular PIAR, managing the particular PIAR in the active state at least in part by periodically receiving and checking, against the condition of the particular PIAR, data from the second third-party application field as provided by the third-party application via the API.

Metadata:
- Claim Count in Document: 50.0
- Percentile: 93.0
- Lexical Diversity: 2.53846
- Patent Class: 719.0
- Transitional Phrase Type: open
- Component Type: 1
- Foreign Priority: False
- Related Applications: ['15994368', '15794994', '15094924', '15343236', '14882360']

Analysis Scores:
- 35 USC 101 Eligibility (BERT): 0.4381267924041075
- 35 USC 102 Novelty (BERT): 0.5039669041424192
- Combined Prediction Score: 0.4447108035779387
- Mean Citation Score: 187.008122
- Max Citation Score: 279.96652
- Similarity Product: 253.88462944696903

Labels:
- Claim Label 101: 1
- Claim Label 102: 1
- Claim Label 103: 1
- Claim Label 112: 0
- Combined Label: 1
- Label 101 Adjusted: 1

Dataset: test