Go to primary content
Agile Product Lifecycle Management Readme
Release 9.3.5
E52160-01
  Go To Table Of Contents
Contents

Previous
Previous
 
Next
Next
 

3 Resolved Issues

This chapter lists issues that were resolved during this release.

For each resolved issue:

3.1 Product Collaboration

17662095

Searches

Issue: SORT BY ATTACHMENT COLUMN UP/DOWN IN SEARCH RESULTS DOES NOT GET SORTED RESULTS

Root Cause: Since Java 7, it throws "comparison method violates its general contract" exception on the sorting attachment column. https://docs.oracle.com/javase/7/docs/api/java/util/Comparator.html

Resolution: Define a comparison that observes the general contract.

Verification:

  1. Log in to Web Client as admin.

  2. Do a basic search: Item-->p0*, run the search.

  3. Sort search results by the Has Attachments column in Ascending order: Click the Has Attachments column, changes Icon to Show the Up Arrow.

    Result: Search results are sorted by Has Attachments column in Ascending order: for Icons, display should be treated as 1, empty as 0.

  4. Sort search results by Has Attachments column in Descending order: click Has Attachments column, changes Icon to Show a Down Arrow.

    Result: Search results are sorted by Has Attachments column in Descending order: for Icons, display should be treated as 1, empty as 0

18044246

Administration/Configuration

Issue: CANNOT BUILD CRITERIA USING CHANGE ORDER | AFFECTED ITEM | ITEM P2 MULTILIST01

Root Cause: $USERGROUP is not handled specially in the save criteria.

Resolution: Handle $USERGROUP in a special manner in the save criteria.

Verification:

  1. Log in to Java Client as admin.

  2. Go to Classes > Parts > Page Two, enable Multilist01, and set it point to dynamic list:User Groups.

  3. Go to Classes > Change Orders > Affected Items, enable Item.P2.Multilist01.

  4. Go to Admin > Criteria, create a new criteria C1: Change orders > Affected item.Item.P2Multilist01 > Contains any > $User Group, and save.

    Result: The new criteria:C1 is created successfully.

18058522

Searches

Issue: EMAIL: SEARCH CRITERIA IS NOT RETAINED/DISPLAYED CORRECTLY IN INPUT SCREEN

Root Cause: When mapping selected values for the multi-selection list, the matching conditions is mistakenly joined with an OR logic operand, ||.

Resolution: Replace the operand with AND, &&.

Verification:

  1. Log in to Java Client as admin.

  2. Go to Admin > Classes > Parts > Page Two, and enable p2.list10. Set it point to a simple list:product line.

  3. Go to Admin > Classes > Documents >Page Two, enable p2.list10, sand et it point to the same simple list:product line.

  4. Go to Classes > Change Orders > Affected Items, enable attribute: Item.P2.List10

  5. Log in to Web Client as admin.

  6. Create a part:P001, sand elect LEO for p001.P2.List10.

  7. Create a change order:ECO001, add P001 to its Affected item table

  8. Do an Advanced Search: Changes > Change orders > Affected Item.Item P2 List10 > In > [Parts]LEO, and click outside the text input widget.

    Result: Selected value:[Parts]LEO can be retained correctly.

18073073

Web Client

Issue: NEW MANUFACTURER DOUG'S HOUSE OF PIES - 005157M IS NOT A VALID MFR NAME

Root Cause: It no longer escapes single quote and back slash character.

Resolution: N/A

Verification:

  1. Log in to Web Client as admin.

  2. Create a Manufacturer with an apostrophe in its name: mf'1.

  3. Create a Manufacturer part. In the Create New window, input mf'1 in the Manufacturer field, then input the Manufacturer Part number and save it.

    Result: The new Manufacturer Part is created successfully.

  4. Create a Manufacturer Part, in the Create New window. Click the Search button besides the Manufacturer field, input m, and run the search.

    Result: The Manufacturer with apostrophe, mf'1, is returned.

  5. Select mf'1, then input the manufacturer part number, and save it.

    Result: The new Manufacturer Part is created successfully.

18174566

Java Client

Issue: UNABLE TO COPY BOM ITEMS BETWEEN BOMS WITHIN AN ECO

Root Cause: The shared redlined image attribute is incorrectly set by Change/AI as editable, thus the content copy/paste in Java Client tries to update the redlined image attribute of the Redline BOM with the hard-coded attribute id "600005" and fails with the error that the customer reported.

Resolution: Correct the editable property of image attributes.

Verification:

  1. In Admin, reorder the AI attributes and move the Item Number (usually modifiable) attribute to the top.

  2. In Java Client, copy some Redline BOM rows from one Affected Item to another.

    Result: The user is able to copy BOM Items between BOMs within an ECO.

18252178

Web Client

Issue: EDIT ATTRIBUTES OF A SUPPLIER RESULTS IN "SUCCESSFULLY SAVED" BUT DID NOT SAVE

Root Cause: Do not handle the case, if popup window "Add Contact Users" is empty, and grey Save button can not be clicked.

Resolution: Make the grey Save button to be non-clickable.

Verification:

  1. Open a non-web supplier.

  2. In the General Info tab of the non-web supplier, set the Web Supplier to Yes, and edit the Description, Address, and so on, then click Save.

  3. On the Add Contact Users page, click Finish.

    Result: The Finish button is greyed out and disabled when there is no contact user. Nothing happens when the user clicks it.

  4. Add a contact user to this supplier.

  5. Click Finish.

    Result: The Add Contact User window is closed. The non-web supplier is changed to web supplier. The Updated attributes like Description, Address, etc. are saved successfully.

18356374

Administration/Configuration

Issue: THE VALUE APINAME OF CASCADING LIST AUTOMATICALLY CHANGE

Root Cause: There is a code defect of not setting APINAME of listentry for different languages.

Resolution: Set APINAME of listentry for all languages to be identical.

Verification:

  1. Log in to Java Client as admin.

  2. Create a new cascade list, CS, with the following structure:

    17

    --- 1701

    --170101

    Set its API Name as 170101_NVS.

  3. Log in to Java Client as Chinese user CN1.

  4. Search for List CS and change its value:170101 API Name to 170101_CN.

  5. Restart the Agile server.

  6. Log in to Java Client as admin/Chinese user:CN1, check API Name of cascade list value:170101.

    Result: The API Name of the cascade list value, 170101, has been updated to the latest version, 170101_CN.

18367296

Web Client

Issue: IN EDIT MODE, THE SUPPLIER TYPE FIELD IS SHORT AND CUTS OFF THE VALUE IN THE FIELD

Root Cause: We ignore the input width for UG:UG Type.

Resolution: Added code to set the input width.

Verification:

  1. Log in to Web Client as admin, and create suppliers with any supplier type.

  2. Open the General Info tab of the supplier, and click Edit.

  3. Check the Supplier Type field.

  4. Drag the border to scale-down the window, check the value of Supplier Type field.

    Result: The Supplier Type field does not cut off the value, for any supplier type. It displays the complete value such as Component Manufacturer.

18390305

Item & BOM

Issue: ABLE TO ADD BOM COMPONENT WITHOUT HAVING DISCOVERY PRIVILEGES ON COMPONENT ITEM

Root Cause: Allow a user to add BOM components without having Discovery privilege.

Resolution: Do not allow a user to add BOM components without having Discovery privilege

Verification:

  1. In Admin, create a user, User01, with Create Items and Modify Items privilege (make sure the user has no Discover Items privilege).

  2. Log in to Web Client as User01.

  3. Create Part01.

  4. Go to the BOM table and search for Items.

    Result: No item (except the Part that this user created) can be searched out.

  5. Type in an existing Item.

    Result: "Insufficient privilege" message appears.

18472594

Standard Reports

Issue: LEGACY BOM COMPARISON REPORT SHOWS INCORRECT RESULT

Root Cause: It uses a wrong data type to compare Find Numbers when run Legacy BOM Comparison Report.

Resolution: Correct to use correct data type.

