Question
QBE
PH
Last activity: 5 Jun 2022 23:22 EDT
Understanding Robotics Automation (*.OS) Files
Hi,
We have an upcoming USE-CASE - create a tool that will scan/analyze the robotics automation file (*.OS) for minor dev's oversight in our best practices e.g. (Automation File has a comment, Unused variables in file, No Exit point, ShowDesignCompNames = true and etc...)
We know for the fact that the (*.OS) file is XML-like structure so the question is, Is there a documentation guide that will help us to understand the code-behind structure of the robotics automation file (*.OS)?
Thanks!
Accepted Solution
Updated: 5 Jun 2022 23:22 EDT
Pegasystems Inc.
US
We do not publish the format of .os files. There is a feature available in our new version that will perform most of these tests. You might be better off waiting for the new version to be released.
Could you provide a list of the checks you are planning? I would like to add any of your needs to the list of tests will provide. Currently, we will be listing unused blocks, unused variables and automations with entry but no exit. There are others as well, but that will give you an flavor of where we are headed.
Thanks,
Jeff Badger
QBE
PH
@jeffbadger Hi, Thanks for the update, will definitely wait for that test feature be available in the upcoming versions. To answer your question, for now we want to automate the checking the compliance of our RPA Engineers in our non-logical best practices:
- There are no unused variables within Automation and GC.
- Automations with Entry has Exit Points
- Automations has a comment
- Automations "ShowDesignCompNames" property is in "True" value for readability of the code
- No Hardcoded input in automation block.
Thanks!
Regads,
Nikko Prado