Expression based declarative data service execution chaining
View Patent ↗Expression based declarative data service execution chaining is disclosed. In various embodiments, an indication is received that a first data service has returned a result indicating the first data service has been invoked successfully. An expression is evaluated, based at least in part on the result. A second data service is invoked based at least in part on an outcome of the evaluation of the expression.
1. A method of data service execution, comprising:
receiving at application runtime an indication that a first data service has returned a result indicating the first data service has been invoked successfully;
evaluating an expression, based at least in part on the result; and
invoking a data service based on whether the result exceeds a threshold, wherein the data service is determined dynamically at application runtime based at least in part on an outcome of the evaluation of the expression.
2. The method of claim 1 , wherein the indication comprises receipt of the result.
3. The method of claim 1 , further comprising receiving via a developer user interface a definition that includes the expression.
4. The method of claim 3 , further comprising generating programmatically, based at least in part on the definition, application code to evaluate the expression at application runtime.
5. The method of claim 1 , wherein a second data service is invoked in the event the result exceeds the threshold.
6. The method of claim 5 , wherein a third data service is invoked in the event the result does not exceed the threshold.
7. The method of claim 1 , wherein the result includes a payload value.
8. The method of claim 7 , wherein the data service that is invoked is based on the payload value.
9. The method of claim 1 , wherein the indication is received in response to user input via an application user interface page.
10. The method of claim 1 , wherein the first data service is associated with an element that is configured to generate an event in response to the result indicating the first data service has been invoked successfully.
11. The method of claim 10 , wherein a second element associated with a different data service is configured to subscribe to the event.
12. A system for data service execution, comprising:
a communication interface; and
a processor coupled to the communication interface and configured to:
receive at application runtime an indication that a first data service has returned a result indicating the first data service has been invoked successfully;
evaluate an expression, based at least in part on the result; and
invoke a data service based on whether the result exceeds a threshold, wherein the data service is determined dynamically at application runtime based at least in part on an outcome of the evaluation of the expression.
13. The system of claim 12 , wherein a second data service is invoked in the event the result exceeds the threshold.
14. The system of claim 13 , wherein a third data service is invoked in the event the result does not exceed the threshold.
15. The system of claim 12 , wherein the result includes a payload value.
16. The system of claim 15 , wherein the data service that is invoked is based on the payload value.
17. The system of claim 12 , wherein the indication is received in response to user input via an application user interface page.
18. The system of claim 12 , wherein the communication interface is further configured to receive via a developer user interface a definition that includes the expression.
19. The system of claim 18 , wherein the processor is further configured to generate programmatically, based at least in part on the definition, application code to evaluate the expression at application runtime.
20. A computer program product for data service execution, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
receiving at application runtime an indication that a first data service has returned a result indicating the first data service has been invoked successfully;
evaluating an expression, based at least in part on the result; and
invoking a data service based on whether the result exceeds a threshold, wherein the data service is determined dynamically at application runtime based at least in part on an outcome of the evaluation of the expression.