Configuring Process Execution

Once processes are created, you can execute them at any time. You can execute your process without intervention or you can execute your process in a step-by-step method. The method you choose depends on the following criteria:

  • If this is the first time executing your process, you should run the process without intervention. This method allows you to see if your process steps are correctly defined and in the correct order for your application.

  • If you are debugging execution of a process, run the process with the step-by-step method. With Certify debugging tools, you can follow the execution and determine where and why failures have occurred.

Prior to actual execution of a process, you will need to configure the process execution to meet your requirements. Configuration consists of the following:

  • Configuring the run and log settings
  • Providing where to find input data and start-up data

The Configuration dialog provides options for choosing the following:

  • Type of execution
  • How and when execution is performed
  • How the results are handled

When you choose a value other than the default in the Configuration dialog, the field is highlighted in red. The configuration that you set is saved to your user profile. You can restore the default values by clicking the Restore Defaults button.

To configure your process execution:

  1. In the Navigation pane, click Processes.

The Processes window opens.

  1. In the Processes Summary pane, complete one of the following tasks:
  2. Select a process and click the Run button
  3. Right-click a process and select Run.

The Configuration dialog opens.

  1. In the Title text field, enter a title to identify the process you are executing or accept the default title.

    By default, the title is displayed as the process name and followed by the current date and time. Titles can have a maximum of 255 characters, and special characters and numbers can be used.

  2. In the Run Settings section, configure the following settings to run your process:

    Setting

    Description

    Stop On Failure

    If you want your execution to stop when a failure is encountered in your process, select this option. By default, execution does not stop on failure. Failure includes failed and aborted steps.

    Set the number of failed steps in which you want the process execution to stop.

    Fail Threshold

    Set the number of failures that can happen before the Stop on Failure feature stops process execution. This feature is helpful if your environment is not configured correctly.

    Run Mode

    Select how you want to manage the execution:

    • Managed - Stop process execution by stepping through execution, setting breakpoints, and capturing screens.
    • Manual -Running your process in manual mode allows you to debug process execution when automation is not working. Manual mode requires user intervention when executing your process. For more information, see Executing Processes Using Manual Mode.
    • Unmanaged - Run process execution without stepping through execution, setting breakpoints, and capturing screens.

    Step Delay

    Enter the number of seconds that you want to delay between each step of your execution or accept the default of 0 seconds.

    Step delay helps resolve timing issues when testing your application.

    Action Timeout

    Set the timeout in minutes for process execution when the execution engine does not receive a response from the interface.

    Valid values are listed below:

    • 0 (Default - no timeout)
    • 1 - 120 minute(s)

    Skip Results Window

    Select this option if you do not want to open the Results window after process execution has been completed.

  1. In the Logging Settings section, configure the following settings:

    Setting

    Description

    Log Step Mode
    • LogAllSteps - All steps are included in the log file. Depending on the size of the process, you may have memory issues. The database grows at a fast pace, and regular maintenance is needed. This option is more appropriate for users who run a daily archive of their results that removes the results from the Certify database.
    • LogAbortedStepsOnly - Only aborted steps are listed in the log file.
    • LogFailedSteps - Only failed steps are listed in the log file.
    • LogProcessOnly - Only the log header and log process tables are listed in the log file.
    • LogStatusOnly - Only the log header table is listed in the log file.
    • LogDisabled - No logging is selected, and all of the log tables are skipped.

    Capture Screen On

    Select the screen capture option:

    • CaptureNone
    • CaptureAbortedSteps
    • CaptureAllSteps
    • CaptureFailedSteps
    • CaptureAbortedAndFailedSteps
    • WindowChange

    For more information, see Capturing Screen Images.

    Screen Capture Mode

    Select how much of the area of the application screen you want to capture:

    • CaptureDesktop
    • CaptureActiveWindow

    Output Location

    If you do not want to accept the default location of where your results are stored, click the Browse button.

    The Results Folder Selector dialog opens. Select a project for which you have permission. After you make your selection, click OK.

    Screenshot History

    Set the number of executed steps that will provide screen captures prior to a failed step.

    This feature assists you with identifying the cause of a failed step.

    Add Interface Debugging to Certify Log

    If you want to add interface debugging to your interface log, select this option.

  2. In the Data section, configure the following settings:

    Setting

    Description

    Layout (Optional)

    If you saved a layout mode with the process, the associated layout appears as the default in this field.

    You can change this layout by clicking the Browse button or remove the layout by clicking the Delete button. If you select a layout and do not choose a recordset, the layout is ignored.

    Recordset (Optional)

    If a layout is associated with this process and a recordset exists for that layout, then this field is active. Select a recordset from the drop-down list.

    Recordset Mode

    If a recordset is associated with the layout, this field is active. Select the recordset mode from the drop-down list:

    Mode

    When Executed

    How Executed

    Read Only

    Reads recordset at the beginning of the execution.

    Loops process once for each row until End of File.

    Append

    Adds recordset at the end of execution.

    Appends to existing recordset and loops process until Abort or Exit.

    Clear and Append

    Creates recordset at the end of execution.

    Creates new recordset for each execution session and loops process until Exit.

    Read and Update

    Reads recordset at the beginning of execution.

    Updates the recordset at the end of the process.

     

  3. If you want the application version checked for context, select the option next to the application in the Application Version Startup Data section. Context means that you have already loaded your application and positioned the application at the state where the selected process begins.

    Application versions only appear in this field when you have defined a start process in the New or Edit Application Version dialogs.

  4. If you want to set attribute fields so that the values are stored with the results, click the Attributes tab. Enter values into the Attribute fields.
  5. Click Start to begin process execution.

To save the current execution configuration parameters in a batch file:

  1. In the Configuration dialog, set your process execution parameters.
  2. Click Export.

The Save As dialog appears.

  1. Select a folder and enter a file name.

  2. Click OK.

    The configuration is saved as a batch file.

 

Related Topics Link IconRelated Topics