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!