Tutorial

PaseoExpress is free software for developer and operations manager. Download freeware PaseoExpress

Content

• Introduction
• Creating a model scenario – Basic functions
• Basic principles
• Creating a variable
• Components
• Using sequences
• Execution Monitor
• Access Execution Monitor
• Execution Monitor interface
• Initiating a scenario's execution

Using sequences

You can use sequences to conditionally or unconditionally link components, and to specify how they are executed.

To use a sequence (color arrow), you must select it by clicking on it in the <Sequences> pane. Actually, there are five types of sequences:

Followed Sequence in case of success of the father component
Followed Sequence in each state of the father component
Followed Sequence in case of execution error of the father component
*************

IMPORTANT NOTE: Components Implicit variables Components have so-called "implicit" variables. Implicit variables are specific system variables, they are linked with the component and are to be modified during the execution. Although they are managed entirely by the Paseo engine, they are accessible to the user in certain circumstances. These variables are visible in the variables manager, in the treatments section.

These implicit variables are:

Status: The variable Status indicates the current status of a process: StandBy, Running, Success or Error. This variable is used in all the triggers conditions.

*************

Then simply select the starting component in the Scenario pane by left-clicking on it and dragging it over the next component (without releasing the mouse button). The sequencing link is established when you release the button over the second component.

If necessary, you can then configure the sequence conditions by selecting the child component and specifying the formulas in its properties.

In our example, the first specified sequence reads <Test file(s) presence> and <Create file>. It is an <Not Triggered> sequence. This sequence executes the <Create file> process if <Test file(s) presence> does not detect the expected file.

To initialize this operation, click on the <Succeeded> sequence and drag the mouse from <Test file(s) presence> to <Create file> without releasing the left-click.

The second sequence links <Create file> and <Rename file(s)>, which will only be executed if the file was generated successfully.

To configure this sequence you must select the Successful sequence and link <Create file> to <Rename file(s)>. This ensures that the management process is run automatically if the file is successfully created by <Create file>.

The sequence handles the case where the file expected by the <Test file(s) presence> component is detected normally.

The components are now interlinked and the scenario can be executed.

To modify the conditions of execution:

However, to obtain the desired sequencing behavior, you must first modify a parameter that is configured automatically by the sequences. This change is necessary because a component that is linked by more than one sequence to more than one component cannot be executed unless all the parent components are in the complete state.

This would never happen in our example, given that depending on the result of the file detection operation performed by <Test file(s) presence>:

• Either <Create file> will not be executed and therefore never complete
• Or else <Test file(s) presence> will be in the <Not Triggered> state and therefore never complete.

The condition set by the sequences automatically, however, stipulates that <Rename file(s)> can only be executed if <Create file> AND <Test file(s) presence> are both in the complete state simultaneously. This condition must therefore be changed to stipulate that a single complete state is required in order to authorize the execution of <Rename file(s)>.

To change the execution condition settings, select the <Rename file(s)> component and access its formulas by opening the popup menu (right-click) and selecting <Properties> \ <Formulas>.

You can then change the execution condition in Properties of <Rename file(s)>, replacing the “&&” with “||”. This modification means that the component will be executed if the state of either <Create file> or <Test file(s) presence> is complete.

Our sample scenario is now fully configured. The final step is to save it. We strongly recommend also saving your work regularly throughout the development process. Star is activated near of the scenario name and specifies that no save has been executed.

Accessing Execution Monitor

As its name suggests, Execution Monitor provides information about the scenario's execution. You can open the monitor by clicking its icon in the toolbar. To run Execution Monitor, select the <Scenario> \ <Execution Monitor> menu option or press function key <F4>.

Execution Monitor interface

The Execution Monitor interface is divided into four panes:

• Scenario: Graphical representation of the scenario depicting its evolution or execution
• Properties: is presenting data's used in the components
• Report: presenting the execution traces of the components
• Variable: presenting the variables created in the scenario

Initiating a scenario's execution

There are two ways to initiate the execution of a scenario: step-by-step mode and standard execution. Simply open the interface and click the button corresponding to the desired execution mode.

For our example, we are going to click <Execution>. The scenario begins to run immediately. An icon is displayed in the top right of the interface. This icon remains green if execution is proceeding smoothly, but turns red if an error is detected during the process.

The trace pane is populated when the scenario has been executed. This pane contains the scenario's execution log, as well as any previous traces relating to the same scenario.

A file named new.html is created in the working directory specified in the @scenario repertory@ variable. This file can be displayed directly in a web browser, allowing the user to check that the scenario was executed successfully.

To return to the Paseosoft Scenario Designer interface you must close Execution Monitor, either by using the dialogue box functions or by selecting the <Execution> \ <Close> menu option.

»Previous page