6983ae69-67a7-47b8-bb71-1114b36a85cd.jpg

Senior Software Engineer

a6e5b969-be6e-4756-ae53-47d3cb899ca4.png

**What**

Activities that output an image file can have their results checked using an image comparison algorithm. The simplest of these is a pixel-by-pixel check for equality. More complex algorithms that take an error metric based threshold parameter can also be used. The latter are implemented using the [Magick.NET](https://github.com/dlemstra/Magick.NET) library's _**Compare**_ method.

  

**Who**

RPA developers, although QAs can also use it to run image specific scenarios.

  

**How**

Drag and drop the **Compare Two Image Files Pixel By Pixel** activity from under the _**UIPathTeam &gt;**_ _**Images**_ node. Locate the two image files to be used in the comparison.

The activity returns a boolean that indicates whether or not the two inputted files are identical.

  

Drag and drop the **Compare Two Image Files Using Threshold** activity from under the _**UIPathTeam &gt; Images**_ node. Locate the two image files to be used in the comparison. Choose one of the available **ErrorMetric** values. An explanation regarding metrics can be found [here](http://www.imagemagick.org/Usage/compare/#statistics). Set the required **Threshold** value. This represents the upper bound of the distortion based on the selected **ErrorMetric** for the two input images to be considered equal. The activity returns returns the computed **Distortion.** It also returns a boolean that indicates whether or not the two inputted files are equal based on the computed distortion and the **Threshold** value.

  

The supported image file types are:

*   PNG
*   JPEG
*   BMP
*   GIF
*   TIFF

A package containing activities for comparing image files

**What**

Sometimes you might need to run specific actions in a workflow depending on the current OS's details. For example you might want to run a workflow that handles new machines coming online in a heterogeneous network by ensuring that they have some piece of software installed on them, and this specific software has variants for Windows, 7, 8 & 10, with their respective bitness of 32 or 64.

  

**Who**

RPA developers, although QAs can also use it to run specific platform scenarios.

**How**

  

Drag and drop the **Get Windows Information** activity from under the _**UiPathTeam &gt; OS**_ node. It returns an **WindowsInformation** object that you can then alongside decision blocks to split the flow based on the scenario needs.

The **WindowsInformation** object exposes the following read-only properties:

*   ProductName (string)
*   EditionId (string)
*   CompositionEditionId (string)
*   ReleaseId (string)
*   CurrentVersion (string)
*   MajorVersion (int)
*   MinorVersion (int)
*   BuildNumber (string)
*   BuildLabEx (string)
*   ServicePack (string)
*   Is64Bit (bool)
*   IsServer (bool)

A package containing activities for querying the operating system for information, specifically for retrieving the Windows version information

**What**

When you need to retrieve information pertaining to the display devices on the computers running a workflow, or set specific characteristics of the device like it being the main display (primary monitor) or set a particular display mode (resolution + frequency). The activities interface with the display devices through the Windows API.

  

**Who**

RPA developers can use it to run display dependent scenarios.

  

**How**

The activities are available under the _**UIPathTeam &gt;**_ _**Display**_ node. 

*   The **Get Display Devices** activity lets you retrieve all of the devices, filter them by avaialability or any other traits you need, include monitor information and output a list of devices. 
*   The **Get Specific Display Device** allows you to retrieve a device by name. Alternatively, if you leave the _**DeviceName**_ field empty, the main (primary) device information is retrieved.
*   The **Set Primary Device** lets you change the main (primary) device to a device you name.
*   The **Get Display Modes** activity lets you retrieve all of the display modes supported by the named device. Alternatively, if you leave the _**DeviceName**_ field empty, the main (primary) device supported modes are retrieved.
*   The **Get Current Display Mode** allows you to retrieve the current display mode of a named device. Alternatively, if you leave the _**DeviceName**_ field empty, the main (primary) device's current mode is retrieved.
*   The **Set Display Mode** lets you change the display mode of a device you name, either by specifying a _**DisplayMode**_ object or by specifying a _**Width**_ and _**Height**_ combo (should there be more than one display mode with the specified width and height, the ones with the highest color depth are chosen, and of these, the one with the highest frequency is chosen).

You can read up more on the Windows API functions for [enumerating devices](https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-enumdisplaydevicesa), [enumerating display modes](https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-enumdisplaysettingsa) and [changing the display settings](https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-changedisplaysettingsexa).

  

Icons made by [Freepik](https://www.flaticon.com/authors/freepik) from [www.flaticon.com](http://www.flaticon.com/)

A package containing activities for interfacing with the display devices, monitors and their respective display modes (resolution, frequency, etc.)

About me