Skip to content

Home

Jump to bottom
Manuel García Romero edited this page Oct 13, 2023 · 18 revisions 
 #####                                           ######   ######      #
#     #   ####   #####   ######  ######  #    #  #     #  #     #    # #
#        #    #  #    #  #       #       ##   #  #     #  #     #   #   #
 #####   #       #    #  #####   #####   # #  #  ######   ######   #     #
      #  #       #####   #       #       #  # #  #   #    #        #######
#     #  #    #  #   #   #       #       #   ##  #    #   #        #     #
 #####    ####   #    #  ######  ######  #    #  #     #  #        #     #
~WELLCOME TO ScreenRPA WIKI~

ScreenRPA is a Screen-based Task Mining Framework in the context of Robotic Process Automation (RPA), designed to discover processes that can be automated by a RPA Bot and why are these proccesses selected. By leveraging the power of Python, driven by the Django framework, and supported by Nginx, ScreenRPA enables businesses to streamline their operations and maximize efficiency. Additionally, the application utilizes a PostgresSQL database to store and manage data efficiently.

One of ScreenRPA’s notable features is its flexibility in deployment. Whether you prefer a local setup or containerization using Docker, ScreenRPA can be effortlessly configured to meet your specific needs. This adaptability allows users to choose the deployment method that best suits their environment and workflow.

ScreenRPA Platform Overview

Getting Started (With the theory)

A user who authenticates in the ScreenRPA application can generate a case study, which is complemented by the following modules in order to generate or discover which processes, given the said case study, are suitable for automation.

  1. Behaviour Monitoring: The user is monitored to extract all the raw features that need to be processed (keyboard keystrokes, mouse clicks, on-screen gaze).

  2. Feature Extraction: After monitoring, a large amount of information is generated, and much of it is non-determining content that needs to be filtered. Therefore, it is important to process this information.

  3. Process and Decision Discovery: Once the information has been processed, with ScreenRPA, we will not only obtain a discovery of processes that need to be automated but also the reasons behind the decisions for each process identified for automation.

  4. Reporting: Finally, a PDD is presented that describes which processes should be automated by an RPA Bot.

We recommend taking a look at the articles located in the following section, 'References', to learn more about the context of ScreenRPA and what its implementation as a tool in the world of RPA entails.

Clone this wiki locally