19c4ac16-f8af-4408-8c3b-1b3805050207.jpg

Product Manager

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

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

A simple Barcode library implemented using a Library to wrap ZXing. It contains 2 activities:

*   decodes barcodes to text
*   generates a code from text

Update 2020-07: Added support of optional Charset for QR Code

Decode or generate barcodes of various types (including QR codes)

10ab5993-c199-4834-b957-8ca760ee8075.jpg

A simple Barcode library implemented using a Library to wrap ZXing. It contains 3 activities:

*   decodes barcodes to text
*   decodes multiple barcodes to text array
*   generates a code from text

Update 2020-07: Added support of optional Charset for QR Code

Update 2021-08: Added support for decoding multiple barcodes in a single image

A simple Barcode library implemented using a Library to wrap ZXing. It contains 3 activities:

*   decodes barcodes to text
*   decodes multiple barcodes to text array
*   generates a code from text

Update 2020-07: Added support of optional Charset for QR Code

Update 2021-08: Added support for decoding multiple barcodes in a single image

Update 2022-04: Added support for "Windows" project types (.Net 6)

Guaranteeing the quality of workflows in an RPA implementation project can directly impact its success. Although experienced developers and practices like peer reviewing can improve the quality of workflows created, having an automated way to inspect many XAML files can be helpful to do a preliminary automatic evaluation.

This creates the need for a tool that can aid RPA Developers and Solution Architects in the process of workflow review, checking whether most commonly used development best practices are being followed.

In addition, since development conventions vary with each implementation project, it is essential that users of the this tool can easily understand it, and that the tool itself can be more easily extended to meet the necessities and standards of each implementation.

The Workflow Inspector addresses the mentioned needs by having the following characteristics:

*   It is offered as a regular UiPath Studio project, making it easy for users to understand and make modifications without having to learn a different programming language or tool.
*   It uses an Excel file to specify checks to be done and their configurations. This file also contains explanations about checks and suggestions for improvements, contributing to the education of developers in an RPA implementation.
*   It traverses the structure of XAML files by using XPath expressions, which is a standard to query XML and XAML documents. This provides the necessary flexibility to adapt the tool to specific needs of an implementation.

Currently, reports can be generate in English, Japanese and Korean.

A tool for evaluating UiPath Studio projects according to the best practices of workflow development.

### Ingredients:

*   **Google Forms**: data input from as many users as necessary, with flexible control on access permission and enterprise grade security
*   **Google Cloud Functions**: to act as a serverless bridge between Google Forms and UiPath Cloud Orchestrator (GCP account with billing enabled required)
*   **UiPath Cloud Platform**: we will leverage the community offering of Orchestrator as a Service for the sake of this demo
*   **UiPath Studio and Robot**: because you probably want to do stuff with your data

### Data flow:

Users logged in with their Google account will access a form via a shared URL.  
In this form, they will enter some information.  
The Forms will be configured with a script in order to forward the data to the Cloud Functions instance (you may think of this setup as a form of webhook.)

The Cloud Functions instance will optionally transform the data, before forwarding it to the Cloud Orchestrator as a QueueItem.

Once the data reaches Orchestrator, we have several options to handle it from there, but we will assume that we want to process the data right away, so the incoming QueueItem will trigger an unattended process.

### Concrete example:

This is a fairly generic use case, that may be leveraged in a variety of scenarios, but in order to better illustrate the topic, we will implement a simple and specific application of a hypothetical user:

You are an internet service provider, and with so many people relying on their mobile phone for online access, things have been a bit slow during the recent years.  
But all of a sudden, everyone is now working from home, and the sales staff that you have posted in electronics stores are submitting thousands of applications in just a few days.  
This is a lot to process; much more than your current setup can handle, especially because the information is filled in paper forms and reaching you in the form of image data that needs to be input by hand.

From now, your customer facing staff will use tablets to input customer information directly into a Google Form, and a Robot will process it by sending a Confirmation email to the customer, and recording the data into your company's ERP system.

  

This _solutio_n uses the following Google services, subject to their specific license terms:

*   Google Forms: 
*   Google Apps Script:  plus 
*   Google App Engine: 

Sample solution based on Google Forms, Google Cloud Platform Functions, and UiPath Automation Cloud to create an unattended automation scenario starting with a form accessible from anywhere.

詳細についてプロジェクトの[githubレポジトリ](https://github.com/qbrandon/FormToQueueItem)をご覧ください。

グーグルフォームズ、グーグルクラウドファンクションズ、UiPathオートメーションクラウドを利用するコネクターのサンプルとなります。どこでもアクセス可能なフォームをトリガーとしたアンアテンデッドオートメーション。

UiPath Orchestrator provides an out of the box trigger mechanism that allows to start processes at a specific time or when a queue item is added to a queue. This can be limiting in scenarios where you want to chain processes (when process A is done, start process B), or react to unexpected events (process failed, schedule did not start). 

O-trigger aims at solving these scenarios by allowing you to create triggers based on Orchestrator events.

O-trigger is designed around the Webhook feature of Orchestrator. Webhooks allow you to configure endpoints where Orchestrator will post data when an event occurs. For example, when a job fails, Orchestrator will push some data regarding the failure (name of the Robot that failed, name of the process that failed, etc.) to all the configured Webhooks.

O-trigger is a web server that can listen for Webhook events and respond with actions. Namely it can send emails and start jobs on Orchestrator when it receives specific events.

Extends the triggers possibilities of Orchestrator, allowing users to trigger jobs based on various Orchestrator events (job failed, new queue created, new robot created, etc.)

Organized list of recommendations and guidance on how to develop attended automation processes with high performance and usability.

Example of addressed topics are: generic configuration recommendations, best practice specific to UI Automation, common approaches to error and exception handling, description of the various background or Picture-in-Picture execution options, etc...

Various recommendations and guidelines for a better user experience with attended automation.

ユーザー情報