Search

Home

Home

Manual Invocation

Manual invocation is performed through the following steps:

  1. Launch the Gravity.exe application.
  2. Create a project (option PROJECTS).
  3. Run the project manually using the Start processing button.
  4. You can view the execution results in the log window.

Running a Project Manually

After creating the process, you can run it manually — either for testing or for actual execution — by using the Start processing button in the project creation window.

image

Next, you will see a window with the Parameters tab. If the project uses parameters, this tab will display their list, and you will be able to fill them in. There are also two options for running the project.

image

Running the Project in Normal Mode

icon
Select this option when you want to run the project.

After filling in the parameters (if they exist and are required for the given project), you can click the Start processing button.

This will start the project and allow you to view the execution log, including the execution times of individual operators and the information about the execution result.

image

Running the Project in Debug Mode

icon
Select this option to step through each operator and review its input and output data.

This option lets you run the process in step-by-step mode. For a large project, you can choose the operator from which you want to start stepping by selecting it with a mouse click. If no operator is selected, stepping mode will start from the first operator.

image

After filling in the parameters (if they exist and are required for the given project), you can click the Execute selected button.

The process stops after executing all operators up to and including the selected one. In the process preview window, under the Result data tab, you can see the data that was sent out from the operator to the data bus.

image

The window also displays debugging buttons:

  • Run to - runs the process forward until the next selected operator,
  • icon
    You can select any operator along the process path that has not yet been executed. If the process includes IF operators, it is possible that the process will skip the selected operator depending on which path is taken.
  • Run step - always moves to the next operator,
  • Pause - pauses the process,
  • Stop - allows you to interrupt the process at any time; all database operations subject to transactions will be rolled back.

By clicking the Run step button, you move to the next step.

image

In the Result data tab, you can see the output data from the next operator that has been executed. At any time, you can view the logs of executed operators by switching to the Execution log tab. For operators that send or receive data from other data sources, you can see a Details button. When clicked, it displays communication details, processed data, and related information.

image

Details - CALL AS2CALL AS2 operator

image

Details - OUTPUT DATAOUTPUT DATA operator

image

Stepping through all the steps (process operators) completes the debugging phase.

❗
Remember that running the process and completing it successfully results in the permanent execution of all operations it contains. If the process adds data to the database, the data will be added; if it deletes data, it will be deleted (the exception is when the process is interrupted in debug mode — in that case, the transactions will be rolled back). However, it is not possible to undo operations performed by input/output operators.
icon
Learn more about maintaining data integrity in the GRAVITY system.

Project Execution Error

If the project fails for any reason, the execution result includes information about the error and the operator where it occurred.

image

To view the error details, click the button on the right side of the execution result field.

A standard system error message window will appear, where you can scroll through the list of errors using the arrow icon buttons.

image