Page 293 -

10 The Resource Service 289
patterns applicable to non-case-handling paradigms. Although it is the default
resource enabler for YAWL, its architecture means that it may be substituted with
other work handlers, if desired. Additionally, its pattern support is fully external-
ized, so that other worklist representations and visualizations can be constructed
that make full use of, and extend from, the service’s capabilities. Also, the service’s
default dynamic forms generation can easily be superseded by custom designed
forms that meet the implementing organizations own requirements. The service
supports the importing of organizational data from external sources, in addition to
supplying a default data structure for that purpose. The sets of filters, constraints,
allocators, and codelets may be added to at any time, to extend the capabilities of
the service to individual requirements. While providing extensive support for the
resourcing of work, the service is also flexible and extensible, and so meets a wide
variety of organizational needs.

Exercises

Exercise 1. What is the difference between a manual and an automated task? If
an automated task is handled by a custom service other than the Resource Service,
what will be the result?

Exercise 2. What is meant by the late binding of tasks to resources? How is it
achieved by the Resource Service?

Exercise 3. Log on as an administrator to YAWL, and go to the “Org Data Man-
agement” form. On the “Roles” tab, add two new roles called “Client Service” and
“Public Relations.” Make the “Client Service” role report to “Public Relations.”
Now, go to the “User Mgt” form and add five new participants: Alan Black, Bobby
Brown, Carly Blue, Doris Orange, and Elvis Green. Give Alan and Bobby the
“Client Service” role, add the rest to “Public Relations.” In the YAWL Process Edi-
tor, Create the simple process shown in Fig. 10.9; assign the “Client Service” role
to A and “Public Relations” to B. Save the specification. Back at the YAWL web
forms, go to the “Case Mgt” form, load the specification you just created, and start
a case. Now, go to the “Admin Queues” form. A and B should appear in the ‘Work-

Fig. 10.9 A simple process model (see Exercise 3)