Page Comparison

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 You can configure the following common properties for a task:

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

Caption
Caption The caption of the task. Captions are shown to users and can be localized when needed. Caption A caption may contain the data templates expressions to replace data from data model.

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.

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

Prework
Script to be executed before the task assigned to the role. Please refer to Task Prework Script section for more details.

Postwork
Script to be executed after the task is completed. Please refer to Task Postwork Script section for more detailsIs 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 tasks.

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

Deadline

Configures the deadline time and action for assigned tasks to complete 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 also can be set in prework script in more dynamic behavior.

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

Send Notify
Send notify notification message about deadline. This option only visible when duration 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 taken, it continues to next step on 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 taken, it continues to next step on workflow.

For evaluation you can configure following:

Enabled
Check this field to enable scheduled operation.

Schedule
Schedule of evaluation. 

Script
Script to execute on scheduled event occurs. 

Common Schedules

Hourly Schedule

Perform every on 10 minutes.

<Schedule Name="">
    <Rule Type="Hourly">
        <Duration>00:10:00</Duration>
    </Rule>
</Schedule>

Weekly Schedule

Perform every day except sunday and saturday.

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

Perform 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

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

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

Yearly Schedule

Perform every 1th day in all months (Example: 20XX-XX-01)

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

Perform start of 4th month in every year (Example: 20XX-04-01)

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

Perform at 4th month and 10th day in every year (Example: 20XX-04-10)

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

Annual Schedule

Perform 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 overriden Pool variables in task scope. Please refer 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.

Condition to Initiate
XPath expression to evaluate task allowed to initiate. XPath expression is evaluated from the active case profile.

Delayed Execution
Check this field to process the task in a delayed context. By default, Emakin executes task steps in a synchronized context until the task is assigned to a user or the workflow is completed. If you check this field, the workflow engine temporarily stops execution at the task and commits the current state to the database. The 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 the remaining operations in another error-checking context.

Variables

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

...

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

• Default The default state inherits the rules from to form. Example; formatting and conditional rules. 
  
• Enabled state permits to enter entering new information or change changing the information in the section.
• Hidden state hides section when related task run.
• Disabled state shows a related section in the form, but it doesn't permit to  add adding new information or to change changing existing information in the section.