Recipes are based on ingredients defined in recipe schema objects.
You can use the recipe editor widget to manage recipes at runtime or to develop your own recipe management solution.

Recipe schemas

Use a recipe schema object to define a set of variables to create recipes. A recipe defines values that correspond with the variables from the schema.
Recipes based on a recipe schema
TIP: You can create multiple recipes based on a single recipe schema object. This is useful for restoring previous recipe settings.

Recipe schema ingredients

Define the recipe schema ingredients at design time by setting the
Target Node
property of the recipe schema object.
The target node can be any project node that contains the desired variables.
For example, the target node can be:
  • The
  • An object inside the
  • A node that contains variables from one or more controllers
TIP: In a complex project, to define variables contained in several nodes as ingredients of a recipe schema, create a dedicated object in the
folder and add variables inside it. Then, create a dynamic link between the variables and the ingredients. If the object is selected as the target node, the selection of the recipe schema ingredients is intuitive because only the variables referenced in the object are displayed.

Edit model node

The knowledge about the edit model node is necessary if you want to develop your own recipe management solution.
When the user creates, edits, or loads a recipe from the database at runtime, an alias to the
Edit model
node is automatically created in the root project node. The alias node has the same name as the recipe schema it refers to. Until the node is saved, deleted, or sent to the controller, it contains a temporary copy of the created, edited, or loaded recipe data.
You can refer to the
Edit model
node at design time.
execution stops, the
Edit model
node and its data is deleted.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.