Verification:

  1. Create two Parts with the same attributes, for example, YO0911-1 YO0911-2.

  2. Create an ECO and add the two Parts to Affected Items.

  3. On the ECO > Affected Items page, redline the two Parts, adding same part to the two parts, the only difference is the Find Num. For example:

    Item Numberyo0911-1 <----yo0911-2 BOM Redline(T)Item Number Qty Find Num907252600A 1 C001Item Numberyo0911-1yo0911-2 <----BOM Redline(T)Item Number Qty Find Num907252600A 1 C002

  4. Run the Legacy BOM Comparison Report as follows:

    1. On page 1, select Default Layout.

    2. On page 2, select the two Parts for the Report. Change revisions to non-introductory, like (?) C00017.

    3. On page 3, select the proper type.

    4. On Page 4, Compare By: Find Number (Or Compare By: Item Number, Then By: Find Number.

    5. Click Finish to get the report.

    Result: The report results are correct.

18809392

Administration/Configuration

Issue: PAGE TWO TABS ARE NOT DISPLAYED FOR DISCUSSION OBJECT IN TAB DISPLAY CONFIGURATION

Root Cause: General Objects show P2 and P3 in the Cover Page if they are set to visible, but for Discussion, its Cover Page needs to show the Discussion Messages, so Discussion shows P2 and P3 in separate tabs. The Personalize window is for public use, so "Page Two" is not shown in Displayed Tabs/Hidden Tabs.

Resolution: Add a special handler for the Discussion object to show Page Two.

Verification:

Prerequisites: 1. User should have Manage Tab Display privilege. 2. Go to Admin > Data Settings > Classes Open Discussion subclass, Open Page Two in User Interface Tabs and set visible=yes.

  1. Log in to Java Client.

    Result: The user is able to log in to Java Client and has the Manage Tab Display privilege.User is able to set the visibility of Page Two to YES.

  2. Log in to Web Client. Create New > Discussions Create new Discussion Test. Validate that Discussion, Page Two, Action Items, Attachments, History tabs are shown.

    Result: The user is able to log in to Web Client and create a new Discussion and validate the Discussion, Page Two, Action Items, Attachments, History tabs.

  3. Click the right icon for tab personalization and open Personalize. Validate that Page Two is shown in Displayed Tabs/Hidden Tabs.

    Result: The user is able to click the right icon for tab personalization and open Personalize. User is able to view Page Two in Displayed Tabs/Hidden Tabs.

  4. Save the Personalize and return to the Discussion object, and validate the Page Two tab.

    Result: The user is able to click on Save and return to the Discussion object. If Page Two is in Displayed Tabs of Personalize window, then it is displayed in the Discussion object after saving. If Page Two is in Hidden Tabs of the Personalize window, then it is not displayed in Discussion object after saving.

  5. Validate the Order Change of the Page Two tab in the Personalize window.

    Result: The user is able to change the order of display of the Page Two tab in the Personalize window.

18914857

Roles & Privileges

Issue: CREATE FILE FOLDER IS VISIBLE THOUGH NO PRIVILEGE IS ASSIGNED TO THE USER

Root Cause: Markup is special, this functionality is onlyavailable in EC, so if user does not have other'Create File folder(class level)' privilege except'Create Markup', we should not shown 'Filefolders' menu item in WebClient.

Resolution: If user does not have other 'Create Filefolder(class level)' privilege except 'CreateMarkup', we should not shown 'File folders' menuitem in WebClient.

Verification:

  1. Create a new user and give the user only 2 roles - My User Profile and Creator can read and discover objects he or she created.

  2. Log in as the user

    Result: User cannot create any objects.

  3. Use Save As on the Create Markup privilege and create a new one test Markup.

  4. Assign it to a new Role, Test Role, and add the user created in Step 2.

  5. Log back in as the user.

    Result: The user can see a Create New || File Folders || File folders.

  6. Click on it.

    Result: The Create New file folders window displays without Type values in the dropdown.

18954093

Import

Issue: IMPORT IS GIVING AN INCORRECT ERROR MESSAGE FOR INCORRECT FILE TYPE

Root Cause: The logic of parsing Excel is wrong, it mishandles the following format:<sstxmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main" count="4"uniqueCount="4"><si><t>b</t></si><si><t>a</t></si><si><t>12d</t></si><si><r><txml:space="preserve">I'm ok </t></r><r><rPr><szval="11"/><color theme="1"/><rFont val="ArialBlack"/><familyval="2"/></rPr><t>with</t></r><r><rPr><szval="11"/><color theme="1"/><rFontval="Calibri"/><family val="2"/><schemeval="minor"/></rPr><t xml:space="preserve">it</t></r></si></sst>An <si> tag may have multiple <t> tags.

Resolution: Changed the parsing logic to consider the multiple <t> tags situation.

Verification:

  1. Log in to Web Client.

  2. Click Tools and Settings > Import menu.

  3. Select an XLSX file with bold text as source, click the Next button.

  4. Validate the Design which is a component of another Design.

    Result: The XLSX file is imported successfully.

19456954

Searches

Issue: AGILE 933 - WHERE USED REPORT FAILS WITH MESSAGE: AN UNEXPECTED ERROR HAS OCCURED

Root Cause: The attribute, Parts.Title Block.Base Model (2000009494), is not supported by search.

Resolution: Remove the attribute, Main Header Attributes.Parts.Title Block.Base Model, from Where Used Report (report id="7").

Verification:

  1. Create an Item, p0001, and P0002, as its BOM.

  2. Go to the Products Reports folder > Where used report and open it.

  3. Choose the Layout tab.

  4. Select DEFAULT LAYOUT > Format.

  5. Unfold the Main Header Attributes in the hidden fields.

    Result: Parts.Title Block.Base Model are removed from the attributes list.

  6. Add other title block attributes to the display field.

  7. Click Save.

  8. Run the execute button and put the P0002.

  9. Click the Next and Finish buttons.

    Result: The Where Used report can runs successfully.

19458214

Notifications & Subscriptions

Issue: EVENT-BASED NOTIFICATION DISPLAYS ** UNKNOWN CUSTOM ATTRIBUTE **IN THE SUBJECT/BODY OF THE NOTIFICATION RECEIVED

Root Cause: The From Status and To Status custom fields are not handled for PPM objects in Notification.

Resolution: The PPM server side needs to set the previous and next status ID into an object before sending out the Notification. The Notification framework then gets the status ID out and transfers them to the displayed status names in subject/body.

Verification:

  1. Configure a Change Status event for Activities.

  2. Create a Notification for Activities From: $SENDER To: $NOTIFY Subject&Body: Status for [General Info.Name][General Info.Number] has been changed from [From Status] to [To Status] by [User Name].

  3. Event Subscriber: Based on above event and event Handler.

  4. Log in to Web Client.

  5. Create a Program and Change Status, set admin as notify user.

  6. Check the inbox of Admin.

    Result: The attribute value in the notification subject and body showed correctly (Status for PROGRAM-002 has been changed from Not Started to Complete by Administrator, a (admin)).

19596787

Searches

Issue: SAVED SEARCH NOT ALLOWING INPUT FOR PROMPT

Root Cause: Saved search prompt dialog is not handled correctly

Resolution: Fixed code for saved search prompt dialog opening.

Verification:

  1. Log in to Web Client.

  2. Create an Advanced Search > File Folders/Designs - Where Used in Structure One Level All Checked-in Versions - Design Number contains Prompt, Search then Save to Personal Search folders.

  3. Click on the link in Folders to Saved Search.

    Result: Prompts the user to enter the search value for respective attribute once the Saved Search link is clicked from personal searches.

19620107

Standard Reports

Issue: ATTRIBUTE HISTORY REPORT DOES NOT GENERATE THE ATTRIBUTE CHANGE HISTORY

Root Cause: Selected attributes length exceeds report layout specific length[REPORT_LAYOUT(VALUE(4000)+VALUE2(4000))].

Resolution: Extend table column length.

Verification:

  1. Log in to Java Client and enable Read and Modify all attributes for Items.

  2. Enable P2 of class Part and make all P2 attributes visible.

  3. Log in to Web Client, go to find Item Attribute History Report, Layout tab, open Default Layout, on Format tab, add all Main Header Attributes and Page Two attributes to Displayed Fields, save.

  4. Use SQL Developer to connect to the Agile DB, run SQL 'select * from report_layout where last_upd like '%-15';' to get the updated layout by step 3. Note the length of Value2 column.

  5. Create a subclass under Part. Enable P3 and make all P3 attributes visible.

  6. In Web Client, open the default layout, add all page3 attributes of the subclass created in step 5 to Displayed Fields, and save.

  7. On SQL Developer, run that command again to get new length of Value2. If the length is larger that before, repeat step 5 & 6, until the length of Value2 reaches 4000 or not increases.

  8. Open the default layout again. Check the Format tab.

    Result: All the fields are in displayed fields.

  9. In Java Client, enable P3 of subclass Part. Make all P3 attributes visible.

  10. In Web Client. create a Part. Create an ECO against this Part.

  11. Actions > Item Attributes History Report. On the first page of the wizard, edit default layout and add all P3 attributes of the subclass part. Save.

  12. Execute the report, check the result.

    Result: All P3 attributes are shown.

19729216

Web Client

Issue: UNABLE TO LOAD CASCADED MULTILIST IN FIREFOX/CHROME

Root Cause: Attribute names that contain special characters like '#' are included in the query URL without proper encoding, which causes the query to fail on the server side.

Resolution: The attribute name is unnecessary, so remove it from the query.

Verification:

  1. In Admin, create a Cascade list CascadeList01, and add some values into it.

  2. Enable Parts.Page2.MultiList01 and rename it to MultiList#01, and point MultiList#01 to CascadeList01.

  3. In Web Client, create Part01.

  4. In Edit mode, click "Launch the Palette" icon of MultiList#01.

  5. On the pop-up palette, check the values of the cascade list.

    Result: The user is able to load the values of the cascade list.

19763413

Web Client

Issue: CHANGE JAPANESE TRANSLATION "MY BOOKMARK"

Root Cause: Translation issue for My Bookmark.

Resolution: Get new translation for My Bookmark in Japanese translation library.

Verification:

  1. Log in to Web Client as a Japanese language user.

  2. Go to the My BookMark area.

  3. Check the new translation for My Bookmark.

    Result: My bookmarKs is translated with the correct Japanese character string.

19774891

Changes

Issue: HAS APPROVED MANUFACTUERS ICON LINK TO THE WRONG REVISION

Root Cause: A UI framework change at 9.3 introduced this issue.

Resolution: Has Approved Manufacturers icon should adopt the same logic as Has Attachment icon, and link to Item's current revision.

Verification:

Preconditions: Enabled Has approved.

  1. Log in to Web Client as admin.

  2. Create a Part, P001.

  3. Go to the Manufacturer tab of P001 and add any existing Manufacturer object.

  4. Create a new Change, C0001, for Part P001.

  5. Release the changes with Revision 1.

  6. Create a new Change for Part P001 as C0002.

  7. Do not release this C0002.

  8. Go to C0002 > Affected Item tab > Click Has approved Manufacturers dot icon for the P001 Item in the Row.

    Result: P0001 is opened with pending changes version.

19776512

Item & BOM

Issue: ON SCO, CLICKING ON AUDIT RELEASE RESULTS DOES NOT ADD UNRELEASED CHILDREN

Root Cause: When adding Affected Items to SCO from the audit release warning, the site id is missed in request. It is an invalid operation to add common site object to SCO, so from Web Client, the customer will find that no object is added.

Resolution: Auditing release sets the side id and passes it to the request when clicking the audit link.

Verification:

  1. Log in to Web Client.

  2. Create Part01 with a Site and release it.

  3. Create Part02 without a Site and release it.

  4. Create an SCO and add Part01 to the Affected Items table.

  5. Go to the redline BOM tab, and redline add Part02. A warning message appears to tell the user that the part doesn't have a Site and default to a Site.

  6. Click OK to continue.

  7. Click More > Click Audit Release. An error is returned: Unreleased child Part02(site).

  8. Click the error message

    Result: The child part Part02 is added to the Affected Items tab of the SCO.

19832973

Web Client

Issue: LIST VALUE "LENGTH" CANNOT BE STORED IN MULTILIST FIELD

Root Cause: Our implementation of the hashmap js library is backed by native Array, so put a map entry into hashmap is equal to <Array Ojbect>[<key>], and length is a property of Array to indicate its length. It should be an integer.

Resolution: Add the prefix, hashmapkey_, to the head of the keys.

Verification:

  1. In Admin, create a simple list SimpleList01 (type: SIMPLE), and add the following values: Color, Length, Width.

  2. Enable Parts.Page2.MultiList02, and point it to SimpleList01.

  3. In Web Client, create Part02.

  4. In edit mode, click the Launch the Palette icon of MultiList02 and select the value Length.

  5. Click Save, and check the result.

    Result: The value for Length can be saved.

19849958

Searches

Issue: ERROR QUERYING QUALITY EVENT WITH CUSTOMER

Root Cause: When a workflow column is in the search condition, the Customer column is not handled correctly in the where clause.

Resolution: Added missing operators, IN and NOT IN, and added a special handler for SIMPLE_RELATION_CUSTOMER table name when generating the where clause.

Verification:

  1. Log in to Web Client as admin.

  2. Do an Advanced Search: Quality Change Requests > CAPA > Cover page.Customer > In > JohnCo (CUST00001) AND Workflow.Approver > Does not Contain > Analyst, Change (ca), and run the search.

  3. Log in to Web Client as ldapdemo1/Oracle2011 at 10:30.

    Result: CAPA that meets the search criteria is returned in results.

20046950

Changes

Issue: VALIDATE BUTTON IN CHANGE ORDERS REMOVES VALUES OF THE ATTRIBUTES

Root Cause: There is a code defect when retrieving the Cascade List value from the request.

Resolution: Correct the retrieve function.

Verification:

  1. In Admin, create a cascade list, and add some values into it.

  2. Point Change Orders.Cover Page.Reason Code to this new created cascade list.

  3. In Web Client, create ECO01.

  4. In edit mode, select a value for Reason Code, and click the Validate button.

  5. Check the value selected for Reason Code.

    Result: The selected value for Reason Code remains after validation.

20065865

Web Client

Issue: EDITING A USER OBJECT CAUSES COUNTRY/AREA FIELD TO DEFAULT TO AFGHANISTAN

Root Cause: When creating an HTML element for this attribute in edit mode, the addBlank flag is set to false by default.

Resolution: This attribute is allowed to be blank, so we should set the addBlank flag to True.

Verification:

  1. Log in to Java Client as admin.

  2. Go to Classes > Users > User > General Info tab, visible attribute: Country/Area.

  3. Go to Lists > Open Country, set its Display Type as List.

  4. Log in to Web Client as admin.

  5. Open any user without a Country/Area value, then click the Edit button, check Country/Area attribute value.

    Result: The default value for the Country/Area attribute is blank.

  6. Select a value for the Country/Area attribute

    Result: The value can be set successfully.

20190756

Folders, Files, & Attachments

Issue: FILE UPLOAD SELECTOR DOES NOT OPEN FOR ONE USER ADD ATTACHMENT IMPOSSIBLE

Root Cause: Bug in code.

Resolution: Eliminated the parameter of styleFileURL passing from Agile 9 to File server to avoid potential security risk.

Verification:

  1. Log in to Web Client as admin.

  2. Create new Item > Documents > Document: DOC01-18"-PLATE.

  3. Activate the Attachments tab.

  4. Click Add > File. The File Upload Selector window opens,

  5. Click Browse for files.

  6. Select a file from disk, for example, C:\tmp\file01.pdf.

  7. Click Upload (if Start Upload immediately is not check marked). The File Upload Manager window opens, showing progress and upload result.

  8. Log out of Web Client.

  9. Log in to Web Client as admin.

  10. Load Document DOC01-18"-PLATE.

  11. Activate the Attachments tab.

  12. Click Add > File

    Result: The File Upload Selector window pops up and the user is able to upload the file successfully.

20200797

Administration/Configuration

Issue: CHANGE WORKFLOW CRITERIA USING AN ITEM PAGE TWO READ-THRU LIST FIELD WITH A USERS

Root Cause: We do not specially handle dynamic list for Affected Item attributes.

Resolution: Specially handle dynamic list for affected item attributes.

Verification:

  1. In Admin, enable Parts.PageTwo.MultiList01, and point it to Users dynamic list.

  2. Enable Change Orders.Affected Items.Item P2 MultiList01.

  3. Try to create a Criteria with condition: Change Orders.Affected Items.Item P2 MultiList01 Contains Any admin.

  4. Check whether user can create the criteria.

    Result: The user is able to create the criteria.

20205831

Web Client

Issue: THE DATE PICKER DOESN'T WORK PROPERLY IN FIREFOX

Root Cause: N/A

Resolution: N/A

Verification:

  1. Log in to Web Client using Firefox.

  2. Create a Change.

  3. Select the Affected Items tab and add a Part.

  4. Change the Effective Date and time value (include hour, minute and AM/PM).

    Result: The user is able to change the date and time (include hour, minute and AM/PM).

20224215

Folders, Files, & Attachments

Issue: AGILE 933 - DRAG AND DROP FILE ATTACHMENTS TO UPLOAD FAILS IN IE 10 AND FIREFOX

Root Cause: Drag and drop is not supported well in IE10 and Firefox in Agile.

Resolution: Fixed code to handle for IE10 and Firefox.

Verification:

  1. Log in to A9 on IE 10, IE 11, Mozilla browser.

  2. Create or access an ECO or MCO.

  3. Go to the Attachments tab and click on Add > Files.

  4. Drag and drop a file to the file upload selector screen.

    Result: The user is able to drag and drop a file to the file upload selector screen and upload the file successfully.

20271472

Web Client

Issue: HISTORY TAB SHOWS FIELD MODIFIED EVEN THOUGH IT HAS NOT BEEN UPDATED

Root Cause: This is a browser-related issue. For a multi-text attribute, if the value is more than one line, the wrap character is "\n" in Firefox; while is "\r\n" in Internet Explorer, which leads to this issue.

Resolution: Ignore the wrap character's difference between IE and FF when sending cell value for a multi-text attribute during a redline.

Verification:

  1. Log in to Java Client Admin > Data Settings > Classes, open ECO subclass, activate the multi-text attribute, for example, yo-longtext, in P3. Set the value which contains the wrap character to default value, for example, yolong text.

  2. Log in to Web Client using Firefox, create an ECO, assign the workflow, set the change analyst, and submit the ECO.

  3. Log in to Web Client using IE, open an ECO, click the Edit button on the Cover Page, update any field, for example, the Description of Change: from null to 'test') and save it.

  4. Click the History tab, check whether the multi-text attribute is shown as modified.

    Result: The multi-text attribute is not shown as modified.

20283032

Item & BOM

Issue: UNABLE TO SEE ATTACHMENT UNDER MCO REVISIONS

Root Cause: When the system got attachments info by clicking an Item from a pending MCO, if the Item had been released by 2 or more MCOs and there was no released revision (REV released by ECO) on this Item, the system returns the current pending MCO as the released change, but actually, the current pending MCO was not a real released change.

Resolution: Return the change with introductory.

Verification:

  1. Log in to Agile Web Client.

  2. Create a Part, Part01, and add file attachments to the introductory revision.

  3. Create MCO01 against Part01 and release it.

  4. Create MCO02 against Part01 and release it.

  5. Create MCO03 against Part01.

  6. Check Part01's Attachments of the rev MCO03.

    Result: File attachments are shown in the Part of the pending MCO03.

20381471

Web Client

Issue: DUPLICATE TEAM MEMBERS IN PROGRAM SEARCH RESULTS

Root Cause: Missing join condition between table 'TEAM' and 'OBJECTACL'.

Resolution: Adding the join clause 'TEAM.USER_ID = OBJECTACL.USERID' when generating SQL

Verification:

  1. Create an active Program with some child objects.

  2. Navigate to the Team tab and add different users with different roles.

  3. Add one of the object names from Step 1 in Advanced Search and format the Output to display Team.Name and Role attribute.

  4. Click on the search button.

  5. Validate the Search results such that Team Member Name and Role are correctly displayed.

    Result: The search results do not display any duplicate records. Search result displays one record for one user (team member) with all his roles assigned.

20384197

Item & BOM

Issue: EDITING A USER OBJECT CAUSES COUNTRY/AREA FIELD TO DEFAULT TO AFGHANISTAN

Root Cause: Post redline no object version gets updated for an Affected Items object in the table model. A duplicate warning has generated an Affected Items object version in the database. The next time when the redline save happens again, the version mismatch is exposed.

Resolution: Refresh the AI object version after the redline edit save.

Verification:

  1. Log in to Java Client as admin.

  2. Go to Classes > Users > User > General Info tab, visible attribute: Country/Area.

  3. Go to Lists > Open Country, set its Display Type as List.

  4. Log in to Web Client as admin.

  5. Open any user without a Country/Area value, then click the Edit button, check Country/Area attribute value.

    Result: The default value for the Country/Area attribute is blank.

  6. Select a value for the Country/Area attribute

    Result: The value can be set successfully.

20438192

Administration/Configuration

Issue: CANNOT REMOVE LOCK FROM COLUMN

Root Cause: When unlocking attribute in Java Client, it does not set the flag to Unlocked in database.

Resolution: Set the flag to Unlocked in the database when unlocking attribute in Java Client.

Verification:

  1. Log in to Java Client as admin.

  2. Go to Admin > Classes > Parts > BOM tab > Attributes:BOM, click the Order button.

  3. Select the Item Number, lock it, save.

  4. Modify multiple Find Numbers with the same value and click Save. A warning tip appears.

  5. Open the Order, check again.

    Result: The lock is removed successfully.

20466281

Standard Reports

Issue: PRIVILEGE NAME IS NOT SORTED ON PRIVILEGE MASK DETAIL REPORT

Root Cause: Privilege name is not sorted on Privilege Mask Detail Report.

Resolution: Add the sort as Privilege Name.

Verification:

  1. Log in to Web Client, go to run Privilege Mask Detail Report.

  2. Open the saved report, check data in the Applied To columns of each row.

    Result: Data in the Applied To column is sorted.

20492867

Export

Issue: CASCADE LIST ATTRIBUTE DOES NOT EXPORT TO XLS

Root Cause: The XLS file does not export Item detail.

Resolution: Add loadDetailsForItems code for it.

Verification:

  1. Log in to Java Client.

  2. Associate Item Category attribute on Parts Title Block with a cascade list.

  3. Enable Item Category attribute on Parts Title Block.

  4. Enable Item Category read through attribute on Changes Affected Items tab.

  5. Create a Part and select value for Item Category.

  6. Create a Change against the Part.

  7. Export the change to Excel(xls) format.

    Result: Item Category on Changes Affected Items tab is exported and displayed correctly in the Excel file.

20495823

Import

Issue: CHANGED AUTO NUMBER SOURCE DOES NOT TAKE EFFECT ON SECOND IMPORT OF PARTS

Root Cause: This is a cache synchronization issue.

Resolution: Add a flag to indicate whether the AutoNumber source has been changed. When it has changed, then load a new autoNumberGenerator.

Verification:

Preconditions: Create a general user that does not have any special administrator-type privileges.

Admin User:

  1. Log in to Java Client as admin.

  2. Create a new subclass, Service, under the Parts class.

  3. Create the following two new Autonumbers for this new subclass "Service":

    1. Name: PartServ321 Prefix: ORASRV-321-P Number of Characters:42. Name: PartServ123 Prefix: ORASRV-123-P Number of Characters:4

  4. Create a import file as below:

    "Number","Part Type","Lifecycle Phase","Service","Preliminary","Service","Preliminary","Service","Preliminary","Service","Preliminary"

  5. Log in to Web Client.

  6. Launch the Import wizard.

  7. Click the Preferences button on the Import wizard.

  8. Select the AutoNumber sources tab, choose Base Class Items.

  9. Find subclass Service, choose AutoNumber PartServ123.

  10. Select the file created in Step 4, following the Import wizard and click Import.

  11. Launch the Import Wizard again.

  12. Click the Preferences button in the Import Wizard.

  13. Select AutoNumber sources tab, choose Base Class Items.

  14. Find subclass Service, choose AutoNumber PartServ321.

  15. Select the file created in Step 4,following the Import wizard and click Import.

  16. Check the Import Log and objects imported.

    Result: The AutoNumber PartServ321 is used on the second import.

20658334

Administration/Configuration

Issue: SMART RULES CONFIGURATION REPORT SHOWS SMARTRULE: DEMOTIONACKNOWLEDGERSREMOVAL

Root Cause: The Smart Rule, DEMOTIONACKNOWLEDGERSREMOVAL, does NOT exist in Java Client, but it appears in the report.

Resolution: Remove this SmartRule from report.

Verification:

  1. Log in to Java Client.

  2. Admin > System Settings > SmartRules The following SmartRules are shown: DemotionReviewersRemoval Remove/Retain DemotionSignoffRemoval Remove/Retain.

  3. Log in to Web Client.

  4. Report > Standard Report > Administrator Report Run Smart Rules Configuration Report.

    Result: The report output does not show SmartRule:DemotionAcknowledgersRemoval.

20668264

SDK

Issue: HISTORY TAB IS TAKING LONG TIME TO SHOW PX ERROR MESSAGE

