Friday Jul 22, 2016

Troubleshooting AutoVue Printing issues

If you are having trouble printing files from AutoVue, there are some general steps you can take to help  troubleshoot your printing issue.
The following knowledge document is intended for AutoVue users and AutoVue administrators to help them  troubleshoot and narrow down AutoVue printing problems. Please refer to Note 1621489.1

Thursday Jul 07, 2016

Customisation Approaches with AutoVue

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!  


Monday Jun 27, 2016

How to add a custom VueAction in AutoVue

Recently support started to receive more SRs related to customizations, especially around adding a functionality to AutoVue Client/Server Deployment. The first thing to note is that yes it is indeed possible to add one or more new AutoVue functionalities to AutoVue by creating custom code using the AutoVue API. There is already a lot of information in the existing AutoVue documentation on this but since there are lots of steps involved I think it make sense to explain how this can be achieved with step by step instructions. Please refer to Note 2151550.1 and feel free to post comments (to this post or to the note itself) if you feel that any of the steps needs additional clarifications.


Monday Jun 13, 2016

User defined views in AutoVue

Last year I wrote about a feature that I felt was underutilized in AutoVue: Real-Time Collaboration with AutoVue. Today I want to write about another feature that is underutilized and maybe misunderstand. User defined views.

Recently a customer wrote me to tell me how user defined views were great but the fact that he had to redo them each session was annoying and time consuming.

First let me review what a user defined view is. In AutoVue, under the view tab, users are able to create views of the model that best fits their needs, they can rotate the model, explode it out, make certain pieces transparent, etc. Many of these views can be made during a session and by “clicking” on one of the views the model is brought back to that position.

For more information on User defined views and other AutoVue features and functionality see our user guide.

  In the image below I have created 2 User views, Exploded and Transparency, I can switch between these or any of the pre-set views in the view tab.

Here is what the user who wrote to me did not realize, you can create user defined views in Markup mode and save them as part of a markup. As shown in image 2. This means that you only need to create a certain view once, save it and it will remain a part of that markup associated with that file.

This feature makes it easy to save a specific “view” of a model that can be user again and again for a variety of reasons.

Wednesday May 25, 2016

AutoVue Applet and Chrome

Chrome browser is no longer supported with AutoVue Client Server 21.0.0. The Java plug-in for web browsers relies on the cross platform plugin architecture NPAPI to be able to display Applets such as AutoVue Applet on a web browser page. Chrome version 45 and up no longer supports NPAPI. Users can consider alternatives to Chrome such as Firefox, Internet Explorer and Safari as longer-term options. Check the following article for more info about this issue: The AutoVue Development team is currently working on an alternative approach in which NPAPI is no longer required see Note 1999704.1.

Thursday May 12, 2016

Uploading assemblies and other multi-part CAD documents (Xrefs) in AutoVue 21.0.0

Hi all,

I wanted to give a quick overview of one of the changes in AutoVue 21.0.0 that I've heard a few questions around.  Many complex CAD documents span multiple files - there will be a base document (often called an assembly in 3D CAD), and a series of associated files that we broadly call external references or Xrefs (often referred to as Parts or sub-assemblies in 3D CAD).  The way these Xrefs are handled when uploading a file from local disk (not when integrated into a system like Agile, P6 or Web Center Content) has changed in AutoVue 21.0.0, and I'll give you some additional details on that here.

In earlier versions of AutoVue there was a mechanism in place that allowed the AutoVue server to request missing Xrefs from the AutoVue client.  The way it worked was that if the user did a 'file open' on a file named 'Assembly1.asm' from their local hard drive, it would get copied to the AutoVue server and processed.  If during that processing it found that it needed a file named 'Part1.prt', the server would tell the client, and the client would search the local filesystem for a file named Part1.prt, and if found, it would copy that file to the AutoVue server.   That process would repeat until all of the associated subassemblies and parts were copied to the server.

 This process has a couple of problems:

  • Performance is problematic, since the copying of files happens as a series of separate transfers, with some processing of the file in between
  • There is a risk of unexpected results.  The algorithm used to find files on the client side was pretty good, but there was a risk that if the files and folders were not set up the way we expected that we might find *some other* local file named "Part1.prt",  and the user might see the wrong part in the model.

As a result, starting with AutoVue 21.0.0, this mechanism of finding and uploading local Xrefs has been removed, and our recommendation is that if you need to open a file with Xrefs from a local file system, that you do it by creating a zip file containing the base file and all Xrefs, and then opening the file through the zip file.    This ensures that AutoVue gets all of the right Xrefs, and improves performance by sending all of the files in single transfer.

