Using a simple drag-and-drop, place the " Run " icon in the desired location in the " Properties " column. Alternatively, double-click the " Run " icon.

This type of property allows you to launch an application or a macro in response to an event (button click, opening, or validation of SmartProperties).

The '' typeRunSmartProperties'' is designed for advanced users who have a basic understanding of application development. These applications can be run with SmartProperties.


 


You can set the application type by selecting an option from the drop-down menu.


 


There are three types available:

"Application" - a program (.exe) will be run

"Macro" - a macro function (.swp) will be executed

" Website "—a link will open a web page to access a website.


In the "Properties" section, you'll find the settings related to this action.

  • Trigger:


 


-> ''Button'' - indicates that the action will be triggered by pressing a button with that name.

-> " When SmartProperties is launched " — indicates that the action will be triggered as soon as the SmartProperties utility is launched.

-> ''SmartProperties validation'' - indicates that the action will be triggered as soon as validate is pressed .

-> ''After closing SmartProperties'' - indicates that the action will be triggered as soon as you exit the SmartProperties utility. In fact, you can validate the information by pressing but if the window has been pinned then this action will not be taken into account.

-> " During specification testing " — indicates that the action will be triggered while the utility processes the parameters defined in the " Specifications " field. Before the properties are created. This allows you to add custom specifications using the “Application Exit Code Specification” option.

-> " Before creating the input mask " — indicates that the action will be triggered before analyzing the properties already present in the file and displaying the SmartProperties input mask in the PropertyManager.


  • Location:

Here you determine the location and application (macro or executable) by pressing which will trigger the action.

  • Argument:

-> For a macro, this parameter is filled in automatically; it is usually the macro's entry point.

-> For an executable application, specify here the parameters to be passed at the start of the program. To declare variables used in the program, prefix the name with the " $ " character.


Once this information has been entered, you can still adjust certain options.


 


" Wait until the application has finished before returning control to SmartProperties"—indicates that as long as the application is still running, the SmartProperties utility is suspended and will not resume control until the program has finished. This option is not available when running a macro; it will therefore be grayed out.

" Update Properties After Execution "—allows you to update the values of the properties (specified in the list) in the SmartProperties input mask after the program has run. If there are multiple properties, the separator used will be ", ".

" Application Exit Code Specification "—used only with the " During Specification Testing " trigger —allows you to add a specification. If the application's exit code differs from the code specified in SmartProperties, the properties are not created. In your application, use the “ Environment. Exit” API to return the application exit code.