By Warren Baird-Oracle on Jul 07, 2016
There are a number of different ways that AutoVue can be customised to better serve user's needs, and I've occasionally talked to people who weren't clear on what the best approach was for what they were trying to accomplish. I'm going to talk about a few of the more popular approaches here, and give you a few pointers about where to find additional information:
1: Add new menu items or toolbar items to AutoVue: This is done by creating what we call a 'Custom VueAction' - which is basically a chunk of java code that can be invoked by a new menu item or toolbar item in AutoVue. The java code can use the AutoVue APIs to access information about the files that are loaded, trigger actions like showing or hiding parts, or creating markup entities, and can easily automate lots of tasks. Dan covered this in more detail in a previous post, and there is a good KM note with more details: KM Note 2151550.1
2: Make parts of drawings or models interactive: This is done by creating what we call 'Hotspots' - with a technique we call Augmented Business Visualization. The idea here is to allow users to click on parts of drawings or models and trigger actions or retrieve information - for instance creating a change order, or retrieving information on a part. We've done a few posts on this in the past, and there is a working sample you can find as KM note 1472899.1
3: Allow users to access files stored in a content repository: This is done using our Integration SDK (ISDK), which can create integrations that allow AutoVue to reach into a repository to find files, get associated metadata and related files, and store annotations back into the repository. This can be very useful when you have a 'home grown' repository of data and need to allow AutoVue to get access to it. The ISDK is provided as a separate installer with AutoVue, and when you install it, you'll get the libraries needs as well as an example integration that shows you how things work. More can be found on our documentation page - look for 'AutoVue Integration SDK' documentation for the release you are working with.
Hope this summary is useful!