To reiterate - this only impacts files coming directly from the user's local filesystem - if you are integrated into a content management system, and are opening a file from that system, it will take care of providing all of the associated Xref files to the  AutoVue server for you automatically, and this change will not impact you.

 If you have any questions about this change, feel free to ask below!



Thursday Apr 21, 2016

Unable to view Creo files using AutoVue 21.0.0

Since upgrading to the latest AutoVue 21.0.0 release users are having problems viewing Creo files. When trying to do so the following message is displayed:

"Cannot display the ProE 2D file that does not have display list!"

The actual cause of this problem is that the Pro/E file was saved without a display. Re-saving the file (from Pro/E) with the Pro/E config save_display set to yes will solve the problem. For more details please see Note 2126383.1.

Tuesday Apr 12, 2016

AutoVue Rollup Patch is Available

We are happy to announce the availability of a new AutoVue Rollup Patch (RUP) for release 21.0.0. This RUP adds support for SolidWorks 2016 service pack 1, Windows 10 and adds back support for WebSphere 7.1.

 This is the second Rollup Patch for AutoVue 21.0.0, the patches are cumulative, so if you did not install (see blog post AutoVue Rollup Patch is Available) you can add and get all the updates from both.

 This RUP is immediately available for AutoVue users under maintenance.

 With the release of this second AutoVue RUP, Oracle continues to demonstrates its ongoing commitment to providing its customers with up-to-date format support needed for their business practices.

. For more information about AutoVue Rollup Patch, please consult the following Knowledge Management Note on My Oracle Support: Note 2091717.1

Friday Mar 11, 2016

Some Paper Sizes Names are Different in The AutoVue Print Dialog

In general when printing in Java mode (which is the standard since AutoVue 20.1.0 and above) the naming of some paper sizes is different than the standard name. In this case it is recommend to look for and pick the matching name as shown in the following wiki page:

For example if you do not see 11x17 explicitly listed as a possible paper size when printing with AutoVue then test with 'Engineering B' or 'Tabloid' paper sizes which  refers to 11 x 17. For your reference see Note 1122779.1.

Wednesday Mar 02, 2016

Opening Streaming Files Directly in AutoVue 21.0.0

One of the changes in AutoVue 21.0.0 is that we now requires a valid filename extension on all files that we open.  It has long been recommended to always pass valid filename extensions to AutoVue to improve performance, and this was made mandatory in AutoVue 21.0.0.

A side-effect of this is that it is no longer possible to directly open a streaming file from the AutoVue Cache folder.    This is not a common day to day usage scenario for AutoVue, but it is often handy when setting up a system, or attempting to debug system issues.

The recommended approach in situations like this is to rename the streaming back to a name similar to the original, for instance if the original file is "myAssembly.asm.1", you could name the streaming file ""  - this will allow AutoVue to open the file correctly, while still making it clear which is the streaming file and which is the original file.

Monday Feb 15, 2016

The AutoVue client jars expired on January 22nd 2016

I would like to take a minute in order to point out that the AutoVue 20.1.1, 20.2.0, 20.2.1, 20.2.2 and 20.2.3 client jars expired on January 22nd 2016. As of now any users trying to view a file using AutoVue or AutoVue for Agile PLM will get a security warning dialog saying the following:

Warning - Security
The application's digital signature has an error. Do you want to run the application?
Name: JVue
Publisher: Oracle USA, Inc.

A set of patches was released in order to get rid of the warning, the patches contains renewed certificates for each AutoVue releases listed above. For more details please see Note 2088885.1.

Monday Jan 25, 2016

AutoVue for Agile 21.0.0 is Now Available!

We are pleased to announce the availability of Oracle’s AutoVue for Agile Enterprise Visualization 21.0.0, a major release within the 21 product family, on the Oracle Software Delivery Cloud.

With this 21.0.0. release, Oracle delivers it’s next generation 3D visualization framework in AutoVue for Agile, providing best-in-class support for core 3D formats and boasting significant 3D performance and fidelity improvements.

AutoVue for Agile release 21.0.0 also includes view handling improvements specific to Model-Based Engineering and continues to deliver on usability enhancements. 

Agile 9.3.5 customers will also benefit from improvements related to the creation and access of AutoVue markups in the context of Oracle’s Agile workflows.

AutoVue for Agile release 21.0.0 includes the following new capabilities and improvements: 

  • New Format Support
AutoVue for Agile 21.0.0 includes support for the following new formats:
    • SolidWorks 2015 and 2016
    • Creo 3.0
    • Inventor 2015 and 2016
    • AutoCAD 2015 and  2016
    • Catia V5-6R2013 (R23), V5-6R2014 (R24) and V5-6R2015 (R25)
    • SolidEdge ST7and SST8
    • JT 10.0
    • Unigraphics NX 8.5, 9, and 10 (3D only)

