get_access_to_registers
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| get_access_to_registers [2019/01/09 10:27] – akuzmuk | get_access_to_registers [2019/01/09 10:43] – akuzmuk | ||
|---|---|---|---|
| Line 114: | Line 114: | ||
| The parameters **variable_name** and **connection_name** work just like in the GetReg function. Since version 3.2 there is no more **connection_name** parameter. | The parameters **variable_name** and **connection_name** work just like in the GetReg function. Since version 3.2 there is no more **connection_name** parameter. | ||
| - | ==== ApplyRecipe(recipeId, | ||
| - | The **ApplyRecipe** function applies the recipe with the number **recipeId** on behalf of the user with id = **userId**. If this user does not have permissions for this recipe, the recipe will not be applied. | ||
| - | |||
| - | The application of the recipe is to write the corresponding values to the registers that are specified in the recipe. | ||
| - | |||
| - | ==== GetRecipeById(recipeId) ==== | ||
| - | The **GetRecipeById** function gets the recipe with the number **recipeId**. Function is available since WebHMI v 3.2. | ||
| - | |||
| - | On success table with following fields will be returned: | ||
| - | * id - Recipe Id | ||
| - | * title - Recipe title | ||
| - | * registers - table with Register Id as key and new value as value | ||
| - | |||
| - | On error (recipe not found, etc) false will be returned. | ||
get_access_to_registers.txt · Last modified: 2024/03/15 16:01 by atolstov