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

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

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

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 completecompleted. 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 save saving the current state and perform remaining operations in another error checking context.

...

Configures the deadline time and action for assigned tasks to complete 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 can be set in 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 notify notification message about the deadline. This option is only visible when duration defineda duration is defined.

Evaluation

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

...

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 on 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 on of a workflow.

For evaluation you can configure following:

...

Schedule
Schedule of evaluation. 

Script
Script to execute on when scheduled event occurs. 

Common Schedules

Hourly Schedule

Perform Performs after every on 10 minutes.

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

Weekly Schedule

Perform Performs every day except sunday and saturday.

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

Perform 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

Perform Performs 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 Performs every 1th 1st day in all months (Example: 20XX-XX-01)

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

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

Perform at Performs on 10th day of a 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 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 refer to the pool page for more information.

...

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