Scheme Editor/en - Versionsgeschichte

Cg: /* Pin Specific Options (Context Menu) */

2025-06-04T15:16:19Z

Pin Specific Options (Context Menu)

← Nächstältere Version		Version vom 4. Juni 2025, 15:16 Uhr
Zeile 107:		Zeile 107:

	;Parameter (Non Consuming; Non Triggering)		;Parameter (Non Consuming; Non Triggering)
	:This option determines whether the select input pin is a parameter pin. For more information see: [[DiagramElements-Pin#Input Pin ~~Trigger Attributes~~\|Diagram Elements]].		:This option determines whether the select input pin is a parameter pin. For more information see: [[DiagramElements-Pin#Input Pin\|Diagram Elements - Input Pin]].

	;Telegram (Non Consuming; Non Triggering; Deliver While Executing)		;Telegram (Non Consuming; Non Triggering; Deliver While Executing)

Cg: /* Pin Specific Options (Context Menu) */

2025-06-04T15:14:53Z

Pin Specific Options (Context Menu)

← Nächstältere Version		Version vom 4. Juni 2025, 15:14 Uhr
Zeile 110:		Zeile 110:

	;Telegram (Non Consuming; Non Triggering; Deliver While Executing)		;Telegram (Non Consuming; Non Triggering; Deliver While Executing)
	:This option determines whether the selected input pin is a telegram pin. For more Information see: [[DiagramElements-Pin#~~Telegram Pin~~\|Telegram Pin]].		:This option determines whether the selected input pin is a telegram pin. For more Information see: [[DiagramElements-Pin/en#Telegram_and_Mailbox_Pins\|Telegram Pin]].

	;Buffered		;Buffered

Cg: /* Pin Specific Options (Context Menu) */

2025-06-04T15:13:39Z

Pin Specific Options (Context Menu)

← Nächstältere Version		Version vom 4. Juni 2025, 15:13 Uhr
Zeile 106:		Zeile 106:
	:This option is only available if the selected pin is frozen to a value or to an environment variable. No matter if the pin was preset with a direct value or with an environment variable, the preset information will be lost.		:This option is only available if the selected pin is frozen to a value or to an environment variable. No matter if the pin was preset with a direct value or with an environment variable, the preset information will be lost.

	;Parameter (Non Consuming;Non Triggering)		;Parameter (Non Consuming; Non Triggering)
	:This option determines whether the select input pin is a parameter pin. For more information see: [[DiagramElements-Pin#Input Pin Trigger Attributes\|Diagram Elements]].		:This option determines whether the select input pin is a parameter pin. For more information see: [[DiagramElements-Pin#Input Pin Trigger Attributes\|Diagram Elements]].

	;Telegram (Non Consuming;Non Triggering;Deliver While Executing)		;Telegram (Non Consuming; Non Triggering; Deliver While Executing)
	:This option determines whether the selected input pin is a telegram pin. For more Information see: [[DiagramElements-Pin#Telegram Pin\|Telegram Pin]].		:This option determines whether the selected input pin is a telegram pin. For more Information see: [[DiagramElements-Pin#Telegram Pin\|Telegram Pin]].

Cg: /* Add / Remove / Test Action User Interface (Action-UI) */

2025-02-24T18:49:33Z

Add / Remove / Test Action User Interface (Action-UI)

← Nächstältere Version		Version vom 24. Februar 2025, 18:49 Uhr
Zeile 300:		Zeile 300:
	[[Datei:NotBeginner.png\|20px]]Note: this field is not shown if your experience setting is "''Beginner''".<br>Go to the "''Extras''" - "''Settings''" - "''Look & Feel''" - dialog to change your experience setting.		[[Datei:NotBeginner.png\|20px]]Note: this field is not shown if your experience setting is "''Beginner''".<br>Go to the "''Extras''" - "''Settings''" - "''Look & Feel''" - dialog to change your experience setting.

	=== Add / Remove / Test Action User Interface (Action-UI) ===		=== Add / Remove / Test the Action's User Interface (Action-UI) ===
	You can specify a graphical user interface (GUI) for an action. If defined, that user interface will be displayed as long as the action is executed during a test run. The action can communicate with the UI using environment variables. The environment variables will be created by the [[GUI Editor-GUICode Editor\|UI Editor]] during creation / editing the UI.		You can specify a graphical user interface (GUI) for an action. If defined, that user interface will be displayed as long as the action is executed during a test run. The action can communicate with the UI using environment variables. The environment variables will be created by the [[GUI Editor-GUICode Editor\|UI Editor]] during creation / editing the UI.

Cg: /* Advanced and Expert Settings */

2025-02-24T18:48:58Z

Advanced and Expert Settings

← Nächstältere Version		Version vom 24. Februar 2025, 18:48 Uhr
Zeile 301:		Zeile 301:

	=== Add / Remove / Test Action User Interface (Action-UI) ===		=== Add / Remove / Test Action User Interface (Action-UI) ===
	You can specify a graphical user interface (UI) for an action. If defined, that UI will be displayed as long as the action is executed during a test run. The action can communicate with the UI using environment variables. The environment variables will be created by the [[GUI Editor-GUICode Editor\|UI Editor]] during creation / editing the UI.		You can specify a graphical user interface (GUI) for an action. If defined, that user interface will be displayed as long as the action is executed during a test run. The action can communicate with the UI using environment variables. The environment variables will be created by the [[GUI Editor-GUICode Editor\|UI Editor]] during creation / editing the UI.

	[[Datei:NotBeginner.png\|20px]]Note: this field is not shown unless your experience setting is "''Expert''".<br>Go to the"''Extras''" - "''Settings''" - "''Look & Feel''" - dialog to change your experience setting.		[[Datei:NotBeginner.png\|20px]]Note: this field is not shown unless your experience setting is "''Expert''".<br>Go to the"''Extras''" - "''Settings''" - "''Look & Feel''" - dialog to change your experience setting.

Cg: /* Declaring Semantic Attributes */

2025-02-24T18:46:58Z

Declaring Semantic Attributes

← Nächstältere Version		Version vom 24. Februar 2025, 18:46 Uhr
Zeile 236:		Zeile 236:

	== Declaring Semantic Attributes ==		== Declaring Semantic Attributes ==
	The block's pop up menu also allows for a number of semantic attributes to be defined for the action.		The block's pop up menu also allows for a number of semantic attributes to be defined for the action. Some of them are informal/documentation, others are used by the system to optimize excution or to help the expeccoALM/AIDYMO scheduler. In any case, they are optional, and they are not obligatory.

	Currently, semantic attributes are:		Currently, semantic attributes are:

Alkurz: /* Variable Number of Pins */

2024-11-06T16:06:15Z

Variable Number of Pins

← Nächstältere Version		Version vom 6. November 2024, 16:06 Uhr
Zeile 148:		Zeile 148:

	=====Variable Number of Pins=====		=====Variable Number of Pins=====
⚫	~~The last~~ input- and output pin can be specified as "''variable~~-number-of-pins''~~". Such a pin appears ~~as a single pin~~ in the block's description (the schema), but ~~may~~ be instantiated as a ~~step~~ ~~with~~ ~~multiple pins~~. In other words, the number of pins can be ~~determined~~ individually for each step.

		⚫	An input and output pin can be specified as a "variable pin". Such a pin appears in the block description (the schema) as a single pin, but it can be instantiated multiple times in one step. In other words, the number of these variable pins can be defined individually for each step. Variable pins are marked with a small plus sign.
	;Variable Number of Pins in Steps
	:This option sets the "''Variable Number''" attribute for the last pin. If checked, the number of pins can be changed in the step, and the last schema pin can be "replicated" an arbitrary number of times. This option is only possible for elementary actions, and the elementary code must be written to access this pin pin with a pin index.
⚫	:See also in [[DiagramElements-Pin/en#Variable_Number_of_Pins \| Diagram Elements-Pin - Variable Number of Pins]].

			Variable pins can only be the last pins, which are combined into a variable pin group. This pin group can be "replicated" in steps as often as required. Individual pins within a group can have different data types, and the replicated pins adopt the data type of their corresponding pin from the schema definition of the action. This is very useful for defining “multi-key-value” groups, e.g. for multi-setter actions of collections or user data objects.
	;Variable Number of Remaining Pins in Steps

	:This is a new feature of the 2.8 version of expecco. Similar to the above "''Variable Number''" of the last pin, this defines a group of pins to be possible repeated in the step. If checked, the number of pins can be changed in multiples of the group size in the step, and the N-last schema pins can be "replicated" an arbitrary number of times. This option is only possible for elementary actions, and the elementary code must be written to access this pin pin with a pin index.
			'''This option is only possible for elementary actions and the elementary code must be written to access these pins with a pin index.'''
	:See also in [[DiagramElements-Pin/en#Variable_Number_of_Pins \| Diagram Elements-Pin - Variable Number of Pins]].

			;Defining the variable pin group

			:In the context menu of a pin, the start of the variable pin group can be set via the sub menu <code>Special attributes</code> - <code>Start Variable Pin Group here</code>. The selected pin and the following pins become variable pins, the pins before them become or remain fixed pins.

			:This function can also be used to subsequently move the start of the pin group.

			;Remove the variable pins.

			:Context menu of a variable pin via the sub menu <code>Special attributes</code> - <code>Convert all Variable Pins to Fixed Pins</code>: This converts all variable pins to fixed pins.

			;Equal Number of Variable Input and Output Pin Groups

			:If a variable pin group is defined in the input and output pins, the number of pin groups can be synchronized. The number of replications of the input and output pins is the same.<br>
			:<code>Special attributes</code> - <code>Equal Number of Variable Input and Output Pin Groups</code>

		⚫	See also in [[DiagramElements-Pin/en#Variable_Number_of_Pins \| Diagram Elements-Pin - Variable Number of Pins]].

	== Action ==		== Action ==

Cg: /* Variable Number of Pins */

2023-10-13T15:04:51Z

Variable Number of Pins

← Nächstältere Version		Version vom 13. Oktober 2023, 15:04 Uhr
Zeile 152:		Zeile 152:
	;Variable Number of Pins in Steps		;Variable Number of Pins in Steps
	:This option sets the "''Variable Number''" attribute for the last pin. If checked, the number of pins can be changed in the step, and the last schema pin can be "replicated" an arbitrary number of times. This option is only possible for elementary actions, and the elementary code must be written to access this pin pin with a pin index.		:This option sets the "''Variable Number''" attribute for the last pin. If checked, the number of pins can be changed in the step, and the last schema pin can be "replicated" an arbitrary number of times. This option is only possible for elementary actions, and the elementary code must be written to access this pin pin with a pin index.
	:See also in [[DiagramElements-Pin/en#Variable_Number_of_Pins \| Diagram Elements - Variable Number of Pins]].		:See also in [[DiagramElements-Pin/en#Variable_Number_of_Pins \| Diagram Elements-Pin - Variable Number of Pins]].

	;Variable Number of Remaining Pins in Steps		;Variable Number of Remaining Pins in Steps
	:This is a new feature of the 2.8 version of expecco. Similar to the above "''Variable Number''" of the last pin, this defines a group of pins to be possible repeated in the step. If checked, the number of pins can be changed in multiples of the group size in the step, and the N-last schema pins can be "replicated" an arbitrary number of times. This option is only possible for elementary actions, and the elementary code must be written to access this pin pin with a pin index~~. See also in [[DiagramElements-Pin/en#Variable_Number_of_Pins \| Diagram Elements - Variable Number of Pins]]~~.		:This is a new feature of the 2.8 version of expecco. Similar to the above "''Variable Number''" of the last pin, this defines a group of pins to be possible repeated in the step. If checked, the number of pins can be changed in multiples of the group size in the step, and the N-last schema pins can be "replicated" an arbitrary number of times. This option is only possible for elementary actions, and the elementary code must be written to access this pin pin with a pin index.
			:See also in [[DiagramElements-Pin/en#Variable_Number_of_Pins \| Diagram Elements-Pin - Variable Number of Pins]].

	== Action ==		== Action ==

Cg: /* Special Attributes */

2023-10-13T15:04:20Z

Special Attributes

← Nächstältere Version		Version vom 13. Oktober 2023, 15:04 Uhr
Zeile 130:		Zeile 130:

	;Consuming / Non-Consuming		;Consuming / Non-Consuming
	:This option determines whether the input pin consumes its input value from the input basket or leaves it. Non-consuming pins are sometimes required, when the step is executed in a loop, and the input value should be reused for each iteration. Also, frozen parameter pins should be defined as non-consuming, as otherwise, the freeze value is only available once (in the first loop iteration)~~.<br>More info in: [[DiagramElements-Pin#Consuming_vs._Non-Consuming \| Diagram Elements-Pin]]~~.		:This option determines whether the input pin consumes its input value from the input basket or leaves it. Non-consuming pins are sometimes required, when the step is executed in a loop, and the input value should be reused for each iteration. Also, frozen parameter pins should be defined as non-consuming, as otherwise, the freeze value is only available once (in the first loop iteration).
			:More info in: [[DiagramElements-Pin#Consuming_vs._Non-Consuming \| Diagram Elements-Pin]].

	;Triggering / Non Triggering		;Triggering / Non Triggering
	:This option determines whether the input pin is considered in the action triggering process or not. Triggering pins must have a value present in order for an activity to be created. Non-triggering pins are not~~. <br>More info in: [[DiagramElements-Pin#Input_Pin_Trigger_Attributes \| Diagram Elements-Pin]]~~.		:This option determines whether the input pin is considered in the action triggering process or not. Triggering pins must have a value present in order for an activity to be created. Non-triggering pins are not.
			:More info in: [[DiagramElements-Pin#Input_Pin_Trigger_Attributes \| Diagram Elements-Pin]].

	; Mailbox / Non-Mailbox (also called "''Telegram Pin''")		; Mailbox / Non-Mailbox (also called "''Telegram Pin''")
	:This option determines whether the selected pin is a telegram pin. Normal pins "latch" their input value when the action is triggered and provide that value to internal steps (be aware, that it might be consumed). If another value arrives at the pin while it is beeing executed, another activity will be started to process the next value.		:This option determines whether the selected pin is a telegram pin. Normal pins "latch" their input value when the action is triggered and provide that value to internal steps (be aware, that it might be consumed). If another value arrives at the pin while it is beeing executed, another activity will be started to process the next value.
	:Mailbox pins behave differently: any value arriving there will be forwarded to inside connected steps. Mailbox pins are most useful to implement a controlled cancel operation (eg. by setting a variable inside, which stops a loop)~~.<br>For more Information see: [[DiagramElements-Pin#Telegram_and_Mailbox_Pins\| Diagram Elements-Pin]]~~.		:Mailbox pins behave differently: any value arriving there will be forwarded to inside connected steps. Mailbox pins are most useful to implement a controlled cancel operation (eg. by setting a variable inside, which stops a loop).
			:For more Information see: [[DiagramElements-Pin#Telegram_and_Mailbox_Pins\| Diagram Elements-Pin]].

	=====Output Pins=====		=====Output Pins=====
	;Buffered / Unbuffered		;Buffered / Unbuffered
	Buffered outputs will send their value(s) when the action has finished with success. Unbuffered outputs will send any value immediately (and thus may trigger other actions while this action is still executing).		:Buffered outputs will send their value(s) when the action has finished with success. Unbuffered outputs will send any value immediately (and thus may trigger other actions while this action is still executing).
			:For more Information see: [[DiagramElements-Pin/en#Output_Pin_Buffer_Attribute\| Diagram Elements-Pin]].

	=====Variable Number of Pins=====		=====Variable Number of Pins=====
Zeile 147:		Zeile 151:

	;Variable Number of Pins in Steps		;Variable Number of Pins in Steps
	:This option sets the "''Variable Number''" attribute for the last pin. If checked, the number of pins can be changed in the step, and the last schema pin can be "replicated" an arbitrary number of times. This option is only possible for elementary actions, and the elementary code must be written to access this pin pin with a pin index~~. See also in [[DiagramElements-Pin/en#Variable_Number_of_Pins \| Diagram Elements - Variable Number of Pins]]~~.		:This option sets the "''Variable Number''" attribute for the last pin. If checked, the number of pins can be changed in the step, and the last schema pin can be "replicated" an arbitrary number of times. This option is only possible for elementary actions, and the elementary code must be written to access this pin pin with a pin index.
			:See also in [[DiagramElements-Pin/en#Variable_Number_of_Pins \| Diagram Elements - Variable Number of Pins]].

	;Variable Number of Remaining Pins in Steps		;Variable Number of Remaining Pins in Steps

Cg: /* Input Pins */

2023-10-13T15:02:02Z

Input Pins

← Nächstältere Version		Version vom 13. Oktober 2023, 15:02 Uhr
Zeile 130:		Zeile 130:

	;Consuming / Non-Consuming		;Consuming / Non-Consuming
	:This option determines whether the input pin consumes its input value from the input basket or leaves it. Non-consuming pins are sometimes required, when the step is executed in a loop, and the input value should be reused for each iteration. Also, frozen parameter pins should be defined as non-consuming, as otherwise, the freeze value is only available once (in the first loop iteration).<br>More info in: [[DiagramElements-Pin#Consuming_vs._Non-Consuming \| Diagram Elements]].		:This option determines whether the input pin consumes its input value from the input basket or leaves it. Non-consuming pins are sometimes required, when the step is executed in a loop, and the input value should be reused for each iteration. Also, frozen parameter pins should be defined as non-consuming, as otherwise, the freeze value is only available once (in the first loop iteration).<br>More info in: [[DiagramElements-Pin#Consuming_vs._Non-Consuming \| Diagram Elements-Pin]].

	;Triggering / Non Triggering		;Triggering / Non Triggering
	:This option determines whether the input pin is considered in the action triggering process or not. Triggering pins must have a value present in order for an activity to be created. Non-triggering pins are not. <br>More info in: [[DiagramElements-Pin#Input_Pin_Trigger_Attributes \| Diagram Elements]].		:This option determines whether the input pin is considered in the action triggering process or not. Triggering pins must have a value present in order for an activity to be created. Non-triggering pins are not. <br>More info in: [[DiagramElements-Pin#Input_Pin_Trigger_Attributes \| Diagram Elements-Pin]].

	; Mailbox / Non-Mailbox (also called "''Telegram Pin''")		; Mailbox / Non-Mailbox (also called "''Telegram Pin''")
	:This option determines whether the selected pin is a telegram pin. Normal pins "latch" their input value when the action is triggered and provide that value to internal steps (be aware, that it might be consumed). If another value arrives at the pin while it is beeing executed, another activity will be started to process the next value.		:This option determines whether the selected pin is a telegram pin. Normal pins "latch" their input value when the action is triggered and provide that value to internal steps (be aware, that it might be consumed). If another value arrives at the pin while it is beeing executed, another activity will be started to process the next value.
	Mailbox pins behave differently: any value arriving there will be forwarded to inside connected steps. Mailbox pins are most useful to implement a controlled cancel operation (eg. by setting a variable inside, which stops a loop).<br>For more Information see: [[DiagramElements-Pin#Telegram_and_Mailbox_Pins\| Diagram Elements - ~~Telegram~~ Pin]].		:Mailbox pins behave differently: any value arriving there will be forwarded to inside connected steps. Mailbox pins are most useful to implement a controlled cancel operation (eg. by setting a variable inside, which stops a loop).<br>For more Information see: [[DiagramElements-Pin#Telegram_and_Mailbox_Pins\| Diagram Elements-Pin]].

	=====Output Pins=====		=====Output Pins=====