This content has been marked as final. Show 5 replies
1) Please contact AutoVue support team on the procedure of how to implement translations.
2) Note that there are 2 types of similar markup entities: attachments and hyperlinks.
The difference is that attachments are embedded inside markup file itself, hyperlinks are not.
You probably want to remove hyperlinks, but attachments should still be OK even with local files.
3) Unfortunately the size is fixed, however the dialog is resizable by the user...
Edited by: Artashes Gamarian on Apr 5, 2012 11:30 AM
As always, thanks for the fast answer, Artash.
Yes, now I see attachments are stored inside the markup file. The problem is, when I open markup mode for the attachment, since the attachment uses some kind of default access method, my url's from the integration with the background CMS are broken completely. I believe the ideal state here would be to make some kind of inner markup for the attachment, maybe stored within the original markup file along the attached file. Or maybe it works that way, and I need to access it with the default gui action instead of my custom one. If that is the case, is there any way to tell the gui file how to differentiate a standard opened file from an attached one? If so, the issue has solution. If not... Well, then maybe something escapes me.
Edited by: Jordi Bosch on Apr 6, 2012 12:27 AM
Markup in markup is quite a good idea actually...
The thing with attachments is that in most use cases users don't need to mark them up.
But of course you need your application to behave consistently.
You cannot define GUI mode based on where the file comes from
However in your action you can check if the file comes from integration - VueBean.getDocID().isDMS() will tell you that.
If it returns false, then you need to fallback to original markup save action. You can do it through JVue.invokeAction(String, String) API.