ThinkTWENTY20

  • HOME
  • ERIC'S BLOG
  • FORUM
  • ABOUT US
  • CONTACT US
  • REGISTER
      • ThoughtLeader Gateway
  • Home | 
  • ERIC'S BLOG | 
  • Robotic Process Automation with StudioX: Lessons Learned 1

Robotic Process Automation with StudioX: Lessons Learned 1

on 24 February 2021

Having worked closely with UiPath StudioX for the last four months, I thought it would be good to revisit some of my points from my earlier series on Robotic Process Automation (RPA), particularly on where “RPA approaches” and “pure programmatic approaches” overlap and contrast.

 

Trying not to be too redundant, RPA is a suite of tools to: 

  • Speed up repetitive manual processes.
  • Reduce errors caused by manual activities.
  • Work alongside your current systems, so that no special accommodations are necessary.
  • In our industry, improve accounting, audit and tax quality and compliance.
  • Free financial professionals from monotonous, repetitive, labor-intensive tasks to focus on more profitable, high-value work.

As RPA is just performing, step by step, what a very fast, very accurate person would do, consistently and repetitively, clicking here and copying there, it acts as a layer on top of the technology you have today rather than requiring any re-engineering.

In my last entry, I noted that I would be talking about the following in upcoming blog entries:

  • How RPA can be used to automate repetitive, monotonous and detail-heavy activities.
  • How programming and StudioX compare, contrast and interrelate.
  • How add-ins to StudioX make it a very powerful personal hub for doing many different tasks.
  • How AI and RPA overlap and complement each other.

And, for no good reason, I’d like to start with the second point; if you have programming skills, is StudioX necessary, helpful, or more?

