Process Simulation
|
|
FlowRunner Designer allows
processes to be tested
without having to deploy
them to the server.
The
builtin debugger simulates
process execution as it would run on
the server,
without
having
to deploy the procedure to the server
or even being connected to
one.
The process simulation
feature is a final step of
create / modify / test cycle
that empowers
a business
user to design and test a
complete business process in
an integrated environment,
without the need for
external connectivity.
|
- Process execution is moved
forward by selecting an active
step
- Process execution stack
can be undone (popped) by
pressing back button
- Process execution can be
stopped at any time
|
 |
When executing a process backwards (popping the
execution stack) the data modified by the
previous step is restored to its original state
prior to step's execution. This work for both
human and
automated steps. |
|
|
HTML user forms are
available during simulation
-
Active HTML forms are fully
operational to accept user
input
-
Filled forms
update instance data
during process simulation
-
Client-side validation
rules are effective as if deployed
to the server
-
HTML forms
can be edited while the
simulation is in progress
-
Automated
steps are editable.
Scripts can be edited and
saved during the
simulation
-
Automated
steps can be executed at
any time during the
simulation, regardless of
whether they are currently
active or not
|
 |
|
Runtime data view
As process is being
simulated its runtime data
may get modified.
FlowRunner's Data tab
will display the current runtime
values. This is most useful
when executing custom steps
that modify instance data.
- Newly updated fields are
displayed in alternate
color
- Both human and system
steps are supported
|
 |
|
|
Improved Test / Modify
cycle
The ability to pause and undo process
execution coupled with the
ability to modify forms
during the
simulation time makes
FlowRunner Designer a superb
development environment.
All plausible execution
paths of a given business
process can be tested in a
single simulation session by
traversing backward (popping
the execution stack),
altering form data and
moving forward.
This shortens the
total design time and
minimizes the number of
future revisions when
deployed to the actual users. |
 |
|
Next section:
Business Rules »
|
Want to evaluate our software? Complete the information request form.
