Define the tasks that complete the process.
There are 3 types of tasks:
Every process has a "START" and "END" task. The "START" task is a user task that is presented when creating an instance of the process. It has no incoming links since it is always the first task in a process. The "END" task provides a single point for terminating a process.
When an instance of the process is created, each Task begins with an initial status of "Waiting".
A task status is changed either directly when a user completes the work on a task or indirectly as a result of defined links. A task link/dependency defines task status changes that should occur as a result of another task status change.
So in the example above, the link defines that when the "START" task status changes to "Completed" the "CONFIRM_MANAGER" task status should be changed to "Open".
So you have to define an incoming link for each task (except for START and END)
Provide a multi-lingual label for each task. If you have the auto-translate license enabled, the globe icon button will auto-translate the label to the currently selected language.
Task names default to the entered Task ID (before it is normalized for use as an ID)
Who can work this task? User and review tasks are worked by authorized users. The selected role identifies who the authorized users can be. Refer to Akumina Flow Roles Page for more information on how to use roles.
Even automated tasks require a role in order to authorize the external agents. Only external agent roles appear in the drop down.
What actions does the assigned user need to complete for this task? Click on the Task Actions button
There are 2 types of actions that can be required to complete a task.
The actions defined here will be the source for the working layout options.
Should this task be completed within a specified time period? If so, configure a due date. Select
There are 4 ways to define a task due date. Use none, any or all of the methods provided. If at least 1 due date is provided, the earliest of all of the configured due dates will be used. Reporting and notifications use due dates if provided.
If using a "Date" property to specify the task due date, the system will assume a time of 23:59:59.
Select "Edit Content"
From this pop-up, you can design the view layout that the assignee will see when they are working the task. There are 2 different layouts used when working a task. Select the desired layout from the radio buttons provided at the top of the pop-up window:
This page is made up of 4 logical sections:
There are 2 recommended approaches for styling the views:
You don't need to add "Task Buttons" to your view. The widgets will add standard task buttons (e.g., Save, Cancel, Submit) if not provided. But you may want to control what task buttons are included and have more control over their display. If so, add the Task buttons and then configure them (via CKEditor source window) as you need.
Akumina Flow Layouts use Knockout JS for 2 way binding. This framework offers the flow designer additional tools to control the UI. For example, if you have a form that has questions that should only be displayed based on the answer to a previous question, you can use knockout to implement this. For this discussion, assume there is a choice question that asks the employee their highest level of education. The valid choices are: High School, College. And if the user selects "College", another question should be displayed which asks them their major area of study. A simple html for this, using knockout js is shown below:
<li class="ia-tp-property-value">
<label for="EDUCATION1642778154469"><strong>Education<span style="color:red"> *</span></strong>:</label>
<div class="ia-input-group" data-bind="css:{'ia-text-input-invalid':!actions.isEDUCATIONValid()}" id="EDUCATION1642778154469">
<select data-bind="value:actions.propEDUCATION"><option value="HIGHSCHOOL">High School</option><option value="COLLEGE">College</option>
</select>
</div>
</li>
<li class="ia-tp-property-value" data-bind="visible:actions.propEDUCATION() == 'COLLEGE'">
<label for="MAJOR1642778154469"><strong>Major</strong>:</label>
<div class="ia-input-group" id="MAJOR1642778154469">
<textarea data-bind="value:actions.propMAJOR" maxlength="512" rows="5"></textarea>
</div>
</li>
The key code is the data-bind="visible:actions.propEDUCATION() == 'COLLEGE'" attribute that was added to the "li" that displayed the "Major" question.
The internal development name for Akumina Flow is "Team Process". You will see that naming convention on lower level development resources and the API.