< Previous | Next >

Create the human task implementation

You will now create the implementation of the human task component.

  1. Double-click on the HelloWorldTask component. Click Yes on the Open dialog indicating you do want to create the implementation. Click OK on the Generate Implementation dialog indicating you want to create the implementation file in the project's root folder. The human task editor opens, as shown here:
    Picture of HelloWorldTask in the human task editor
  2. Strictly speaking, there is nothing more you need to do here, but you want to learn! So click in the white space of the editor canvas, near the bottom. Then select the Properties view below the editor, and the Details tab.
  3. In the bottom right of the properties view, click the check box Bind the life cycle to the invoking business process, as shown here:
    Human task properties

    This action ensures that outstanding instances of this task (to-dos) will be cleaned up when the process that invoked the task is cleaned up.

  4. Select the Duration tab in the Properties view. Set the Duration until task expires to 6 minutes. This way it will clean itself up if you forget to claim and complete it in a reasonable amount of time.
    Duration properties of the human task
  5. In the editor canvas, note the People Assignments section, as shown here:
    People assignments section

    By default, anyone can create instances of this human task (in other words, create to-dos), and anyone can claim those instances and work on them. However, you can restrict that. Select the Everybody cell in the Potential Owners row, and go to the Properties page. There is only one tab – Assign People. In the People assignment criteria list, select User Records by user ID as shown here:

    Assign people tab

    Scroll down in the Assign People property view and set the user ID to that specified for the server at install time. If you did not change it, then it will still be admin.

    Escalations section

    In the People Assignment section you see that the table has changed:

    People assignment table

  6. Optional: Note the Escalations section, as shown here:
    Escalations section


    In addition to specifying a duration for how long users have to process a task before it expires, you can also specify a series of escalation actions in case the task is not claimed in a certain amount of time after it is created (Ready state), or in case it is not completed in a certain amount of time after it is claimed (Claimed state).

    Actions include creating a new to-do task for someone else, or sending an email notification. This is where you set these escalations up, using the green “plus” button when one of the state icons is selected.

    There is an online sample that explores escalations.

  7. Note: For both durations and escalations, you can specify not only elapsed time not only with absolute hours, minutes or days, but you can also specify it with a business calendar. By creating and specifying a business calendar, you can identify non-contiguous time, allowing for example that it escalates only after two business days have elapsed.
  8. Close and save the human task editor, and save your work in the Assembly Diagram so far.





Feedback



(C) Copyright IBM Corporation 2007, 2008. All Rights Reserved.

< Previous | Next >