Root Cause: Change History cache doesn't refreshwhen the user clicked force-refresh button in webclient.

Resolution: Correct the functionality.

Verification:

  1. Create a new ECO.

  2. Go to the Affected Items Tab.

  3. Drag and drop an existing Item that has pending changes into this change.

    Result: The PX shows a custom message on screen "Cannot add[Item Number01]as affected item onto this change since a pending change already exists."

  4. Click on the History Tab. No information is logged about the PX that got executed.

    Result: The History tab should get updated with the error message from the PX: "Cannot add[Item Number01]as affected item onto this change since a pending change already exists"

20674212

Item & BOM

Issue: TREE NAVIGATION FAILS FOR DOCUMENT BOM EXPAND

Root Cause: If there is a different column enabled/disabled in the BOM table for Part & Document classes the getCellValue from code throws an Out of Bounds exception.

Resolution: If the column index is -1, which means the attribute is disabled for the current class, we do not get the cell value from table.

Verification:

  1. In Admin, enable Parts.Page2.Multilist01 and point to a dynamic list, and enable Parts.BOM.Item P2 Multilist01.

  2. Enable Documents.Page2.Multilist01 and enable Documents.BOM.Item P2 Multilist01.

  3. Log in to Web Client.

  4. Create Part01 with the following structure:

    Part01- Doc01- - Doc02

  5. Click the Navigator button on Part01.

  6. From the left pane, expand the BOM of Doc01.

    Result: The BOM of Doc01 is expanded.

20776859

Changes

Issue: CHANGE IS NOT GETTING CREATED IF THE ITEM NUMBER HAVING = SYMBOL

Root Cause: The warning string and code are parsed with "=" as delimiter. If the subject name contains "=" the problem occurs.

Resolution: For the warning string which contains more than one "=" we take the last "=" occurring as delimiter.

Verification:

  1. Log in to Web Client.

  2. Create a new Part named 15600-SA=.

  3. Create a new Change from Part 15600-SA= as change C00222.

  4. Go to15600-SA= > Actions menu > create new changes again.

    Result: A warning message window appears saying Part 15600-SA= is already on pending changes: C00222.

  5. Click Finish in the warning window.

    Result: It works fine now without duplicated message windows popping up.

20786892

Searches

Issue: HF298 IS CAUSING SAVED PARAMETRIC SEARCHES TO FAIL WITH ERROR "0"

Root Cause: Caused by the fix of bug 19645466.

Resolution: If it cannot get class id, use base class id instead.

Verification:

  1. Log in to Web Client as admin.

  2. Do an Advanced Search: Items > Title Block.Name/Number/Description > Contains any phrase, click Prompt check box, run the search.

    Result: Enter search value window displayed.

  3. Enter Search Values: P001 in Prompt search window, then run the search.

    Result: Parts that meet the search criteria are returned as results.

  4. Save the search as s1, and input it under Global searches folder.

  5. Run the saved search: s1.

    Result: The saved search can be executed successfully without any errors.

20807051

Web Client

Issue: RENAMING MFR NAME ON GENERAL INFO PAGE CORRUPTS PART FAMILY

Root Cause: When changing the Manufacturer Name, the Manufacturer Name in the Parts tab of Part family does not get updated. When loading the Manufacturer Parts and searching the Manufacturer by the old Manufacturer Name, it throws an Object Does Not Exist error.

Resolution: If the user can not search the Manufacturer by the old Manufacturer Name when loading the Parts, set the same value from the Manufacturer Name of the Manufacturer Part object.

Verification:

  1. Log in to Web Client as admin.

  2. Create a Manufacturer, MF1.

  3. Create a Manufacturer Part, MFP1, with MF1.

  4. Create a Part Family, PF1, add Manufacturer Part, MFP1, to its Parts table.

  5. Open MF1, change its name to be MF1-new name.

    Result: MF1-new name is displayed in MFP1.GI.Manufacturer Name field

  6. Return to the PF1.parts table.

    Result: MFP1 with its related manufacture:MF1-new name is displayed correctly in the Parts table.

  7. Use Save As to save PF1 to a new Part Family, then go back to open PF1.

    Result: PF1 can be opened successfully and its Parts table can be accessed successfully.

20809503

Folders, Files & Attachments

Issue: GET OF A FILE DOES NOT SHOW A PROGRESS

Root Cause: When downloading, there is no apparent message to indicate that the downloading action is in process.

Resolution: Added a "Downloading file." message.

Verification:

  1. Log in to Web Client.

  2. Access a business object, navigate to the Attachments tab.

  3. Add a single file, multiple files, and multiple files in a single file folder.

  4. Select the single file or multiple files or multiple files in a single file folder and do the Get, Checkout, Open actions and verify the display of Downloading File message.

    Result: The message Downloading file is displayed for Get, Checkout , Open actions on Attachments or Files tab of File Folder /Design.

20971437

Folders, Files & Attachments

Issue: MISSING FILE UTILITY FAILS WITH JAVA.SQL EXCEPTION

Root Cause: The missing file existed on more than one iFS which causes this issue. The location id is a string and cannot be converted to integer directly.

Resolution: Fixed the code considering case of location is more than one.

Verification:

  1. Log in to Web Client or Java Client.

  2. Access a BO, and navigate to the Attachments tab.

  3. Add 10 files.

  4. Delete the 3 files from the Agile Vault

  5. Run MissingFilesLocator tool.

    Result: The MissingFilesLocator tool report lists the missing files in the vault.

21051857

SDK

Issue: RUNNING SAVED SEARCH MANUALLY ON INACTIVE LIST VALUE RETURNS INCORRECT DATA.

Root Cause: SDK fails to get the correct multilist value from the server if the value is inactive.

Resolution: Changed code to get the correct multilist value.

Verification:

  1. Log in to Web Client and create a search: Parts Object Search for Product Lines promote.

  2. Save this search as MySearch.

  3. Create several parts (part1, part2, part3, part4, part5) and set product lines value as Pisces.

  4. Log in to Java Client, open the list for Product Lines and set Pisces as inactive.

  5. Execute the attached SDK code to run MySearch.

    Result: The parts' product lines set as Pisces (part1, part2, part3, part4, part5) appeared in search results.

21142843

Standard Reports

Issue: CHANGE CYCLE TIME REPORT HAS DATE GAP OF 4 HOURS

Root Cause: Transfer of the status date 2 times caused the timing to be off.

Resolution: Correct the transfer.

Verification:

  1. Log in to Web Client.

  2. Go to the current user's preference, set Timezone to GMT+8, Preferred Date Format to "yyyy-MM-dd".

  3. Create a new Change Order, change status to Released. Notice the Local Client Time is like "2015-05-25 09:38:11 PM CST".

  4. Run the Change Cycle Time Report against the new Change Order, status: from Pending to Released. Execute the report, check the result.

    Result: There is no 4 hour gap. End Status Date is almost the same as local client time in Step 3.

21227091

Administration/Configuration

Issue: AGILE EVENT SCHEDULED TO RUN ONCE EVERY DAY AT 6AM DOES NOT GET TRIGGERED

Root Cause: When the Enable/Disable button is clicked, it does not update the extra column, Active, in the scheduled_event table for scheduled event type.

Resolution: Update this column when a scheduled event is enabled/disabled.

Verification:

  1. Create a new Scheduled event (or update an existing) in Java Client, to run at a specific time.

  2. Make sure to save the configuration for Event/Event Handler/Event Subscriber.

  3. Select the Event created (or modified) abnove, and Enable the evet by clicking on the "Enable" toggle button in the Events node.Please refer the screenshot, "01 Enable Event.png".

  4. Run the below SQL query in the database to observe the status of the Event.

    Result: Select ID, Name, Owner, Description, active, action, to_char(created - 7/24, 'dd-mon-yyyy hh24:mi:ss') "Created", to_char(last_upd - 7/24, 'dd-mon-yyyy hh24:mi:ss') "Last Updated" from scheduled_event where name = 'Schedule Event Task';

21239825

Item & BOM

Issue: UNABLE TO CREATE A NEW BOM ITEM ON WEB CLIENT WHEN ADDLIFECYCLEPH

Root Cause: There is a code defect if AddtoLifecyclePhaseOnBOMRule warning occurs when adding a newly created obj to BOM table. The system fails to delete the newly created obj if user does not have privilege.

Resolution: Corrected the code to avoid the delete action and retain the newly created object in the request to avoid the duplication error.

Verification:

  1. Log in to Java Client as admin.

  2. Create Role CreateItem.

  3. Assign the following privileges to this role.

    Create Items

    Discover Items

    Modify Preliminary Items

    Read Items

  4. Create a User, user1, and assign role "CreateItem".

  5. Make sure that user, user1, does not have Recycle Bin Search.

  6. Go to Data Settings > Classes.

  7. Set AddLifeCyclePhaseOnBOMRule to Warning for Items base class lifecycle phase Preliminary.

  8. Log in to Web Client as user1.

  9. Create new Part P1.

  10. Go to the BOM tab.

  11. Add > Create to Add, and create new Part. Message "Part <Part Number> Lifecycle Phase is Preliminary" pops up.

  12. Click OK.

    Result: The newly created Part is added to the BOM table. This also works for the RedlineBOM table.

21304850

Import

Issue: EXCEL IMPORT FORMAT DOES NOT SUPPORT FORMULAS

Root Cause: This issue was introduced when upgrading POI-3.0.1-Final to POI-3.5-Final in the Agile 9.3.1 release. The way to check whether a FormulaRecord has cached string value in the following StringRecord was changed in POI-3.5-Final.

Resolution: Use the new method FormulaRecord.hasCachedResultString() in POI-3.5-Final.

Verification:

  1. Create an Excel file with formulas.

  2. Log in to Web Client.

  3. Launch Import wizard and select the Excel file with formulas.

  4. Define the mapping for the attributes on Items Page Two, Page Three and BOM tables.

  5. Open the Items imported and check the attributes' value.

    Result: The Excel file with formulas is imported correctly.

21415410

Item & BOM

Issue: HISTORY TAB SHOWS NUMERIC ATTRIBUTE MODIFIED WHEN IT IS NOT ACTUALLY MODIFIED

Root Cause: Number has Scale, so the number in database may be different than the one shown in the UI, for example, scale a numeric field is 2, we enter a value 1.1256, 1.1256 is stored in database, but in UI it is shown as 1.13, obviously if we compare 1.1256 to 1.13, they are different, so before we compare the numbers with scale setting, we need to format them first.

Resolution: Format the numbers before comparing them.

Verification:

Precondition: enable Page2.Numeric attributes

  1. Log in to Web Client.

  2. Create Part1 and edit Part1.Page2.Numeric01 = 1.08368293.

  3. Create ECO01 against Part1 and release it.

  4. Open Part1 on the released rev and edit TitleBlock.Description and Save.

  5. Check History information for the Modify action.

    Result: Only the modified attribute is recorded in the History table (the numeric attributes that are not modified will not appear as modified).

21525295

Standard Reports

Issue: CANNOT RUN AGILE CLASSES REPORT IN FRENCH

Root Cause: Single quotes needs to be specially handled classes report selection page.

Resolution: Specially handle single quotes in this page.

Verification:

  1. Log in to Java Client, go to Admin > Preference > Language, enable French. Restart Agile Server.

  2. Log in to Web Client with admin, go to My Settings > Preference, set Language to French.

  3. Log off and log in as admin, go to find Agile Class Report(Spécifier un paramètre de classe Agile). Click Execute to run the report.

    Result: The lower half of the page shows a multilist for class selection.

21661620

Changes

Issue: NOT GETTING POP UP WHEN FORGOT TO SAVE REDLINE CHANGES IN FULL DISPLAY MODE.

Root Cause: Missed unsaved change check while navigating via backward/forward arrow in full display mode.

Resolution: Added unsaved change check.

Verification:

  1. Open an unrealeased Change Order with multiple Affected Items.

  2. Click on the Affected Items Tab, select an Affected Item row.

  3. In the Redline Table, click on the BOM Tab.

  4. Select a row in the BOM Table.

  5. Click on the Full Display Mode button.

  6. Try to modify any attribute, e.g. Qty.

  7. Without saving the changes, click on the Backward/Forward arrow button.

    Result: The following message is displayed: You did not save your changes. Are you sure you want to discard the changes on this page?

21673303

Web Client

Issue: CANNOT CHANGE SCHEDULED START DATE TIME USING FIREFOX VIA CALENDER OPTION

Root Cause: N/A

Resolution: N/A

Verification:

  1. Log in to Web Client using Firefox.

  2. Create a new project, P1, and try to change the time in Schedule Start / Schedule End date fields by invoking that date field's calendar.

    Result: The user is able to change the time in the calendar of Schedule Start/End date.

22019877

Changes

Issue: AGILE 9.3.4 AUDIT STATUS REPORTS MORE WARNINGS/ERRORS THAN AGILE 9.3.2

Root Cause: There is a For loop defect in checking whether criteria is matched. When one or more rows match the criteria, it returns true for all rows.

Resolution: Fix the defect in related functions to correctly check whether criteria is matched.

Verification:

  1. Log in to Java Client as admin.

  2. In Admin, enable Change Orders.Affected Items.Dispositions06.

  3. Create criteria:

    AllChangeOrdersAffectedItemsLifecyclePhaseInObsolete:

    Affected Items.Lifecycle Phase In Items.Obsolete

  4. Add the criteria to Pending status of Default Change Orders workflow, and set its Exit Required Fields = Change Orders.Affected Items.Disposition06.

  5. Save.

  6. Log in to WebClient as admin.

  7. Create ECO01 and set workflow: Default Change Orders.

  8. Add two Affected Items, Part01 and Part02. Set Part01.Lifecycle Phase = Obsolete, and set another to Production.

  9. Click Actions > Audit Status and check the audit result.

    Result: On the Audit Status Results dialog, there is only missing required field for Part01 for ECO01.Affected Items.Disposition06.

3.2 Product Cost Management

19602316

Export

Issue: RFQ EXPORTS TO EXCEL FORMAT SEVEN DIGIT NUMBERS IN EXPONENT REPRESENTATION

Root Cause: We do not correctly handle integral numbers with 7 or more digits, and the last digit is zero, such as 10000000 or 20000000.

Resolution: Use a new approach to avoid this issue.

Verification:

  1. Open an RFQ and go to Response Status tab.

  2. In the Supplier Response Status section, select the row(s) of the non-Web supplier to whom the RFQ should be sent.

  3. Make sure the response contains the data of an integral number with 7 digits or more than 7 digits and last digit is zero, such as 10000000 or 20000000.

  4. Click Export > Export (csv) or Export > Export (xls), depending on the file type you want to export (Microsoft Excel Workbook or CSV).

  5. Click the Save button to download the file.

  6. Open the exported file and check the value.

    Result: The value shows the correct format, such as 10000000 or 20000000.

20382822

Sourcing Project

Issue: VIEW LATEST CURRENCY RATE THROWS ERROR UNABLE TO SAVE YOUR CHANGES ON UPDATE

Root Cause: An error is thrown as one of the RFQs is in status closed if update currency rate in sp.

Resolution: The user is able to do updates even if a closed RFQs exists in a related sourcing project.

Verification:

  1. Create a Sourcing Project, and add an Item.

  2. Change the project to open, create an RFQ, and add a supplier.

  3. Open an RFQ to a supplier, and get response from supplier.

  4. Close the RFQ.

  5. Go to the Analysis tab of the sourcing project, click More >View Latest Currency Rates

  6. Click the Update on View Conversion Rates window.

    Result: The View Conversion Rates window is closed after the update. The prices in the Analysis tab are updated with the latest currency rate.

21203114

PCM/SDK

Issue: SDK RETRIEVE SOURCE PROJECT ITEMS BOM FIELD GIVES CLASSCASTEXCEPTION

Root Cause: The BOMTable cell is not set correctly if the 2nd (or more) root item is a component.

Resolution: Corrected the code to ensure a sampleChildTable is set to each root Item no matter if it is an assembly or component.

Verification:

  1. Create a Sourcing Project and add one Item to the Item list. Run the attached program against that Sourcing Project and it works.

  2. Add a second Item to the Item list, then run the attached program.

    Result: The code also executed without error.

21475638

Administration/Configuration

Issue: VISIBLE PROPERTY IS NOT SHOWN IN ATTR:RESPNUMBER6 OF SOURCING PROJECTS ANALYSIS

Root Cause: Meta data for this attribute is wrong.

Resolution: Correct the meta data.

