Firstly you need to know how UiPath is working. All actions like clicking, typing, sending hotkeys etc. are dependent on something we called UiElements. Each application have their own buttons, text boxes, areas, lists etc. What UiPath does is to find each of this element and get it’s properties to allow to perform any of these actions on particular application’s element. If application is written with use of something different or developer of application secured somehow possibility to reat those UiElements then UiPath is able to “read” elements based on their look (image processing) or on text written in element (ocr processing).
I can’t tell you if Adobe Framemaker will be 100% compatible with UiPath. What I can tell you is that if isn’t then you have plenty of ways to co-operate with this application with OCR/Image/Computer Vision activities. Like we used to say: “Sky is the limit!”