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

RPA Developer

RPA developer

This activity allows us to translate a saved \*.eml or \*.msg file to a PDF file by providing the path to the \*.eml or \*.msg file and generating the PDF into a folder that we designate.

Custom Activity allowing to save email files as a PDF

With the help of this activity, users can effortlessly convert saved \*.eml or \*.msg files into PDF format. Simply specify the path to the \*.eml or \*.msg file and the PDF file will be generated into a designated folder. This package streamlines the translation process for your convenience.

  

Some of the use cases where this activity can be of great help:

*   Archiving: PDF files provide a convenient and universal format for archiving emails. By saving emails as PDFs, you can ensure that they are preserved in a format that will be accessible and readable in the future, even if email software or file formats change.
*   Legal and compliance requirements: Many organizations are required to retain emails for legal and compliance purposes. Saving emails as PDFs can help ensure that they are properly preserved and can be easily retrieved if needed.
*   Sharing and collaboration: PDFs are a common and widely used format for sharing and collaborating on documents. By saving emails as PDFs, you can easily share them with others, regardless of the email client they use or the device they are using.
*   Formatting and content preservation: Saving emails as PDFs can help preserve the formatting and content of the original email, including any attachments. This can be useful if you need to refer back to the email at a later time or if you need to present it as evidence in a legal or regulatory proceeding.

Custom activity allowing to save email files as a PDF.

46b3b09a-e80c-4fe7-8c1e-947406f1ab34.png

This activity allows you to read a .eml file (email file) and to convert into a .Net MailMessage object. The .Net object can be handled in any RPA workflow as your automation requires.

Use cases:

*   an archive of saved emails can be easily transformed into a database table for ease of use
*   any saved .eml can be 'read' and be used as necessary (for example save the attachment or read that one too or respond to email sender automatically)
*   from an entire folder with .eml files you can search the one(s) corresponding to your needs (for example if you have an archive with emails containing reports, you can find the right one using this activity and looking into each MailMessage object for key words)

