4 Known Issues Introduction

This chapter contains a list of known issues for this release. These were deferred from this release, but may be fixed in a future release. Numbers in this section are for Oracle Agile internal use only.

4.1 Known Issue Disclaimer

This list of Known Issues consists of those found at the time of the initial release. The product may have additional issues found after the initial release and therefore this list is subject to change and is not always comprehensive. Oracle support will continue to track known issues of this product release found on My Oracle Support. Please check for updates at https://support.oracle.com.

17810742

Standard Reports

Issue: REPORT RESULT WITH HTML OUTPUT FORMAT DOES NOT HAVE OPEN TAB

Steps to Reproduce:

Log in to Java Client as admin.
Go to Server Settings >Preference, set Enable BI Publish for reports ”Yes”.
Log in to Web Client as admin.
Execute any Standard Report.
Select the output format as HTML
Check the result.

Actual Result: There is no open tab in the result.

Expected Result: There are three tabs (Open, Save, Cancel) in the result.

Workaround: N/A

17992888

Web Client

Issue: DESCRIPTION VALUE CAN NOT BE DISPLAYED ALL WITH FF NEW VERSION 25.0.1

Steps to Reproduce:

Log in to the system as admin using a Firefox browser.
Create a Part with full description values.
Check the header field of Part description.
Move the mouse into the Description field.

Issue: Check the pop up tips in FF, the values are truncated.
Go to the Recently Visited field.

Issue: Check the pop up tips in FF, the values are truncated.

Workaround: N/A

18494456

Excel & IPC Integration

Issue: OPEN IN EXCEL CAN NOT SUPPORT EXCEL 2010 & 2013

Steps to Reproduce:

Install Excel 2010 or 2013 on the client.
Log in to Web Client as admin.
Create a JGP declaration and click Open in Excel on Actions menu.

Actual Result: Can not open in Excel.

Expected Result: Opens correctly.

Workaround: N/A

18548187

Excel & IPC Integration

Issue: ROLLUP IN EXCEL CANNOT WORK ON IE11 +EXCEL 2007

Steps to Reproduce:

Install Internet Explorer11 and Excel 2007.
Log in to Java Client as admin, set the Process Extension for Part.
Log in to Web Client as admin.
Open a Part and Actions >Rollup in Excel.

Actual Result: Get message like "The feature is supported only with Internet Explorer version 5.5 or later."It works fine on IE10+Excel 2007.

Workaround: N/A

18642356

SOA Scripting

Issue: ATTRS UPDATED IN SPX DONOT SHOW IN THE DIRTY ROW

Steps to Reproduce:

Pre-conditions:

Configure Event: Event Type = Update Title Block;

Object Type = Parts;

Event Handler = <configured event handler with SPX. In the SPX, it updates the attributes' value of the triggered object>;

Trigger Type = Pre;

Execution Mode = Synchronous;

Error Handing Rule = Continue;
Enable Page two and page three of Part.

Steps:

Log in to Web Client as admin.
Create a Part.
Update the attributes on P1, P2, P3 and Save.

Title Block.Product Line = Leo;

Page Two.Text05 = UI set value for P2 attr;

Page Three.Text05 = UI set value for P3 attr;
Validate the Event Monitor.

Actual Result: The dirty row only shows the updated attributes from the UI.Title Block.Product Line = Leo;Page Two.Text05 = UI set value for P2 attr;Page Three.Text05 = UI set value for P3 attr;

Expected Result: The dirty row contains the updated attributes from both UI and SPX.Title Block.Description:set desc from CO1398161140799;Title Block.Product Line = Leo;Page Two.Text01:setCell() for P2 attr;Page Two.Text05 = UI set value for P2 attr;Page Three.Text05 = UI set value for P3 attr;Note: please refer to the attachment for the SPX scripts.

Workaround: N/A

18649006

Event Java PX

Issue: ATTRIBUTES NOT UPDATED SHOW IN THE EVENT DIRTY ROW

Steps to Reproduce:

Pre-conditions:

Configure Event:

Event Type = Update Title Block;

Object Type = Parts;

Event Handler = <JPX - Print all the updated

attributes in dirty row>;

Trigger Type = Pre;