Most RPA solutions require basic programming (basic meaning rudimentary, as opposed to BASIC programming, the Beginners' All-purpose Symbolic Instruction Code) skills. Once the solution – often called a ‘Bot,’ to some controversy – is in place, the steps can run unattended or hand in hand with a person as necessary.

What makes StudioX unique is that it was designed to hide the coding (although it is possible to take off the cover and use Visual Basic (VB) programming). Is your repetitive task to go to a web site or open a PDF? With StudioX, you don’t need to write lines of code; you can drag and drop an “activity,” or process step, which then tells the computer to go to that web site or open that PDF when you run the ‘Bot’ in the future. Once you have opened the resource you use, do you type in a search term, highlight a table and then switch to Excel to paste it in? Once again, instead of code, you drag and drop specific activities for each step you would take, each click, each copy, each paste into Excel. You can even turn on a “recorder,” perform the steps you normally do and StudioX will create the sequence for you.

While most RPA suites follow a somewhat similar model, StudioX is much more visual, guiding you through how to complete the information needed by the computer. You might say they have considered which 20% of the functionality accomplishes 90% of the common tasks, and highlighted that on the fill-in cards for each process. You can then clean things up, or fill in any missing information so the computer can do the exact steps you want in the future, without your interaction.

So, when the profession recommends that financial professionals consider learning programming – especially Python, but also R or VB – does StudioX mean you don’t need to learn any programming, or at least the foundations of programming?

So, What Can RPA Solutions Do that Python Can’t? 

Let’s look at some of the things StudioX does that Python doesn’t:

  • Provide a limited/no-code environment in which to operate, particularly focused on screen scraping.
  • Integrate with larger suites for collecting business requirements, moving to the field and managing the implementation.
  • Minimize programming errors with components tuned for purpose.
  • Python is a general-purpose tool, so you aren’t starting off with a user-friendly user interface to get the work done.
  • As a visual tool, RPA is not just easier for non-programmers to create, but also for non-programmers to review and manage.

StudioX, as part of the broader Studio Suite, has a wide variety of extensions that simplify tasks like cryptography, working with a wide variety of accounting software products, such as Dynamics 365 and OCR. Although Python libraries also add this functionality, the visual approach simplifies working with software products for the person creating the process.

What Can Python Do that RPA Can’t?

Conversely, Python is incredibly flexible:

  • There are few limitations to Python; there’s even an RPA library for Python (imaginatively named RPA for Python or RPA-Python), which simplifies website automation, OCR and interaction with people on the keyboard and mouse.
  • Python is open-source, and there is no vendor lock-in. Creation of helpful tools that expand Python is fast and frequent. There have been some open-source visual RPA tools, such as the Sikuli Project, but support is very limited. 
  • Python can be used on any platform. StudioX is limited to Windows (which makes sense given its focus on Excel and Office products).
  • Python runs far more quickly and efficiently.

So, for simple repetitive tasks, having an expert with Python may result in more efficient code that is perfectly catered to the job; reviewing the code and making later changes without that expert may, however, be a problem. RPA is simpler for non-programmers to create, manage and update.

Leave a comment

    Comments

    • No comments found
    Powered by Komento
    Forum Recent Posts
    Data Driven Sustainability Decisions
    Tuesday, 03 May 2022

    Gerald Trites, FCA, CISA

    While companies have traditionally viewed sustainability decisions as separate from monetary decisions, this is changing. It’s partly because of generational changes, with millennials now being the largest component of the workplace and partly considerations driven by customer demand, investor demand regulatory requirement and common-sense observation of the destruction caused by climate change. Compelling reasons.

    Companies have been moving more clearly to data driven decision making for several years. So it makes sense they would turn to data to drive their decisions in the sustainability area.  

    To accomplish this, they need to first define their sustainability goals. This usually begins with industry trends and information from stakeholders about their sustainability concerns and the development of a sustainability strategic plan. Second, begins the process of data modelling and analysis drawn from internal and external sources. Many organizations have well defined data gathering processes already in place, but these need to be modified to take into account sustainability goals. Finally, the adoption of data driven sustainability decision making requires the adoption of AI techniques to automate data gathering, modelling and reporting functions.

    Established enterprise systems are moving in this direction, the availability of which, as well as their compatibility with existing systems, is an important consideration.

    Overall, a creative combination of data management, analytics, AI and integration of sustainability processes with established corporate processes are crucial to a successful outcome – the creation of a truly sustainable enterprise.

    How All Accounting Reports Will be Digitized
    Thursday, 31 March 2022

    Gerald Trites, FCA

    The SEC was the major regulatory body that got the ball rolling in 2009, when it mandated rules for the use of the interactive data format (XBRL) for public company financial statements. Then several other countries and organizations got on the band wagon. There was a relatively quiet period for a few years, when the new electronic form of reporting seemed stalled. But then the EU stepped in and began requiring their ESEF filings in 2021. That meant most of the major companies in the world were using digitized reporting.

    For regulators and governments, digital filing of reports has been an opportunity to streamline the processing and analysis of the reports. Users such as investors, on the other hand, have often been unsure about what to do with these reports.

    The fact is, much attention has been given in recent years to the production of digital reports, but very little given to their consumption. True, there are utilities that can be purchased to enable people to read reports in digitized form, the SEC provides such a one, and the recent moves to inline XBRL mean the reports can be read in the conventional way, (ESEF is a variation on inline XBRL). But most of these attempts to render digital reports readable cater to the idea of sequential reading in the conventional sense. Most people do not read this way, unless perhaps they are reading a novel. When they want information, they tend to go to that information as fast as they can. This is the standard approach most people follow in using the internet. People don’t read the internet. Nor generally do they read a corporate website from beginning to end. That would be bizarre!

    But yet, we provide annual reports in paper or PDF form, which extend to around 150 pages and often more, of difficult, often technical, material and expect people to read them. It doesn’t happen. Professional analysts might, but they are more likely to employ analytical tools to get the information they need.

    There is an excellent article on the website of the International Federation of Accountants (IFAC) by Amir Ghandar, titled “The Accounting Revolution Will Be Digitized”.[1] In that article, Mr Ghandar points out that “A 2D, static annual report format in paper or pdf is not that different to the papyrus on which Egyptian scribes reported on the royal inventories more than 7,000 years ago.”

    Much more than this is needed in the modern world. Technology and complexity have advanced tremendously and the style of reporting needs to keep pace.

    Two areas need further work. One involves the steps necessary to encourage legislators and regulators in countries to adopt digital reporting. While a majority of countries have adopted it, there is still a number who haven’t. Then there is the need to take the steps to change digital reporting to make it more understandable and usable to the users. This means providing the resources for them to actually draw out the data they want. These resources need to be made available along with the reports themselves. Some companies in their websites have started doing this, through the provision of data banks and some analytical tools, however it needs to become commonplace and much more powerful and sweeping.

    Developing this approach to corporate reporting requires interaction and discussion between corporate reporters and users, regulators and standards-setters to address the issues.

    Those issues involve more than figuring out how to present digital information and how to use it. It involves determining what information to present, how to present it and when. It involves looking back at the basic tenets that have ruled accounting since its beginnings. The need for annual and other periodic reports. Can they be continuous? Can we eliminate the need for those pesky annual accounting judgements that cause so much trouble? Can we include the tools for analysis within the disclosures rather than relying on the software industry to deliver them? This cannot be accomplished within paper or pdf reports, but rather on the corporate websites. Most companies have moved their reporting to their websites. But they generally have ported over the old paper paradigm, rather than seriously adopting new and innovative ways to report in the information age. It’s well past time we did that.

    https://www.ifac.org/knowledge-gateway/contributing-global-economy/discussion/accounting-revolution-will-be-digitized

     

    [1] https://www.ifac.org/knowledge-gateway/contributing-global-economy/discussion/accounting-revolution-will-be-digitized

    ThinkTWENTY20 © 2022. Privacy Policy
    Login

    username / password