Verification:

  1. Log in to Java Client.

  2. Admin > Data Settings > Classes.

  3. Open Sourcing Projects class.

  4. User Interface Tabs > Analysis > Attributes: Analysis.

  5. Open resp Number 6, select the Visible property.

    Result: The property, Visible, is shown next to the Description property. The default value is No. The user can modify it to Yes.

21686769

PCM SDK

Issue: UNABLE TO INVOKE "PRICE.SAVEAS" WITHOUT PROGRAM PARAMETER USING SDK

Root Cause: Code defect of not handling null value of program attribute of Price object while doing Save As via SDK.

Resolution: Handled null value of Program attribute of Price object while doing Save As via SDK.

Verification:

  1. Create a price object by following code:

    IPrice price = (IPrice)sc.session.getObject(IPrice.OBJECT_TYPE,"CONTRACT00001");IAgileClass subclass = price.getAgileClass();IAutoNumber[] numSources = subclass.getAutoNumberSources();String nextNumber = numSources[0].getNextNumber();ISupplier supplier = (ISupplier)sc.session.getObject(ISupplier.OBJECT_TYPE, "SUP-00003");Map params = new HashMap();params.put(PriceConstants.ATT_GENERAL_INFORMATION_NUMBER, nextNumber);params.put(PriceConstants.ATT_GENERAL_INFORMATION_SUPPLIER, supplier);params.put(PriceConstants.ATT_GENERAL_INFORMATION_ITEM_NUMBER, "2075700");params.put(PriceConstants.ATT_GENERAL_INFORMATION_ITEM_REV, "CO-00035");price.saveAs(price.getAgileClass(), params);

    Result: New price object is created successfully.

3.3 Product Governance & Compliance

19309406

Administration/Configuration

Issue: NEW SPECIFICATION SUBCLASS EXEMPTIONS COVER PAGE DYNAMIC LIST NOT WORKING

Root Cause: The business logic of active exempt checking has a defect if the exemptions list is a dynamic list.

Resolution: Improved the logic to support exempt checking for dynamic list.

Verification:

  1. Log in to Java Client as admin.

  2. Create a subclass: Exemption under Specifications.

  3. Create a criteria, CR1, based on subclass Exemption.

  4. Create a dynamic list, DL001, with criteria, CR1.

  5. Go to Classes > Specifications > General Info tab, open attribute, Exemption, set it point to DL001.

  6. Go to Classes > Substance Declarations > Manufacturer Parts, open attribute Exemption, set it point to DL001.

  7. Log in to Web Client as admin.

  8. Create several specifications with Exemption type: ex1,ex2 and ex3.

  9. Create a specification, sp001, and select ex1 and ex2 for sp001.GI.Exemption.

  10. Create a substance declaration, MD001, with sp001, then add a Manufacturer Part, mfp001, to its MPN table. Try to select a value, ex1 for mfp001.exemption, and Save.

    Result: The user can select value successfully.

3.4 Product Portfolio Management

17662656

Administration/Configuration

Issue: DISCUSSIONS - REPLY CREATE NOTIFICATION DOES NOT HAVE [ALL RECIPIENTS] DATA TAG

Root Cause: This issue is because NotificationInitiator.java code does not handle the recipients for creation event. The recipients cannot receive the notification, even if the event has executed successfully.

Resolution: Add the recipients handle code for creation event in NotificationInitiator.java.

Verification:

  1. Log in to Java Client.

  2. Enable discussion - discussion Create.

  3. Notification - Disable default "Discussions - Reply Create Notification".

  4. Create a new discussion from the default by using Save As. The TO field is $NOTIFY.

  5. Create Event - Create an object with Discussion subclass root level.

  6. Configure Event Subscribers by using the custom notification from Step 1 and the new Event in step 2.

  7. Log in to Web Client as admin (or a user).

  8. Create a discussion and add 2 users (A & B) in the Notify List and save it. Note: The newly created discussion history does not show that users have been notified.

  9. Log in as user A and B to check the Home page Notification tab.

    Result: Both users received the newly created Discussion in step 1.

19633882

Web Client

Issue: UNABLE TO REMOVE CANCELLED CHANGE FROM CONTENT TAB OF THE TASK

Root Cause: The check status list should specially handle the PPM object when there is an update content.

Resolution: Add special handler for PPM content when updating content.

Verification:

  1. Log in to Web Client.

  2. Create a Program with a Task and Gate as a child activity.

  3. In the Content tab of Task, add a Change.

  4. Change the status of the Change to cancelled.

  5. Remove the cancelled Change from the Content tab of the task.

Result: The user is able to remove the cancelled Change from the Content tab of the task.

20084674

Web Client

Issue: SCHEDULE END DATE IS NOT EDITABLE ON OBJECT PROPERTIES WINDOW WHEN PROJECT IS OPENED IN GANTT CHART

Root Cause: When disable the Attribute-ACTIVITY.DURATION_TYPE, it will null point exception, as cannot get the value of ACTIVITY.DURATION_TYPE.

Resolution: Handle the null point exception.

Verification:

  1. Disable ACTIVITY.DURATION_TYPE and ACTIVITY.DAYS_EFFORT for Activities in Java Client.

  2. Launch Gantt chart for a Project having child objects.

  3. Open a Project's child, for example, Task2, in Gantt chart and edit the Scheduled End date field in the fProject Information window.

    Result: The user can successfully edit and save changes in Schedule End date and any other attributes in General Info tab of Task/Phase/Program (with no errors).

20578829

Java Client

Issue: AGILE 9.3.0.2 JAVA CLIENT UNABLE TO LAUNCH THE APPLICATION ERROR SINCE JAVA 7 UP

Root Cause: JRE new security enhancement

Resolution: Add all-permissions attribute in META-INFO

Verification: N/A

20922228

Folders, Files & Attachments

Issue: 'ADD TO TABLE' PRIVILEGE NOT WORKING WITH ACTIVITY AND FILE FOLDER OBJECTS

Root Cause: This is caused by a code defect. The Project object is not taken into consideration for this case.

Resolution: Include the Project object in this case.

Verification:

  1. Log in to Java Client.

  2. Go to Add to Table privilege - Add to Table Items and Add to Table Changes.

  3. Create 2 more privileges. Add to Table File Folders and Add to Table Activity with criteria as "All File Folders" and "All Activities".

  4. Create Modify privilege for Item, Change Order, Activity and File Folder with the Applied To field empty.

  5. Assign the Add to Table privilege and the Modify Privilege to user User12.

  6. User12 has only Discover/Read privilege on Changes, Items, File Folders and Activity - no other privileges.

  7. Log in as user12.

  8. Search and open an Item and navigate to the Attachments tab.

  9. Enable the Add button.

  10. Add Text file.

  11. Try the same with a Change Order and Project.

    Result: The user is able to add files in the Attachments table of all the objects.

3.5 Product Quality Management

21079203

Web Client

Issue: JAVA CLIENT DOES NOT SHOW HAS QUALITY ISSUES INDICATOR WHEN QCR IS ATTACHED

Root Cause: Java Client honors the PSR, but does not honor QCR case, so QCR case does work fine.

Resolution: Improved the logic to support exempt checking for dynamic list.

Verification:

  1. Log in to Java Client as admin.

  2. Create a subclass: Exemption under Specifications.

  3. Create a criteria, CR1, based on subclass Exemption.

  4. Create a dynamic list, DL001, with criteria, CR1.

  5. Go to Classes > Specifications > General Info tab, open attribute, Exemption, set it point to DL001.

  6. Go to Classes > Substance Declarations > Manufacturer Parts, open attribute Exemption, set it point to DL001.

  7. Log in to Web Client as admin.

  8. Create several specifications with Exemption type: ex1,ex2 and ex3.

  9. Create a specification, sp001, and select ex1 and ex2 for sp001.GI.Exemption.

  10. Create a substance declaration, MD001, with sp001, then add a Manufacturer Part, mfp001, to its MPN table. Try to select a value, ex1 for mfp001.exemption, and Save.

    Result: The user can select value successfully.

3.6 Agile PLM Framework

13071753

Software Development Kit

Issue: THE SYNTAX FOR IPRICE.SAVEAS() DOES NOT WORKAS DESCRIBED IN SDK GUIDE

Root Cause: code defect of not handling null value of program attribute of Price object while doing Save As via SDK.

Resolution: Handled null value of program attribute of Price object while doing save as via SDK.

Verification: Create a price object by following code:

IPrice price = (IPrice)sc.session.getObject(IPrice.OBJECT_TYPE, "CONTRACT00001");

IAgileClass subclass = price.getAgileClass();

IAutoNumber[] numSources = subclass.getAutoNumberSources();

String nextNumber = numSources[0].getNextNumber();

ISupplier supplier = (ISupplier)sc.session.getObject(ISupplier.OBJECT_TYPE,"SUP-00003");

Map params = new HashMap();

params.put(PriceConstants.ATT_GENERAL_INFORMATION_NUMBER, nextNumber);

params.put(PriceConstants.ATT_GENERAL_INFORMATION_SUPPLIER, supplier);

params.put(PriceConstants.ATT_GENERAL_INFORMATION_ITEM_NUMBER, "2075700");

params.put(PriceConstants.ATT_GENERAL_INFORMATION_ITEM_REV, "CO-00035");

price.saveAs(price.getAgileClass(), params);

Result: The new Price object is created successfully.

13617191

Folders, Files, & Attachments

Issue: OPENED ZIP FILE ATTACHMENT DOES NOT SHOW LIST OF FILES AFTER FIRST TIME

Root Cause: When the user opens one file in ZIP, the system creates a CMF file and maps to the ZIP file.

Resolution: Skip the creation of the CMF for the ZIP file.

Verification:

  1. Log in to Web Client.

  2. Upload the zip file to admin's user record Attachments tab.

  3. Select the zip file and click on View, or click on File Name link so that the AutoVue Main Window displays the File list contained in the zip file.

  4. Click on a filename in the list of zip files in AutoVue, so that the secondary AutoVue window displays.

  5. Close all of the AutoVue windows and log out and log in.

  6. Select the zip file and click on View or click on File Name link.

    Results: The AutoVue main window displays the zip file containing the file list.

17446509

Web Client

Issue: UNABLE TO SAVE AS PERSONAL SEARCH ONCE SEARCH DEFENITION IS MODIFIED

Root Cause: N/A

Resolution: N/A

Verification:

  1. Log in to Web Client as admin.

  2. Do an Advanced Search: Items > Parts > Title Block.Description > Is Not Null, save it as s1 and put it into Personal Searches.

  3. Run the saved search, S1, then edit the search criteria to: Items > Parts > Title Block.Description > start with > test, run the search.

    Result: Parts that have a description that starts with "test" are returned in search results.

  4. Try to save as updated search.

    Result: The Save As button is enabled and the updated search can be saved to a new one successfully.

17777333

Event Java PX

Issue: SEARCH RETURNS INCONSISTENT RESULTS AND FILTERING BY SUBCLASS DOES NOT WORK

Root Cause: Bug in code: The code does not take the current rev and Site object information when opening files in Object Attachment tab, QuickView, Affected Item, and Redline Attachment tabs.

Resolution: Code fixed by taking the current rev and site information while performing the Open action.

Verification:

  1. Set up the custom PX in Java Client and drop the custom jar to /sdk/extensions/ setup Event Handler for the PX.

  2. Create a new Event - Get File for Items.

  3. Create Event Subscriber for new Event Handler and Get File event.

  4. Set Event Subscriber to Pre trigger type and Execution Mode = Synchronous.

  5. Log in to Web Client to create a Part with an attachment and release on a Change.

  6. Navigate to the Part to get file from the Attachments tab Part's history log correct PX info: item xxx has associated iChange object Cxxx.

  7. Click the change again.

  8. Highlight the Part from the Recently Visited section and click the Quick view to the Part to Get file again.

  9. Refresh the UI and check the Part's History tab.

    Result: item xxx has associated iChange object Cxxx.

17876092

Admin Config Propagation

Issue: REQUIRED SET BACK TO ALLOWED IN CHANGE ORDER WF COMMENTS ATTRIBUTE

Root Cause: We do not support this attributes in 932.

Resolution: Update attribute commentForApprove and commentForReject when doing import workflow.

Verification:

  1. Log in to Java Client of source instance.

  2. Create a new workflow, Test-WF, with status CCB.

  3. Go to the Status tab.

  4. Open the property of CCB status. Ensure that the Comments for Approval attribute and Comments for Rejection attributes are set to Required.

  5. Configure config.xml to include the following workflow:

    <copy><workflow><include><pattern>Test-WF</pattern></include></workflow></copy>

  6. Run acp export source.

  7. Run acp import source target.

  8. Log in to Java Client of the target instance.

  9. Ensure that the Test-WF workflow is imported.

  10. Open the CCB status property.

    Result: The value for attributes Comments for Approval and Comments for Rejection is set to Required.

18045943

User/User Group

Issue: UNABLE TO ADD USERS IN USER GROUPS WHICH HAVE PARENTHESES

Root Cause: N/A

Resolution: N/A

Verification:

  1. Log in to Web Client as admin.

  2. Create a new user: testsri(sr).

  3. Open any User Groups, such as ug001, and go to its Users table.

  4. Click Add, and try to add testsri(sr) to the Users table.

    Results: A user with parentheses in the name, testsri(sr), can be added to the Users table successfully.

18087905

Searches

Issue: WEB CLIENT SHOWS INCORRECT SORT ORDER FOR OBJECT TYPE COLUMN IN QUICK SEARCH

Root Cause: The column, Object Type, was not sorted by dictionary order of its text display.

Resolution: Sort it by dictionary order.

Verification:

  1. Log in to Web Client as admin.

  2. Do a quick search: All > *.

    Result: All objects can be searched out.

  3. Click the column header of the Object Type to sort search results.

    Result: All objects are sorted by object type in Ascending order.

  4. Click the column header of the Object Type again

    Result: All objects are sorted by object type in Descending order.

18145784

Web Client

Issue: ERROR IN THE FRENCH TRANSLATION

Root Cause: Translation issue.

Resolution: Provide new translations.

Verification:

  1. Log in to Web Client with user in French.

  2. Create a Part, P00022, and add mfrs with MFR_001.

  3. Create an ECO, C00017, for P00022.

  4. Go to the Affected items of C00017. Select P00022.

  5. Go to the Manufactures tab and Select Manufacturer Item from the row MFR_001.

  6. Select Undo redline.

    Result: The user gets a popup message to confirm Undo Redlines. The undo button value is translated into the Défaire.

18146283

Java Client

Issue: $USER IS NOT AVAILABLE AS LIST VALUE FOR ADVANCED SEARCH FO CHANGES JAVA CLIENT

Root Cause: This is an enhancement.

Resolution: N/A

Verification:

  1. Log in to Java Client and navigate to Admin ; System Settings ; Dashboard Management.

  2. Create a New Tab and add a Table with advance search having criteria "Change with Cover Page.Change Analyst In $USER"

    Result: $USER value should display in MultiList attributes while configuring Dashboard tabs.

18366643

Admin Config Propagation

Issue: OLD CONFIGURATION IS PROPAGATED INSTEAD OF CHANGED ONE

Root Cause: This is a specific AI tab attribute issue. For this case, when the object id is the same and the class id is different, it picks up the incorrect criteria value.

Resolution: Compare the class id when exporting criteria with AI attributes.

Verification:

  1. Log in to Java Client as admin.

  2. Open the criteria Commodity Prelim_Proto(CUP).

  3. Make sure that the criteria has Affected Items.Source System In [Parts]AGILE as one of the criterias.

  4. ACP export this criteria.

  5. Check the .agl file that is created.

    Result: The .agl file contains the [Parts]AGILE attributes.

18491062

Folders, Files, & Attachments

Issue: 'INFORMATION ONLY' DISPLAYED AS 'AWAITING APPROVAL' ON HOME SCREEN

Root Cause: The Workflow Routing tab did not cover this case

Resolution: Special handle for "All File Folders That I Am An Approver Of"

Verification:

  1. Log in to Web Client.

  2. Create a File Folder object.

  3. Add a file attachment and check in the file attachment.

  4. Select a Routing Slip tab.

  5. Add Approver "user1" and Observer "admin" The Routing Slip tab shows Reviewer: Admin with Action "Information Only" Reviewer: user1 with Action "Awaiting Approval".

  6. Log in as Observer "admin".

    Result: The Workflow Routing tab of the Observer shows "Information Only".

18597947

Averify Issues

Issue: AGIL-00025060 CHECK ON AGILE 933 VERSION OR ABOVE

Root Cause: Test case does NOT cover all the situations.

Resolution: Modify test cases to cover all the situations.

Verification:

Case 1:

  1. Import 935 demo DB.

  2. Run "select change_history_id_seq.nextval from dual;" to check the next sequence id.

  3. Insert data into the change_history table. The data's id is smaller than the next sequence id from step 2.

  4. Run Averify on this user.

    Result: There is no AGIL-00025060 related issues reported in oracle_averify_report.log.

Case 2:

  1. Import 935 demo DB.

  2. Run "select change_history_id_seq.nextval from dual;" to check the next sequence id.

  3. Insert data into change_history table. The data's id is larger than the next sequence id from step 2.

  4. Run Averify on this user.

    Result: AGIL-00025060 related issue such as "AGIL-00025060 : C : CHANGE_HISTORY table has bad data (Table ID:-2099999000 is greater than the Sequence ID -2099999960)" reported in oracle_averify_report.log

18676633

Export

Issue: UNABLE TO EXPORT AN ITEM

Root Cause: We need a special handler for BOM Items without object IDs.

Resolution: Added special handler for Items without object IDs.

Verification:

  1. Create Parts P00001, P00002.

  2. Add a non-existent Part number, P00003, to the BOM tab of P00001.

  3. Add P00002 to the BOM tab of P00001.

  4. Add a blank row to the BOM of P00001.

  5. Create an ECO, C00001, on P00001.

  6. Release the ECO at rev A.

  7. Export the Part at 'A C00001' revision to all the formats (aXML,PDX,csv,xls).

    Result: The export functions properly without any null pointer exceptions. The blank row is exported with default data (Qty, Find Num...) as well.

18842149

Software Development Kit

Issue: HOW TO USE SDK TO GET DATA BY

Root Cause: The SDK query criteria "[CoverPage.Status] In ('$STATUSTYPE.RELEASED'" is not properly built into SQL condition 9224 release.

Resolution: This issue has been fixed by Search Server side code change in latest release.In 9224, the generated SQL for the SDK query condition is: ((CHANGE_P2P3.STATUS = '-17')))). In 934 or latest 935, the generate SQL for the SDK query condition is: ((((CHANGE_P2P3.STATUSTYPE) IN ('3'))))))

Verification:

  1. Create an Advanced Search for ECO.

  2. Set Search Criteria "Change Type" and "Status" as promote .

  3. Execute the following SDK code:

    String strFolderPath = "/Personal Searches";

    String strCriteriaName = "testWS_forAllChange";

    ArrayList arrList = new ArrayList();

    arrList.add("ECO");

    arrList.add("$STATUSTYPE.RELEASED");

    IFolder searchFolder = (IFolder)session.getObject(IFolder.OBJECT_TYPE,strFolderPath);

    IAgileObject agileObject = searchFolder.getChild(strCriteriaName);

    IQuery query = (IQuery)agileObject;

    Object[] objParams = new Object[arrList.size()];

    for(int i=0; i<arrList.size(); i++)

    objParams[i] = arrList.get(i);

    query.setParams(objParams);

    ITable queryTable = query.execute();

  4. Check the Search results.

    Result: The search result is correct.

18999047

SDK Import & Export

Issue: PLM ERROR 60086 - CREATING ORF SUB REQUEST FOR ORF THAT CONTAINS HYPERLINKS

Root Cause: When creating a user, the application does not use the selected currency as the default valURL file is not a real file stored in File Server. When the File Server WS API is called to replicate a non-real file it encounters an exception.

Resolution: If the attachment file type is a URL, then do not call the File Server WS API to replicate attachment.

Verification:

  1. Create a Part named Part1.

  2. Attach URL address to Part1's attachment.

  3. Create a Part named Part2.

  4. Execute the SDK code:

    IItem sourceItem = (IItem) session.getObject(ItemConstants.CLASS_PART, "Part1");IItem destItem = (IItem) session.getObject(ItemConstants.CLASS_PART, "Part2");ITable oldBTAttachmentsTab = sourceItem.getTable(ItemConstants.TABLE_ATTACHMENTS);ITable attachmentsTab = destItem.getTable(ItemConstants.TABLE_ATTACHMENTS);Iterator oldBTAttachmentsItr = oldBTAttachmentsTab.iterator();Map params = new HashMap();while (oldBTAttachmentsItr.hasNext()) {IRow attachment1 = (IRow)oldBTAttachmentsItr.next();params.clear();params.put(CommonConstants.ATT_ATTACHMENTS_CONTENT, attachment1);params.put(CommonConstants.MAKE_DEEP_COPY,Boolean.TRUE);IRow attachment2 = (IRow)attachmentsTab.createRow(params);}

19064118

Administration/Configuration

Issue: SDK QUERY ORA-01722 DUE TO INCORRECT CREATE FROM TEMPLATE ATTRIBUTE TYPE

Root Cause: Need to resolve String To Ids for the attribute Created From Template.

Resolution: Resolve String To Ids for attribute Created From Template.

Verification: Execute query with [General Info.Created From Template] successfully:

For example:

IQuery query = (IQuery)session.createObject(IQuery.OBJECT_TYPE,

"SELECT " +"[General Info.Division],[General Info.Root Parent], "

+"[General Info.Owner],[General Info.Name], "

+"[General Info.Description],[General Info.Status], "

+"[General Info.Schedule Status],[General Info.Workflow], "

+"[General Info.Type] "

+"FROM " +"[Projects] "

+"WHERE " + "( [General Info.Created From Template] == 'HOT - Phase II NPD Template - CORE 2013' ) "

+"AND " +"( [General Info.Division] == 'Belson') "

+"ORDER BY " +"1, 4, 3" );

19080100

Averify Issues

Issue: DUPLICATE AFFECTED ITEMS ADDED TO A CHANGE

Root Cause: AGIL-00075102.sql is added, you could use delete from rev where id not in (select min(id) from rev group by item, change, site).

Resolution: The fix script has been included in AGIL-00075102.sql changed file AGIL-00075102.sql.

Verification:

  1. Create a Part and add several sites to this Part.

  2. Create an MCO, add this Part into the Affected Items tab of the MCO.

  3. Log in to sqlplus as an agile db user, insert bad data with the following SQL statement: insert into rev(id, item, change, site) values($ID,$item_id,$change_id, $site_id); make $site_id is duplicated with existed one in the part.Define Query > Advanced Search Items > Parts Attribute >Title Block Number, equal to P001 >Finish.

  4. Run Averify against the database.

    Result: The Averify Report logs the following error message. AGIL-00075102 : E : REV table has bad data (find duplicate site $site_id in table rev for item $item_id in change. )

19263708

Admin Config Propagation

Issue: ACP RESULTS IN ERRORS WHEN TRANSFERRING XSLT TEMPLATE FOR ACS FORMAT LIBRARY SAP CHANGECAST

Root Cause: This is an ACS Format Library import issue. We do not clean the template data before processing the next object. It causes a null pointer error.

Resolution: Clean the template data before processing th enext library object.

Verification:

  1. Configure the config.xml file as follows:

    <copy>

    <acs_format_library/>

    </copy>

  2. Execute acp export:acp export golden.

  3. ACP import source to target: acp import golden dev

    Result: ACP propagates the ACS Format Library successfully.

19597534

Folders, Files & Attachments

Issue: FILE ADD - DRAG AND DROP OF XML FILE DOES NOT WORK

Root Cause: Drag & Drop is not supported well in IE10 and Firefox in Agile.

Resolution: Fixed code to handle for IE10 and Firefox.

Verification:

  1. Log in to Web Client.

  2. Access an ECO.

  3. Navigate to the Attachments tab.

  4. Click on Add > File so that file upload selector is displayed.

  5. Drag and drop an XML file to the file upload selector.

    Result: The user is able to drag and drop an XML file to the file upload selector and upload the file successfully.

19641654

Software Development

Issue: IPROPERTY.GETVALUE DOESN'T RETRIEVE BASE CLASS OBJECT TYPE

Root Cause: The base class object type of filter is not returned from the server Admin interface.

Resolution: Added special handling code for the Base class object type at SDK level.

Verification:

  1. Log in to Java Client, Admin > System Settings > Agile Content Service > Filters.

  2. Create yo-test-filter1 with object Changes (Base Class).

  3. Compile testmain.java and run it.

  4. Check output of SDK.

    Result: If the object type for filter is base class, the object type gets correctly.

19651886

Web Services

Issue: ADMINMETADATA.GETTABLEMETADATA WS INCORRECTLY REPORTS FIELD AS INTEGER

Root Cause: This is a metadata issue.

Resolution: Run the script to correct the type. Update propertytable set value=3 where parentid=2000000100 and PROPERTYID = 2; Commit;

Verification:

  1. Create a Project. Perform an AdminMetaData WS operation.

  2. Verify that Actual Time (In Days) data type is double.

    Result: Actual Time (In Days) data type is double.

19724751

Standard Reports

Issue: NO SPACE BETWEEN REV AND CHANGE NUMBER IN WHERE USED REPORT WITH MS EXCEL 2010

Root Cause: MS Excel 2010 can not parse space symbol '&nbsp;' but '&#160;'.

Resolution: Special handler for type .xls.

Verification:

  1. Log in to Web Client, run the Where Used Report.

  2. Specify Excel format.

  3. Specify an Item, which is in an assembly's BOM and released by an ECO.

  4. Run the Where Used Report for Level 1 BOM items.

  5. Check outputted Excel file with Microsoft Office Excel 2010 and Notepad++.

    Result: In Excel, there are spaces between Revision and ECO number, like C 24433. In Notepad++, the spaces are shown as &#160.

19819184

Searches

Issue: ITEM SEARCH RESULTS ARE NOT SORTED BY ITEM TYPE

Root Cause: Currently, we only support sorting in the database by the sqlorder clause. Some attributes are stored in the DB with id, and for these attributes, it does not make sense to sort by id. They should be sorted by their values.

Resolution: Added sorting process in memory for list and multi-list type data.

Verification:

  1. Log in to Web Client as admin.

  2. Do an Advanced Search: Items > ClickFormat > Sort result by Attribute: Item Type(Title Block) in Ascending Sort Order, run the search.

    Result: Search results are sorted by Item Type in ascending order correctly.

19842717

Averify Issues

Issue: INCLUDE 18603331 INTO AVERIFYL

Root Cause: No case to handle the situation.

Resolution: Add a new case AGIL-00075103 to handle the situation.

Verification:

  1. On Agile 935 database, create bad data by below SQLs.

    select id from page_two where class in (6159,6367);insert into attachment(id, attachment_number, class) values (112,'AverifyP2Test2', 6367);--Make sure the id not exist in page_two.select id from page_three where class in (6159,6367);insert into attachment(id, attachment_number, class) values (113,'AverifyP3Test1', 6159);--Make sure the id not exist in page_three commit.

  2. Run Averify 1.7.7 against this db user with the following options.

    i. averify.runOption=allii. averify.runOption=modules averify.modules=pcpqmiii. averify.runOption=testcases averify.testcases=AGIL-00075103

  3. Check Averify log and report.

    Result: It shows BUILD SUCCESSFUL in Averify.log. There are no errors in the log. The following error messages are reported in oracle_averify_report.log.AGIL-00075103 : E : PAGE_TWO table has bad data (Missing Default row for class (6159,6367).)AGIL-00075103 : E : PAGE_THREE table has bad data (Missing Default row for class (6159,6367).)

19866821

Web Client

Issue: LABELS OVERLAPPING WHEN TWO COLUMNS DISPLAY ENABLED

Root Cause: Long words are not wrapped, so content is overlapped.

Resolution: Break the long words with CSS:word-break: break-all;word-wrap: break-word;

Verification:

  1. Log in to Java Client. Go to the Preferences and set MultiColumn Display = Two Columns.

  2. Click Save.

  3. Go to Classes > Change Orders > User Interface Tabs > Cover page.

  4. Edit the attribute name with long words: Change Orders.Cover Page.Description of Change to "Description of Changeeeeeeeeeeeeeeeeeeeeeeee"

  5. Click Save.

  6. Log in to Web Client.

  7. Create an ECO.

  8. In Edit mode, check the labels displaying of Description of Changeeeeeeeeeeeeeeeeeeeeeeee.

    Result: The names are automatically shifted different rows ahead of the name fields.

19893735

Web Services

Issue: HOW TO CHANGE STATUS OF DECLARATION VIA WEB SERVICE

Root Cause: In the PG&C module, a Declaration is a routable object that has a workflow. Since Web Services do not consider it as routable object, the error like "MDXXX is not routable" is thrown when GetStatus is invoked.

Resolution: A Declaration should be also a routable object. Need to implement routable interface.

Verification:

  1. Create a Declaration.

  2. Add Workflow to the Declaration object.

  3. Execute Change Status WS method.

  4. Verify that Status should be changed for Declaration successfully through WS.

    Result: Status for Declaration is changed successfully through WS.

19907103

Searches

Issue: ERROR WHEN TRYING TO INCLUDE VERSION LABEL IN RELATIONSHIPS SEARCH FORMAT

Root Cause: File folders attributes with VERSION.*attributes (base id 20000####) were not handled when building select and from list

Resolution: Handle additional VERSION.* attributes

Verification:

  1. Grant read/modify privilege on File Folders.Title Block.Label in Java Client.

  2. Log in to Web Client as admin.

  3. Create a Part, P001, and add a file folder (with label values of 123) into the p001 Relationships tab.

  4. Go to the Advance Search field and do the following search: Items > Parts > Relationships Search >> File folders.

  5. Open Format, Move File folders.TitleBlock.Label to Displayed Fields.

  6. Click the Apply button.

    Result: P001 is returned successfully and the label value shows 123.

19908850

Process Extension

Issue: USER.HASPRIVILEGE(USERCONSTANTS.PRIV_DISCOVER, OBJECT) PROVIDES WRONG RESULT WHE

Root Cause: Currently, the system gets the user context of PX role by default, even if the login user role is wanted.

Resolution: Added a new API to get the correct user context of a specific role for both PX role and login user role.

Verification:

Process Extension:

  1. Make sure the login user has Modify Part Privilege.

  2. Create a Custom PX:

    Internal Custom Action = <check the user privilege using the IUser.hasPrivilege() method>;

    Initiate From = Action Menu;

    Roles = Role_CCB37 (this role does not have Modify Part privilege);

  3. Trigger the custom PX from Action Menu of Part object.

    Expected Result: Since the original user has Modify Part privilege and the assigned PX role does not have Modify Part privilege, it should return the following:user.hasPrivilege(UserConstants.PRIV_PRIV_MODIFY, part) = false;user.hasPrivilege(UserConstants.PRIV_PRIV_MODIFY, part, true) = true;user.hasPrivilege(UserConstants.PRIV_PRIV_MODIFY, part, false) = false;

Event:

  1. Make sure the login user dones't have Modify Part Privilege.

  2. Create a Event handler:

    Event Action = <check the user privilege using the IUser.hasPrivilege() method>;

    Roles = Role_CCB37 (this role has Modify Part privilege);

  3. Configure Event:

    Event Type = Create Object;Object Type = Item;Event Handler = <Event handler in step 2>;Trigger Type = Post;Execution Mode = Synchronous;Error Handing Rule = Continue;

  4. Create a Part to trigger the Event.

  5. Check the Event Monitor.

    Expected Result: Since the original user does not have Modify Part privilege and the assigned PX role has Modify Part privilege, it should return:user.hasPrivilege(UserConstants.PRIV_PRIV_MODIFY, part) = true;user.hasPrivilege(UserConstants.PRIV_PRIV_MODIFY, part, true) = false;user.hasPrivilege(UserConstants.PRIV_PRIV_MODIFY, part, false) = true;

19915218

Import

Issue: IMPORT WITH NO DISCOVERY PRIVILEGE, GIVES A SUCCESS UPDATE MESSAGE

Root Cause: The issue is caused by a privilege error.

Resolution: Use && instead of || between Discovery privilege and Read privilege. affect area: import;

Verification:

  1. Create a source file as follows:

    Number Desc P2.Text02KP00001 Part Desc Test0234

  2. Log in to Java Client as admin.

  3. Create a criteria, cri001: Items.Title Block.Number Starts With KP.

  4. Create a role with modify and read Privilege for Items using above criteria.

  5. Assign this Role along with Import Privilege to a user intg001.

  6. Create an Item KP00001, set Text02 = test.

  7. Log in to Web Client as the user intg001.

  8. Import the source file to update the attribute Parts.Page Two.Text02.

    Result: It displays the result "Items 0(1 rejected,0 ignored)" and the message "Insufficient privilege" in the import log.

20002799

Web Client

Issue: UPDATED/NEWLY ENTERED VALUES ARE NOT SAVED WHEN CREATING AN ECO USING SAVE AS OF

Root Cause: This is caused by Bug 8996384 - FIELD ON CHANGE UPDATED FROM POST JAVA EVENT HANDLER RESET WHEN USING VALIDATE.

Resolution: 9951460: ALL CREATE NEW REQUIRED FIELDS DELETED IF YOU MISS JUST ONE.

Verification:

Precondition: ECO description and reason for change attributes are required

Steps:

  1. Create a Part, p01, and add an attachment.

  2. Create an ECO, c001, against p01 with new values and/or update values of the ECO's Description, Reason for Change and other attributes.

    Example: The ECO's Description value is ECO on the Part with attachment V0Reason for change value is ECO on the Part with attachment V0.

  3. Go to the C001's Action menu > click Save As.

  4. Create a new change and input the new value in the ECO's description and Reason for change like" ECO on the part with attachment V1.0".

    Result: A pop-up window appears that asks if you want to proceed with attachments or proceed without attachments.

  5. Select Proceed with attachments.

  6. Click Save.

  7. ECO created successfully: C002.

    Result: C0002 was saved with Description and Reason for change with "ECO on the part with attachment V1.0".

  8. Open c001, and re-save as c001 to c0003.

  9. Input the new value on ECO description and Reason for change as in "ECO on the part with attachment V2.0".

    Result: The same pop-up window appears with the attachment message: select proceed without attachments.

  10. Click Save.

    Result: Check C003 with Description and Reason for change with "ECO on the part with attachment V2.0""

20046518

Searches

Issue: AGILE 9.3.3 EXPORT DOES NOT CREATE NEW WORKSHEET IN EXCEL FOR ROWS > 65536

Root Cause: Microsoft Excel 2003 can not support more than 65,536 rows. When the customer export file includes more than 65536 rows, Web Client shows an error message.

Resolution: If a customer exports a file that includes more than 65,536 rows, the server creates more sheets in one Excel file, the remainder of records are written in the next sheet.

Verification:

  1. Log in to Web Client as admin.

  2. Import more than 65536 new Parts into the system.

  3. Do a basic search: Item > Parts, run the search.

    Result: All Parts are returned in the search results.

  4. Export search results into an Excel 2010 file by clicking More > Export(xls).

  5. Check search results in the exported file.

    Result: All Parts are displayed in the Excel 2010 file, rows greater than 65536 spill over to new sheets in the same file.

20141781

Standard Reports

Issue: BOM COMPARISON REPORT IS EMPTY AFTER APPLYING HF9.3.2.0.81/9.3.2.0.130

Root Cause: There is still an encoding issue in attribute values of BOM Comparison Report.

Resolution: Read the input stream as UTF-8 encoding.

Verification:

Prerequisites: 1. Ensure that you are running Agile on Windows with locale set to Japanese. 2. Ensure that 933HF90 is patched if you are using 933

  1. Log in to Web Client, create a Manufacturer in Japanese.

  2. Create a Part on the Manufacturer Tab, add a Manufacturer Part, with the Manufacturer from Step 1.

  3. Go to the BOM Comparison Report:

    1. On page 1, select the PDF, select Description on LAYOUT > Format.

    2. On page 2, check AML.3. On page 3, select the Part from Step 2.

  4. Run the report.

    Result: a). The file is not 0 byte.b). The file can be opened correctly.

    c). In the file, Traditional Chinese Manufacturer Name can be shown correctly, instead of garbled characters like "??".

