ONLINE HELP
 WINDEV, WEBDEV AND WINDEV MOBILE
Help / Editors / Software Factory
  • Overview
  • How to?
  • Creating an action plan
  • Describing an action plan
  • Actions that can be used in an action plan
  • Characteristics of the actions
  • Action with parameters
  • Handling errors
  • Specific action: Launch WINDEV, WEBDEV or WINDEV Mobile
  • Specific action: Running an action plan
  • WLanguage events associated with an action plan
  • Testing an action plan
WINDEV
WindowsLinuxJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac Catalyst
Others
Stored procedures
Overview
The action plans group all actions that will be performed by the Software Factory. An action plan editor allows you to easily define these actions. It is used to define the sequence of actions that will be performed automatically. Action plans are created from WINDEV, WEBDEV or WINDEV Mobile.
How to?

Creating an action plan

To create an action plan:
  1. Open the project for which an action plan must be created.
    Note: A single action plan can be used for multiple projects. However, a project must be used to create an action plan. You also have the ability to create an "Action plan" project.
  2. Click in the quick access buttons.
    • In the window that appears, click "Automation", then "Action plan".
    • The project configuration creation wizard opens automatically.
  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. Confirm the creation of the project configuration.
  5. A default action plan is generated and it is displayed in the action plan editor.
  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

Here is a preview of the action plan editor:
1: Action plan name. Use the "Description" option in the context menu to:
  • rename 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, simply drag and drop an action onto the list. The action will be included the cursor position.
The context menu of the action allows you to:
  • Open the description window of the action. This window allows you to specify the necessary parameters (e.g., project name) and to manage errors and the recipients of the status report.
  • Move up, move down or delete the action.
3: List of actions in the action plan.

4: Action performed if an error occurs. This operating mode was defined in the action configuration window.

Actions that can be used in an action plan

The following is a non-exhaustive list of actions that can be executed in an action plan:
  • Open WINDEV, WEBDEV, WINDEV Mobile.
  • Close WINDEV, WEBDEV, WINDEV Mobile.
  • Open a project from the SCM.
  • Open a project on the disk.
  • Close the project.
  • Migrate a project from the SCM.
  • New in version 2025
    Migrate a project from disk.
  • Clone and open a project from Git.
  • Commit and push project to Git.
  • Subscription-exclusive new feature
    Change save format.
    This action switches from binary to text format and vice versa.
    Note: This feature is only available in subscription-based versions, starting with WINDEV Suite 2025 - Update 1.
    For more details, see Using new features exclusive to the subscription-based version of WINDEV Suite 2025.
  • Update components.
  • Update web services.
  • Synchronize templates.
  • Update styles.
  • Update skins.
  • HTML generation.
  • Relocate a component.
  • Select a configuration.
  • Generate a configuration.
  • Multiple generation.
  • Generate a library patch.
  • Generate help about new features.
  • Compile help files.
  • Publish external component in SCM.
  • Generate project technical documentation.
  • Generate the setup program.
  • Generate the 32-bit/64-bit setup program.
  • Start setup.
  • Deploy installation to a Private Store.
  • Deploy site / web service to PCSCloud or to an application server.
  • Push a docker image to GitHub.
  • Extract messages for translation (WDMSG).
  • Reintegrate translated messages (WDMSG).
  • Check in all elements to the SCM.
  • Undo all SCM check-outs.
  • Label SCM.
  • SCM check-out.
  • Check-out from SCM for test.
  • SCM check-in.
  • Cancel SCM check-out.
  • Undo all SCM check-outs for test.
  • Retrieve content of an SCM directory into a local directory (outside the project).
  • Search in SCM history.
  • Create SCM branch.
  • Subscription-exclusive new feature
    Delete SCM branches.
    Note: It is not necessary to open the project to delete a branch, but it is necessary to open the corresponding IDE (WINDEV, WEBDEV, WINDEV Mobile). This means the action plan can consist of three actions: Open IDE, delete branches, close IDE.
    Note: This feature is only available in subscription-based versions, starting with WINDEV Suite 2025 - Update 3.
    For more details, see Using new features exclusive to the subscription-based version of WINDEV Suite 2025.
  • New in version 2025
    Add project to SCM.
  • Detach project from the SCM.
  • Start static audit.
  • Run automated tests.
  • Command line of test mode.
  • Enable code coverage.
  • Disable code coverage.
  • Reinitialize code coverage.
  • Check code coverage.
  • Generate test library.
  • Recompile project.
  • Repare project.
  • Enable/Disable:
    • UI errors
    • warnings.
    • programming standard errors
    • information.
    • Reports & Queries.
    • code style.
  • Show/Hide code prefixes.
  • Enable/Disable the spelling checker.
  • Delete test data.
  • Delete test mode parameters.
  • Run a WLanguage procedure.
  • Run an exe, bat, etc.
  • Execute an action plan.
  • Run an action plan for all configurations.
  • Define the comment.
  • Define name of the file to be generated.
  • Define version number.
  • Define the string with the version of the generated file.
  • Define major version number.
  • Enable/Disable version number increment.
  • Define Copyright.
  • Configure manifest.
  • Signature of the executable.
  • Name of the company.
  • URL of the company site.
  • Email address of company.
  • Description of the generated file.
  • Executable icon.
  • Splash screen image.
  • Modify library use mode.
  • Regenerate documentation of a component.
  • Reinitialize WLanguage error message.
  • Last compatible version of the component.
  • Path of the Android SDK.
  • Android application package.
  • Sign Android application.
  • SCM directory for publishing external component.
  • Delay.
  • Emit a sound.
  • Copying files.
  • Copy a directory.
  • Burn a CD or DVD.
  • Delete a directory.
  • Open/close all project elements.
  • Close all open elements.
  • Add a file to the project.
  • Send an email.
  • Restart Software Factory after the action plan is completed.
  • Delete unused items from the analysis.
  • Save and generate the analysis.
  • Reset the version number of the analysis generation to 1.
  • Stop execution if an error occurs.
