i

Oracle Part Number – E72044-03

May 2017

Agile Product Lifecycle Management

MCAD Connectors for Agile Engineering Collaboration

Release Notes V 3.5.0.2

ii

Copyrights and Trademarks

This document contains information protected by copyright.

All rights are reserved, including the translation. No part of this documentation may be

reproduced in any way (print, photocopy, microfilm or any other form) or processed, duplicated or

distributed by use of electronic system without written permission of the company. The

information contained in this documentation does not constitute any obligation on the part of the

seller. The software described in this documentation is delivered under licensing contract which

governs its use.

XPLM Solution is not liable for errors in this documentation.

All trademarks are the property of their respective owners.

Contact Address (for Support Services see Preface chapter):

XPLM Solution GmbH XPLM Solution Inc.

Altmarkt-Galerie Dresden, Altmarkt 25 250 Commercial Street, Suite 520

01067 Dresden, Germany Worcester, MA 01608 USA

www.xplm.com

Preface

Contacting Oracle Support Services

For Oracle Agile Engineering Collaboration support contact the Oracle Global Customer Support (GCS) via

www.oracle.com/support or My Oracle Support via https://support.oracle.com.

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for

writing code require that closing braces should appear on an otherwise empty line; however, some screen

readers may not always read a line of text that consists solely of a bracket or brace.

This documentation may contain links to web sites of other companies or organizations that XPLM Solution

does not own or control. XPLM Solution neither evaluates nor makes any representations regarding the

accessibility of these web sites.

iii

CONTENT 1. Important Notice ....................................................................................................................................... 4

2. Architectural Changes and Enhancements ................................................................................................ 4

3. New Features ............................................................................................................................................. 5

4. Solved Issues .............................................................................................................................................. 7

5. Known Issues and Limitations.................................................................................................................. 14

MCAD Release Notes 3.5.0.2

1. Important Notice This release contains fixes and changes to

Web Components

Solid Edge binaries

SolidWorks binaries

Creo Parametric binaries

2. Architectural Changes and Enhancements

CAD Platform and Operating System Support

Supported Agile PLM Releases

Agile PLM 9.3.5

o Agile PLM HF 9.3.5.0.11 required

MCAD Release Notes 3.5.0.22

5

3. New Features

Design File Release Process

The MCAD connector now supports the Design Change Order objects provided by Agile PLM. Design

Change Orders (DCOs) can now be assigned to CAD Design objects and accessed as well as managed

from MCAD. This feature includes a makeover of the Change assignment functionality available in

MCAD’s Save Preview dialog: Change assignment is now performed in a separate dialog window, which

allows creating and assigning both, Design and Item Change objects. This supersedes the Change

assignment function known from previous MCAD versions. For details regarding this functionality, please

refer the user guide, chapter “Design File Release Process”.

AutoVue Access from MCAD

MCAD dialogs now provide controls to directly access AutoVue. This allows users to easily access

AutoVue displaying a certain Design object, without having to access Agile’s web client first.

Link Access from MCAD

Design, Item and Change objects in Agile can now be accessed more directly from the MCAD dialogs.

Instead of having to select a Design, Item or Change object and then open the corresponding web client

page using a menu Item, some MCAD dialogs now provide direct links for accessing an Agile object.

Selecting an object prior to accessing the web client is not necessary, in this case.

Load Preview Dialog

The MCAD connector’s Load Preview dialog can now be displayed or switched off (which is the default

setting in this MCAD release) depending on a CAD engineer’s needs. The dialog can be activated or de-

activated using an option setting in the MCAD Preferences dialog. If de-activated, the most important

load related option settings can be accessed via the Preferences dialog as well. This includes the load

structure resolution and the behavior regarding overwriting files in the CAD workspace folder.

CaxConfig.xml Refactoring and Documentation

The central MCAD configuration file, CaxConfig.xml, has been refactored in order to be easier to

understand, shorter and with more comprehensive documentation in the administration guide. In

addition, the settings shipped with the default CaxConfig.xml have been updated to reflect best

practices. The documentation for CaxConfig.xml is provided in the administration guide, chapter

“CAXConfig.xml Settings”.

MCAD Release Notes 3.5.0.22

6

Reworked Save Options

The previously existing save options (Save, Check In, Increment) have been replaced by Save and Check

In/Incorporate. This rework also reflects the changed workflow regarding Design Change Orders, which

has been implemented in this MCAD release. For details, refer the administration guide, chapter “EC