The AutoVue for Agile customers are provided the following formats supported in the patch within the 9.3.5 installer: AutoCAD 2016, AutoCAD Mechanical 2-D 2016, Autodesk Inventor 2016, CATIA V5-6R2015, SolidWorks 2015 SP2 and above for 2D files, SolidWorks 2016*
*To enable support for SolidWorks 2016 2D, customers need to download GA Patch 22518352 from ARU.

  • Improved view handling for Model Based Enterprise (MBE)
    • Support for Combined Views (PMI visibility, cut views) in Creo
    • Improved support for Product and manufacturing information (PMI).

 To learn more about AutoVue and MBE see our blog post “Model Based Enterprise - An Introduction

  • Simplified access and creation of AutoVue markups in Agile 9.3.5  
    • Launch AutoVue directly in markup mode from the new Change Affected files tab, eliminating unnecessary clicks.
    • Easily see and access AutoVue markups related to specific Affected Files regardless of the file version, revision and the associated workflow.
    • Easily navigate through multiple files directly from within the AutoVue client using AutoVue’s Multi-content feature.
  • New Platform Support
    • Server: Oracle Linux server 7.X and up
    • Client: Windows 8.1+

Click here to read about the latest features and their corresponding benefits.
Click here to access the latest AutoVue Format Support Sheet.

Wednesday Jan 13, 2016

AutoVue Rollup Patch is Available

We are happy to announce the availability of a new AutoVue Rollup Patch (RUP) for release 21. This RUP adds support for a number of formats including SolidWorks 2016, SolidEdge ST8, Inventor 2016, CatiaV5-6 R2015, and AutoCAD 2016; and is immediately available for AutoVue users under maintenance.

With the release of this AutoVue RUP, Oracle demonstrates its ongoing commitment to remaining at the forefront of format support and delivering the formats strategic to its customers’ business practices.

For more information about AutoVue Rollup Patch, please consult the following Knowledge Management Note on My Oracle Support: Note 2091717.1

Friday Dec 18, 2015

A Browser Page with the Link "" When using IE 11 and launching AutoVue Applet from Agile PLM

When opening a file in AutoVue from Agile Product Life Cycle Management (PLM) with Internet Explorer 11, an additional browser window with the link: is launched. The AutoVue Applet page opens fine and displays the file correctly. 

The root cause of this additional page is that the Agile code suggests a JVM update and queries for that URL. It has this specific code inside the agile page (which can be viewed by reviewing the source page of the AutoVue Applet page)

if(windowsIE=="Microsoft Internet Explorer" {
else {
var time = new Date();
var newWindowName = time.getTime();
myWindow ="",newWindowName);
myWindow.alert("Please Install Java Runtime Environment";

The above code is causing this annoying extra page to pop up aside from AutoVue Applet page.  Support has logged Bug 22049068 with Oracle Agile PLM development team to resolve this issue but as a workaround users can use the following possible workarounds depending on their requirements:

  1. Use Firefox browser instead of Internet Explorer (IE) 11.
  2. Use an earlier IE Version than 11.
  3. Configure IE 11 to use "Enterprise Mode" as specified in the following page:

Thursday Nov 26, 2015

Support for Creo Combined Views in AutoVue 21

Hi all,

I wanted to say a little bit about one of the new features in the recently released AutoVue 21: support for Creo's 'Combined Views' capability.  

Combined views are a pretty key feature when working with Model Based Designs (MBD) - you can see a bit of background on this here:  - when building an MBD in Creo, it is very common to add views that capture a particular aspect of the model that will be important for some aspect of the product's process - assembly, maintenance etc.  

The combined view feature in Creo allows you to create views that substantially filter down what is shown to the user - hiding parts that aren't relevant, hiding PMI information that isn't relevant, even doing a cut through the model to show exactly the part of the model that is relevant.

In previous releases of AutoVue, all that we supported was the camera viewpoint for these views - so you would see that entire model and all PMIs, but from the correct view port.   This makes it very hard to see what was intended by the designer.

In AutoVue 21, we support all of the aspects of the combined view, so you will see the model just as it was intended in Creo.

This will be very valuable for anyone working in a model based enterprise - but will also be useful for many other users of Creo.

Happy visualizing!


The authors of this blog are members of the AutoVue Enterprise Visualization team at Oracle. The views expressed on this blog reflect those of the members and do not necessarily reflect the views of Oracle.


« July 2016