49cdba47-e21a-4f31-a225-f7ea783ace07.png

We were founded in 2005 in a tiny apartment in Bucharest, Romania as DeskOver.

Fittingly, it was a customer who, in 2012, first saw the immense possibilities for us in the fledgling RPA market. Our desktop automation product launched in 2013. In 2015, we introduced our enterprise platform along with our new name.

Today, UiPath is the fastest-growing enterprise software company in history with scores of offices, thousands of employees, partnerships with the world’s best consulting and BPO firms, a **500,000-strong developer community**, and **5MM+ robots at work** in over **5,000 global enterprises.**

Our mission is to deliver the leading Robotic Process Automation platform to our clients for an automation first mindset.

We build software robots that automate repetitive processes. Our software robots take on the tedious, mind-numbing work and free people to do the more stimulating, creative work worth doing.

But no matter how much we’ve grown, one thing hasn’t changed. We’re still building a company we love to work for

Senior Software Engineer

22ac2b39-8e69-4be8-8c56-879cf6d99177.png

This is a simple engine to pull and process a Transaction from a local data source.

The workblock contains code that will do the following:

1\. Reads a configuration file, by default located in Data\\Config.xlsx and output as a dictionary named config

2\. Calls ProcessLayer\\InitAllApplications.xaml, where you should initialize apps

3\. Reads the collection of data

4\. For each piece of data (if you have only one transaction pull 4.1 out of 4):

*   4.1 Execute Process - retry if you run into a AppEx
*   4.2 Calls ProcessLayer\\ProcessTransaction.xaml, where you should input data into your opened applications
*   4.3 Evaluate Process wb output
*   4.4 Recover if wb failed with AppEx
*   4.4.1 Call ProcessLayer\\CloseAllApplications.xaml
*   4.4.2 Call ProcessLayer\\InitAllApplications.xaml

5\. Call ProcessLayer\\CloseAllApplications.xaml

A couple of workblocks in UiPath Studio solving simple processes with local data

Simple engine to pull and process a Transaction from an Orchestrator queue

This engine contains code that will do the following:

1\. Read a configuration file, by default located in Data\\Config.xlsx and output as a dictionary named config

2\. Calls ProcessLayer\\InitAllApplications.xaml, where you should initialize applications

3\. While there are items in the Queue, read a new Item and process it.

*   3.1 Get Item from queue
*   3.2 Execute Process - retry if you run into a AppEx
*   3.2.1 Calls ProcessLayer\\ProcessTransaction.xaml, where you should input data into your opened applications
*   3.2.2 Evaluate Process wb output
*   3.2.3 Recover if wb failed with AppEx
*   3.2.3.1 Call ProcessLayer\\CloseAllApplications.xaml
*   3.2.3.2 Call ProcessLayer\\InitAllApplications.xaml

4\. Call ProcessLayer\\CloseAllApplications.xaml

A simple workblock engine made in UiPath Studio to process Orchestrator queue items

Dashboards in Kibana for displaying data about running and finished processes to business, development and management audiences.

All UiPath processes using the workblock concept to log data can use these dashboards.

Attached you will find three files, each containing a set of visualisations and a single dashboard that groups the visualisations together.

In the documentation section, you will find the installation guide.

Kibana dashboards based on the workblock fields

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

Appulate powers the digital transformation of insurance by bringing together the insured, agent, wholesale broker, MGA and carrier on a single “point of sale” platform designed to expedite the rate, quote and bind process for property and casualty risks.  Carriers and MGAs use Appulate to not only digitize their products and programs, but to expose them to more than 30,000 agencies using Appulate. 

This accelerator provides activity to connect to Appulate Web Service, send ACORD New Business Application PDF documents and fetch ACORD compliant XML data in response to be ready for integrating with any Policy Administration and Rating System of Insurer.

The incoming XML can then be seamlessly ingested into the Policy Administration System either through service-based integration or through UI-based integration using UiPath's RPA.

Provides activity to send Insurance (ACORD) PDF documents to Appulate & fetch back ACORD XMLs

*   composed of workflows that record hierarchical and execution data in a consistent way, termed Workblocks
*   using State Machine layout
*   offering top level exception handling and application recovery
*   offer a mechanism to abort process execution in certain cases where continuing is destructive
*   keeps external settings in Data\\Config.xlsx file and Orchestrator assets
*   pulls credentials from Credential Manager and Orchestrator assets
*   takes screenshots in case of application exceptions
*   provides extra utility workflows
*   implements services (off by default - see Data\\Config.xlsx) to solve specific tasks independently

A UiPath Studio template upon which you can build, test and run attended and unattended business processes, irrespective of process data types and process linearity

*   ワークブロックと呼ばれる、一貫した方法で階層データと実行データを記録するワークフローで構成されます
*   ステートマシンのレイアウトを使用します
*   トップレベルの例外処理とアプリケーションリカバリを提供します
*   プロセスの実行を継続すると危害がもたらされる場合に実行を中断するメカニズムを備えています
*   Data\\Config.xlsx ファイルと Orchestrator アセットに外部設定を保持します
*   資格情報マネージャーと Orchestrator アセットから資格情報を取得します
*   アプリケーション例外が生じた場合にスクリーンショットを撮ります
*   追加のユーティリティワークフローを提供します
*   特定のタスクを個別に解決するサービスを実装します (デフォルトではオフ - Data\\Config.xlsx を参照)

プロセスのデータタイプや線形性にかかわらず、Attended および Unattended のビジネスプロセスを作成、テスト、および実行するための基礎になる UiPath Studio テンプレート。

Overview

*   composed of workflows that record hierarchical and execution data in a consistent way, termed Workblocks
*   using State Machine layout
*   offering top level exception handling and application recovery
*   offer a mechanism to abort process execution in certain cases where continuing is destructive
*   keeps external settings in Data\\Config.xlsx file and Orchestrator assets
*   pulls credentials from Credential Manager and Orchestrator assets
*   takes screenshots in case of application exceptions
*   provides extra utility workflows
*   implements services (off by default - see Data\\Config.xlsx) to solve specific tasks independently

ユーザー情報