Web Connector Administration”, sub-section “Save Options”.

Removal of Attributes Caching

Until release 3.4, MCAD connectors used a local cache of an Agile server’s data model. Since release 3.5,

the caching has been removed. This omits the necessity to build the cache file prior to using the MCAD

connector and update the cache file every time a data model change is implemented.

Performance Improvements

Several changes have been implemented to improve the load performance of the MCAD connector when

used together with Agile 9.3.5.

MCAD Release Notes 3.5.0.22

7

4. Solved Issues The following issues have been fixed in this release:

23584027 - 1OFF:22916173:THE BOM QUANTITY SHOWING IN AGILE PC NOT

EQUAL THE NUMBER OF TIME

When de-activating configuration resolution in the MCAD connector for SolidWorks ("Configured" file

property), the quantities of the configuration instances were not correctly stored in Agile. The quantity

of a configuration instance, regardless of how often it was actually integrated in an assembly, was always

set to one in Agile (Structure tab and Item BOM).

23153910 - 1OFF:21818353:THE LOCAL VERSION IN WORKSPACE MANAGER IS

NOT UPDATING CORRECTL

When performing a Checkout or Cancel Checkout operation of a Design object in the web client of Agile

PLM, the Design version change introduced through this procedure was not correctly picked up by the

MCAD connector's Workspace Manager dialog. This caused the Workspace Manager to display and

incorrect Design version.

23024900 - 1OFF:23100348:RELEASED CHANGES CAN BE ASSIGNED TWICE,

CAUSING AN UNWANTED REVISI

After having assigned a Design or Item Change (e. g. DFCO or ECO) in the MCAD connector's Assign

Change dialog, the number of the Change assigned is not cleared from the Change number text field of

this dialog. This would allow users, to release this Change and, within the same MCAD session, re-open

the Assign Change dialog and attempt to assign the (now released) Change again. This caused an

unintended Design revision increment that was initiated by the MCAD connector.

22835289 - 1OFF:21968161:ITEM NOT CREATED WHEN USING "AGILE PLM SAVE

AS" WINDOW IN SOLID

The MCAD connector used display names for creating Items in the Save Preview dialog. This only works,

if the API name and the display name are equal for the particular Item sub-class. If this is not the case, e.

g. in case that the display name contains spaces, the Item sub-class is not recognized by the EC services

layer, and Items could not be created.

22818953 - 1OFF:20478571:PUBLISHING TO A RELEASED ITEM RETURNS

INACCURATE/CONFUSING MESSAGE

When saving several CAD files to Agile, among which a number are assigned to released Item objects

while having the Publish to Item option activated in the MCAD connector, the reporting of failed publish

MCAD Release Notes 3.5.0.22

8

processes due to the released Items was not sufficiently distinguished from the reporting of possible

errors during the actual save process, which only takes Design objects into account. This caused the

MCAD connector to display a confusing report in the Save Summary dialog.

22811064 - 1OFF:18845915:FAMILY TABLE SAVE ISSUES & INCONSISTENCIES

When performing a Checkout or Cancel Checkout of a part family instance via the Checkout or Cancel

Checkout functions available in the main ribbon bar, the Save Preview or the Workspace Manager of the

MCAD connector, for the related part family generic, the checkout status was not changed alongside the

instance's status change, vice versa.

16849245, 20538608 - AGILEEC MAPPING EDITOR OPTION 'SUBSTRING' AND

'DATEFORMAT' DOES NOT WORK

The property formatting functions “SubString” and “DateFormat”, available in the Mapping Editor, have

been fixed for the SolidWorks and Solid Edge connector.

20859272 - PRO/E BULKLOAD IS CREATING NON EXISTING ITEMS EVEN IF THE

CAXCONFIG.XML IS SETUP

The legacy save (batch save) function of the Creo Parametric connector did not take the

“NonExistingPartsFromCAD” option setting into account. This caused Item objects to be created, though

the connector was actually configured, not to create them.

21240912 - EC, SAVE CONFIGURATIONS, DESCRIPTION

Mapping configuration specific file properties to PLM attributes did not work correctly for SolidWorks

files containing configurations, when using the Save Configurations save function. The file property

transfer has been corrected accordingly.

21473872 - CHECKIN FROM WORKSPACE MANAGER TAKES MORE TIME

COMPARED TO SAVE PREVIEW

The performance of save operations triggered from the Workspace Manager has been improved to