20169521

Administration/Configuration

Issue: WRONG PREFERRED START PAGE IS PRINTED IN USERS CONFIGURATION REPORT

Root Cause: When displaying the value of User.Preference.PreferredStartPage attribute in Java and Web Client, we handle the attribute specially, but do not for user configuration report.

Resolution: Special handle this attribute on the user configuration report.

Verification:

  1. Log in to Web Client.

  2. Open user:administrator and set Notification to Preferred Start Page field and save it.

  3. Execute Users Configuration Report.

  4. Check the report.

    Results: The notification is shown in the Preferred Start Page for user: administrator in Users Configuration Report.

20175093

Application Server

Issue: 9.3.3: USERS ARE UNABLE TO SAVE WORK IN AGILE PLM

Root Cause: common.js function submitFormForMultipleWindows(args, xtraArgs)If SSO is enabled, when Agile times out, the user is not able to extend the session and there is no prompt to notify the user that Agile has timed out, so if user is trying to save the object which is in edit mode, the server will serve a login page. There is syntax error caused by the following JS:responseObject = eval('(' + response.text +')');

Resolution: try{...}catch(e){...} to handle unexpected response.text

Verification:

  1. Log into Web Client in an SSO environment.

  2. Open any object.

  3. Do not execute any actions on Web Client. Wait for 30 minutes, since 25 minutes is the default session timeout for Web Client.

  4. Navigate to Web Client after 30 minutes. Check the console to see if any errors are showing.

    Results: No errors are displaying in the console.

20179869

Web Client

Issue: THE FIELDS OF WHERE USED TAB AND PART NUMBER FIELDS ARE INCONSISTENT

Root Cause: String matching error.

Resolution: Changed the code.

Verification:

  1. Find an assembly Item which is not Preliminary.

  2. Save As a new Item from this assembly Item.

  3. Click the original assembly from Recently Visited.

  4. Click the BOM tab, choose any item and click it.

  5. Go to the child Item's Where Used tab.

  6. Check the columns Item Rev and Item Lifecycle Phase for new assembly.

    Results: Item Rev is empty and Item Lifecycle Phase is Preliminary for the new assembly.

20196326

Software Development Kit

Issue: ISSUE WITH IQUERY EXECUTION FOR ATTRIBUTES CONTAINING DOT

Root Cause: String matching error.

Resolution: Changed the code.

Verification: Execute following Query successfully and correctly:

IQuery query = (IQuery)agileSession.createObject(IQuery.OBJECT_TYPE,"Parts");

query.setCaseSensitive(false);

query.setCriteria("[Manufacturers.Mfr. Name] contains 'm'");

ITable results = query.execute();

System.out.println("Size: " + results.size());

20306808

Web Client

Issue: LAST ROW NOT EDITABLE ON 1080P DISPLAY WHEN THE LIST IS SAME AS WINDOW HEIGHT

Root Cause: If the Y coordinate of the bottom of the edit box exceeds the bottom of the grid table, the edit box is hidden.

Resolution: Do not hide the edit box.

Verification:

  1. Log in to Web Client.

  2. Create a ECO C0001.

  3. Add 9 or more Affected Items in C0001.

  4. On the Affected Items tab, reduce the width of all visible columns in the Affected Item panel, such as Item Number, Item Description, and so on.

  5. Reduce each column until the horizontal scroll bar is not visible.

  6. Ensure that the change has 9 or more Items on it.

  7. Scroll down using the vertical scroll bar until the last Item of Affected Items of C001.

  8. Edit the New Rev Column for the LAST ITEM IN THE LIST.

    Result: The value is editable.

20405743

Web Services Security

Issue: VARMGMT FLOW FAILED DUE TO WEB.XML IN VMSERVICE.WAR IS BROKEN AFTER ENABLE WSS

Root Cause: Linux script did not disable basic authorization when enabling PIP web service security.

Resolution: Modify the Linux script file to copy the correct WSS protected web and WebLogic XML when enabling PIP web-service security.

Verification:

  1. Follow the relevant documentation to run wssconfigurator.sh to enable Agile Web Service Security.

  2. Go to check application.ear/VMService.war/WEB-INF/web.xml and weblogic.xml.

    Result: No <security-constraint> <login-config> <security-role> sections in web.xml, no <security-role-assignment> in weblogic.xml.

20427923

Web Client

Issue: HEADING LINK DOES NOT JUMP TO THE CORRECT POSITION IN FIREFOX

Root Cause: In Firefox and Chrome, <a> tag in <fieldset> share the same space with <fieldset>.

Resolution: Put the <a> in a separate <dl>.

Verification:

  1. Log in to Java Client.

  2. Define multiple heading attributes and text attributes for P2 & P3 For example, Subclass Part:

    Page2 attributes:Page2Heading01text1text2Page2Heading02text3text4text5Page2Heading03text6text7Page3 attributes:Page3Heading01text1text2Page3Heading02text3text4..

  3. Log in to Web Client with Firefox.

  4. Create a Part: P00001 with Part subclass.

  5. Click Page2Heading02 link on Title Block page.

    Result: Jump to the position of Page2Heading02.

  6. Click Page3Heading01 link on Title Block page

    Result: Jump to the position of Page3Heading01.

20456840

Web Services

Issue: WEBSERVICE REQUEST TO GET TABLE META-DATA FAILS WITH EXCEPTION ID 60086

Root Cause: This error is caused by BOM.SITE attribute or other site attribute from different table. The customer did not license Site object and does not use the Site class.

Resolution: Will not return possible values if site is disabled.

Verification:

  1. Create an Item, add a BOM item which has Site.

  2. Disable the Site in Licneses in JAVA Client.

  3. Run the getTableMetadata WS.

  4. Verify that no error was displayed.

    Result: No error was displayed.

20544031

Java Client

Issue: REPACKJAVACLIENTFILES.CMD CANNOT REPACK ALL FILES RELATED OF JAVA CLIENT

Root Cause: Dot not use the jar command correctly.

Resolution: "@JAVA-HOME@\bin\jar" uvfM ..\JavaClient.war *.* corrected to be:"@JAVA-HOME@\bin\jar" uvfM ..\JavaClient.war *

Verification:

  1. Run <Agile_HOME>\Install\bin\ExtractJavaClientFiles.cmd to extract Java Client.

  2. And hotfixes folder with some jar files under the extracted Java Client.

  3. Run <Agile_HOME>\Install\bin\RepackJavaClientFiles.cmd to repack Java Client.

    Results: Can repack all files related of Java Client.

20548073

Averify Issues

Issue: AUT 1.7.6 EXITS DUE TO FALSE CRITICAL ERRORS AGIL-00025060 AND AGIL-00025066

Root Cause: The test case does not cover all the situations.

Resolution: Modify test cases to cover all the situations.

Verification:

AGIL-00025060 Case 1:

  1. Import 935 demo DB.

  2. Run "select change_history_id_seq.nextval from dual;" to check next sequence id.

  3. Insert data into change_history table, data's id is smaller than the next sequence id from step 2.

  4. Run Averify on this user.

    Result: There is no AGIL-00025060 related issues reported in oracle_averify_report.log.

AGIL-00025060 Case 2:

  1. Import 935 demo DB.

  2. Run "select change_history_id_seq.nextval from dual;" to check next sequence id.

  3. Insert data into change_history table, data's id is smaller than the next sequence id from step 2.

  4. Run Averify on this user.

    Result: AGIL-00025060 related issue such as "AGIL-00025060 : C : CHANGE_HISTORY table has bad data (Table ID:-2099999000 is greater than the Sequence ID -2099999960)" reported in oracle_averify_report.log

AGIL-00025066 Case 1:

  1. Import 935 demo DB.

  2. Run "select change_history_id_seq.nextval from dual;" to check next sequence id.

  3. Insert data into change_history table, data's id is smaller than the next sequence id from step 2.

  4. Run Averify on this user.

    Result: There is no AGIL-00025066 related issues reported in oracle_averify_report.log.

AGIL-00025066 Case 2:

  1. Import 935 demo DB.

  2. Run "select change_history_id_seq.nextval from dual;" to check next sequence id.

  3. Insert data into change_history table, data's id is smaller than the next sequence id from step 2.

  4. Run Averify on this user.

    Result: AGIL-00025066 related issue such as "AGIL-00025066 : C : ITEM_HISTORY table has bad data (Table ID:-2099999000 is greater than the Sequence ID -2099999500)" reported in oracle_averify_report.log.

20617259

Admin Config Propagation

Issue: UNABLE TO COPY THE SERVER FILE MANAGER CONFIGURATION TYPE VIA ACP

Root Cause: Miss new jars in class path script.

Resolution: Added new jars to class path script.

Verification:

  1. Configure in ACP as follows

    <copy><server_file_manager><include><pattern>iFS</pattern></include></server_file_manager></copy>

  2. ACP export the property: acp export golden

    Result: ACP Export is successful.

20632630

Software Development Kit

Issue: PXS FAILING AFTER INSTALLING HF 9312.306

Root Cause: A class was missed while rebasing on 9312HF94.

Resolution: Added the class to HF306.

Verification:

  1. In MultiItemCostedBOMReport.war, change config.properties and log4j.properties to point to your local Agile and local tomcat logs folder. Update AgileAPI.jar & pxapi.jar to your Agile version. Put this WAR file under $AGILE_HOME/FileManager/webapps.

  2. Log in to Java Client, configure the email server, create two new users and update their user profiles to have two separate email IDs for which you can view emails.

  3. Configure URL PX to be invoked from the Action menu of Parts class by setting URL format as: http://<tomcat_host:port>/MultiItemCostedBOMReport/Process.

  4. Log in to two separate browsers (pick two different brands, for example, Internet Explorer & Firefox) as two separate users (madaraju, testbhanu respectively).

  5. In both browsers, search for Part 53-000210 and invoke Multi-Item Costed BOM from the Actions menu.

  6. In the pop-up window with the "Multi Item Costed BOM" screen where 53-000210 is shown as default, click Submit in both browsers simultaneously (couple of seconds difference is ok).

    Result: The user receives two emails with the correct report results.

20633730

Admin Config Propagation

Issue: ACP IMPORT ERROR:PRIVILEGE NOT IMPORTED DUE TO ERROR

Root Cause: Root Cause:Similar to 20633655, when migrating default value of list attribute of privilege, need handle specially.

Resolution: Handle specially for default value of list attribute via ACP.

Verification:

  1. Login Java Client of source.

  2. Open List05 on Parts Page Two, set a default value for it.

  3. Create read/modify privilege with List05 in the criteria.

  4. ACP export read/modify privilege in source.

  5. ACP propagates source to target.

  6. Check the privilege in the target.

    Result: The privilege is propagated to target without error message.

20635031

Java Client

Issue: UNABLE TO OPEN ONLINE HELP MANUAL VIA JAVA CLIENT USING JRE 7U71

Root Cause: BasicService bs = (BasicService) ServiceManager.lookup("javax.jnlp.BasicService"); bs.showDocument(new URL(helpURL));We use this code to show the help URL, but in new JREs, for example, JRE7u79 JRE7u71 JRE8, it does not work.

Resolution: String helpUrlEncoded = new URI(helpUrl).toASCIIString();Used thiscode to encode the non ASCII characters in the help URL.

Verification:

Precondition: Java Version:1.8.0_45

  1. Log in to Java Client.

  2. Go to Admin > Setting > Server Setting > Locations Online Help Manual URL:

  3. Input http://www.oracle.com/technology/??/ agile.html.

  4. Save.

  5. Click Help->Manual Results:IE can lunch the link: https://www.oracle.com/technology/%E6%96%87%E 6%9B%B8/agile.html

  6. Go to the product index.

    Result: The user can find related document.

20649007

Import

Issue: ERROR WHILE IMPORTING THE SMALL NUMERIC VALUES

Root Cause: Numbers like 0.0005, 0.00001, and so on are formatted as 0.00050 or 0.000010 by the BigDecimal tool class. This adds one more zero and the scale length is not as expected.

Resolution: Use # of NumberFormat to remove the last zero of the decimal.

Verification:

  1. Log in to Java Client.

  2. Open Numeric01 on Items Page Two, change the Scale to 4.

  3. Create a source file and enter a value between 0.0001 and 0.0009 for the numeric attribute.

  4. Click Import under Tools & Settings and select the source file.

  5. Specify file content Items > Item only.

  6. Select Content options:

    1. Data Mapping > Use Currently defined mapping definition.

    2. Data Transformation > No transformations are necessary.

    3. Redline Options > Updates do not require redlining.

  7. Do required mapping.

  8. Click Validate button.

    Result: There is no message for scale violation.

20712219

Averify Issues

Issue: AGIL-00025154 FOR VERSIONS LOWER THAN A932

Root Cause: Prior to 932, there is no criteria for the Create from Template privilege. Since 932, the related criteria is added into system.

Resolution: Modify the AGIL-00025154 case to exclude the error message before 932.

Verification:

Case 1:

  1. Import Agile 9312 dbsetup or lower version dump file.

  2. Run Averify 1.7.7 against this database.

  3. Check if th following two AGIL-00025154 errors were reported in the oracle_averify_report.log. AGIL-00025154 : E : ADMINMSATT table has bad data (Missing adminmsatt data reference at nodetable id 32705.Java Client may show blank screen.) AGIL-00025154 : E : ADMINMSATT table has bad data (Missing adminmsatt data reference at nodetable id 2000007917.Java Client may show blank screen.)

    Result: The specific two AGIL-00025154 errors were not reported on the Agile database versions lower than 932.