Execution Mode = Synchronous;

Error Handing Rule = Continue;
Enable the attribute of Part: Page Three.Numeric01.

Steps:

Log in to Web Client as admin.
Create a Part and click Save.
Validate the Event Monitor.

Actual Result: Page Three.Numeric01:0.0.

Expected Result: No attribute shows in the dirty row since there were no attributes updated from the UI.

Workaround: N/A

18650725

SOA Scripting

Issue: CAN MODIFY EVENT CONTEXT OBJECT IN POST EVENT VIA SPX API

Steps to Reproduce:

Pre-conditions:

Configure Event:

Event Type = Update Title Block;

Object Type = Part;

Event Handler = <SPX - update the attribute

value: P2.Text01 = "set by event">;

Trigger Type = Post;

Execution Mode = Synchronous;

Error Handing Rule = Continue;
Enable Page Two and Page Three of Part.

Steps:

Log in to Web Client as admin.
Create a Part.
Update the attribute on Title Block and Save.

Title Block.Product Line = Leo;
Validate the Event Monitor.

Actual Result: P2.Text01 is updated to "set by event".

Expected Result: It should show the Error Message: It is not allowed to modify event context object in post event.

Workaround: N/A

18660642

Event Java PX

Issue: MISS ERROR MESSAGE WHEN INSUFFICIENT PRIVILEGE USER UPDATES ATTRIBUTES

Steps to Reproduce:

Pre-conditions:

Configure Event:

Event Type = Update Title Block;

Object Type = Part<tested object>;

Event Handler = <JPX - Print the updated

attributes in dirty row>;

Trigger Type = Pre;

Execution Mode = Synchronous;

Error Handing Rule = Continue;
Enable Page Two and Page Three of Part <tested object>.
Privilege check: Ensure that the user does not have the privilege to update the attributes on Page Two.

Steps:

Log in to Web Client.
Create a Part.
Update the attributes on P1, P2, P3 and Save.

Title Block.Description = UI set value for P1 attr;

Page Three.Text05 = UI set value for P3 attr;
Validate the Event Monitor.

Actual Result: No error message is given about insufficient privilege.

Expected Result: Message displays as follows: "Change of the attribute *** to setcell() for **attr is not allowed because of insufficient privilege or constraint violations.

Workaround: N/A

18670665

Documentation

Issue: PGC WEB SERVICES SHOULD BE DOCUMENTED

Steps to Reproduce:

Steps:

Documentation for all the WS Methods of PGC has to be documented.
Currently we do not have any documentation for PGC.(Issue).

Workaround: N/A

18900435

EC Services

Issue: PART VALUE IS NOT COPIED FROM DESIGN ALTHOUGH DESIGN UPDATET

Steps to Reproduce:

Steps:

Log in to Java Client, set Event as below:

Event Type: Update Title BlockObject Type: DesignsEvent Handler: DesignMappingHandler Type: Java PXTrigger Type: PostExecution Mode: Synchronous
Log in to Web Client, create one file folder named MCAD_SOLUTION_PACK.
Add attached ec-solution-mapping-config.xml into Files tab and Check In

SourceValue>[Design.Title Block.Type]</SourceValue>

TargetAttribute>Item.Title Block.Description</TargetAttribute>
Launch SolidWorks and set Agile > Preferences as follows:

Save As: Item and Design

Item Assignment: Create and Link

Publish to Item: BOM and Attachments

Save Option for Modified: Check In
Create a new CAD and click Agile > Save Preview.
Click Save As to assign new Design Number and Item Number on the Save Preview window.
Highlight the row and right click to bring up the context menu then click Edit Properties.
Set the Design Description with a1, Item Description with b1 on left pane.
Click Save on the left pane.
Go to Agile Java Client, open the Event Handler Monitor.
Check if the event has been triggered or not, and how many were triggered.
Check the Message on Event History Details.
Check the value of item Description from Agile Web Client.
Click the Continue button on the save preview then repeat Step 11 - Step 13.

Actual Results:

Step 11: The event is triggered seven times.

Step 12: The Message shows ”No object has been modified in event history details.”

Step13: The value of item Description is b1 (not changed).