match the performance of the save operations triggered from the Save Preview window.

21674721 - EC LIFECYCLE PHASE PREFERENCE FOR ITEM PART IS NOT

POPULATING A9

Changing the Item Lifecycle attribute in the Save Preview window as well as initially setting the Item

Lifecycle attribute on Item creation did not work. Both use cases have been corrected accordingly.

MCAD Release Notes 3.5.0.22

9

22270335 - SUBASSEMBLY'S BOM WILL BE LOST WHEN USING TRANSFER FIND

NUMBER

When updating the find numbers of an assembly structure using the “Transfer BOM Find No.” function of

the MCAD connector, under certain circumstances, the BOM structure was unintentionally changed, so

that sub-assemblies were not part of the BOM after executing the process. This issue has been

corrected.

21303952 - PUBLISH RESULTS SHOWS SUCCESS, BUT THE DESIGNS HAS STILL THE

OLD FILES IN AGILE

When attempting to publish to an Item object, to which publishing is not possible (e. g. released Item),

the MCAD connector displayed a SUCCESS status in the Save Summary dialog nevertheless. The

implementation has been changed to display a WARNING status, if saving to Agile succeeded, but the

related publish to Item process did not.

21881686 - EC33/UAT-ISSUE WITH LOAD DRAWINGS IN LOAD PREVIEW

WINDOW

An error message was displayed by the MCAD connector, if users used the Load Drawings functions both

from the context menu and from the check box in the toolbar of the Save Preview window in the same

Save Preview session. The related problem was corrected, mixing the different Load Drawing functions

now works without displaying any unintended error messages.

20422285 - DELETE ITEM ASSIGNMENT DOES NOT FULLY WORK FOR A SINGLE

ITEM

When manually deleting Item assignments in MCAD (context menu), the related PLM attributes (Design,

Page Two, Part Number) were not cleared out, instead, the number of the previously assigned Item

remained visible.

20429108 - PUBLISHING RESULTS SHOWS ONLY ONE ERROR INSTEAD OF ALL

ERRORS

When users attempted to perform a publish to Item for Item objects, to which publishing is not possible

(e. g. because, they are released), it could have happened that the corresponding error message was

only displayed for the first object in the Save Summary dialog, regardless of whether or not this object

showed the error in the first place. Error handling has been improved so that publish errors should now

be displayed correctly in the Save Summary dialog of MCAD.

MCAD Release Notes 3.5.0.22

10

21303882 - DOUBLE CLICK ON DESIGN OBJECT IS CHANGING IT'S RESULT IN

PUBLISH RESULTS WINDOW

An error state (ERROR) displayed in the Save Summary dialog of MCAD could change to SUCCESS, when

users double clicked the resulting table row in order to open the web client. This has been corrected.

20693790 - NORMALLY LINED SUB-ASSEMBLIES ARE PICKED UP AS EXTERNAL

REFERENCES

Under certain circumstances, SolidWorks sub-assemblies within an assembly structure were picked up as

externally referenced by MCAD, though the actual reference between the sub-assembly and its parent

component was a normal reference. This problem has been corrected.

21808046 - EC - SAVE WITH DRAWING CREATES NEW DOCUMENTS

With activated renaming on save, the Solid Edge connector’s Save As Override dialog could cause

incorrect behavior when used in combination with the Save with Drawings save function: Un-renamed

instances of a CAD drawing remained in the local workspace, even though the renamed instance had

already been created, which caused the Save with Drawings function to pick up both instances, the un-

renamed and the renamed one. Actually, these instances are equal and only the renamed one should

have been picked by MCAD’s Save with Drawings functionality. This issue was solved by deleting un-

renamed instances during the renaming process.

20854097 - EC WORKSPACE MANAGER CORRUPTION

When downloading a non-latest version of a CAD assembly or drawing from Agile and performing a

check out in the Workspace Manager, the checked out version displayed by the Workspace Manager was

incorrect: The version displayed was the local version with check out brackets, instead of the latest

checked in version in Agile incremented by one with check out brackets (means, for a downloaded

version 2 out of a total of five checked in Design versions, [2] would be displayed in this case instead of

[6]).

21351917 - WHEN SAVE PREVIEW IS PERFORMED, AGILE EC CRASHES SOLID

EDGE

Certain assembly or drawing structures with unusual properties (missing the full name internal attribute)

caused the Save Preview window to crash. This issue was fixed, missing full name attributes are now

