Create your first automation in just a few minutes.Try Studio Web →
by Clayton Marischen
3
Snippet
401
Summary
Summary
Hard kill from a list of process names to clean Windows environment of open applications for the active user / robot
Overview
Overview
With high-density server environments, this shared workflow can be used as part of the ReFramework or other frameworks to kill any open processes or applications that could potentially interrupt a job from running successfully.
This component will essentially only kill processes under the active user logon session.
Additionally, this component can be published as a job to run daily or adhoc to ensure environments are kept tidy.
If explorer is killed, the component is coded to start explorer again until the taskbar is found
Arguments
If a Process Name is not known, a list of all available processes will be listed in the Output panel from within Studio. An example text file of process names will be provided with component upload and also in the screenshots.
Note: Some applications, such as Mainframe terminals, may require some soft kill actions in order to exit certain screens before a hard kill is performed; this should be considered prior to running this hard kill component, so systems are not locked up.
Further in-code documentation.
Features
Features
Can be used at the beginning, after an exception, and at the end of a process to hard kill all processes from a list of process names. This component will only kill the processes found in the active user logon session, so this is useful for high-density robot environments.
Additional Information
Additional Information
Dependencies
Workflow Manager Activities --- required in the project's dependencies for IsTrue activity
Code Language
Visual Basic
License & Privacy
Apache
Privacy Terms
Technical
Version
1.0.1Updated
February 18, 2020Works with
Studio: 18.2 - 22.10
Certification
Silver Certified
Tags
Support
UiPath Community Support