Step14: The event is triggered one time; The message displays as ”Object(s) [Part P00979] have been modified”;. Item description is updated with the correct value.

Workaround: Use the checkIn event instead of Update Design Title Block.

19067255

Standard Report

Issue: PREFERENCE MAXIMUM BOM COMPARE LIMIT DID NOT WORK

Steps to Reproduce:

Pre-upgrade:

Log in to Web Client.
Create two assemblies:

Report_1440_REQ00695_Ass001 and Report_1440_REQ00695_Ass002, add some Items, Manufacturers and Attachments to them, and make sure that these two assemblies have more than 10, but less than 100 nodes in BOM, AML and Attachments

Post-Upgrade:

Log in to Java Client as admin.
Go to Admin > Server Settings >Preferences, set the preferences Maximum BOM Compare Limit=10.
Log in to Web Client.
Open BOM Comparison Report and execute it.
In Step 2, Select Compare Level,Check BOM, AML and Attachment as Compare structure.
In Step 3, add the assemblies, Report_1440_REQ00695_Ass001 and Report_1440_REQ00695_Ass002, and click Finish button
Check the report result.

Actual Result: The report result can be displayed successfully without an error.

Expected Result: It should display an error message in the report results like ”Error: The estimated number of nodes needing to be processed by this report is 20. This exceeds the maximum allowed compare nodes of 10. lease reduce the number of results being requested to be able to run this report.”

Workaround: N/A

19185101

Web Client

Issue: OPEN IN EXCEL AND ROLL UP IN EXCEL DO NOT WORK ON LATEST BUILD

Steps to Reproduce:

Case 1: Open in Excel

Log in to Web Client as admin.
Create a JGP Declaration then route it to open to the supplier.
Log in as a supplier user
Click Open in Excel.

Actual Result: Cannot open the Excel file

Case 2: Weight Rollup

Create a substance Declaration, add an Item to it, then release it.
Open the Item in the previous step, click Actions > Roll Up in Excel

Actual Result: The Open function in Excel does not work.

Workaround: N/A

19193116

EC Services

Issue: DESIGN SYNC DOESN'T WORK WHEN THE FIRST TIME SAVE

Steps to Reproduce:

Preconditions:

1. Update the correct mapping file to MCAD_SOLUTION_PACK.

2. In Java Client, create an Event Subscriber: Update Design Title Block - Design Sync.

Launch the CAD system and log in to Agile via workspace manager.
Open a simple assembly, like staff_and_rings.sldasm.
Click Agile > Save preview.
In Agile, Save the preview, click the Save As button.
Highlight the component of the assembly model and double click it.
Modify Design Description and save.
Click Continue button to save it to Agile.
In Agile web client, open the design and check the History tab.

Actual Result: It displays that ”Design sync: No object has been modified.”

Expected Result: It should display the correct mapping history, like ”DesignSync: Object(s) [Design DESIGN00100.SLDPRT, Design DESIGN00102.SLDPRT, Design DESIGN00101.SLDPRT] have been modified.”
Open the Child Design and check its description.

Actual Result: The child's design description is not updated.

Expected Result: The child's design should have the same description as the parent design.

Workaround: Use checkIn event instead of Update Design Title Block.

19536505

Custom Reports

Issue: FAIL TO RUN SAME REPORT SIMULTANEOUSLY ON AGILE CLUSTER

Steps to Reproduce:

Notes:

This issue is cluster specific.
This issue is related with SLA 14272626. This issue blocks verification of 14272626.
It is most probably an old issue, but there is no env to try it.

Steps:

Get in an Agile Cluster env.
In Java Client, make sure that the Maximum Reports Executed Simultaneously > 1 and Multiple Report Restriction = No.
Log in to Web Client as admin. Create a Custom Report, CR001, which may run a while to show the result.
On IE and FF, log in to Web Clients as admin. Run CR001 almost simultaneously.

Actual Result: On one browser, the user gets an error in the report page like above. (The other one gets a correct report.)

Expected Result: On both browsers, we should get correct reports.

Workaround: N/A

19790700

Java Client

Issue: JAVA CLIENT IS NOT WORKING ON SSL

Steps to Reproduce:

Set up SSL and change all the required settings to HTTPS and t3s.
Open Java Client and try to log in.

Workaround: Java Client: Import the self-trusted certification to JVM and add system property -Dweblogic.security.SSL.ignoreHostnameVerificatio n=true to the Runtime Parameters of corresponding JRE in the Java Control Panel.

19790720

Java Client

Issue: JAVA CLIENT IS NOT WORKING IN WEBSERVICE SECURITY MODE

Steps to Reproduce:

Set up SSL and change all the required settings to HTTPS and t3s.
Open Java Client and try to log in.

19790727

Process Extension

Issue: AGILE SDK IS NOT WORKING ON SSL, THROWS ERROR ON T3S

Steps to Reproduce:

Create SDK session:

>>>

HashMap<Integer, String> params = new HashMap<Integer, String>();

//Put username and password values into params

params.put(AgileSessionFactory.USERNAME, USERNAME);

params.put(AgileSessionFactory.PASSWORD, PASSWORD);

params.put(AgileSessionFactory.URL, URL);

//Get an Agile server instance.

IAgileSession session = AgileSessionFactory.createSessionEx(params);

Actual Result: SDK session creation failed.

Expected Result: Create SDK session successfully.

Workaround: Add the following code on self-signed SSL based on JKS:HttpsURLConnection.setDefaultHostnameVerifier(new HostnameVerifier() {@Overridepublic boolean verify(Stringhostname, SSLSession sslSession) {return true;}});

19812297

Web Client

Issue: NO MULTIPLE-CALENDAR SUPPORT FOR TOP-DOWN CALCULATION IN PPM

Steps to Reproduce:

”No multiple-calendar support for top-down calculation in PPM”.

There are three symptoms caused by this issue:

1. Create from Template: If you assign multiple calendars in one Template, you encounter an error message when you try to create a new project from the template.

2. Move Schedule: If the activity (usually a Project or a Phase) has any children using a different calendar from itself, you will encounter an error message when you try to run the Move Schedule function in the Schedule tab or in Gantt.

3. Add Dependency: If the successor has any children using a different calendar from itself, you will encounter an error message when you try to add a dependency in the Dependency tab or in Gantt.

Workaround:

1. Create from Template: Make sure that only a unique calendar is used in the template and the user can update after a new project is created (Tips: It is more efficient to update the calendar in Gantt). Besides, we also suggest the Administrator or PPM Implementer to disable the Modify privilege to the Calendar attributes of activities/gates in Template state.

2. Move Schedule: Make sure the activity to be moved, as well as its children, are using the same calendar; If you do need multiple calendars, try to group the tasks using the same calendar into one phase and then you can run Move Schedule in the phase level.

3. Add Dependency: Similar to Move Schedule.

19864032

Webdav Integration

Issue: WEBDAV IS NOT WORKING IN READ-WRITE MODE ON WS SECURITY ENABLED

Steps to Reproduce:

Preconditions: Set readonly flag to false in agileDomain\applications\webdav.war\WEB-INF\classes\ - settings.conf

Configure webdav "net use * https://slc07die.us.oracle.com:8443/webdav/ agilesz /USER:admin".
Access BO from BookMarks.
Try to add/delete files

Result: An unexpected error occurs. The "Copy File" window shows that files are not not being added and are unable to be deleted.

Workaround: N/A

19879815

Excel & IPC Integration

Issue: FUNCTION: EXTERNAL ROLL-UP IN EXCEL IS BLOCKED ON SERVER WITH SECURITY

Steps to Reproduce:

Open Excel with AgilePGCExcelAddin.
Try to connect web service.

Actual Result: Cannot connect to web service,. PGC function: External roll up in Excel is blocked.

Expected Result: Should connect web service successfully.

Workaround: N/A

19947340

Main Install

Issue: FAIL TO LAUNCH JAVACLIENT IF DESELECT SSL V3

Steps to Reproduce:

Install Agile934.
Add the following property in setUserOverfides set JAVA_OPTIONS=%JAVA_OPTIONS% -Dweblogic.security.SSL.protocolVersion=TLS1.
Start Agile, Launch Java Client.

Expected Result: Launch Java Client successfully.