handled by the MCAD connector correctly.

MCAD Release Notes 3.5.0.22

11

19553434 - WORKSPACE MANAGER IS DISPLAYING INCORRECT INFORMATION

AFTER AN UPDATE WITH STRUC

When executing the Update with Structure function available in the Workspace Manager, once the

function has had finished, the Workspace Manager displayed incorrect version information which

required a manual refresh of the Workspace Manager to overcome this problem. The Update with

Structure function now takes care of updating the Workspace Manager, so that this is not required any

longer.

20585646 - LOAD OF A FAMILY OF ASSEMBLY IS BREAKING LINKS OF OTHER

STRUCTURES WHEN LOADED

When loading several Solid Edge Alternate Assembly members from Agile’s web client (multi selection),

the references replacement functionality of MCAD stopped working as soon as the first Alternate

Assembly member had been encountered. This caused internal references within the loaded structure(s)

to be broken.

19896844 - MIGRATED DATA IS SHOWING MODIFIED WHEN LOADED TO CAD

When loading Solid Edge files from Agile, under certain circumstances these files were displayed as

locally modified directly after MCAD having finished the load process. This is normal, in so far, that Solid

Edge sometimes replaces internal attributes, if the storage location of a Solid Edge file changes. To

prevent such files from showing up as locally modified in MCAD, the SolidEdge_ResetTimestampOnLoad

option setting was implemented. This allows users, to configure MCAD that way, that file timestamps are

reset after a load process has finished.

20438314 - AGILE EC LOAD PREVIEW SCREEN ISSUE

When using the Update with Structure function of the MCAD connector to fetch a more recent version of

a CAD file from Agile, while this CAD file is being checked out by another user, it could have happened

that the file sync status in the Load Preview was incorrectly displayed as “in sync”, which is incorrect

when taking the checked out version of the other user into account.

20429553 - REFERENCED PART ATTRIBUTE NOT UPDATED, THOUGH THE

EXTERNAL REFERENCE IS BROKEN

If an assembly was changed that way, that a previously existing external reference has been removed, on

next check in, the external reference was removed from the Relationships tab, but not from the Title

block tabs of the source and target Design objects ("Link Type" and "Link Reference" fields). These Agile

attributes are now updated correctly.

MCAD Release Notes 3.5.0.22

12

21881870 - EC CANNOT EDIT REVISION ON SAVE PREVIEW

In version 3.4 of the MCAD connector, the Design revision was not editable any longer, even though it

should be. This problem has been corrected in this release, the Design revision can be changed again.

22455891 - EC AUTHENTICATION OCCURS 4 TIMES SIMULTANEOUSLY DURING

ONE LOG IN ATTEMPT

When users provided and incorrect password for logging in to Agile and the MCAD connector, the MCAD

connector performed four separate authentication attempts against Agile, which all failed due to the

incorrect password. This caused problems with central login providers (LDAP servers), which counted all

four failed login attempts in this case, possibly locking the user’s account. In case of incorrect passwords,

MCAD now stops sending login requests after the first failed login attempt.

21533039 - EC WORKSPACE MANAGER NOT UPDATING WITH PLM

When configuring a Cascading List attribute to be visible in the Design or Item Title Block, Page Two or

Page Three, the Workspace Manager did not correctly display the PLM status of CAD files any longer.

This was caused by a communication problem introduced through the Cascading List attribute.

20964095 - TOGGLE BETWEEN LATEST IN WORK AND LATEST RELEASE THROWS

AN INDEX ERROR.

When switching between different structure resolution options in the Save Preview, sometimes an

unintended error message was displayed by the MCAD connector. The underlying problem was

corrected, switching between the options now works without displaying any errors.

20744985 - NOT SAVING DESIGN OBJECT ATTRIBUTES DEFINED BY MAPPINGS

Mapping to Design Page Three attributes did not work in the previous release of the MCAD connector.

This issue has been corrected.

22657726 - EC34 CAXCONFIG SETTING FOR CHANGE_CATEGORY NOT WORKING

Defining a default Change Category in CaxConfig.xml did not work in the previous MCAD release: The

defined value was not assigned to Change objects created from MCAD. This problem has been corrected;

the Change Category value now transfers correctly to Agile.

21434165 - ERRONEOUS FILE ATTACHMENT WITH SAVE AS ¿ YES TO LOAD

DRAWINGS

When performing a Save As in the Save Preview dialog of MCAD, and error occurred when confirming

