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.  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. 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

...

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 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.

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.

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.

Deadline

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

Duration
Duration of deadline after the task is assigned.  Duration can be selected from the 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 behaviorbehaviour.

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

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

...

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

Start Point

If the 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 the 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 You can configure the following for evaluation:

Enabled
Check this field to enable scheduled operation.

...

Script
Script to execute when scheduled event occurs. 

Common Schedules

Hourly Schedule

Performs after every 10 minutes.

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

Weekly Schedule

Performs every day except sunday Sunday and saturdaySaturday.

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

Performs only once on mondaysMondays.

<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>

...

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

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

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

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

Annual Schedule

Performs by on a 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 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 allows permits entering new information or changing the information in the section.
• Hidden state hides the section when related task runsrun.
• Disabled state shows a related section in the form, but it doesn't allow to add permit adding new information or change changing existing information in the section.