Actual Result: Fail to launch Java Client. Displays "Services is not available"

Workaround: Add -Dweblogic.security.SSL.protocolVersion=TLS in client JRE Java Control Panel/Java/Runtime Parameters.

20030253

Java Client

Issue: NEED TO LOG IN AGAIN IF OPEN REPORT FROM JAVA CLIENT ON SSL ENVIRONMENT

Steps to Reproduce:

Log in to Java Client as admin.
Open a Standard Report.

Expected Result: Runs report successfully.

Actual Result: Displays a login page in the browser.

Workaround: Log in manually and then run the report.

20300341

Main Install

Issue: UNDELETE POLICY CONFIGURATIONS IN AGILE.PROPERTIES IF DISABLE WSS

Steps to Reproduce:

Install Agile934.
Enable policy by using the wssconfigurator tool.
Disable policy by using the wssconfigurator tool.
Check agile.properties.

Expected Result: The WSS.ServicePolicy.A9 configurations and the WSS.ClientPolicy.ReferenceObjects should be deleted.

Actual Result: No such configurations.

Workaround: Manually delete configuration'WSS.ServicePolicy.A9 and WSS.ClientPolicy.ReferenceObjects then restart Agile.

20271775

EC Services

Issue: DIFFERENT BEHAVIOR WITH 933 FOR UPDATE PROPERITES ON ITEM DESCRIPTION

Steps to Reproduce:

Launch SolidWorks and connect to Agile.
Open Preferences > Mapping Editor.
Add mapping between CAD property P_P1_DES and Item Description in CAD Properties tab.
New one CAD file and click Save Preview.
Save to Agile with new assigned Design Number, Item Number and Change ECO1 @ with Rev (A).
Open the linked part from Agile Web Client.
Set part description as below under different rev: Introductory: Des_Introductory

@ >Rev (A): Des_A
In the CAD Tool, click Update Properties.
Check the property value of P_P1_DES from Files > Properties > Custom tab.

Actual Results:

933: P_P1_DES = Des_Introductory

934: P_P1_DES = Des_A
Set part description under rev (B): Rev (B): Des_B.
Go back to the CAD Tool and click Update Properties.
Check the property value of P_P1_DES from Files > Properties > Custom @ tab.

Actual Results:

933: P_P1_DES = Des_Introductory

934: P_P1_DES = Des_A
Manually set Design->Relationships Tab->Published Change(Text02) from ECO1 to ECO2 by Agile Web Client
Go back to the CAD Tool and click Update Properties.
Check the property value of P_P1_DES from Files > Properties > Custom tab.

Actual Results:

933: P_P1_DES = Des_Introductory

934: P_P1_DES = Des_A
Release ECO2, then do Update Properties.
Check the property value of P_P1_DES from Files > Properties > Custom .tab

Actual Results:

933: P_P1_DES = Des_B

934: P_P1_DES = Des_A

Expected Result: The desired behavior is that an update properties should use the Item Pending Rev data even if the Relationship.published change is not populated (item added as affected item in webclient). Updating the CAD data with Item data after the release is too late as the Item attachments will not be correct. Both 9.3.3 and 9.3.4 behavior are incorrect. 9.3.4 should update using the pending Item Rev. If there is no Pending Rev then use the latest Released Rev.

Workaround: Assign change by MCAD Save instead of manually assigning from Agile.

20302563

EC Services

Issue: HAVE ERROR MESSAGE WHEN SAVE WITH AN ITEM WHICH HAS RELEASED ECO ASSOCIATED

Steps to Reproduce:

In Agile Web Client, create an Item, for example P01, then assign a Change, for example, ECO01, and Release it.
Create a CAD file in MCAD and then open the Save Preview .
Select the CAD file in the Save Preview window >Right click > Click Edit properties.
Type in the Item Number which is created in Step 1 and generate a design number then save.
Click Continue in the Save Preview Window.

Expected Result: There should be no error.

Actual Result: Thee is an error with message: ”BOM Table is read only.”

Workaround: N/A

20307219

EC Services

Issue: UNKNOWN ERROR WHEN ASSIGN CHANGE FOR ALL COMPONENTS

