Tasks

A task defines a step in the process diagram. Tasks can be defined as user tasks or module tasks to execute automated steps in a workflow. Every task has a list of actions to complete the step in a workflow.

For a task you can configure following common properties:

Name (Not visible on diagram)
Name of the task. Name information is not visible to users, and is being used to identify the task.

Caption
Caption of the task. Captions are shown to users and can be localized when needed.

Type
Type of the task. A task can be Normal or Module.

Is Start Point ?
Specifies the task if it is the start point of workflow or not. It color is green. You can use that feature just for the start task.

Is Case Handler?
When you click this option, the task-related form is used in the case.

Instructions
Enter the descriptions for the task. The explanations will appear in the notification/reminder e-mails, under the form title and in the tasks falling on the job lists.

Role
The role to which the task will be sent is selected.

Allow Forwarding?
Click to permit users else to assign.

Is Hidden?
Click to hide the relevant task from users with reading permission. This feature can be used in starting task.

Delayed Execution
Check this field to process the task in delayed context. By default, Emakin executes task steps in synchronized context until task is assigned to a user or workflow is completed. If you check this field, workflow engine temporarily stops execution at task and commits the current state to the database. Remaining execution is performed in another transaction. In some cases you may need to use this field to ensure saving the current state and perform remaining operations in another error checking context.

Prework
The script which is executed before the task is assigned to the role. Please refer to the Task Prework Script section for more details.

Postwork
The script which is executed after the task is completed. Please refer to the Task Postwork Script section for more details.

Deadline

Configures the deadline time and action for assigned tasks to be completed automatically.

Duration
Duration of deadline after task is assigned. Duration can be selected from list or can be manually entered in "d.hh:mm:ss" format. Duration can also be set in the prework script in a more dynamic behavior.

Action
Action to be selected if the deadline occurs. This option is not mandatory if auto completion of task is not requested.

Send Notify
Send notification message about the deadline. This option is only visible when a duration is defined.

Evaluation

Configures the task to perform scheduled operations. Depending on the task type, performs following:

Start Point

If task is configured as a start point, emakin periodically initiates new instances depending on the schedule and executes the evaluation script. When any action is taken, it continues to the next step of a workflow.

Normal

If task is configured as an intermediate task, emakin periodically checks any waiting tasks and executes the evaluation script on it. When any action is taken, it continues to the next step of a workflow.

For evaluation you can configure following:

Enabled
Check this field to enable scheduled operation.

Schedule
Schedule of evaluation.

Script
Script to execute when scheduled event occurs.

Common Schedules

Weekly Schedule

Performs every day except sunday and saturday.

Weekly

<Schedule Name="">
    <Rule Type="Weekly">
        <DayOfWeek>Sunday</DayOfWeek>
        <DayOfWeek>Saturday</DayOfWeek>
    </Rule>
</Schedule>

Performs only once on mondays.

<Schedule Name="Weekly Leave Request Report">
    <Rule Type="Weekly">
        <DayOfWeek>Sunday</DayOfWeek>
        <DayOfWeek>Tuesday</DayOfWeek>
        <DayOfWeek>Wednesday</DayOfWeek>
        <DayOfWeek>Thursday</DayOfWeek>
        <DayOfWeek>Friday</DayOfWeek>
        <DayOfWeek>Saturday</DayOfWeek>
    </Rule>
    <Rule Type="Daily">
        <Start>09:05:00</Start>
        <End>09:05:59</End>
        <Invert>True</Invert>
    </Rule>
</Schedule>

Daily Schedule

Performs every day, exactly at 16:01:00.

Daily

<Schedule Name="">
    <Rule Type="Daily">
        <Start>16:01:00</Start>
        <End>16:01:59</End>
        <Invert>True</Invert>
    </Rule>
</Schedule>

Yearly Schedule

Performs every 1st day in all months (Example: 20XX-XX-01)

<Schedule Name="">
    <Rule Type="Yearly">
        <Day>1</Day>
   </Rule>
</Schedule>

Performs at the beginning of a 4th month in every year (Example: 20XX-04-01)

<Schedule Name="">
    <Rule Type="Yearly">
        <Month>4</Month>
   </Rule>
</Schedule>

Performs on 10th day of a 4th month in every year (Example: 20XX-04-10)

<Schedule Name="">
    <Rule Type="Yearly">
        <Day>10</Day>
        <Month>4</Month>
   </Rule>
</Schedule>

Annual Schedule

Performs by yearly basis. It basically excludes the date given and runs the scheduled task on every day except the given one.

<Schedule Name="">
    <Rule Type="Annual">
        <Date>2000-02-25T00:00:00.0000000+00:00</Date>
   </Rule>
</Schedule>

Variables

List of the overriden Pool variables in a task scope. Please refer to the pool page for more information.

Forms

This feature can be used to set form to default, enabled, hidden or disabled status for each task. Forms feature becomes available after determining an element in the form design part. You can decide section status for every process step.

Default state inherits the rules from to form. Example; formatting and conditional rules.
Enabled state allows entering new information or changing information in the section.
Hidden state hides the section when related task runs.
Disabled state shows related section in the form but it doesn't allow to add new information or change existing information in the section.