Directory Interface |
Most real life use cases
involving users in business
processes are quite complex.
Users are usually tasked
based on their location in
a corporate hierarchy, their
responsibilities and domain
knowledge. Very often the
information used to make the
decision whether to task a
user is stored in a
corporate directory.
Many other products require
the user to simply type in a
complex expression and hope
it works when deployed. This is
highly unlikely. Many things
could go wrong. There could
be an error in expression
itself, or users might not
exists, or there is a type
mismatch in expression.
FlowRunner works with
existing
LDAP-based
directory out of the box.
Just configure and connect.
Users, groups, attributes
will simply become available
for simple or complex task
assignments.
Most of the complicated user
addressing scenarios are
handled with ease by one of
a kind filtering
capabilities available in
FlowRunner Designer.
|
 |
|
|
Highlights
- Multiple addressee items per
user step. A task can be
sent to multiple
organizational branches at
the same time
- Any directory item can be
configured as a starting
point of an individual
addressee item
- Multiple search filters
per addressee item are
supported
- Directory attributes are
typed. Type-specific
operators are used when
specifying individual search
filters
- Search expressions can
involve process data. This
is needed for dynamic task
assignments
- Scripted expressions can
be specified in search
filters
|
|
|
Reveal Users
Addressing a task to users
can sometimes involve
complex search criteria. To
minimize errors at
deployment time the task
assignment rules need to be
tested at design time.
Web Runner Designer offers Reveal Users button on both
the addressee item level and
on aggregated (step) level.
When this button
is invoked the software makes a
directory request with
parameters specified at
design time. A dialog box
containing the list of users is
displayed. If the box comes
back empty, there is a good
chance the task will end up
in the undelivered
box. |
|
|
|
Next section:
Deployment » |
|
|