Steps to Reproduce:

Preconditions: In the Preference tab, set Check out during save = Automated Check out; set Save As = Item and Design.

Create a part model Part1.sldprt.
Create an assembly model, Ass1.sldasm, and insert Part1.sldprt as its component.
Save Ass1.sldasm with Part1.sldprt to Agile.
In the CAD system, create another part model Part2.sldprt and insert it to Ass1.sldasm.
Click Agile > Save preview again.
In Agile save preview, highlight Part2.sldprt then click Save As button to create design number and item number (Key step 1).
Click the Create change using Autonumber button to create a change number.
Highlight all components and assign the change for them (Key step 2).

Actual Result: An error window appears: "You do not have the required privileges on some Objects.”

Expected Result: Assign change successfully without error.
Click Continue button, can save to Agile successfully

Workaround: In Step 8, do not select all components. Assign the change for the components one by one. It will not pop up unknown error.

20307657

EC Services

Issue: CANNOT CHECK IN FILES WHEN ENABLE VIEWABLE FOR CAD FILE AND ADD COMPONENT

Steps to Reproduce:

Preconditions: In the Preference tab, set Save As = Item and Design, and set Save Option for Modified = Check In.

In the Preference tab, enable viewable for models, set STEP, IGES, JT and X_T for all CAD files. (Key step, if disable viewable for Models, the issue is not reproducible)
Open a simple assembly Ass1.sldasm which contains a component Part1.sldprt
Save Ass1.sldasm to Agile.
In the CAD system, create another part model, Part2.sldprt, and insert it into Ass1.sldasm.
Click Agile -> Save preview again.
In Agile, save the preview, highlight Part2.sldprt then click Save As button to create design number and item number.
Highlight the other two components and check them out.
Click Continue to save all to Agile.

Actual Result: It pops up an error window with the message: ”Someone is working on this object. Please try again later.”

Expected Result: Save to Agile successfully without error
Log in to Agile web client and check the Design and Item objects.

Expected Result: The files can be saved to Agile with check in version.

Actual Result: The designs are displayed with pending versions and files are not checked in.

Workaround: N/A

20315684

EC Services

Issue: USER WITHOUT DISCOVER CHANGE PRIVILEGE WILL NOT DISCOVER RELATED ITEM IN

Steps to Reproduce:

Create one user, u1, with discover item, read item, and all design related privileges. Make sure u1 without discover change privilege
Launch CAD Tool and connect to Agile with admin
Create one CAD file and save it to Agile with the linked item and assigned change.
Disconnect Session for admin.
Connect to Agile as u1 and click Save Preview, highlight the component.

Actual Result: The Item is not displayed in the Agile save preview.

Expected Result: The Item should be displayed in Agile save preview.
Go to the Workspace tab and check the design, item and change info.

Actual Result: Item is not displayed in Agile workspace manager.

Expected Result: Item should be displayed in Agile workspace manager.
Log in to Agile Web Client as u1 and check design, item and change info. User u1 can discover item in web client.

Note: In step 3, if not assigning a change, then u1 can discover the item in agile save preview and workspace manager.

Workaround: N/A

20357773

EC Services

Issue: LATER DELETED BOM ITEM IS LOST UNDER FORMER PUBLISHED INTRODUCTORY REV

Steps to Reproduce:

Launch CAD tool and connect to Agile.
Create one Part and one Assembly.
Add the Part as the Assembly's component.
Click 'Save Preview.
Click 'Save As to assign a new Design number and Item number.
Click Continue to save to Agile.
Log in to Agile web client to check the BOM table of the linked part for the assembly. One BOM item is published well under the linked part object with Introductory rev.
Go back to the CAD tool.
Delete the part component from the Assembly.
Click 'Save Preview.
Highlight the row and click Check Out.
Assign one Change with Rev A to the assembly row.
Click Continue to save to Agile with design version 2.
Log in to Agile web client to check the BOM table of the linked part for the assembly

Actual Result: Under rev A, the BOM table is blank as expected, however, for rev Introductory, also blank BOM table, the original published BOM item is removed.

Expected Result: The deleted BOM item under Rev A should not be deleted under Rev Introductory.

Workaround: N/A