Wenn Paket

Use the Aktionen in the Wenn Paket to control the sequence of execution based on one or more conditions of a task.

Use the Aktionen in the Wenn Paket to check whether an application is running, a folder or file exists, a variable matches the specified value, an application window exists, or a machine or server is running before executing a set of Aktionen.

Aktionen in the Wenn Paket

The Wenn Paket includes the following Aktionen:


Aktion	Description
If	See Wenn Paket
Else if (optional)	See Aktion „Sonst Wenn (optional)“
Else	See Aktion „Sonst“

Conditions in the Wenn Aktion

Use the following conditions in the If Aktion to control the flow of execution in an automation task:

Anmerkung: You can add up to a maximum of 32 conditions in a single If Aktion.


Condition	Description
Application	Use the Application is running or Application is not running condition to run Aktionen based on whether an application is running or not running. Enter the application path or specify the path using a variable along with the amount of time to wait (in seconds) for the condition to be true. Anmerkung: The Application is running and Application is not running conditions are not applicable for Internet Explorer Bots because its corresponding process iexplore.exe runs in the background when Microsoft Edge is launched in IE mode.
Boolean	Use the Boolean variable condition to execute Aktionen based on whether a Boolean variable contains the value True or False. You can also use this condition to compare the values of two Boolean variables by selecting the second variable from the Insert a Variable window.
Data table	Use the Data table is empty condition to execute Aktionen based on whether the specified table contains values. Use the Number of rows and Number of columns conditions to execute Aktionen based on whether the number of columns or rows is Equal to, Greater than, or Less than the specified value.
Datetime	Use the Datetime variable condition to execute Aktionen based on whether the value of the source datetime variable is Equal to or Not Equal to, is Greater than or Equal to, or is Lesser than or Equal to the value of the target datetime variable.
Dictionary	Use the Check key condition to execute Aktionen based on whether the value of the specified key is Equal to or Not equal to, or Contains or Does not contain the target value. Anmerkung: The key comparison is case-sensitive. Use the Check for a single value condition to execute Aktionen based on whether a specific key contains the target value.
DLL	Use the Dll session exists and Dll session does not exist condition to execute Aktionen based on whether a Dll session is open or closed in a Bot.
File	Use the following conditions to execute the Aktion: File date Use this condition to verify the date and time when a file was created or modified. Specify a date or date range using the On a date, Is within last, Is between, or Is before options. For the On a date option, specify a date to verify whether the file was created or modified on that date. For the Is within last option, specify the number of days or time (in hours, minutes, and seconds). Enter the amount of time (in seconds) to wait for this condition to be true. File exists and File does not exist Use these conditions to execute an Aktion based on whether a file exists. For example, if a data file exists, format the file and upload it to a database. File extension Use this condition to check the file extension of a selected file and then execute Aktionen based on the results. Use the File path field to select a file. File size This condition verifies if the specified file is larger, smaller, not the same, or the same as the size you specify. Enter the amount of time (in seconds) to wait for this condition to be true.
Folder	Use the Folder exists or Folder does not exist condition to execute an Aktion based on whether a folder exists.
Image Recognition	Use these conditions to verify whether: Image file is found in the Image file or not. Image file is found in the Window or not. Window is found in the Image file or not. Window is found in the Window or not. For the Window conditions, you can use the Resize window option to specify the window dimensions. This option delivers a more reliable Bot. It resizes the window to the dimensions at which the task was recorded, which enhances the bot's ability to identify the target object. Anmerkung: This option is only available for windows that can be resized. It is not available for Desktop or Taskbar options. For the Window conditions, you can use the Preview option to select a specific captured occurrence and position your click location relative to the image.
JavaScript	Use the Script is successful or Script is unsuccessful condition to execute Aktionen based the status of the specified JavaScript. Select the file that contains the script and optionally specify the parameters by selecting a list variable.
Legacy automation	The Legacy automation conditions are only used in migrated Bots to ensure that they run seamlessly in Automation 360. We do not recommend using these conditions for new Bot development. The following conditions to verify the following: Whether Web control exists or not. Whether Window control exists or not. Whether Window control is active or not. Whether Script is successful or not. Whether Child window exists or not. For the Window control conditions, you can use the Resize window option to specify the window dimensions. This option delivers a more reliable Bot. It resizes the window to the dimensions at which the task was recorded, which enhances the bot's ability to identify the target object.
List	Use the List variable condition to execute Aktionen based on whether the specified list variable contains a particular value. The value can be of Number, String, or Boolean data type.
Number	Use the Number variable condition to execute Aktionen based on whether the specified number variable is Equal to or Not Equal to, or is Greater than or Equal to, or is Lesser than or Equal to a particular value.
Ping	Use the Ping is successful or Ping is unsuccessful condition to verify if a machine or server is running, and execute Aktions based on the result. Enter the amount of time (in seconds) to wait for the condition to be true.
Recorder	Use the Object exists condition to detect an object in a window. Select a window or variable to capture the object. Enter the amount of time (in seconds) to wait for this condition to be true, that is, for the object to be detected. Use the Object does not exist condition to verify whether a specific object exists in a window, and then based on the result, execute Aktionen. Enter the amount of time (in seconds) to wait for this condition to be true. For example, you can use the Object does not exist condition inside the Loop > While condition to make sure that the Bot does not execute the next Aktion until the object on the business application is loaded. Anmerkung: The Object exists and Object does not exist Recorder conditions support Chromium-based Microsoft Edge with Internet Explorer mode.
Service	Use the Service is running or Service is not running condition to execute Aktionen based on whether a service is running or not. Select Service list to choose a service from the list of available services.
String	Use the String variable condition to execute Aktionen based on whether the specified source string value is Equal to or Not equal to, or Includes or Does not include the target value. You can select the Match case option to only execute Aktionen if the two strings have matching uppercase and lowercase letters. When you extract text from a Microsoft application, the extracted text contains the `/r/n` special characters which indicate a new line. Select the Ignore Carriage return option if you want to ignore the `/r` special character when you compare the text. To create a condition based on whether a string is empty or not empty, compare the source value to an empty target field using the Equal to operator. See Beispiel für die Verwendung einer bedingten Anweisung.
TaskBot	Use the Task successful or Task unsuccessful condition to execute Aktionen based on the status of the specified TaskBot.
VBScript	Use the Script is successful or Script is unsuccessful condition to execute Aktionen based on the status of the specified Visual Basic script. Select the file that contains the script and optionally specify the parameters by selecting a variable.
Window	Use the Window exists or Window does not exist condition to verify if a specific application window is open by entering the Window title or using a variable. Enter the amount of time (in seconds) to wait for the condition to be true. These conditions are used when the window title remains constant and to verify if the specific window is open and execute further Aktionen based on the output. Use the Window with same title does not exist or Window with same title exist condition to verify whether a window with the same title exists or whether the window title has changed. Enter the amount of time (in seconds) to keep verifying if the condition is true. These conditions are used for window titles that are dynamic. For example, when you open a Google account webpage, enter your username and password to log into your account, the window title changes. If you want to compose a new email as a next Aktion, you can use these conditions before you execute the next Aktion to verify if the window with the same title exists or if the title has changed.

Group conditions

Verwenden Sie die Option Gruppe hinzufügen, um mehrere boolesche Bedingungen hinzuzufügen oder mehrere Bedingungen mit den Optionen und und oder innerhalb einer Gruppe zu kombinieren, wenn Sie möchten, dass der Bot mehrere Bedingungen gleichzeitig prüft, bevor er eine Reihe von Aktionen ausführt.

Sie können eine Gruppe auch innerhalb einer Gruppe hinzufügen.

Example

Einen einfachen Bot erstellen, der eine Desktop-Anwendung nutzt

An example of how to build a basic TaskBot that uses the Wenn Paket.

Automation 360

Wenn Paket