 | Loading… |
|
|
|
Setting up a Workflow
        
Creating workflow definition starts with adding objects to a diagram. Every workflow definition starts with Start block. To add objects to diagram, click one of the objects in the object toolbar, and then click in the diagram at the position you want the object to be inserted (or press the mouse button, move the mouse and release the button, to insert the object with a specified size).
Every object (block) can be connected by using transitions. If a transition type is already selected (button pressed), you don't need to reselect the transition type every time you want to create a transition.
Once a transition type is selected, press the mouse button in any link point of the source block (a link point is the blue "x" displayed in the diagram object), drag the mouse, and then release the mouse button in any link point of the target block. A transition will be created connecting the source block to the target block.
After a task block is added, there are some additional properties to be set.
The task definitions are created in the task definition editor (Tasks dialog) for the Task block. When you double-click a Task block, the dialog is shown.
| Title |
Title of the task is positioned at the left side of the dialog. Under title, there's a multi-line description of the task. Here all the instructions about the task should be inserted. |
| Assigned to |
The name of the user (or group) that the task instance will be assigned to. If it is a user, a single task instance will be created and will be assigned to that user. If it is a group, then the behaviour depends on the value of property:
- MultipleTasks: This is default value. A task will be created for each user in the group. So, if a group has users "john" and "maria", one task will be created for John, and antoher to Maria, and the tasks will be independent (both will have to be concluded)
- SingleTask: A single task will be created that will be visible for all users in the group. If you later include/remove users to/from the group, the existing tasks will become not visible for users removed from the group, and will become visible to users added to group. Any user from the group can update the task, including finishing it.
|
| Status list |
Status List contains a list of the valid status for the task. The initial status of the task will be the first status in the list. Some status can be marked as completion status, by checking the "Completion" option. When the status of a task instance changes to a completion status, the task is considered finished. You can have more than one status marked as a completion status. Status with the "Hidden" option checked is a possible status to the task, but will not be displayed in user interface for changing the task status (like in the status combo box). When a task instance is created, the valid status are displayed in a grid in the task list dialog, and then user can change the status of a task. If you have status templates predefined in your application, the user will be able to choose one of the templates or either create new status. |
| Expiration |
Defines the date/time for expiration of a workflow task. If a task has a defined expiration date/time, when it exceeds this date/time without being closed by an user (changed to a completion status), its status is automatically changed to an expiration status. To use this feature check the section Running workflow instances for tasks expiration. Task does not expire, this is the default option. If checked, the task will never expire, and will keep
assigned to the current user/group until finished (changed to a completion status). Expiration term Check this option to enter an expiration term for the task, and enter the amount of days, weeks or months (integer or floating point value). The expiration date will be calculated from the creation date of the task. Expiration date/time, check this option to enter a fixed due date/time for the task. Custom date/time expression, this option allows to enter a custom expression to evaluate the task expiration date/time. The expression must return a DateTime value and may use variables from the current workflow, task properties, as well as all the features allowed in expressions. Expiration status, determines the status to which the task will be automatically changed after expiring. It must be a completion status. Date templates can also be used for expiration. Templates can be used in combination with Expiration term or Expiration date/time or standalone. Example of templates:
- dd+W.mm.yyyy - today if it's a work day or next work day (d+W is equivalent to d+0W)
- dd-W/mm/yyyy - today if it's a work day or prev work day (d-W is equivalent to d-0W)
- d+1W/mm/yyyy - next work day after today
- dd-1W.m.yyyy - last work day before today
- dd+6W.mm.yy - sixtth work day after today
- yyyy-mm-dd+5+7W - today plus five day and then get sevens work day
- dd-5W+3.mm.yyyy - today minus five work days and then plus three days
- ddp+10W.mm.yyyy - tenth work day of current month
- ddz-10W.mm.yyyy - tenth work day before end of current month
- ddp+14+2W.mm.yyyy - sencond work day after two first weeks of month
- If you need to specify 15 day of month or next work day (if 15 day is a holiday) then you can use the following template ddp+14+w.mm.yyyy
|
| Template |
Integrate a template that was created on any form. |
| Mandatory input |
Integrate Mandatory inputs that was created on a form. With a variable Automatic (True, False) and variable Automatic Status (approved, rejected, etc.) data on form is automatically fulfilled and status changed. |
 |
Run current task, opens Pantheon form. |
 |
Save and verify task settings |
 |
A timer for periodic expiration is then checking tasks. Tasks are checked every 5 minutes for expiration. |
| Loading… |
| Loading… |
|
|
|
|