planning:userguide:results_api
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| planning:userguide:results_api [2018/08/21 19:45] – [Context based ResultsAPI functions] kerhart | planning:userguide:results_api [2021/07/29 18:24] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 51: | Line 51: | ||
| * If the ResultsAPI function signature has changed, the calculation request will be constructed for the Planning ResultsAPI version that corresponds for the returned context ID. | * If the ResultsAPI function signature has changed, the calculation request will be constructed for the Planning ResultsAPI version that corresponds for the returned context ID. | ||
| - | === Processing a Function === | + | === Function |
| These context based ResultsAPI functions return a special type of calculation request object that is not directly usable within a Thinknode META request as they contain the additional context data needed to ensure the desired calculation is performed with the appropriate Astroid Planning App version. The process of running a context based ResultsAPI request consists of the following steps: | These context based ResultsAPI functions return a special type of calculation request object that is not directly usable within a Thinknode META request as they contain the additional context data needed to ensure the desired calculation is performed with the appropriate Astroid Planning App version. The process of running a context based ResultsAPI request consists of the following steps: | ||
| Line 57: | Line 57: | ||
| * Submit the initial " | * Submit the initial " | ||
| * Retrieve the result of the above calculation and get the context ID | * Retrieve the result of the above calculation and get the context ID | ||
| - | * Perform a META request using the above context, setting the META Generator as the calculation object | + | * Perform a META request using the above context, setting the META Generator as the request |
| ==== Non-context based ResultsAPI functions ==== | ==== Non-context based ResultsAPI functions ==== | ||
planning/userguide/results_api.1534880749.txt.gz · Last modified: (external edit)