**NOTE**: Installation Guidelines for Custom Activities can be found [here](https://dmtyylqvwgyxw.cloudfront.net/instances/214/assets/help-guides/UiPath-Go-Installation-Guide-Custom-Activities.pdf).

This activity returns a .net MailMessage object, that can be handled by other existing activities, from a saved .eml file.

In certain instances, users may encounter emails that have been saved in a file folder, therefore these cannot be accessed directly. As a consequence, these emails must be opened in order to be read. However, complications may arise when attempting to extract specific data from these emails. In such cases, selectors may prove to be ineffective and more advanced techniques, such as string manipulation, may be necessary to retrieve the desired information.

  

This activity allows you to read a .eml file (email file) and to convert it into a .Net MailMessage object. The .Net object can be handled in any RPA workflow as your automation requires.

  

There are 2 inputs needed:

*   **EmailFileName** - this is the filename of the email we need to convert (must be an .eml file).
*   **EmailFilePath** - the path to the directory containing the .eml file.

The activity will generate one output:

*   **EmailNet** - which is the .Net object MailMessage and can be used with other existing mail activities.

**Objectives:**

*   Provide a possibility to launch highly customizable forms by receiving some sort of Markup file.
*   Allow the developer to dynamically initialize the values of the fields inside the form, capture user input and use it inside workflows.
*   Find a way for users to globally customize and design the workflow through a StyleSheet (basically, like a .css file for a HTML page)

**Technical Approach:**

  

All objectives above are achieved by leveraging the features of the **Windows Presentation Foundation** framework. This way, we can receive as input a custom XAML (or Json) mark-up from which we can generate a Form that we can further initialize with whatever data the developer passes to our custom activity. 

  

This means that, inside our forms, we can use any type of UI element (also called **controls**) that we could normally use in a standard WPF form. Since the WPF library is quite extensive and provides plenty of controls and configuration options, we can make sure that the users of this custom activity are provided with all the flexibility and customization possibilities they need.

Basically, the custom activity is designed to receive a XAML file with a Grid control as its parent element which will contain all the controls of our current page. This mark-up is passed to a WPF window and the form gets launched. The developer can optionally pass a XAML file which contains a **ResourceDictionary** control. This control can contain styles which will be applied to the entire form.

  

In order to enhance the number of possible elements in our forms, we also include the **Extended WPF Toolkit** in this package. Therefore, all controls in this library can be used in our forms.

  

This package provides some minimal visual enhancements in addition to the standard WPF look. This is done by using the **MetroLight theme.**

  

**For more details, please see the attached documentation.**

  

More information about this approach can be found here:

*   WPF Framework: [https://learn.microsoft.com/en-us/dotnet/desktop/wpf/?view=netdesktop-7.0](https://docs.microsoft.com/en-us/dotnet/framework/wpf/)
*   Metro Light: [https://www.nuget.org/packages/Infragistics.Themes.MetroLight.Wpf/](https://www.nuget.org/packages/Infragistics.Themes.MetroLight.Wpf/)
*   Extended WPF Toolkit:  [https://github.com/xceedsoftware/wpftoolkit](https://github.com/xceedsoftware/wpftoolkit)

Custom activity that accepts XAML mark-up for WPF forms and intialization data for the form. Launches the form on the screen, where the user can complete it.

**LockFolder** allows us to lock a folder access until we decide that it is safe to unlock it.

**UnLockFolder** allows us to unlock a folder that was previously locked.

This action can be useful in order to protect main data during the processing of the copy files

! Note: the default UiPath Studio activity for "Delete file" is able to perform the deletion of a file from inside the locked folder as long as you provide the full path and the correct name of the file.

The activity allows you to lock and unlock a certain folder

LockFolder allows you to lock the access to a folder until decided that it is safe to unlock it. UnLockFolder allows you to unlock a folder that was previously locked.

  

This action can be useful in order to protect main data during the processing of the copy files, as well as in other scenarios, like:

*   **Protecting sensitive data:** prevent unauthorized access to a folder containing sensitive data, such as financial records, personal information, confidential business documents etc.
*   **Ensuring data integrity:** prevent any accidental modifications or deletions of files in a folder during a critical process, such as a backup or system update. 
*   **Collaborative work:** prevent accidental changes to files in a shared folder while multiple people are working on them simultaneously. This can help prevent version conflicts and ensure that everyone is working with the most up-to-date files.
*   **Preventing accidental deletion:** the ability to delete files from a locked folder can be useful in preventing accidental deletion of important files. Users can still delete files if they have the correct path and filename, but LockFolder can provide an additional layer of protection.
*   **Ensuring compliance:**  ensure compliance with regulations that require certain files to be kept secure and only accessible by authorized personnel. 

**Note:** The default UiPath Studio activity for "Delete file" is able to perform the deletion of a file from inside the locked folder as long as you provide the full path and the correct name of the file.

The activity allows you to lock and unlock a certain folder.

**Objectives:**

*   Providing a robust and facile manner of processing very large Excel files in the background and without relying on COM Interop.
*   The implementation of these custom activities will give the user the last row of the Excel file (extremely useful when trying to process a file in chunks). Currently trying to read a file in chunks is impossible without knowing the number of rows and columns in the sheet.
*   The implementation of an Application Scope activity that will allow the grouping of the custom activities in this package.
*   Providing activities that are similar in structure and type of parameters to the current Excel application.

**Observation and limitations:**

  
The activity will not keep track of the formats used to display values in the Excel application. For example, a cell with a value of 43006 formatted as date will be displayed as 9/28/2017 in Excel, but this activity will still retrieve it as 43006.  

Files in which the row starts with the index 0 (this index can be found in the XML mark-up of the row) will not be processed. The row number also needs to be under 1048576 (the maximum number of rows in an Excel Sheet). If a row number outside of this interval is found, the application will throw an exception. This limitation is also valid for the Read Range in the Workbook activities package.  

This package is not compatible with .xls files or .csv files. Only .xlsx files can be read with this activity. Reading Large XLS files can be done in conjunction with the Conversions Package, which will convert the file to an .xlsx file, thus making it compatible with this package.  

Some very minor differences when deciding where a range ends between the standard Excel processing activities and this one.

  

**Technical Approach:**  

The files will be processed in the background using the Open XML SDK library and the SAX (Simple API for XML) approach which instead of reading the entire document and exposing its DOM, will independently read the XML files that comprise the Excel document.

  

**Read Range**

  

**Principles**

  

This custom activity reads a Range of cells from an Excel Sheet. It achieves its goal by using the Open XML SDK framework and the OpenXmlReader class to parse the File in a SAX like approach. To get the number of rows, we simply parse the file and count the rows.  

The custom activity is created by simply inheriting the CodeActivity class from the Windows Workflow Foundation framework. We define the logic of the function by implementing the Execute method and we define the input and output of the activity by fields of the InArgument and OutArgument types.  

This activity can only be placed inside a XL Excel Application Scope activity (not necessarily directly inside, but one of its parents must be the XL Excel Application Scope).

An activity pack used to read and process extra large Excel files.

Product Manager

Sample HTTP Service implemented in JavaScript (depending on Node.JS) exposing a simple Chat interface, and interacting with Dialogflow to recognize user intents and transform them into queue items (pushed through the Orchestrator API).  

The sample also includes a workflow able to process such queue item in order to transform the user request into RPA actions and feedback.

  

This covers the whole chain, from chat interface, to Robot, with Orchestrator and NLP in between, to create a basic but functional and extensible RPA-enabled chatbot.

Sample integration with Dialogflow to create an RPA-enabled chatbot

RPA 対応チャットボットを作成するためのダイアログフローとのサンプル統合

JavaScript で実装された (Node.JS に依存)、単純なチャットインターフェイスを表示するサンプル HTTP サービス。DialogFlow と対話してユーザーの意図を認識し、キューアイテム (Orchestrator API によりプッシュ) に変換します。

このサンプルには、ユーザーの要求を RPA アクションとフィードバックに変換するためにキューアイテムを処理することのできるワークフローも含まれています。

このサンプルは、チャットインターフェイスから、Orchestrator と NLP を間に挟んでロボットに至るチェーン全体を網羅しており、基本的ながら機能的で拡張可能なRPA 対応のチャットボットを作成します。

Sample HTTP Service implemented in JavaScript (depending on Node.JS) exposing a simple Chat interface, and interacting with DialogFlow to recognize user intents and transform them into queue items (pushed through the Orchestrator API).

The sample also includes a workflow able to process such queue item in order to transform the user request into RPA actions and feedback.

This covers the whole chain, from chat interface to Robot, with Orchestrator and NLP in between, to create a basic but functional and extensible RPA-enabled chatbot.

Sample integration with Dialog flow to create an RPA-enabled chatbot

Solution Architect

The System Service Manager package contains the four activities listed below.

1.  **Get Service Status:** This activity can be used to check the status of a particular service. For example, if you are running an application that depends on a specific service, you can use this activity to check if the service is running or not. If the service is not running, you can take appropriate action to start the service.
2.  **Start Service:** This activity can be used to start a service that is not running. If you need to start a database service before running a script that relies on it, you can use this activity to start the service before running the script.
3.  **Stop Service:** This activity can be used to stop a service. If you are running an application that is causing issues, you can use this activity to stop the service associated with the application.
4.  **Restart Service:** This activity can be used to restart a service. For example, if you need to apply changes to a service configuration, you can use this activity to stop and start the service to apply the changes.

The mandatory input field ServiceName is expected as the service name in the general tab of service property sheet.

  

The workflow will be blocked until the service operation finishes or the amount of time specified in Timeout field is reached. If the Timeout field is not specified, the workflow will be blocked until the service operation finishes.

  

**Note:** Regarding the permission of the execution of activities 2,3,4, the User Access Control dialogue will be prompted, and you need to manually click the button or disable the the notification. Please refer to this link for more details: https://support.microsoft.com/en-gb/topic/guided-help-adjust-user-account-control-settings-in-windows-7-and-windows-8-605f891d-42c5-2b93-4b4b-e4c5d4d35f60.

These activities will help users identify the status of service, start or restart the service if necessary.

a44749f2-092f-4322-af4f-c53173a83a5e.png

The System Service Manager package contains the four activities listed below:

1.  **Get Service Status:** This activity can be used to check the status of a particular service. For example, if you are running an application that depends on a specific service, you can use this activity to check if the service is running or not. If the service is not running, you can take appropriate action to start the service.
2.  **Start Service:** This activity can be used to start a service that is not running. If you need to start a database service before running a script that relies on it, you can use this activity to start the service before running the script.
3.  **Stop Service:** This activity can be used to stop a service. If you are running an application that is causing issues, you can use this activity to stop the service associated with the application.
4.  **Restart Service:** This activity can be used to restart a service. For example, if you need to apply changes to a service configuration, you can use this activity to stop and start the service to apply the changes.

The mandatory input field ServiceName is expected as the service name in the general tab of service property sheet.

  

The workflow will be blocked until the service operation finishes or the amount of time specified in Timeout field is reached. If the Timeout field is not specified, the workflow will be blocked until the service operation finishes.

  

**Note:** Regarding the permission of the execution of activities 2,3,4, the User Access Control dialogue will be prompted, and you need to manually click the button or disable the the notification. Please refer to this link for more details: https://support.microsoft.com/en-gb/topic/guided-help-adjust-user-account-control-settings-in-windows-7-and-windows-8-605f891d-42c5-2b93-4b4b-e4c5d4d35f60.

These activities will help users identify the status of a service, start or restart the service if necessary.

This package contains the following activities:

*   Gmail authentication scope: handles the authentication into Google account and it is a placeholder for all the other activities in the package.
*   Get emails (with optional Gmail filter): retrieves all emails matching the query.
*   Get message by ID: retrieves a Message by ID.
*   Get attachments: saves all the attachments of a message in a specific folder.
*   Send email: sends an email with optional attachments.
*   Get labels: list the labels in the user's mailbox.
*   Create label: add a new Label to user's mailbox.
*   Modify message labels: modifies the labels on the specified message.

**Notes:**

*   Some namespaces (Google.Apis.Data) might need to be imported in the workflow.
*   Every activity should be placed inside a Gmail scope activity.

For more details about how to configure the activities, please refer to the documentation attached in the Resources section.

Activities using Gmail API to manage emails and labels.

Integrations Lead

Ever wanted to start a process from your phone, smart watch, or Amazon Echo? How about tell a robot when something important happens in Salesforce or SAP?

With Node-RED, the entire Internet of Things is now at your disposal when building workflows. With an easy drag-and-drop interface that treats everything–from Slack to a smart washing machine–as a node within a network, you can connect together every piece of your digital ecosystem, including UiPath. We provide two nodes for you to use:

1.  Request: A wrapper of the full Orchestrator API allowing any request to be made. Create assets, add to queues, check robot status, etc.
2.  Start Job: Start a job in 1 step. Supports input arguments as of Orchestrator v2018.3.

So go ahead and tell Siri to run that report you forgot about before your boss gets in; have a smart barometer play Purple Rain every time the pressure drops; let your imagination fly!

NOTES:

*   Node-RED is a free 3rd-party platform that hosts this Orchestrator connector. Click the **External Link** button for instructions on how to install Node-RED.
*   For further details on the connector itself, please visit [https://integrations.uipath.com/docs/node-red](https://integrations.uipath.com/docs/node-red).

Orchestrator in overdrive. Webhooks, Custom UIs, IoT. Node-RED is the bridge that connects UiPath to the digital world over.