|
|
Scripting Tracker is a utility and a replacement to the SAP GUI Scripting Development Tools. It contains a GUI analyser, comparator and recorder on SAP GUI Scripting base, with an API viewer.
Jump to Scripting Tracker
Editor |
You can choose any editor you like and know best. On Windows plattform Notepad++ is a good choice and if you want to use one editor on different OS plattforms Geany is a good choice. |
|
Shell |
Each operating system has its own shell which you can always use, e.g. on Windows plattform cmd or on Linux plattform bash. A good choice is PowerShell Core. It is cross-plattform and offers great conditions. A detailed documentation of PowerShell is available. |
|
Browser |
A browser is also always available. A good choice ist Google Chrome or Mozilla Firefox. Hint: If you need Chrome for Linux, change the platform parameter of the URL to linux, and for macOS, change it to mac |
|
Language |
To code in your favorite language you need an SDK like or a compiler. | .NET e.g. C# Installation: Extract SDK in target directory. Set DOTNET_ROOT variable to the sdk-subdirectory and add to the PATH variable %DOTNET_ROOT% directory.
|
|
Java Installation: Extract JDK in target directory. Set JAVA_HOME variable to the jdk-subdirectory and add to the PATH variable %JAVA_HOME%\bin directory.
|
||
| Python | ||
Sources of Information |
More information is also available at ... | Microsoft .NET site API catalog of .NET .NET CLI overview |
| Oracle Java Documentation site | ||
| Python documentation site | ||
Tool |
.NET debugger and assembly editor dnSpy NuGet Package Explorer |
|
| Java decompiler JD | ||
| Exposing .NET Core components to COM |
#-Begin-----------------------------------------------------------------
Param(
[String]$UserName
)
#-Sub Main--------------------------------------------------------------
Function Main {
Add-Type -AssemblyName System.Windows.Forms;
[String]$Result = [System.Windows.Forms.MessageBox]::Show("Hello $($UserName)", `
"Hello", [System.Windows.Forms.MessageBoxButtons]::OKCancel);
$Result;
}
#-Main------------------------------------------------------------------
Main;
#-End-------------------------------------------------------------------
Now the integration of this PowerShell script into a UiPath sequence. Here is one way to read the PowerShell script as text file into a UiPath variable. This variable is the command text for the UiPath activity Invoke PowerShell. It is necessary to set the IsScript flag of the PowerShell Invoke activity in this case. The parameter for the script must be defined also as parameter for the activity, with the same name. Set the TypeArgument property to string and the result of the script will be a collection of strings too, which are stored in the variable Result. With the Write Line activity this result is shown in the output window of UiPath. Here the workflow file of UiPath. On this way it is possible to combine PowerShell in UiPath seamlessly and to communicate directly from UiPath with the PowerShell script and vice versa.
Data: AutoIt Type OLE2_OBJECT, pid Type i. Create Object AutoIt 'AutoItX3.Control'. Call Method Of AutoIt 'Run' = pid Exporting #1 = 'notepad.exe'. Call Method Of AutoIt 'WinWaitActive' Exporting #1 = 'Unbenannt - Editor'. Call Method Of AutoIt 'Send' Exporting #1 = 'Hello from ABAP'. Free Object AutoIt.
