Recipe definitions are displayed in the project explorer below the corresponding access node. They contain a set of parameters that are saved in the project file and are used to tell the recipe server how the recipe definitions are to be interpreted at runtime.
Recipe definitions provide the following functionality, among others:
- Specification of digital variables that trigger the five basic functions "Read", "Write", "Load", "Send" and "Save".
- Relative or absolute interpretation of the recipe values via target and standard factor.
- Nesting of recipes via sub-recipes.
Parameters
| Name | Description of the |
|---|---|
| Activate change history | Changed values are saved in the recipe file. |
| File extension | Extension of all recipe files generated by this recipe definition. |
| File path | Determines the path under which the recipe files are stored. |
| Definition active | Determines whether the object definition is valid. |
| Initial recipe description | Description of the recipe that is used the very first time it is saved. |
| Initial recipe name | Name of the recipe that is used when saving for the very first time. |
| Comment | Optional commentary on the object. |
| Load last recipe file at start | Defines whether the recipe file last loaded in the last application session should be loaded immediately into the corresponding process variables when the application is started. |
| Name | Name of the object. |
| Standard factor | Multiplication factor of the recipe data for a relative specification of the recipe values. (only  standard server) |
| Recipe name variable buffer | Contains the name of the recipe that was last loaded into the buffer. |
| Recipe name variable SPS | Contains the name of the recipe that was last loaded into the process . |
| Automatically save recipe buffer in current recipe file when changes are made | If a value changes in the recipe buffer, the buffer is automatically saved in the current recipe file. |
| Automatically write recipe buffer to the variable server when changes are made | If a value changes in the recipe buffer, the buffer is automatically written to the variable server . |
| Protectrecipe from manipulation | Determines whether recipes in XML format are provided with a checksum to protect them from unauthorised changes. (only standard server) |
| Recipe values absolute/relative | Determines whether the recipe values are converted using standard and target factors (only standard server) |
| Target factor variable | Variable that contains the multiplication factor of the recipe server data for a relative specification of the recipe values. (only standard server) |
| Text | Localisable text for the object. |
| Save sub-recipe class values in this recipe class | Determines whether recipe values from sub-recipes are also saved in the file. |
| Variable for file description | Variable that provides a descriptive text for the recipe. |
| Variable for file name | Determines the variable that contains the recipe file name. |
| Variable for load trigger | Variable name whose value change leads to the values being loaded from the recipe file. |
| Variable for read trigger | Variable bit whose value change leads to the recipe values being read from the variable server. |
| Variable for write trigger | Variable bit whose value change leads to the values being written to the variable server. |
| Variable for transmission trigger | Variable bit whose value change leads to a recipe file being sent to the variable server. |
| Variable for memory trigger | Variable bit whose value change leads to the values being saved in the recipe file. |
| Automatically save variable server values to current recipe file when changed | If a variable value changes in the variable server, it is automatically saved in the current recipe file. (only standard server) |
| Automatically read variable server values into the recipe buffer when changes are made | If a variable value changes in the variable server, it is automatically transferred to the recipe buffer. (only  Cross-Platform Server) |