Databases Reference
In-Depth Information
By default, a participant type of
Single
approver is selected, which is fine for our
purpose. Labels are used to provide a meaningful description of the routing rules
and are also useful if we specify multiple participants for a stage. So for our purpose,
just enter a meaningful value (for example,
Manager Approval
).
We now need to specify the
list
of participants that the task is going to be assigned
to. Each participant can either be a specific user, group, or application role (and we
can have any combination of these in our list).
For our purpose, we are going to assume that the CEO of the company is required to
approve every holiday, so we will always assign it to
cdickens
. This is probably not
ideal! But we will revisit this later in the chapter to look at how we can make it
more realistic.
Click on the plus symbol, and select
Add User
, as shown in the preceding
screenshot. This will add a participant of type
User
to our participant list, as
shown in the following screenshot. We can either directly enter the name of a user
into the
Value
field or click the browse icon (
…
) to bring up the identity lookup
dialog. This allows you to search and browse the users and groups
defined in the identity service.
Once you've specified the participant details, click
OK
; this will take us back to the
task definition window, which will have been updated with our routing policy.
Select
Save
on JDeveloper to make sure you save the task definition.