Characteristics of the actions

Action with parameters

An action may require parameters. For example, the action called "Open a project from 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" in the context menu of the action).
The parameters can be defined:
  • As a "fixed" value. In this case, the value is specified directly in the action plan.
  • 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 as parameter by the developer.
Tip: Whenever possible, it is advisable to use parameters when creating action plans, so that they can be used for different projects.

Handling errors

An important part of the action plan is to define what to do if the action fails. A simple example would be what to do when updating a window that has been checked out in exclusive mode by a developer.
The error handling mode that best suits the action is selected by default. You also have the ability to customize it. Let's take a look at the available error handling modes:
  • Stop the execution of the action plan and save the error in the status report.
    This management mode is reserved for the major errors (for example, a project that failed to open): 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 do not 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 retrieve all potential errors in a project, you can use the "Save error in status report and continue execution" mode and a special action: "Stop 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 UI errors, these errors will be stored. Therefore, all the project errors are found in a single execution of the action plan.
Special case: Executing a procedure within 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
New in version 2025

Specific action: Launch WINDEV, WEBDEV or WINDEV Mobile

The action for launching an IDE via an action plan offers multiple settings in the "General" tab of the description window:
  • Version and directory of the IDE to be launched.
  • Type of license used: Dongle-based or subscription-based.
  • Project Management Hub login credentials.
In the case of a dongle-based license, each computer must be connected to a local or network dongle.
Subscription-exclusive feature
In the case of a subscription-based license, the license is already used on the computers running the automated plans. Therefore, you must:
  • own a subscription-based license for each computer that runs the plans.
  • have launched the IDE at least once on the computer running the plans, to log in using the corresponding subscription credentials.
  • connect to Control Centers using this license.

Specific action: Running an action plan

You can 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 events associated with an action plan

Two events associated with an action plan:
EventRuntime condition
Initialization of action planRun before the execution of action plan.
End of action planRun after the execution of action plan.
Testing 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.
See also
Minimum version required
  • Version 16
This page is also available for…
Comments
Click [Add] to post a comment

Last update: 09/29/2025

Send a report | Local help