A key value of BPM is supporting the interaction between automated process steps and steps requiring human interaction performed by an assignee.Processes interact with human tasks through Task steps.

 

Introduction to Tasks:

A task represents human interaction in a business process, a unit of work that a My webMethods user must complete before the business process can proceed. Tasks are started from task types that are published to My webMethods Server from webMethods Designer.

 

webMethods Designer Task Development provide you to create tasks that perform  human activity that will be carried out at run time like approving an order.you can create task user interface web applications with Designer. These task user interface applications can be published to other runtimes, such as Apache Tomcat, Oracle WebLogic Server, where they can interact with tasks running on the Task Engine within My webMethods Server.

The task itself runs on the Task Engine within My webMethods Server and the Process Model runs on the Process Engine within Integration server.So for start the work with task we have to first configure the Task Engine.

Using IS Administrator you must a configure a connection between the Process Engine and the Task Engine that it is to work with.

Configuring the Task Engine in My webMethods

Use the following procedure to configure a connection from the Task Engine on My webMethods Server to that Integration Server.

 

•              In My webMethods: Navigate > Applications > Administration > My webMethods > System Settings > Task Engine
•                   In the Task Engine Settings we have to put Username,Password,    information.
•                  In the Integration Server (Process Engine Host) area we have      specify values for Host and Port of the IS

·         If you are connecting to the Integration Server in a Secure Socket Layer environment, select the Use SSL check box.

·         Click save for saving all this details.

 

 

Setting Task Development Preferences:

You can set  Task Development preferences:

·         In the main menu, click Window > Preferences >+ Software AG > Task Development.

 

•          On the Task Development page, click any of the following preferences:

 

 

1.      Automatic task creation using “Implement with New Task” in the process editor:

When this check box is selected, the Task wizard does not appear, and the task is created with the default settings.

2.      Default task project name created from the process editor:

Use this box to specify the default name for the composite application project containing tasks you create from within the process editor. The default value is {0}Tasks. The variable {0} represents the name of the process you are adding a task to.

3.      Always use GUID for new Task Type ID:

When this check box is selected, an automatically generated globally unique identifier (GUID) to a new task when the task is created. For example of the type of GUID that is automatically generated is: 1736DJ52-9E63-316F-5H83-GH8E141EF123

When this preference is not selected, we have several choices when we are creating a new task. We can: Manually request that Designer generate a GUID for the task type ID orType your own unique task identification or Accept a task type ID based on the project name and task type name.

4.      Create Task View Portlet for new Task:

Select this preference to always create a task view portlet when a new task is created.

5.      Create Task Start Portlet for new Task:

Select this preference to always create a task start portlet when a new task is created.

6.      Create Task Inbox Portlets for new Task:

Select this preference to always create two task inbox portlets when a new task is created

click OK to apply your selections and close the Preferences dialog box.

 

 Task Features:

The following key features are available with the tasks we create:

·         Portable Task Interfaces:

Using Designer you can create a portable task interface application for any task you create. In this case, the task itself runs on the Task Engine within MWS, but the portable task interface associated with the task can be published to other runtimes (such as Tomcat), where the user can use it to interact with the underlying task through Task Engine web services.

·         E-form Integration:

Designer enables you to integrate electronic forms (e-forms) into the task workflow. Supported e-form templates can be imported into webMethods Designer where they are converted to a standard IS document type. You can use the IS document type as the business data for a task, or for any other supported IS document type use. We can implement flexibility for users to download and upload an e-form from.

·         Collaborative Workflow:

Designer and MWS provide a set of design-time and run-time functions that allow users to create, modify, assign, and view free-form comments within the task they are working on. Tasks also provide the ability for users to add or delete attachments. We can define how business data and other task information is shared among collaborative users.

·         Task E-mail Notifications:

webMethods Designer enables you to create a task e-mail notification that can be sent to any MWS user who is subscribed to the notification. You can also include a Task Action Link control in the e-mail notification.

Task Creation:

We can create tasks using many ways :

1.      On the UI Development perspective:

a.      By starting the Task wizard with the File > New > Task menu command.

 

 

b.      By clicking the New > Task arrow button in the main toolbar.

c.       By clicking the New button on the main toolbar, expanding Software AG > Composite Applications, and clicking Task.

2.      By right-clicking an existing project in the Tasks folder of the Solutions view and clicking New Task.

3.      By right-clicking an IS document in the Package Navigator view and clicking CAF > Generate New Task.

 

 

 

4.      By right-clicking a task step within a process model and clicking Create Implementation > New Task.

Once clicking on new task:

Select an existing project name from the drop-down list, or click the New button to create a new task application project.Than there is two option is coming :

·         Enable advanced options in this wizard

If check this option than we can create a task with the advanced option otherwise task will create with default settings.

·         Don't show this wizard next time and auto create new task

In this case tasks are always created with the default settings.

 

If you want to work with the advanced options, click Next. Otherwise click Finish to create the task.

 

 

           If you click Next, the Task Information page appears.

·         In Task Information page:We have to give task type name .Task type Id is automatic generated or else we can create by using button”generate”

·         Task view Option:

Enable User Routing: Select this check box to provide the ability for a user to forward a task in the user’s inbox to another user.

Auto Accept Task upon Modification: Select this check box to cause a task to be automatically accepted by a user when the user modifies the task

 

