Additional information
This section provides additional information on methods, events, parameters and
metadata.
- You can set a specific target where to deploy the recipe. The structure of the target must be the same as the structure saved in the recipe schema.
- You can use recipes with a ListView or by using NetLogic.
- A recipe parameter is an Item or DataItem selected in the RecipeSchema editor. The recipe parameters represented in a ListView are always presented as read-only.
- The recipes introduce an elevated number of insert/update/delete operations for certain tasks. This may increase the time needed to complete operations, especially for remote databases and high latency. To prevent data loss, minimal transaction management is supported. Transaction management is not customizable.IMPORTANT: To prevent data loss when working with DataLogger and EventLogger, it is highly recommended not to use the same database that is used for recipes.
- You can use the legacy recipe schema and the new recipe schema in the same project but it may require manual adjustments.
- Query toEmbeddedDatabaseexample:SELECT R.*, M.* FROM Recipes AS R LEFT JOIN "RecipeMetadata_RecipeSchema1" AS M ON R.Id = M.RecipeId WHERE R.RecipeSchemaName = 'RecipeSchema1' ORDER BY R.Name
Methods
The following tables describe methods and related parameters:
Method | Input arguments | Output arguments |
|---|---|---|
CreateRecipe |
|
|
DuplicateRecipe |
|
|
RenameRecipe |
|
|
DeleteRecipe |
|
|
Refactor |
| None. This is the only async method. When the operation is
completed, an event (RefactorCompleted) is dispatched. |
GetDataItems |
|
|
SetRecipeDataItemValue |
|
|
SetRecipeMetadataValue |
|
|
TransferFromEditModelToStore |
|
|
TransferFromEditModelToTarget |
|
|
TransferFromStoreToEditModel |
|
|
TransferFromStoreToTarget |
|
|
TransferFromTargetToEditModel |
|
|
TransferFromTargetToStore |
|
|
Method | Input arguments | Output arguments |
|---|---|---|
GetRecipes | No input arguments |
|
GetRecipeMetadataValue |
|
|
GetRecipeMetadataValues | RecipeId [RecipeId] |
|
GetRecipeDataItemValue |
|
|
CreateEditModel |
|
|
TransferFromStores | RecipeId [RecipeId] |
|
TransferToStore |
|
|
TransferToTarget |
|
|
TransferFromTarget |
|
|
SetDataItemValue |
|
|
Events
The Recipe schema includes the following events:
- RefactorCompleted
- Fired when the method Refactor is completed.
- RecipeApplicationEvent
- Fired when TransferFromStoreToTarget or TransferEditModelToTarget are completed.
Parameters and metadata
You can create, edit, and store recipe schemas with unlimited parameters and
metadata.You can define and store custom metadata, such as author or creation date
or an associated image, which enhances traceability and contextual understanding of
recipes.
Database Tables
Recipe schema model structure can be stored in the database, preserving the
information if a variable stands alone or is part of an object. Recipe parameters
are displayed in rows organized as follows:
- Recipes:
- Id (Primary key) [UInt32]
- Name [String]
- Version [String]
- RecipeSchemaName [String]
- RecipeSchemaNamespaceUri [String]
- RecipeSchemaTimestamp [DateTime]
- CreatedAt [DateTime]
- ModifiedAt [DateTime]
- RecipeItems:
- Id (Primary key) [UInt32]
- RecipeId [UInt32]
- RelativeBrowsePath [String]
- TypeId [String]
- RecipeDataItems:
- Id (Primary key) [UInt32]
- RecipeItemId [UInt32]
- RelativeBrowsePath [String]
- ElementAccess [String]
- DataTypeId [String]
- Value [String]
- RecipeMetadata:
- Metadata1 [UserDefined]
- Metadata2 [UserDefined]
- …
- Metadata_n [UserDefined]
Provide Feedback