c4a7c20d-6ad1-46c6-b0f1-595699a6e412.jpg

My question:  Is there any way (or plan) to get console text before Close command?

I know we can use Execute Single Command activity to get output for each command but it seems a little bit inefficient.

How to execute python file in cmd as it asking for cmd process ?

So as per cmd process it python.exe but not able to pass the same in process.

Any chance to make it work on remote machine ? 

I've tried with RDP connection but the command prompt is executing on my local machine, instead of the remote one (yes, activity have been inside of Use Application card).  I've running the automation from my local machine from where I have installed Studio 2022.4.2

I am trying to run move command and i want to get error message as output (like "Access is denied" for example) .

Great package! Runs everything in the background much more reliably than using UI manipulation to try and run commands, which don't always cooperate.

I downloaded the package and everything ran smoothly. Thank you!

It's working successfully.
good job Manish....

Amazing Amazing Amazing!!!Thank you Manish!

Here are some of the benefits I saw so far (might be more)

1. Rapid execution (for long code) - it used to take my old bot 25 - 30 mins to finish the process now only took the new bot 7 mins because the CMD Activity "executes"  the extremely long code directly and rapidly instead of "typing code into" the cmd prompt. The bot was able to execute five long cmd codes in a row without any error (I used the single cmd execution) which is Fantastic!

2. NO NEED to set up delay time. I used to set up a delay time btw cmd activity and the next non-cmd activity to allow my cmd code to generate output(an excel file). The single cmd execution is intelligent enough to move to the next activity automatically.

3. NO MORE Screen Scaping BC everything runs in the backend ? HOW AWESOME IS THAT!!!

PS: Looking forward to seeing more features of this package. E.g: changing direction in single-cmd- execution, running multiple long code(long time code) using multi-cmd-execution. etc...

9fd7757e-4eb0-48b5-a838-9dbe6aae5605.nupkg

ExecuteSingleCommand Activity: This activity opens the command prompt, executes the provided command and returns the console output as a string.

If the input property SingleLineOutput is set to True then only the specific command output will be retrieved, else by default the entire console output will be fetched.

This activity is helpful when only a single command has to be executed and the command output has to be fetched.

OpenCommandPrompt Activity: This activity opens the command prompt session and provides the CMD process as output. This activity has no input parameters. The output from this activity is used as input for the activities ExecuteCommand, CloseCommand and GetConsoleOutput.

ExecuteCommand Activity: This activity executes the specified input command on the already opened command prompt process. This activity is useful when multiple commands have to be executed on the same command prompt session.

CloseCommand Activity: This activity closes the input stream to the specified command prompt process. This activity must be used after the OpenCommandPrompt and ExecuteCommand activities. 

GetConsoleOutput Activity: This activity is used to get the command prompt console output as a string once the commands are executed and closed using the ExecuteCommand and CloseCommand activities respectively. The activity has the complete console output of the executed commands of the specified command prompt session. 

Complete details of how to use these activities can be found in the attached document.

The package contains five Windows command prompt custom activities. These activities can be used to execute CMD commands and also retrieve the command outputs from the command prompt console


297b86b9-a9cb-461b-a561-feb3f8aefc04.png

2e95f9ae-20ab-4382-b07c-ed94ccd51b53.png

258d7a96-ec2e-4494-be2b-9b962732a152.png

18230d1f-909c-4832-8fd2-46e7edc94248.png

c448af76-ada3-4bd5-b75c-e0e9fcdbca0e.png

0b86a6ed-cf1e-4bfe-bb25-b9b8210e6fbf.png

4151c08f-362d-4b29-adb5-4bf3b65b79bc.PNG

MIT License Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Visual Basic

7ada14c7-cdb5-41c7-a8fe-29fb269ad984.docx

3afd0c83-976e-4d61-ae6c-3fadb6b05dbf.docx

dae4119d-3262-4d26-b314-074a3a7431f1.zip

1fad3e12-ce45-4a0d-b684-507133a2e4e4.nupkg

Feature: You can now specify the directory or folder in which the command prompt session has to be started in the activities ExecuteSingleCommand and OpenCommandPrompt

Bugfix: For long running commands (generally taking more than 5 minutes) the activities failed to complete the command and provide the output. The issue is now fixed.

Command Prompt Activities

Command Prompt Activities