the popup dialog, which allows users to include related drawings in the Save As process: In case that

MCAD Release Notes 3.5.0.22

13

users decided to include drawings, the underlying file objects were not renamed to match the naming

definition based on the new Design object. Instead, the file name was still based on the old Design

object.

20964764 - CONFIGURED ITEMS FROM SOLIDWORKS MISSING BOMS IN AGILE

The Bills of Material of SolidWorks assembly configurations were missing, only for the generic of the

assembly the BOM was correctly written to Agile. This issue has been fixed, both, the generic and all the

instances of an assembly including configurations, get correct BOMs assigned from MCAD.

22115622 - NOT ABLE TO PUBLISH TO ITEM ON MANUALLY ASSIGNED ECO

The MCAD connector’s Publish to Item function returned an error, when users attempted to execute a

publish process on an Item, that had an ECO assigned which was not created by the MCAD connector.

This issue has been corrected.

22181945 - EC REVISION RULE "LATEST RELEASED" IS LOADING INCORRECT

STRUCTURES

When attempting to load Solid Edge structures which are connected through external references at least

three levels deep, the structure resolution could miss parts in the Load Preview, depending on the

checkout status of some of the components. This issue was corrected by introducing a new data model

for external references (Relation-to-Structure tab migration) in the previous MCAD and Agile PLM

release.

MCAD Release Notes 3.5.0.22

14

5. Known Issues and Limitations

Remove Workspace Context Menu Item has been Removed

Related Bug: Bug 21388279 - [3.5NEW]WORKSPACE FOLDER IS NOT DELETED FROM LOCAL DISK

In MCAD release 3.5 the context menu item allowing users to delete workspace folders has been

disabled. It is possible to enable the menu item again by adding the following option to the

BrowserDisplay option set in CaxConfig.xml:

<Structure>

<Name>BrowserDisplay</Name>

<FieldCollection>

<Field><Name>Tree.Menu.Removal</Name><Value>true</Value></Field>

…

Revision Logic Flag “Increment” and Minor Revision Increment Functionality

have been Removed

Related KB Document: Doc ID 2200878.1

In MCAD release 3.5, the minor revision increment functionality for Design revisions has been removed.

Since this release, Design revision increment functionality is part of the Solution Pack (“Rev Sync”). Refer

the knowledge base document mentioned above for additional details.

Custom Attribute Configuration in MCAD Preferences Does Not Work

Related KB Document: Doc ID 2196543.1

Related Bug: Bug 25253796 - UNABLE TO ADD LINES OR UPDATE FIELDS IN THE SUBCLASS TABS OF THE

EC PREFERENCES

Starting with this release, it is not possible to define custom property mappings in the sub-classes tabs of

the MCAD Preferences dialog any more. This functionality has been removed in order to avoid violations

of the MCAD data model.

Removing the sub-class property mapping mentioned above also prevents customers from setting up a

custom mapping for the CAX_COPY_FROM attribute (mapping from CAD to Agile). In HF 3.5.0.6 an

additional mapping option has been provided to accommodate this. Refer to the release notes of HF

3.5.0.6 for details.

Limitation to Working with List Attributes

This product version contains some issues regarding Dynamic, Cascading and Multi List attributes. Some

list attributes will be cleared during an Agile MCAD update save and mapping from CAD to Agile and

MCAD Release Notes 3.5.0.22

15

Agile to CAD does not work for some list attributes. This is resolved with Agile HF 9.3.5.0.78 and Agile

9.3.5 RUP 1.

Transfer BOM Find Number Fails to Create New Items

Related Bug: Bug 22310481 - [3.5NEW]NEW BOM ITEMS ARE NOT CREATED BY TRANSFER BOM FIND

NUMBERS

In this release, the Transfer BOM Find Number functionality of the MCAD connector does not create Item

objects, if required. Refer the bug mentioned above for additional details.

Error During BOM Update when Changing the Part Site Setting

Related Bug: Bug 24945430 - [3.5NEW]IT HAS ERROR UPDATE ROWS OF BOM TABLE IF CHANGE PUBLISH

PART SITE IN CAX

When activating a custom Part Site in the MCAD connector, publishing the BOM to Agile fails with an

error message in case that the Part Site setting in CaxConfig.xml has been changed in between the save

and the publish process. The error message displayed is “Cannot add the bom for site %PARTSITE%,

because the parent does not have that site association”.