Case 2:

  1. Create a DB user and import a Agile 9312 or prior version dump file.

  2. Log in to sqlplus as this user, get aprivilege's id from nodetable asfollows:

    select id from nodetable where parentid=12075;

  3. Delete reference data in ADMINMSATT table using the following SQL:

    delete from adminmsatt where parentid=xxxx (xxx is the ID selected from step 2) commit;

  4. Run Averify 1.7.7 with run.Option=all against this db user.

    Result: The following error is reported in oracle_averify_report.log AGIL-00025154 : E : ADMINMSATT table has bad data (Missing adminmsatt data reference at nodetable id xxxx. Java Client may show blank screen.)

20753351

Import

Issue: THE USER'S PASSWORD CHANGE IS NOT SUPPORTED APPEARS ON IMPORT EVEN THOUGH NOT ATTEMPTED

Root Cause: When the pwd attribute is not mapped, it should not throw an exception.

Resolution: Check whether the pwd attribute is mapped before throwing an exception.

Verification:

  1. Log in to Java Client as admin user.

  2. Create a user ImpUser1.

  3. Click Tools > Import.

  4. Click Import Preferences, and confirm that Blank Data Action is set to Overwrite Data.

  5. Select a file with the user ImpUser1, and click Next.

  6. Specify file content User > User only, and click Next.

  7. Select Define attribute mapping in the next step, and click Next.

  8. Define the mapping for the attributes except Login Password and Approval Password.

  9. Click the Import button.

    Results: The user is imported without the message "For security, the user's password change is not supported by import functionality." in the Import Log.

20759560

Import

Issue: ITEM NUMBER WITH LOWER CASE IS NOT IMPORTED THROUGH IMPORT

Root Cause: To support upper/lower/mixed case, the method, createRealObjNumberCollection, of super class BatchHandler.java should be overwritten, but item/mfr/mfr part handler does not overwrite it.

Resolution: Overwrite the method, createRealObjNumberCollection, to support upper/lower/mixed case for creating item/mfr/mfr part.

Verification:

  1. Prepare a data source file to import. Input the value for Manufacturer Part Number using both lowercase and uppercase.

  2. Log in to Web Client, and run Import.

  3. Select the file created in Step 1 for Import File.

  4. On the Specify File Content screen, select Manufacturer Part | Manufacturer Part only.

  5. Define the attribute mapping.

  6. Run Import. Check the imported Manufacturer Part.

    Results: The Manufacturer Part Number is created in its original case, instead of all upper case.

20760803

Web Client

Issue: TABLE WITH MERGED CELL COPIED FROM MS WORD GETS CORRUPTED IN LARGE TEXT FIELD

Root Cause: The HTML attribute 'colspan' on 'td' of table is not allowed.

Resolution: Allow attribute 'colspan' on 'td' of table.

Verification:

  1. Create a Microsoft Document with a table with merged cells.

  2. Copy and paste to a large text field in Web Client.

  3. Check the copied table.

    Results: The borders are copied properly.

20776093

Software Development Kit

Issue: API "AGILESESSIONFACTORY.REFRESHINSTANCE(URL)" THROWS OUT OF MEMORY ERROR

Root Cause: The SDK client always creates a new NetworkClassLoader instance even for the same cluster node when calling AgileSessionFactory.refreshSessionEx. The class loader instance is held by a WebLogic thread, and cannot be released. After many calls, too many class loader instanced eat all the PermSpace memory. That cause OOM.

Resolution: Only create one class loader instance for each cluster node and cache it. Next time when we try to get class loader for the same cluster node, try to get it from cache first.

Verification:

  1. Set up the Cluster server.

  2. Create Agile session more than 50 times via AgileSessionFactory.refreshInstance(?). >>>

    AgileSessionFactory factory =AgileSessionFactory.refreshInstance(URL);HashMap params = new HashMap();params.put(AgileSessionFactory.USERNAME, USERNAME);params.put(AgileSessionFactory.PASSWORD, PASSWORD);IAgileSession session =factory.createSession(params);

  3. Create Agile session more than 50 times viaAgileSessionFactory.refreshInstanceEx(?). >>>

    HashMap params = new HashMap();params.put(AgileSessionFactory.URL, URL);params.put(AgileSessionFactory.USERNAME,USERNAME);params.put(AgileSessionFactory.PASSWORD,PASSWORD);AgileSessionFactory factory =AgileSessionFactory.refreshInstanceEx(params);session = factory.createSession(params);

  4. Create Agile session more than 50 times via AgileSessionFactory.refreshSessionEx(?). >>>

    HashMap params = new HashMap();params.put(AgileSessionFactory.URL, URL);params.put(AgileSessionFactory.USERNAME,USERNAME);params.put(AgileSessionFactory.PASSWORD,PASSWORD);AgileSessionFactory factory =AgileSessionFactory.getInstanceEx(params);session = factory.refreshSessionEx(params);

    Result: There is no Perm Gen out of memory issue and the Agile session is created successfully.

20801980

Import

Issue: FATAL EXCEPTION ON IMPORTING USER GROUP IF BLANK DATA ACTION IS SET TO OVERRIDE

Root Cause: null point exception

Resolution: When the attribute, Max Num of Named Users, is mapped and the Blank Data Action is set to Overwrite Data, but the source file does not provide a value for it, throw a warning message.

Verification:

  1. Log in to Web Client.

  2. Create a User Group, UG0001.

  3. Prepare a source file with the following data:

    User Group Name Global/Personal User Name Max Num of Named Users

    UG0001 Global User0001

  4. Click Tools and Settings > Import, select the file created above.

  5. Go to Preferences, and make sure that Blank Data Action is set to "Overwrite Data".

  6. In the Specify File Content step, select User Group > Users.

  7. Define mapping for the required fields and Max Num of Named Users.

  8. Click Import button, and check the Import Log.

    Result: The user is imported to the user group with a warning message in the Import Log.

20810775

Averify Issues

Issue: AVERIFY FIX: AFTER RUNNING AUT FROM 9.2.1.4 TO 9.3.3 API NAME HAS DUPLICATES

Root Cause: There should be a unique api name for node with objtype (13,21,111,24,22,106,205). In the customer's env, there are duplicate api names.

Resolution: Change the test case in latest 9.3.4 to handle it differently to avoid the error.

Verification:

  1. Create a new listentry on Country List in Java Client.

  2. Edit data on nodetable. Make two node(objtype in 13,21,111,24,22,106,205) have duplicate apinames.

  3. Run Averify1770 on the DB user.

  4. In oracle_averify_report.log, we should see logs below:

    AGIL-000155026 : E : NODETABLE table has bad data (Duplicate API name xxxx in same parent node 3642 with same objtype xxx.)

20824408

Folders, Files, and Attachments

Issue: INTERNET EXPLORER 10 DOES NOT ALLOW MULTIPLE FILES DOWNLOAD ON AGILE 9.3.3

Root Cause: Code-side issue.

Resolution: Fixed code.

Verification:

  1. Log in to Web Client on IE10.

  2. Access a BO Attachments tab.

  3. Add multiple files or multiple files in a single folder.

  4. Select multiple files or multiple files in a single folder and click on Get or Quick View the BO, select multiple files or multiple files in a single folder and click on Get.

    Result: The file is downloaded successfully as download.zip.

20860504

Web Services

Issue: EC CONNECTION LOGIN WAS NOT SUCCESSFUL

Root Cause: Oracle JAXP document builder instance which doesn't support the reset feature, is loaded and created.

Resolution: Specify to use apache xerces JAXP document builder implementation.

Verification:

  1. Create an object.

  2. Add an Attachment to the new object through AddAttachment WS.

  3. Download the attachment through Get Attachment WS.

  4. Verify that there was no connection failure when attachment was added and downloaded.

    Result: There was no connection failure when attachment was added and downloaded.

20894125

Internationalization

Issue: [JP TRANSLATION]NOTIFICATION MAIL TITLE URGENT INCLUDED IN JAPANESE ENVIRONMENT

Root Cause: All cap words like "URGENT" are reserved for technical use (for example, variable names) and are therefore not processed by our translation tools.

Resolution: Modified "URGENT" in the property file to lowercase, and moved to I18N team to translate the Urgent string.

Verification:

  1. Log in to Agile with a Japanese user.

  2. Create Change Order, C00269.

  3. Press Next Statu.

  4. To : Japanese user .

  5. Check Send notification as urgent.

  6. Click Finish.

  7. Check if the user received 2 mails with the title "URGENT" included in Japanese mail.

    Result: The word urgent is translated into Japanese.

20985409

Searches

Issue: RESOURCE UTILIZATION REPORT, CHANGE FIELD DOES NOT WORK

Root Cause: This is caused by a lack of the Days Effort process method.

Resolution: Added the Days Effort process method.

Verification:

  1. Log in to Web Client.

  2. Go to any Program.

  3. Go to the Team tab.

  4. Click Add.

  5. In the Add resource window, add a member, then from Actions menu, select the Project Resource Utilization option from Reports and Analytics.

  6. In the field Display Values by the default is Percent Utilization.

  7. Change value from Percent Utilization to Days Effort, click Refresh.

    Result: The Days Effort Chart gets loaded in the Project Resource Utilization Report.

21105883

DB Upgrade/AUT

Issue: AUT UPGRADE TOOL CAUSED DATA LOSS

Root Cause: When upgrading from one schema to another, the index named FILES_CONTENT_IDX on the files table is rebuilt - backup files table, delete the original files table and copy the backup table to files table, when delete action is executed, FILES_DEL_TRIGGER is triggered, which deletes related records corresponding to the files table.

Resolution: Disable the trigger FILES_DEL_TRIGGER when deleting the original files table, and enable it after copying the backup table to the files table.

Verification:

  1. Import the 934 presales DB dump to schema demofrom.

  2. Check the number of records in table file_info.

    Result: There are 5583 records, no records had data loss.

  3. Use AUT1770 to upgrade from 934 to 935 (schema demofrom to schema demoto).

  4. Check the number of records in the table file_info in schema demoto.

    Result: There are 5583 records, no records had data loss.

21117940

Searches

Issue: WILDCARD SEARCH WITH "LIKE" OPERATER DOES NOT WORK IN MULTIBYTE CHARACTERS

Root Cause: A fix to a previous bug removes trailing asterisk from user input.

Resolution: Skip the removal of trailing asterisk when the operator is Like.

Verification:

  1. Log in to Web Client as admin.

  2. Create a Part: P001 with a description using Chinese characters.

  3. Do an Advanced Search: Items > Parts > Title Block.Description > Like > [Description from Step 2]*, and run the search. (Append a trailing asterisk to the description.)

    Result: P001 can be searched out.

21118625

Internationalization

Issue: WPTG_TSN:T9N:LOC-MSG:3:AGILE:4-292677:NON STANDARD LEGAL TEXT:PLM-AGILE-9.3.5-D1

Root Cause: Copyright information does not comply with Oracle's latest guidelines.

Resolution: Revised related copyright information.

Verification:

Case 1:

  1. Log in to Web Client as admin.

  2. Go to Help > About.

  3. Check copyright information on the About and Login pages.

    Result: It shows: "Copyright © 1995, 2015, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. "

Case 2:

  1. Log in to Java Client.

  2. Go to Help > About.

  3. Check the copyright information.

    Result: It shows: "Copyright © 1995, 2015, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners."

Case 3:

  1. Log in to Web Client as admin.

  2. Create Program object.

  3. Open Gantt > Help > About.

  4. Check the copyright information.

    Result: It shows: "Copyright © 1995, 2015, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners."

21248768

Administration/Configuration

Issue: RFQ NUMBER FIELD DOES NOT CHECK CHARSET VALUES

Root Cause: This is a code defect. When creating RFQ object, we do not check charset.

Resolution: Check charset when creating an RFQ object.

Verification:

  1. Log in to Java Client. Go to Admin > Data Settings > Character Sets, create a Character set as follows: Name: Special, All Characters with Space Valid Character Set: ^s^p^^ABCDEFGHIJKLMNOPQRSTUVWXYZ_-?/1234567890

  2. Go to Classes > Requests for Quote > Cover Page attribute, change the RFQ Number to use the new character set.

  3. Log in to Web Client, create a Sourcing Project.

  4. Add Items to the Sourcing Project and change the Status to open.

  5. Create RFQ with Number: RFQ00942 @#$*.

    Result: The system should not accept that RFQ Number by throwing the following message. Only "Special, All Characters with Space" values are allowed for RFQ Number.

  6. Create RFQ with Number: AZ^ _-?/1234567890.

    Result: The RFQ is created successfully.

21389523

Admin Config Propagation

Issue: ACP IMPORT ON GLOBAL SEARCH ENDS IN ERROR: STRING INDEX OUT OF RANGE: -1

Root Cause: $USER is not handled.

Resolution: Need to handle $USER specially.

Verification:

  1. Log in to source instance.

  2. Create searches with $USER in criteria.

  3. Use Save As to save the searches to Global Searches folder.

  4. Configure the config.xml file as below:

    <copy>

    <searches/>

    </copy>

  5. ACP export source instance.

  6. ACP import source to target instance.

    Result: Global searches are imported to the target instance successfully without the error message "ERROR: String index out of range: -1"

21617418

DB Upgrade/AUT

Issue: UNABLE TO SORT/ORDER LARGETEXT ATTRIBUTES AFTER THE UPGRADE

Root Cause: When there are newly created subclasses prior to 934, there will be no records in tableinfo table for large text attributes after upgrading to 934.

Resolution: Add records in tableinfo table for large text attributes when upgrading from 933 to 934.

Verification:

  1. On Agile 933 environment, create a new subclass for Parts/Changes.

  2. Use AUT1770 to upgrade the DB user.

  3. Connect the DB user to Agile 935 application and sort these LargeText attributes.

    Result: LargeText attributes can be sorted.

21876123

Application Server

Issue: CLUSTER INSTALL MODE NOT DISPLAYING PANEL APPLICATION SERVER INFORMATION

Root Cause: The application installer uses the hostname and domainname commands to create the default hostname/domainname for the configuration. The panel 'Application Server Information' allows this to be overridden at install time before the configuration is generated, but the Panel Application Server Information' is being displayed in the Standalone case, but not in the 'Cluster' case.

Resolution: Updated the installer condition to display the Application Server Information panel whenever the Application Server and/or File Manager component is selected.

Verification:

  1. Launch Agile935 Installer.

  2. Choose Cluster Install Mode.

  3. Check Application Server Information Panel.

    Result: Display after this panel.

21920836

Administration/Configuration

Issue: CAN NOT REFRESH THE VISIBILITY OF THE ATTRIBUTE RIGHT NOW AFTER CHANGING THE PART

Root Cause: Attributes of Title Block, Page Two did not change with the Part type change when edited in the Item. The old cache has not been invalidated.

Resolution: When Part type is changed, save the new subclass and return back to view model with attributes refreshed. Old cache is invalidated.

Verification:

  1. Log in to Java Client as admin.

  2. Go to Admin > Classes > Parts, create two subclasses, SUBPART01 and SUBPART02.

  3. Go to SUBPART01 > Title block, make sure Size is visible. Go to its Page Two, enable P2.Text01, and make sure P2.Text02 is invisible. Go to its Page Three, enable Multilist01, and make sure P3.Multilist02 is invisible.

  4. Go to SUBPART02 > Title block, disable attribute Size. Go to its Page Two, enable P2.Text02, and make sure P2.Text01 is invisible. Go to its Page three, enable Multilist02, and make sure P3.Multilist01 is invisible.

  5. Log in to Web Client as admin.

  6. Create a Part, sp01_01 with SUBPART01 type, check its attributes.

    Result: Title block.Size, P2.Text01 and P3.Multilist01 are all displayed for sp01_01.

  7. Change sp01_01 type to SUBPART02, save it. Refresh the page.

    Result: Title block.size, P2.Text01 and P3.Multilist01 are not visible. P2.Text02 and P3.Multilist02 are displayed.

3.7 Autovue for PLM

20326877

Electro-Mechanical Pro Int

Issue: AUTOVUE AND CLICK ANALYSIS-->COMPARE THE DOCUMENT VERSIONS DROPDOWN LIST SHOWS

Root Cause: N/A

Resolution: N/A

Verification:

  1. Log in to A9 Web Client.

  2. Create an Item and navigate to the Attachments tab to add a file.

  3. Create an ECO, ECO1, for the Item with Rev as A.

  4. Bump up the folder version to 3 for Item with Rev A and release ECO1.

  5. Create another ECO, ECO2, for Item with rev as B.

  6. Bump up the folder version to 5 for Item with Rev B and release the ECO2.

  7. View the file of version 5 in Item rev B Attachments tab, so that the AutoVue window is displayed.

  8. Click on Analysis > Compare.

  9. Make sure that the Document versions box is checked.

  10. Click on the dropdown list for document versions and versions.

    Result: The dropdown list the version 3 Rev B, version 4 Rev B.

