UI Action Config - Revision history

KNO at 12:26, 2 September 2016

2016-09-02T12:26:42Z

KNO: KNO moved page UI ACTION CONFIG to UI Action Config

2016-09-02T12:25:02Z

KNO moved page UI ACTION CONFIG to UI Action Config

BMA at 14:33, 6 July 2015

2015-07-06T14:33:01Z

KNO: Text replacement - "{{UBIKSTUDIO" to "{{UBIK Studio"

2015-05-08T10:10:38Z

Text replacement - "{{UBIKSTUDIO" to "{{UBIK Studio"

KNO: /* Parameters */

2015-03-18T15:44:13Z

‎Parameters

KNO: /* Properties for the Relation */

2015-03-18T15:43:32Z

‎Properties for the Relation

KNO: /* Workflows */

2015-03-18T15:43:16Z

‎Workflows

KNO at 12:03, 4 March 2015

2015-03-04T12:03:17Z

MHM: Created page with "{{UBIKSTUDIO}} provides a mechanism to custom Workflows that are be executed after the user performed an action. This action is a trigger for the workflow, and t..."

2014-07-14T15:28:02Z

Created page with "{{UBIKSTUDIO}} provides a mechanism to custom Workflows that are be executed after the user performed an action. This action is a trigger for the workflow, and t..."

New page

{{UBIKSTUDIO}} provides a mechanism to custom [[Workflow| Workflows]] that are be executed after the user performed an action. This action is a trigger for the workflow, and the object he performed the action with, is handed over (as input parameter) for the workflow.

UI (user interface) Action configuration objects are used to configure these Workflows that should be executed after the user performs a certain user action.
You can find the standard UI Configuration objects in the "System.Main.Settings" namespace.

== Configuration ==
Use the Namespace, Name and Description property of the UI Configuration objects to organize your objects.

== Action key ==
The action key defines for which UI Action the configuration object is defined for.
Supported actions are:
* Click
* Doubleclick
* Drag and Drop

{{Hint|It is suggested to structure your configurations object wisely and define several configs for the same Action!}}

== Workflows ==
You can define the workflows that are executed for the configuration object via a relationship ("SYSREL_UIACTION_WORKFLOW").

=== Properties for the Relation ===
Enabled: you can enable/disable the execution for every single workflow without removing it from the relation.

AdminRights: this Checkbox indicates whether the user needs Admin - Rights to execute the workflow. As the user has not switched to Admin mode, the workflow is ignored.

Configured Name Rule: Refer to the Name Rule Configuration object you need to pass to the workflow.

{| class="wikitable" | width = "50%"

|-
! Property!! Description

|-
| Enabled||you can enable/disable the execution for every single workflow without removing it from the relation

|-
| AdminRights||this Checkbox indicates whether the user needs Admin - Rights to execute the workflow. As the user has not switched to Admin mode, the workflow is ignored.

|-
| Configured Name Rule|| Refer to the Name Rule Configuration object you need to pass to the workflow.

|-
|}

== Parameters ==
Define the trigger parameters for the Action via the Parameter Relationship ("SYSREL_UIACTION_PARAMETER").

=== Parameter Key ===
The parameter Key defines the type of the criterion. It is important to set the correct parameter key to get the expected behavior.

Moues Click Parameter Keys are:
* Click Target

Drag&Drop Parameter Keys are:
* Drag Source
* Drop target
* DragDropSource

{{Attention|As it is not possible to create a relation to one object more often then once, you have to use DragDropSource in the case you want to use this object as well as DragSourcen and as DropTarget!}}

Keys without any action are:
* UserParameter_01 to UserParameter_05

=== Evaluation Type ===
The evaluation type indicates whether the related Metaclass and all its derivates are the object you want to perform the action with (evalutation type = Metaclass) or whether you want to perform the action with all instances of the given Metaclass (evaluation type = instances).

@@ Line 17: / Line 17: @@
 {{Hint|It is suggested to structure your configurations object wisely and define several configs for the same Action!}}
@@ Line 55: / Line 54: @@
 * DragDropSource
-{{Attention|As it is not possible to create a relation to one object more often then once, you have to use DragDropSource in the case you want to use this object as well as DragSourcen and as DropTarget!}}
+{{Attention|As it is not possible to create a relation to one object more often then once, you have to use DragDropSource in the case you want to use this object as well as DragSource and as DropTarget!}}
 Keys without any action are:
@@ Line 65: / Line 64: @@
 The evaluation type indicates whether the related Metaclass and all its derivates are the object you want to perform the action with (evalutation type = Metaclass) or whether you want to perform the action with all instances of the given Metaclass (evaluation type = instances).
-[[Category:Workflow]]
+[[Category:Workflow|UI ACTION CONFIG]]

← Older revision		Revision as of 10:10, 8 May 2015
Line 1:		Line 1:
−	{{~~UBIKSTUDIO~~}} provides a mechanism to custom [[Workflow\| Workflows]] that are be executed after the user performed an action. This action is a trigger for the workflow, and the object he performed the action with, is handed over (as input parameter) for the workflow.	+	{{UBIK Studio}} provides a mechanism to custom [[Workflow\| Workflows]] that are be executed after the user performed an action. This action is a trigger for the workflow, and the object he performed the action with, is handed over (as input parameter) for the workflow.

	UI (user interface) Action configuration objects are used to configure these Workflows that should be executed after the user performs a certain user action.		UI (user interface) Action configuration objects are used to configure these Workflows that should be executed after the user performs a certain user action.

← Older revision		Revision as of 15:43, 18 March 2015
Line 24:		Line 24:

	=== Properties for the Relation ===		=== Properties for the Relation ===
−	~~Enabled: you can enable/disable the execution for every single workflow without removing it from the relation.~~
−
−	~~AdminRights: this Checkbox indicates whether the user needs Admin - Rights to execute the workflow. As the user has not switched to Admin mode, the workflow is ignored.~~
−
−	~~Configured Name Rule: Refer to the Name Rule Configuration object you need to pass to the workflow.~~
−
	{\| class="wikitable" \| width = "50%"		{\| class="wikitable" \| width = "50%"

← Older revision		Revision as of 12:03, 4 March 2015
Line 71:		Line 71:
	=== Evaluation Type ===		=== Evaluation Type ===
	The evaluation type indicates whether the related Metaclass and all its derivates are the object you want to perform the action with (evalutation type = Metaclass) or whether you want to perform the action with all instances of the given Metaclass (evaluation type = instances).		The evaluation type indicates whether the related Metaclass and all its derivates are the object you want to perform the action with (evalutation type = Metaclass) or whether you want to perform the action with all instances of the given Metaclass (evaluation type = instances).
		+
		+	[[Category:Workflow]]

@@ Line 3: / Line 3: @@
 UI (user interface) Action configuration objects are used to configure these Workflows that should be executed after the user performs a certain user action.
 You can find the standard UI Configuration objects in the "System.Main.Settings" namespace.
 == Configuration ==
 Use the Namespace, Name and Description property of the UI Configuration objects to organize your objects.
 == Action key ==
@@ Line 17: / Line 15: @@
 {{Hint|It is suggested to structure your configurations object wisely and define several configs for the same Action!}}
 == Workflows ==
@@ Line 24: / Line 21: @@
 === Properties for the Relation ===
 {| class="wikitable" | width = "50%"
 |-
 ! Property!! Description
 |-
 | Enabled||you can enable/disable the execution for every single workflow without removing it from the relation
 |-
 | AdminRights||this Checkbox indicates whether the user needs Admin - Rights to execute the workflow. As the user has not switched to Admin mode, the workflow is ignored.
 |-
 | Configured Name Rule|| Refer to the Name Rule Configuration object you need to pass to the workflow.
 |-
 |}
@@ Line 58: / Line 50: @@
 Keys without any action are:
 * UserParameter_01 to UserParameter_05
 === Evaluation Type ===
 The evaluation type indicates whether the related Metaclass and all its derivates are the object you want to perform the action with (evalutation type = Metaclass) or whether you want to perform the action with all instances of the given Metaclass (evaluation type = instances).
 [[Category:Workflow|UI ACTION CONFIG]]

← Older revision	Revision as of 12:25, 2 September 2016
(No difference)

@@ Line 42: / Line 42: @@
 == Parameters ==
-Define the trigger parameters for the Action via the Parameter Relationship ("SYSREL_UIACTION_PARAMETER").
+Define the trigger parameters for the action via the parameter relation [[SYSREL_UIACTION_PARAMETER]].
 === Parameter Key ===

@@ Line 21: / Line 21: @@
 == Workflows ==
-You can define the workflows that are executed for the configuration object via a relationship ("SYSREL_UIACTION_WORKFLOW").
+You can define the workflows that are executed for the configuration object via a relation [[SYSREL_UIACTION_WORKFLOW]].
 === Properties for the Relation ===
@@ Line 46: / Line 46: @@
 |-
 |}
 == Parameters ==