·         And as per the requirement we can customize the settings  for below portlets

 

Task Details View Portlet

Task Audit View Portlet

Task Comments Portlet

Task Collaboration Portlet

 

Generate default Task Start portlet: Select this check box to include a default Start portlet in the task.

Generate default Task Inbox portlets: Select this check box to include the default Task Inbox Bar and Task Inbox Results portlets in the task.

Accept Task on Open: Select this check box to cause a task to be automatically accepted by the first user to open the task from the task type inbox.

 

·         Click Finish to create the task.

 

 

After the new task is created, the task appears under the task application project in the Solutions view, as well as the Navigator view, and all other locations where tasks are displayed.

 

Now we can add task business data, define task assignments and event actions, and create task rule sets.

 

Adding a Task to a Process

If we develop a process within webMethods Designer, and we want  to add one or more tasks to the process to represent human activity. So we have two ways to add task in out Process:

·         We can create a task step within the process and then implement a new task from the task step.

·         We can Add a Task by Drag and Drop

·         We can Add a Task by Selecting from a Task List

Creating a New Task from a Task Step in a Process

·         Add a new Activity step to the process.

 

•                  Right-click the Activity step, click Change Step Type, and click Task.

 

 

•          Right-click the task step and click Create Implementation > New Task

 

Than New task window is open and we can proceed same as above describe.

 

 

In Overview Tab Task summary is showing with all information about the task like:

·         General Information-Task Type Id,Task Type Name,comments..etc.

·         Task assignments

·         Task Business Data

·         Task Events and user Interfaces

 

 

Create a task assignment:

After you create a task you can create one or more task assignments. This enables you to select different assignee lists and conditional behavior for different task implementations in the run-time environment.

•          Use add button to add new assignment. For this we have to give assignments name, Assignments description and we can also define Rule set.
•          We can define Assignee for task. Assignee can be a Role, User or a service.

 

 

Create a Event:

Click the Events tab of the task editor and click the event you want to work with in the Events list.

·         In General area:

we have to specify Event Name, Event Description, Rule set.

·         In Event Type:

Select event type as per condition. Here we can define Task Event action perform on which event type.

Event types are-Accepted, Assigned, Cancelled, Comment Added,Queued..etc.

·         In Event action:

You must specify an action that occurs when the task event type is triggered in the run-time environment.

Some Simple Event actions are- Accept,send notification,Invoke Service..etc.

 

 

Click default view of the task for customize task view.You can add Business data in Default view of the task for task details in MWS.

 

 

Properties for task:

 

In webMethods Designer Task have some properties:

·         General:we can set Label,Font Style,Step ID,Description and Actor for the Task.

 

 

·         Inputs/Outputs:in this we are able to see Inputs and Outputs of task.we can edit Data Mapping.

 

 

·         Transitions:In this we can define Transition Type like 'If condition'.'Else','Error'..etc for flow of task as per any conditions

 

 

·         Documentation:This Properties we can use for documention on Task.

·         KPIs:In this properties we can define business KPIs for Task.

 

 

 My Inbox:

The My inbox views is implemented by an own portlet and aggregates all tasks instances  assigned to the MWS user in a list.

The list is specific to a user.In contrast to other views,no filters can be applied.

 

 

Task List Management:

The Task List Management view is implemented by an own portlet and shows all available task instances.To reduce the number of displayed task instances,filters can be applied.This view should be visible to task list administrators only .

 

Task Inbox:

The Task inbox view is implemented by an own portlet ans shows a list of task instances related to a certain task type .The resulting list can be influenced by applying certain filters.

Task Instances Details:

Task instances details is shown as follows up af all previous view when selecting a Task ID.It offers different views which can be customized and enabled/disabled.Below three views are provided:

 

•          Data View:Shows user interface with task business data .
•          Details View: Shows Task related system Data.
•          Audit View: shows the task audit data for the task instances.
•  

 

 

 Task engine Administrator:

In My webMethods: Navigate > Applications > Administration > Business > Tasks > Task Engine Administration

Task Configuration Portlet allows to:

 

•          Search for tasks of certain type
•          Start a Task instances rules
•          View Assignments
•          View filters
•          View Schedules
•          View changes Reules deletions
•          Delete all related Task instances
•          Delete checked Task type

 

 

Click on Task type ID link to see details page :

Task Type Details page allows to enable/disable a Task Type for execution and analysis.

Communication between Process Engine and Task Engine:

At Runtime, Process Engine Calls Task Engine via SOAP communication to execute a desired task acting as implementation of a task step of a process instance.

Process Flows between Process Engine and Task engine is:

 

•          When Process Execution reaches a task step, control is passed from the process Engine within IS to the Task Engine running inside MWS.A Task instance is created.
•          The Task Engine manages the task instance.
•          Users and administrators manage and manipulate task instances the assigned task interfaces. If Configered,Task Notification will be send using SMTP.This is related to events like change to the task state, such as Task is queued,accepted,completed etc..
•          When a Task instance is finished, the Task Engine calls.

Task oriented BPM:

BPM includes human interactions.Human interaction is covered by tasks.With task oriended BPM,users have a single list of action requiring their attention: tha Task Inbox.

With a Task Oriented BPM users also more easily understand the priorities and order of their action they must perform.

Process designers clearly define a unit of work which formalizes and simplifies human interaction with automated processes.