|
|
| __Active__ indicates if the process is free from errors and available for public use.
|
|
|
| -__Valid__ is a {img src=/Galaxia/icons/green_dot.gif} green or {img src=/Galaxia/icons/red_dot.gif} red circle indicating whether the process can be activated or not. This is dependent on whether it has any errors - mentioned above.
|
| +__Valid__ is a {img src=/galaxia/icons/green_dot.gif} green or {img src=/galaxia/icons/red_dot.gif} red circle indicating whether the process can be activated or not. This is dependent on whether it has any errors - mentioned above. |
|
|
|
|
| Lastly, the __Action__ icons are shortcuts to administer the process's activities, instances and other components. These are:
|
| -* {img src=/Galaxia/icons/Activity.gif} __activities__ - This is a shortcut back to the __Admin process activities__ page.
|
| -* {img src=/Galaxia/icons/book.gif} __code__ - This is a shortcut back to the __Admin process sources__ page.
|
| -* {img src=/Galaxia/icons/myinfo.gif} __roles__ - This is a shortcut back to the __Admin process roles__ page.
|
| -* {img src=/Galaxia/icons/export.gif} __export__ - This allows you to save a process to an XML file for later uploading.
|
| +* {img src=/galaxia/icons/Activity.gif} __activities__ - This is a shortcut back to the __Admin process activities__ page. |
| +* {img src=/galaxia/icons/book.gif} __code__ - This is a shortcut back to the __Admin process sources__ page. |
| +* {img src=/galaxia/icons/myinfo.gif} __roles__ - This is a shortcut back to the __Admin process roles__ page. |
| +* {img src=/galaxia/icons/export.gif} __export__ - This allows you to save a process to an XML file for later uploading. |
| + |
| +Click on the first __Action__ icon - __activities__ {img src=/galaxia/icons/Activity.gif}. |
|
|
| -Click on the first __Action__ icon - __activities__ {img src=/Galaxia/icons/Activity.gif}.
|
| !Admin Activities
|
| -Activities are actions that are performed during your process. A process can consist of many activities. By default, a ''start'' and ''end'' activity are created for you, but these can be renamed or deleted at a later stage. I'll define two other terms so you can understand their context later.
|
| +An ''Activity'' is an action that is performed during your process. In Galaxia activities are mapped to PHP scripts so an activity can do anything that can be done from a PHP script. A process can consist of many activities. By default, a ''start'' and ''end'' activity are created for you, but these can be renamed or deleted at a later stage. I'll define two other terms so you can understand their context later. |
|
|
| An ''instance'' is a particular process currently being executed. An activity can have many instances associated with it at any time. An instance is created when a process is initiated by a user and the instance will pass through the process activities until the process is terminated or completed.
|
|
|
| A ''transition'' is the path between two or more activities. A transition defines what has to be done after each activity is completed.
|
| + |
| +A ''workitem'' is added to the instance when an activity is completed. Workitems thus represent completed activities. |
|
|
| Activities are broken up into different types. Here are two types listed below:
|
| -* {img src=/Galaxia/icons/mini_circle.gif} __start__ - This activity type marks an entry point into the process. A process can contain many start type activities allowing for multiple ways to begin a process. Processes with many start activities are very strange but possible. Every process must contain at least one start activity. Instances are created when a start activity is executed. No transitions can lead to a start activity and only one outgoing transition is allowed per start activity.
|
| -* {img src=/Galaxia/icons/mini_dbl_circle.gif} __end__ - This activity type marks the end point of the process. When an instance reaches the end activity the process is considered completed. A process can must contain only one end type activity. This doesn’t mean that processes can’t end in different ways. Since the end activity represents the process end, how the process ends depends on the activities visited beforehand. The end activity can have many inbound transitions but Outbound transitions are not allowed.
|
| -* {img src=/Galaxia/icons/mini_rectangle.gif} __activity__ - Normal activities don’t have any special meaning so they are used to represent things that should be done as a part of a process. Normal activities can receive many inbound transitions but can only have one outbound transition.
|
| + |
| +* {img src=/galaxia/icons/mini_circle.gif} __start__ - This activity type marks an entry point into the process. A process can contain many start type activities allowing for multiple ways to begin a process. Processes with many start activities are very strange but possible. Every process must contain at least one start activity. Instances are created when a start activity is executed. No transitions can lead to a start activity and only one outgoing transition is allowed per start activity. |
| +* {img src=/galaxia/icons/mini_dbl_circle.gif} __end__ - This activity type marks the end point of the process. When an instance reaches the end activity the process is considered completed. A process can must contain only one end type activity. This doesn’t mean that processes can’t end in different ways. Since the end activity represents the process end, how the process ends depends on the activities visited beforehand. The end activity can have many inbound transitions but Outbound transitions are not allowed. |
| +* {img src=/galaxia/icons/mini_rectangle.gif} __activity__ - Normal activities don’t have any special meaning so they are used to represent things that should be done as a part of a process. Normal activities can receive many inbound transitions but can only have one outbound transition. |
|
|
|
|
| -* {img src=/Galaxia/icons/mini_diamond.gif} __switch__ - A switch activity represents a point of decision in a process. Instances reaching a switch activity are evaluated and depending on programmed conditions, the instance is routed to different activities. Switch activities can have many inbound transitions and many outbound transitions.
|
| -* {img src=/Galaxia/icons/mini_triangle.gif} __split__ - When two or more activities in a process can be performed independently in paralell - a split activity is used to split the an instance, routing the same instance to many activities. This allows an instance to be in many activities at the same time. Split activities represent subflows in a workflow. A split activity can receive many inbound transitions and can have many outbound transitions.
|
| -* {img src=/Galaxia/icons/mini_inv_triangle.gif} __join__ - A join activity is used to re-group multiple instances from a split activity. When an instance reaches a join activity, it is verified that all other related instances have reached the join activity. At this point, the instance can be directed to the next activity. Join activities can have many inbound transitions (more than one is expected) and can only have one outbound activity.
|
| -* {img src=/Galaxia/icons/mini_hexagon.gif} __standalone__ - A standalone activity is not part of the normal flow of the process and are not related to process instances. A standalone activity can be executed any time by a user with the right permissions. These activities are ideal for data management related to the process, listings, adding items, removing items, etc. If there is no order relationship between different activities in a process, it can be designed as a set of standalone activities. Otherwise a processes will consist of a route of activities and a set of auxiliar standalone activities. Standalone activities can not have inbound or outbound transitions.
|
| +* {img src=/galaxia/icons/mini_diamond.gif} __switch__ - A switch activity represents a point of decision in a process. Instances reaching a switch activity are evaluated and depending on programmed conditions, the instance is routed to different activities. Switch activities can have many inbound transitions and many outbound transitions. |
| +* {img src=/galaxia/icons/mini_triangle.gif} __split__ - When two or more activities in a process can be performed independently in paralell - a split activity is used to split the an instance, routing the same instance to many activities. This allows an instance to be in many activities at the same time. Split activities represent subflows in a workflow. A split activity can receive many inbound transitions and can have many outbound transitions. |
| +* {img src=/galaxia/icons/mini_inv_triangle.gif} __join__ - A join activity is used to re-group multiple instances from a split activity. When an instance reaches a join activity, it is verified that all other related instances have reached the join activity. At this point, the instance can be directed to the next activity. Join activities can have many inbound transitions (more than one is expected) and can only have one outbound activity. |
| +* {img src=/galaxia/icons/mini_hexagon.gif} __standalone__ - A standalone activity is not part of the normal flow of the process and are not related to process instances. A standalone activity can be executed any time by a user with the right permissions. These activities are ideal for data management related to the process, listings, adding items, removing items, etc. If there is no order relationship between different activities in a process, it can be designed as a set of standalone activities. Otherwise a processes will consist of a route of activities and a set of auxiliar standalone activities. Standalone activities can not have inbound or outbound transitions. |
| In our first example, we will only use the defaults, __start__ and __end__.
|
|
|
| -=Add or edit an activity=-
|