20456036

2D Pro Integration

Issue: SAVE MARKUP NOT WORKING, MISSING NAME AND DESCRIPTION IN SAVE DIALOG

Root Cause: Code defect.

Resolution: Fixed code.

Verification:

  1. Log in to A9 Web Client.

  2. Create an Item.

  3. Navigate to the Attachments tab and add a file.

  4. Create an ECO from the Actions menu of Item.

  5. Navigate to the Affected Items tab of ECO.

  6. Select the Item in Affected Items tab and switch to the Attachments table.

  7. Select the file and click on Redline, so that the file is loaded in viewer in markup mode.

  8. Click on Markup > New and then create a markup entity and click on Save.

    Result: The Name and Description fields are displayed on the Save Markup File As window. When the user enters the Name and Description and clicks on OK, the changes are saved. This is also verified for File Folder, Design and ECR objects.

20456184

2D Pro Integration

Issue: AGILE SEARCH,AGILE BROWSE,NOT WORKING FOR COMPARE

Root Cause: Code defect.

Resolution: Fixed code.

Verification:

Scenario 1:

  1. Log in to Web Client or Java Client.

  2. Create an Item, P1, and add attachments and Bookmark the object.

  3. Create an Item, P2, and add attachments and Bookmark the object.

  4. Select the file in P1's Attachments tab and click on View.

  5. In Auto Vue, click on Analysis > Compare.

  6. In the File Open window, click on "Agile"

    Result: All the bookmarked objects are listed in File Open window and double click on the Bookmarked object displays the files list and on selecting the similar file type the files are compared.

Scenario 2:

  1. Log in to Web Client or Java Client.

  2. Create an Item, P1, and add attachments and-Bookmark the object.

  3. Create an Item, P2, and add attachments and Bookmark the object.

  4. Select the file in P1's Attachments tab and click on View.

  5. In Auto Vue, click on Analysis > Compare.

  6. In the File Open window, click on Search Agile with the search parameter <Item 2> and click on Search.

    Result: The BOs are displayed based on search criteria. Click on the object so that all the files added to that object are listed in the File Open window and on selecting the similar file type the files are compared.

3.8 Agile Engineering Collaboration

20379361

EC Services

Issue: DRAWING DESIGN OBJECT STRUCTURE IS NOT CORRECT FOR INCREMENT SAVE

Root Cause: We can not reproduce the issue. All previous versions were copied to structure table, not latest version when server side does checkout.

Resolution: Only the latest structure is copied to the structure table and make sure that there is no version 1 design in this case.

Verification:

  1. Create a Part model and save it locally.

  2. Create a drawing model against the Part model and save it to Agile.

  3. In Agile > Preference tab, set "Save Option for Modified" with value "Check In" and save preference setting.

  4. Click Agile > Save preview and save the drawing with Part to Agile.

  5. Go to Agile > Preference tab, set "Save Option for Modified" with value "Increment" and save preference setting.

  6. Click Agile > Save preview again. Check out both components and click Continue button to save them to Agile.

    Result: In save result, the version for drawing and part should be 3.

  7. Log in to Agile Web Client and check the design object for part and drawing.

    Result: There should be one row for the part design, the version should be version 2.

20628818

EC Services

Issue: PUBLISH ERRORS - "EJB EXCEPTION"

Root Cause: The version number was shared among threads.

Resolution: Implement version number with a thread local variable.

Verification: QA can not reproduce it due to lack of specific settings.

20838691

EC Services

Issue: LOAD PREVIEW SLOW USING LOAD DRAWING OPTION

Root Cause: The load preview step performance issue is caused by redundant calls between MCAD client & Agile server and due to chattiness between Agile Server and the database in resolving multi-level recursive design structure data.

Resolution: The following steps have been taken to improve the Load To CAD performance:

  1. Client Server call sequence has been optimized to load the design efficiently without preview and with Load Preview (configurable in MCAD client).

  2. Removed chattiness by moving structure resolution into DB process and also load objects in bulk.

Verification: Overall ~45% performance improvement reported for Load to CAD use case without the Load Preview window. Tested with several different size assemblies and confirmed this improvement.

21368122

EC Services

Issue: PART FAMILY INSTANCE LINKED ITEMS ARE REMOVED FROM BOM TAB BY TRANSFER

Root Cause: There are NullPointException and IndexOutofArrayBound errors.

Resolution: Before using the Java object reference, check if it is null or not.

Verification:

  1. Launch Solidworks, download and open below test drawing or create a drawing with balloons using the following instructions.

    Test drawing: ftp://agile@slc03syl.us.oracle.com/QA/Rico/ballooning.zip

    Instructions how to create this feature:

    https://beehiveonline.oracle.com/teamcollab/wiki/Agile+Integration+Development+Partner+xPLM:kb_solidworks_ballooning

  2. Save the Drawing to Agile by clicking Agile > Save Preview.

  3. In Agile Save Preview, create and assign Items for each component.

  4. Click Continue and save successfully.

  5. Check the BOM rows of the assembly design linked Item > BOM published correctly including part family instance linked Items.

  6. Back to MCAD Connector and click Agile > Transfer BOM find numbers.

  7. Go to Agile Web Client and refresh it (refresh button).

  8. In the Web Client, check the BOM structure.

    Result: Transfer BOM find numbers does not remove the BOM Items linked with part family instance.

21604386

EC Services

Issue: NPE EXCEPTION AFTER REDLINE BOM BY MANUALLY ADD

Root Cause: The object is null when it is referenced.

Resolution: Add a null check before using the reference to an object.

Verification:

  1. Launch CAD Tool and connect to Agile.

  2. Create one assembly file, assem1, and save locally.

  3. Save to Agile with assigned Design1 version 1, Item1 and ECO1.

  4. Open Affected Items tab of ECO1 from Agile Web Client.

  5. Redline BOM table of Item1, manually create and add one new BOM Item, Item2, from the Web Client.

  6. Go back to the CAD Tool and click Save Preview again.

  7. Highlight the row and click Publish to Item from the right-click menu.

    Result: Publish Success without error.

  8. Highlight the row and check out.

  9. Click Continue to save to Agile.

    Result: Save Success without error.

21663392

EC Services

Issue: REDLINE FLAG DOES NOT DISPLAY IN CHANGE AI TABLE WHEN DELETING MODEL FROM ASSEMBLY

Root Cause: The logic to check BOM redline data for flag updates has a defect and is missing some scenarios.

Resolution: Improved the logic.

Verification:

  1. Create an Assembly, ASM001, with one child Part, PART001, as follows:

    ASM001 - v1|--PART001(QTY = 1)

  2. Save the ASM and all its components into PLM with design and Item assigned.

  3. Update the ASM structure as below:

    ASM001 - v2

    |--PART001(QTY = 0)

  4. Click Save Preview, assign an ECO1 for the assembly and save to Agile.

  5. Check the redline BOM table of ECO1.

    Result: In the ECO1.AI table, the Item of ASM001 displays as "Has been redlined".

21689441

EC Services

Issue: DIFFERENT REDLINE INFO WHEN NO UPDATE ON BOM ITEM QTY WITH MULTI ECOS

Root Cause: The logic of prepareDataForPublishBOM() has a defect if the same item is redlined via multiple changes.

Resolution: Adopt the same behavior as 933. Delete the repetitive items if they do not exist in the current redline.

Verification:

  1. Launch CAD Tool and connect to Agile.

  2. Create ASSM001.SLDASM as follows and click Save Preview:

    ASSM001 - v1

    |-- PART001(qty=1)

  3. Click Save As to assign design numbers and Item numbers on them.

  4. Assign new Change, ECO1, on ASSM001 row.

  5. Click Continue to save to Agile.

  6. No Update on ASSM001.

  7. Click Save Preview.

  8. Highlight the ASSM001 row and check out.

  9. Assign another new change ECO2 on ASSM001 row.

  10. Click Continue to save to Agile.

  11. Release ECO1 from Agile Web Client.

  12. Check the Redline BOM table of ECO2. Now there are 2 rows for PART001, one is shown as without redline with qty 1.0, another one is shown as redline added with qty 1.0. There is NO warning message for conflicting with a released change when switch to AI tab of ECO2.

  13. Go back to the CAD Tool.

  14. Click Save Preview.

  15. Highlight the ASSM001 row and check out.

  16. Click Continue to save to Agile.

  17. Check the Redline BOM table of ECO2.

    Result: There are two rows for PART001. One row is shown as redline deleted with qty 1.0, another row is shown as redline added with qty 1.0.

21689497

EC Services

Issue: DIFFERENT REDLINE INFO WHEN UPDATING BOM QTY ON ECO2 AFTER RELEASE ECO1

Root Cause: The logic of prepareDataForPublishBOM() has a defect if the same item is redlined via multiple changes.

Resolution: Adopt the same behavior as 933. Delete the repetitive items if they do not exist in the current redline.

Verification:

  1. Launch CAD Tool and connect to Agile.

  2. Create ASSM001.SLDASM as below and click Save Preview

    ASSM001 - v1|-- PART003(qty=1)

  3. Click Save As to assign design numbers and Item numbers on them.

  4. Assign new Change, ECO1, on ASSM001 row.

  5. Click Continue to save to Agile.

  6. No Update on ASSM001.

  7. Click Save Preview.

  8. Highlight the ASSM001 row and check out.

  9. Assign another new Change, ECO2, on ASSM001 row.

  10. Click Continue to save to Agile.

  11. Release ECO1 from Agile Web Client.

  12. Check the Redline BOM table of ECO2 - now there are 2 rows for PART001, one is shown as without redline with qty 1.0, another one is shown as redline added with qty 1.0. There is NO warning message for conflicting with a released change when switch to AI tab of ECO2.

  13. Go back to CAD Tool and update ASSM001 as below

    ASSM001 - v3|-- PART003(qty=2)

  14. Click Save Preview.

  15. Highlight the ASSM001 row and check out.

  16. Click Continue to save to Agile.

  17. Check the Redline BOM table of ECO2.

    Result: There are totally two rows for PART003, one row is shown as redline deleted with qty 1.0, another row is shown as redline added with qty 2.0.

21695618

EC Services

Issue: THE REDLINE BOM FLAG IS MISSING WHEN DELETING THE COMPONENT IN SAME ECO

Root Cause: The logic to check the BOM redline data for a flag update has a defect and is missing some scenarios.

Resolution: Improved the logic.

Verification:

  1. . Create one assembly assm1.sldasm as below

    assm1 - v1

    |-- part1(qty=1)

    |-- part2(qty=1)

  2. Click Agile save preview, highlight all components and click save as button to generate design and item numbers.

  3. Highlight the row of the assembly, assign a change ECO1 for the assembly then click continue button to save to Agile.

  4. Check design structure, BOM structure and ECO redline bom table from Agile web client.

    Result: Design structure, BOM Structure and ECO Redline BOM table should display correctly, the item for part1.sldprt and part2.sldprt should display with Qty 1 (redline added).

  5. In CAD system, update assembly as follows:

    assm1 - v2

    |-- part1(qty=0)

    |-- part2(qty=1)

  6. Click Agile save preview, check out the assembly and then click Continue button.

  7. Check design structure, BOM structure and eco redline bom table from Agile web client.

    Result: It displays the redline BOM flag for the Item of the assembly; Design structure, BOM Structure and ECO Redline BOM table are displayed correctly, the Item for part1.sldprt is not displayed. The Item for part2.sldprt is displayed with Qty 1 (redline added).

21744374

EC Services

Issue: REDLINE FOR BOM IS NOT CORRECT WHEN REDUCING AND ADDING BACK AGAIN

Root Cause: The BOM redline delete via MCAD tool in A934 has a defect and leads to the current issue.

Resolution: Correct the logic of BOM redline delete.

Verification:

  1. Create one assembly with two components.

  2. Save the assembly to Agile with Item assigned.

  3. In CAD system, remove one of the components, for example, part1.sldprt.

  4. Click Agile Save Preview again, assign a change for the assembly and save it to Agile with version 2.

  5. In CAD system, add the component to the assembly again.

  6. Click Agile Save Preview, check out all files and click continue to save them to Agile with version 3.

  7. Log in to Agile Web Client, check the design and BOM structure.

    Result: Check the Redline BOM table for the change.

  8. Check the Redline BOM table for the change.

    Result: Check the Redline BOM table for the change.

21744382

EC Services

Issue: NO REDLINE ON BOM QTY ALTHOUGH ASSEMBLY HAS THE 'HAS BEEN REDLINED' FLAG

Root Cause: The BOM batch redline logic serving for MCAD tool in A934 has a defect and leads to the current issues.

Resolution: Add the missing logic.

Verification:

  1. Launch the CAD Tool and connect to Agile.

  2. Create Assem2.SLDASM with the following structure:

    Assem2.SLDASM

    |-Assem1.SLDASM(qty=1)

    |- Part1.SLDPRT(qty=2)

  3. Save them to Agile with linked Items.

  4. Add Part1.SLDPRT into Assem2.SLDASM - now Assem2.SLDASM has one Part1.SLDPRT.

  5. Open Assem1.SLDASM.

  6. Delete one Part1.SLDPRT from Assem1.SLDASM - now Assem1.SLDASM has one Part1.SLDPRT.

  7. Now the updated structure is as follows:

    Assem2.SLDASM

    |-Assem1.SLDASM(qty=1)

    |-Part1.SLDPRT (qty=1)

    |-Part1.SLDPRT (qty=1)

  8. Save above all locally.

  9. Click Save Preview.

  10. Highlight 2 rows, Assem2.SLDASM and Assem1.SLDASM.

  11. Create one new change ECO1 and assign to Assem2.SLDASM and Assem1.SLDASM.

  12. Click Continue to save to Agile.

  13. Open the ECO1 from Agile Web Client.

  14. Check the redline BOM table on Assem6.SLDASM.

    Result: QTY of Part1.SLDPRT under Assem1.SLDASM redline BOM table is shown as redlined from 2.0 to 1.0.

21744416

EC Services

Issue: OPEN BOM TABLE HAS WARNING - CHANGE WITH CONFICTING REDLINES IN BOM

Root Cause: The BOM batch redline logic serving for MCAD tool in A934 has a defect and leads to the current issues.

Resolution: Add the missing logic.

Verification:

  1. Launch the CAD system and log in to Agile via workspace manager.

  2. Create one Assembly, assm01.sldasm, with two Part models part1.sldprt and part2.sldprt.

  3. Click Agile > Save preview for assm01.sldasm.

  4. Highlight all components, click Save As button to generate design and Item numbers.

  5. Click the Create Change button and assign the change for the assembly file.

  6. Click Continue to save it to Agile.

  7. In the CAD system, remove part1.sldprt from assembly, insert part2.sldprt to the assembly again, create a new part part3.sldprt and add to the assembly.

  8. Click Agile > Save preview, highlight the row of part3.sldprt and click the Save As button.

  9. Highlight the row of the assembly and check it out.

  10. Click the Continue button.

  11. Log in to Agile Web Client, open the Item object of the assembly file.

  12. Go to the BOM table and select the pending rev.

    Result: It displays the BOM Structure correctly without such warning message.

21807147

EC Services

Issue: WILL HAVE TWO ITEM OBJECTS IN RELATIONSHIP WHEN ASSIGNING A DIFFRENT SUBCLASS

Root Cause: The logic of ecBulkRelationships() has a defect for the case.

Resolution: Correct the logic.

Verification:

Prerequisites: Preference Settings:Save As: Item and DesignPublish to Item: BOM and AttachmentClass Default Settings: Item Subclass-Part

  1. Create one Object Design001 in CAD tool.

  2. Click Save Preview.

  3. Select the Object and then click Save As to assign Design and Item to the object > Click Continue in the Save Preview window.

  4. Go to Agile Web client to check the Design Relationship Tab. There will be one Item object linked to the Design.

  5. Go back to the CAD tool and click Save Preview again,

  6. Check Out the Object and then right click > Edit Properties.

  7. Change Item Subclass in the opened Detail window, for example, Change Item subclass from "Part" to "Model").

  8. Click "Autonumber Source for Selected Subclass" to generate one new Item number

  9. Click Save in Details window.

  10. Click Continue in the Save Preview window.

  11. Go to Agile Web client to check the Design Relationship Tab.

    Result: The old Item is be deleted from the Design Relationship and only the newly assigned one is linked to the Design.