PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • How to proceed?
  • Creating an action plan
  • Describing an action plan
  • Characteristics of the actions
  • Action with parameters
  • Managing the failures and errors
  • Specific action: Running an action plan
  • WLanguage processes associated with an action plan
  • Running the test of an action plan
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Overview
The action plans group all actions that will be performed by the software factory. An editor of action plans is used to easily define these actions. It is used to automatically define the sequence of actions to perform. The creation of action plans is performed from WINDEV, WEBDEV or WINDEV Mobile.
How to proceed?

Creating an action plan

To create an action plan:
  1. Open the project for which an action plan must be created.
    Note: An action plan is not necessarily linked to a project as it can be used by several projects. However, a project must be used to create an action plan. You also have the ability to create an "Action plan" project.
  2. Select "File .. New .. Automation .. Action plan". The wizard for creating a project configuration is automatically started on the current project. Click among the quick access buttons.
    • In the wheel that is displayed, hover "Automation" and select "Action plan". The window for creating a new element is displayed: click "Automation" then "Action plan".
    • The wizard for creating a project configuration is automatically started on the current project.
  3. In the wizard, specify:
    • the name and description of the action plan.
    • the elements included in the action plan. In most cases, no element must be included in the action plan. This plan allows you to include elements used by a specific action of the action plan (procedure used by a WLanguage action for example).
  4. Validate the creation of project configuration.
  5. A default action plan is generated and it is displayed in the editor of action plans.
  6. Save the action plan (CTRL + S). The action plan corresponds to a file with a "wpa" extension. The action plan is displayed in the project explorer.

Describing an action plan

The editor of action plans is as follows:
1: Name of the action plan. The "Description" option of the popup menu is used to:
  • modify the name of the action plan.
  • specify the parameters of the action plan.
2: List of actions that can be performed by the action plan. To add an action to the action plan, all you have to do is "drop" an action into the list of actions of the plan. The action will be included at the location hovered by the mouse cursor when the action is dropped.
The popup menu of the action is used to:
  • Display the description window of the action. This window is used to specify the necessary parameters (the name of the project to open for example) and to manage the errors and the persons affected by the status report.
  • Move up, move down or delete the action.
3: List of actions found in the action plan.

4: Action performed if an error occurs. This operating mode was configured in the configuration window of the action.
Characteristics of the actions

Action with parameters

An action may require parameters. For example, the action called "Opening a project from the SCM" requires the name of the project to open. The definition of these parameters is performed in the "General" tab of the description window of the action ("Description" from the popup menu of the action).
The parameters can be defined:
  • As a "fixed" value: the value is specified in the action plan directly.
  • As parameters passed during the execution of the action plan.
This parameter will be required to run the action plan.
For the name of the project to open, it must be specified in parameter by the developer.
Tip: If possible, the parameters should be defined when creating the action plans in order for these action plans to be re-used for different projects.

Managing the failures and errors

Important point of the action plan: defining the behavior if the action fails. Simple example: what to do when updating a window that is checked out in exclusive mode by a developer.
The management mode of errors that is the most consistent with the action is selected by default. You also have the ability to customize it. Let's take a look at the possible management modes of errors:
  • Stop the execution of the action plan and save the error in the status report.
    This management mode should be reserved for the major errors, a project that fails to open for example...: there is no need to try to continue.
  • Run the custom error process of the action plan.
    This management mode allows you to manage a specific error mechanism. For example, send an SMS if an error occurs.
  • Save the error in the status report and continue the execution.
    This management mode allows you to continue the execution of the action plan even if an error occurs.
    For example, if a component is not updated (offline server, etc.), the action plan can continue.
  • Save for information but don't generate any error.
    For example, when the audit detects that unused files are found in the project directory, this is not an error but it may be important to have this information.
If the action fails, you have the ability to select one or more persons to inform ("Message" tab of the description window of the action). In any case, the owner of the action plan is informed of the execution result (success or failure).
Tip: To get all the potential errors of a project, you have the ability to use the "Save the error in the status report and continue" mode and a specific action: "Stop the execution if an error occurs". For example, if the synchronization of the templates is not performed, the error is saved and the action plan continues to run. In the rest of the action plan, if the recompilation detects some GUI errors, these errors will be stored. Therefore, all the project errors are found in a single execution of the action plan.
Special case: Running a procedure in an action plan:
Depending on the result of the procedure, the action plan must be interrupted. The following code must be used in the WLanguage procedure:
IF bRes = False THEN
sErrorMessage is string = "Error in XXX function" + CR + ...
ErrorInfo(errSystemMessage)
ExceptionThrow(1, sErrorMessage)
END

Specific action: Running an action plan

You have the ability to run an action plan from another action plan.
This action may be useful to share the operations common to the WINDEV, WEBDEV and WINDEV Mobile projects.
For example, a specific action plan can be used to start WINDEV, WEBDEV or WINDEV Mobile according to a parameter. The useless actions can be disabled by apDisableAction.
In this case:
  • The action plan contains the 3 startups of the products.
  • The initialization code of the action plan is as follows:
    SWITCH pProductName
    CASE ~= "WD"
    // We don't want to start WEBDEV or WINDEV Mobile
    apDisableAction(Start_WEBDEV)
    apDisableAction(Start_WINDEV_Mobile)

    CASE ~= "WB"
    // We don't want to start WINDEV or WINDEV Mobile
    apDisableAction(Start_WINDEV)
    apDisableAction(Start_WINDEV_Mobile)

    CASE ~= "WM"
    // We don't want to start WINDEV or WEBDEV
    apDisableAction(Start_WINDEV)
    apDisableAction(Start_WEBDEV)

    OTHER CASE
    ExceptionThrow(1, "This type of project is not associated with a product")
    END

WLanguage processes associated with an action plan

Two processes are associated with an action plan:
ProcessRuntime condition
Initialization of action planRun before the execution of action plan.
End of action planRun after the execution of action plan.
Running the test of an action plan
WINDEV allows you to perform a "Go" of an action plan in order to check its operating mode locally, especially the custom actions containing WLanguage code.
Minimum required version
  • Version 16
This page is also available for…
Comments
Click [Add] to post a comment