Skip Headers

Agile Product Lifecycle Management Readme Release 9.3.3 E39274-01 |
| Contents

Previous | Next |

# 3 Resolved Issues

This chapter lists issues that were resolved during this release.

For each resolved issue:

- On the first line, the number is the internal Defect number.

- On the second line, numbers in bold (for example, 3-123456789) are Customer Support ID numbers from customer-reported issues. If there is not a number in the second line of an issue, its origin was not customer-reported.

## 3.1 Product Collaboration

7669934

SR 2-3874571, 3-5939117781, 7190027.993

Standard Reports

Issue: UNKNOWN NUMBER: OBJECT DOES NOT EXIST ON SHARED REPORT AFTER REPORT IS DELETED

Root Cause: The function to delete report attachments sharing is missed.

Resolution: Add the function.

Verification:

1. Schedule a report to be run. It could be any report.

2. After the scheduled report has run, go to the Historical Report tab.

3. Share the historical report with user A.

4. Delete the historical report.

5. Restart the Agile server.

6. Go to user A and click the Share tab.

Result: Able to open the Share tab without error message.

9278114

SR 3-1296340941

Item & BOM

Issue: INCONSISTENT DISPLAY OF 0 SCALE NUMERIC ATTRIBUTE

Root Cause: N/A

Resolution: N/A

Verification:

1. Go to Java Client > Admin > Data Settings > Classes > Parts > Page Two > Numeric 07. Set max, min, and default to blank, Scale to 0.

2. Log in to Web Client.

3. Create a Part and go to Page Two.

4. Enter a value for Numeric07 < 1000, like 999. It displays as "999".

5. Enter a value for Numeric07 > 1000, like 1245.

Result: The value displays as "1,245".

10176535

SR 3-6502392801, 3-2334036961

Web Client

Issue: GO TO BUTTON DOES NOT WORK IN WEB CLIENT

Root Cause: Due to a system default max limitation of 2500, the components cannot use go to in Web Client if the BOM number on its parent level is over 2500.

Resolution: In 9312 and later versions, a new setting "Maximum rows for expansion" was added in Preferences in Java Client. The default value of this option is 0, which means that it loads all rows without any limitation. Therefore, it will be able to go to any BOMs. Also, the option's value can be adjusted according to performance customer satiation.

Verification:

1. Log in as admin.

2. Import Part with BOM to Agile.

3. Search/open Part Q00001.

4. Open the BOM tab of Item Q00001.

5. Click the Go To button, find component Q03017 with all levels.

Issue: The system displays a warning message "No matches were found for the specified levels."

Expected Result: System can find Q03017 in this function.

6. Click the Go To button, find component Q03018, Q03050, Q03121, Q03139 with all levels.

Issue: The system displays a warning message "No matches were found for the specified levels."

Step 6 Expected result: The system can find Q03018, Q03050, Q03121, Q03139 in this function.

10304940

SR 3-6502392801, 3-2334036961

Web Client

Issue: GO TO BUTTON DOES NOT WORK IN WEB CLIENT

Root Cause: Due to a system default max limitation of 2500, the components cannot use go to in Web Client if the BOM number on its parent level is over 2500.

Resolution: In 9312 and later versions, a new setting "Maximum rows for expansion" was added in Preferences in Java Client. The default value of this option is 0, which means that it loads all rows without any limitation. Therefore, it will be able to go to any BOMs. Also, the option's value can be adjusted according to performance customer satiation.

Verification:

1. Log in as admin.

2. Import Parts with BOM to the Agile system: Parts from Q00001 to Q03159 with different levels.

3. Search and open the root Q00001.

4. Click BOM tab of Item Q00001.

5. Click the Go To button, and find component Q03017 with all levels (Q03017 is in Level 3).

Result: The system is able to find Q03017 with the Go To function.

6. Click the Go To button, and find component Q03018, Q03050, Q03121, Q03139 with all levels.

Result: The system is able to find Q03018, Q03050, Q03121, Q03139 with the Go To function

10359870

SR 3-2437534221

Changes

Issue: UNABLE TO CHANGE STATUS OF ANY CHANGE WHEN USER DOES NOT HAVE MODIFY COVER PAGE PRIVILEGE

Root Cause: Lack of logic for judging dirty values in method setWorkFlowAndChangeAnalyst().

Resolution: Add necessary logic.

Verification:

1. Log in to Java Client as admin.

2. Create a user, userA, with a role, role01, that includes the following privileges:

· Discover Changes (All changes)

· Read Changes (All changes)

· Modify Changes (Changes.Cover Page.Workflow is not applied to)

· Change Status for changes

3. Create a change, C0001, and assign the workflow Default Change Orders to it.

4. Log in to Web Client as userA.

5. Open C0001, click Next Status to route it from pending to Submitted. In the pop-up window, select a Change Analyst, and click Continue.

Result: The user is able to change status without getting an error message, though the user does not have the modify Cover Page.workflow attribute privilege.

10413584

SR 3-2154706991

Item & BOM

Issue: ADDING A NEW ITEM TO A BOM IS DEPENDENT ON UNNECESSARY PRIVILEGE AND SEARCH

Root Cause: The function to process the creation of a related object has a defect.

Resolution: Fix the defect.

Verification:

Case 1:

1. Log in to Java Client as admin.

2. Create Role YN-CreateItem.

3. Assign the following privileges to this role:

· Create Items

· Discover Items

· Modify Preliminary Items

· Read Items

4. Create user yn1, assign the YN-CreateItem role.

5. Make sure that user, yn1, does not have any Recycle Bin Searches.

6. Go to Data Settings > Classes > Items > Lifecycle.

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

8. Log in to Web Client as yn1.

9. Create a new Part, P1.

10. Go to the BOM tab.

11. Add > Create to Add, and create a new Part, p2.

Results: Message "Part p2 Lifecycle Phase is phase Preliminary" pops up.

12. Click OK.

Results: Part p2 is added successfully.

Case 2:

1. Log in to Java Client as admin.

2. Open role "YN-CreateItem", and add the privilege, Delete unreleased item.

3. Log in to Web Client as yn1.

4. Open P1.

5. Go to the BOM tab.

6. Add > Create to Add, and create a new Part.

Result. The message "Part <Part Number> Lifecycle Phase is phase Preliminary " appears.

7. Click OK.

Result: The object can be added successfully.

Case 3:

1. Log in to Java Client as admin.

2. Open the profile for user, yn1, and add "Recycle Bin Search" to Searches.

3. Log in to Web Client as yn1.

4. Open P1.

5. Go to the BOM tab.

6. Add > Create to Add, and create new Part.

Result: The message "Part <Part Number> Lifecycle Phase is phase Preliminary " appears.

7. Click OK.

Result: The user can successfully add a newly created Part as BOM Item.

11671995

SR 3-2743572391

Changes

Issue: AGILE INTERNAL ERROR WHILE REJECTING A CHANGE OBJECT AS APPROVER

Root Cause: When rejecting a Change, the Change goes to the prior status, while the current status breaks the criteria.

Resolution: Throw the correct error message.

Verification:

1. Log in to Java Client as admin.

2. Create a criteria: Change Orders Affected Items.Item Number Is Not Null.

3. Open CCB status of Default Change Orders, set If Rejected, set Status to Pending.

4. Remove the pre-existing criteria and add the criteria from step 2 for CCB status.

5. Log in to Web Client as admin.

6. Create a Change and add an Item into Affected Items, then change it to CCB status by adding one group as an approver (another user, e.g. u001, in the group).

7. Delete the Item from Affected Items.

8. Log in to Web Client as u001 and reject the Change.

Result: The system gives the error message: "No exit criteria matches for this change. CCB"

11692588

SR 3-2845190591

Web Client

Issue: THE PAGE SHOULD BE REFRESHED AUTOMATICALLY AFTER UPDATE BOM TABLE EVENT (POST)

Root Cause: The BOM table does not refresh after the row(s) are added.

Resolution: Make the BOM table refresh after the rows have been added.

Verification:

1. Log in to Java Client as admin.

2. Create an Update Item BOM Table Event.

3. Create an SPX Event Handler.

4.Create an Event Subscriber to bind Event Type and Event Handler. For Trigger Type choose Post, Execution Mode choose Synchronous.

5. Create an Item.

6. Go to the BOM Tab, add a Part. (Add actions including Drag & Drop, add by new, add by search, add by typein)

7. Change the Find Num to 0, click Save.

Result: The Find Num changed to 10 automatically.

8. Add a new part, check Find Num.

Result: The Find Num is set to 20 automatically.

11692640

SR 3-2845190591, 3-3028078421

Web Client

Issue: THE PAGE SHOULD BE REFRESHED AUTOMATICALLY AFTER UPDATE AFFECTED ITEMS TABLE EVE

Root Cause: The Affected Items table does not refresh after the row(s) are added.

Resolution: Refresh the Affected Items table after the rows are added.

Verification:

1. Log in to Java Client as admin.

2. Create an Update Change Affected Items Table Event.

3. Create an SPX Event Handler.

4. Create an Event Subscriber to bind Event Type and Event Handler, for Trigger Type choose Post.

5. Create an ECO.

6. Go to the Affected Items Tab, add an Item. (Add actions including drag & drop, add by new, add by search, add by typein.)

Result: The New Rev increases by 1 automatically.

11822227

SR 3-3077129721

Workflow

Issue: WORKFLOW EXIT REQUIRED FIELD IS NOT WORKING

Root Cause: If the originator is not set, the cell value is "0::()" not "null".

Resolution: modify value=null

Verification:

1. Log in to Java Client.

2. Go to Admin > Workflow > Workflows > Default CAPAs > Status Tab > Identified Status > Criteria Pane > Exit Required Fields Include Corrective and Preventive Actions.Cover Page.Originator.

3. Create New CAPA, CAPA00001.

4. Remove the originator and make it null.

5. Click the Next Status button to change the status.

Result: Audit Window shows an error/warning for the missing required field originator: "The following required fields are missing: CAPA00001: Cover Page.Originator".

11828694

SR 3-3088440571

Web Client

Issue: MAXIMUM NUMBER OF EXPRESSIONS IN A LIST IS 1000 WHEN TRYING TO

Root Cause: This is an Oracle limitation issue. In SQL, lists like table.column in (1,2,3,..) can not exceed 1000.

Resolution: Split the list into pieces, if it exceeds 1000.

Verification:

1. Create a user, usera, with all PSR-related privileges.

2. Add usera to 1500 user groups.

3. Log in to Web Client as usera.

4. Search for a certain PSR by Quick Search or Advanced Search.

Result: The user can search for and find the PSR without error.

5. Log in to Java Client as usera.

6. Search for a certain PSR by Quick Search or Advanced Search.

Result: The user can search for and find the PSR without error.

11874885

SR 3-2657012541, 3-5998937021

Changes

Issue: DROPDOWN LIST NOT SORTED

Root Cause: If the count of the list values is more than the threshold limit, the list values are not sorted.

Resolution: Remove the threshold limit.

Verification:

1. Log in to Java Client as admin.

2. Create a simple list and add 267 entries (245 active entries and 27 inactive entries. Ensure that the number of active entries is not more than 250, because list type will change to search automatically when it is more than 250).

3. Open Change Orders class and go to the Page Two tab.

4. Enable a list, list11 as example, and assign the list value.

5. Log in to Web Client as admin.

6. Create or search an ECO.

7. Click List11 in Edit mode.

8. Check entries of list11.

Result: All list entries are sorted.

11895091

SR 3-3230843021, 3-6350627907, 3-5170861991

Item & BOM

Issue: FATAL ERROR WHEN YOU DELETE THE ITEM WHICH IS ADDED TO THE LIST ATTRIBUTE OF THE RELATIONSHIP

Root Cause: The function to process empty reference objects has a defect.

Resolution: Fix the defect.

Verification:

1. Log in to Java Client.

2. Go to Change > Relationship tab > List04.

3. Enable List04 and make it point to Items.

4. Create an ECO in Web Client, add another ECO as a related object, and modify List04 to point to a newly created Part.

5. Open the part and soft-delete the Part. Go back to the original ECO.

Result: The ECO is displayed without any error, and in the Relationships tab, the part is removed from List04. attribute

12398370

SR 3-3312725721, 3-3576285411

Item & BOM

Issue: CHARACTER SET ON CHANGE AFFECTED ITEM TAB IS NOT WORKING

Root Cause: Missed proper conversation or date validation for the Item description being given from the Change's Affected Items tab when there is a variety character set configured in Java Client.

Resolution: The code was modified to set an indication flag in the request row to validate data, otherwise correct the description to have the proper character.

Verification:

1. Log into Java Client as admin.

2. Open the Parts class.

3. Open the Description of Title Block and set "Include Characters" as "All Characters without Special Characters".

4. Log in to Web Client as admin.

5. Create a new Part, P001.

6. Create a Change Order, C001, and add P001 into Affected Items.

7. Double-click Item Description on Affected Items.

8. Enter special characters, like "YZ%5es@$%25%5e%5e()~:,.+-", then Save.

Result: Cannot save successfully, special characters are not allowed in this case.

12412464

SR 3-3475229751

Item & BOM

Issue: INCORRECT USER IN PART HISTORY

Root Cause: No user information is persisted when redline attribute is performed.

Resolution: Persist redline information to the additional column of the existing table and read user information from that table when the history log is built.

Verification:

1. On a Part subclass, Page Two: set change controlled part attributes PAGE_TWO.TEXT01,

PAGE_TWO.DATE01, PAGE_TWO.LIST01, PAGE_TWO.MONEY01, PAGE_TWO.NUMERIC01, PAGE_TWO.MULTITEXT01, PAGE_TWO.MULTILIST01.

2. Logged in as User A, modify all of these attributes at the Part level.

3. Place the Part on a change.

4. Update the item: P2 text, date multitext, list, money, numeric, multilist fields through the change.

5. Change Analyst releases the Change Order.

6. Check the History tab of the part.

Result: User A is shown in the Part history as the person who made the changes.

12549422

SR 3-3490440521

Web Client

Issue: ERROR IN AUDIT STATUS WINDOW ERROR MESSAGE SHOWS INCORRECT STATUS

Root Cause: The error message shows the default next status of the routable object.

Resolution: Make sure that the correct status name appears in the error message.

Verification:

1. In Java Client, go to the Default Problem Reports workflow.

2. Make sure that the users are able to go to all the statuses manually (privileges and in Manual Valid Next Status on each status).

3. Notice that the workflow status has Pending, Submitted, Review and Released statuses.

4. Make sure that the Review status has an Entry Required Field, for example, Problem Reports.Cover Page.Expected Resolution Date.

5. Log in to Web Client and create a new Problem Report, PR00037.

6. Add the Default Problem Reports workflow to the Cover Page.

7. Go to the Workflow tab and from the Pending status click on the Review status (this will jump to the Submitted status which does not have any required fields). You will then get the following message:

"The following issues exist. All errors must be resolved before the status can be changed to Submitted. You may continue when there are only warnings."

9. Notice that the message states Submitted, and not Reviewed, which is expected.

Result: The message states Reviewed, instead of Submitted.

12581923

SR 3-3641449041

Item & BOM

Issue: WHERE USED REPORT SHOWS WRONG ITEM DESCRIPTION

Root Cause: The function to process parameters in the Where Used report has a defect.

Resolution: Fix the defect.

Verification:

1. Create a Part with Part Description set as "TEST001".

2. Release the Part as Rev A.

3. Change the Part Description to TEST002" and Release the part as Rev B.

4. Run Reports > Standard Reports > Product Reports > Where Used Report for the Part.

Result: The Part description is "TEST002" in the report result. There is one warning in this case: "WARNING: This item is not used by any BOM."

12607535

SR 3-3711605091

Sites

Issue: WEB CLIENT NAVIGATOR PANE ALWAYS SHOWS SITE [ALL] EVEN IF LICENSE OF SITE IS NO

Root Cause: Agile does not check whether the license of the Site is enabled or not.

Resolution: Fix the defect.

Verification:

Case 1:

1. Log in to Java Client as admin.

2. Go to Admin > Server Settings > Licenses > Modules, set Sites to No.

3. Restart the Agile Server.

4. Log in to Web Client.

5. Search for any BOM and click on the Navigator.

Result: The BOM tree is displayed in the Navigator Pane. P00007 [Introductory] : test

12621728

SR 3-3657323401

Item & BOM

Issue: NO ERROR SHOWN IN WEB CLIENT WHEN ADDING AN ITEM TO A CHANGE WITH INVALID FILE

Root Cause: The function to process the uploaded file repository check is not present.

Resolution: Add the function.

Verification:

1. Log in to Java Client.

2. Navigate to Admin > System Settings > SmartRules > Copy Files To Rev - File Folders to Copy.

3. Log in to Web Client as admin.

4. Create an Item. Add attachments, either a single file or multiple files.

5. Remove the attachment from the iFS (vault).

6. Create a Change and try to drag/drop that Item on to the Affected Items tab or add the item by search in Web Client.

Result: The following error is given: "Specified file (120Dodge1727.jpg) could not be located. Please contact the administrator."

12663282

SR 3-3568126791

Item & BOM

Issue: UNABLE TO CHANGE REVISIONS. NEED TO CLICK BACK AND THEN IT ENABLES CHANGE.

Root Cause: The function to set grid cell value in client has defective.

Resolution: Fix the defect.

Verification:

1. Log in to Web Client in Firefox.

2. Click on Report > Standard Reports > Product Report > BOM Explosion report.

3. Click on Execute.

4. Choose the Default layout and Standard Output format and click next.

5. Click on Custom Search > Advanced Search.

6. Choose Parts from the dropdown menu.

7. Select the attribute Pending Changes > Number is not null.

8. Select several Parts.

9. Click on each Affected Item and change the revision the revision using the dropdown.

10. Click on the Next or Previous button, then go back to the Select item for Report page.

11. Click Next and then the Finish button.

12. Repeat the steps using a Safari browser..

Results:

9. The user is able to edit Revision for each part.

10. The revision is editable for each part.

11. The BOM Explosion Report generates successfully with the correct data.

12684054

SR 3-3779471361, 3-4530320961

Java Client

Issue: AGILE JAVA CLIENT LAUNCHES NO MATTER WHICH VERSION OF JAVA IS INSTALLED ON THE SERVER

Root Cause: N/A

Resolution: N/A

Verification:

1. Use a lower version of Java 1.6, such as 1.5_07.

2.Try to launch 933 Java Client.

Result: 933 Java Client cannot be launched successfully with a lower version of Java 1.6. Therefore, the user is prompted with a message which asks the user to upgrade the JRE version.

12795606

SR 3-4077427971

Changes

Issue: INSUFFICIENT PRIVILEGE FOR REVIEWER COLUMN IN THE WORKFLOW TAB OF CHANGE

Root Cause: We do not pass the subclass for the user for the privilege check, but need to since the criteria are at the subclass level.

Resolution: Passed the subclass of the user for privilege check.

Verification:

1. Log in to Java Client as user admin.

2. Admin > Data Settings > Criteria > New > Create a Criteria named ECO Subclass with object type as ECO.

3. Admin > Data Settings > Criteria > New > Create a Criteria named Part Subclass with object type as Part.

4. Admin > Data Settings > Criteria > New Create a Criteria named User Subclass with object type as User.

5. Admin > User Settings > Users > Create New > u1 as the ID.

6. Admin > User Settings > Users > Create New > u2 as the ID.

7. Admin > User Settings > Roles > Create New > named My Role.

8. Assign Users u1 and u2 to the role My Role.

9. Admin > User Settings > Privileges > Discover > Create New > Discover ECO Subclass privilege using ECO Subclass Criteria.

10. Admin > User Settings > Privileges > Discover > Create New > Discover Part Subclass privilege using Part Subclass Criteria.

11. Admin > User Settings > Privileges > Create > Create New > Create ECO Subclass privilege using ECO Subclass Criteria.

12. Admin > User Settings > Privileges > Create > Create New > Create Part Subclass privilege using Part Subclass Criteria.

13. Admin > User Settings > Privileges > Modify > Create New > Modify ECO Subclass privilege using ECO Subclass Criteria.

14.Admin > User Settings > Privileges > Modify > Create New > Modify Part Subclass privilege using Part Subclass Criteria.

15. Admin > User Settings > Privileges > Discover > Create New |Discover User Subclass privilege using "User Subclass" Criteria.

16. Admin > User Settings > Privileges > Read > Create New > Read ECO Subclass privilege using ECO Subclass Criteria.

17. Admin > User Settings > Privileges > Read > Create New > Read Part Subclass privilege using Part Subclass Criteria.

18. Assign the privileges created in steps 9 to 17 to role My Role.

19. Assign the privilege Approve/Reject Changes to role My Role.

20. Create a part, P0001.

21. Actions > Create New > Change > ECO C0001.

22. Provide the workflow as Default Change Order.

23. Provide the Lifecycle Phase and Revision details in the Affected Items tab of the Change Order, C0001.

24. Move the change to Submitted Status.

25. Move the change to CCB status with approvers as u1 and u2.

26. Log in to Web Client as user u1.

27.Open the Change Order C0001

Result: In the Workflow Tab, user u1 is able to see the u2 user in the reviewer column.

12808554

SR 3-4109518421, 3-7257684371

Web Client

Issue: WHERE-USED TOP LEVEL LATEST RELEASED REV REPORTS DO NOT SHOW EXPECTED RESULTS

Root Cause: The Where Used search does not handle this case at all.

Resolution: Add a new list to store multiple result rows when there are manufacturer attributes in selected columns.

Verification:

1. Log in to Web Client as admin.

2.Create a Part, PA, with two manufacturers:

----manufacturer.mfr name, manufacturer.mfr partNumber

---mf1, mfp1

---mf2,mfp2

3. Create a part, PA1, with three manufacturers:

---manufacturer.mfr name, manufacturer.mfr partNumber

---manufacturer1, manufacturer part1

---manufacturer2, manufacturer part2

---manufacturer3, manufacturer part3

4. Add PA1 to PA's BOM table.

5. Create another part, PA1-1, then add it to PA1's BOM table.

6. Do an Advanced Search: Items > Parts > Where-Used Top Level Latest Released Revision Only > Title block.Number > Equal to > PA1-1, click Format button, move manufacturer.mfr name to the Displayed field and run the search.

Results: PA with its two manufacturers are returned:

---Number, mfr.Name(manufacturer)

---PA, mf1

---PA,mf2

12836199

SR 3-4190244231

Web Client

Issue: WEB CLIENT DOES NOT REFRESH WHILE DOING REDLINES

Root Cause: The RedLineDataModel does not correctly load the redlined BOM.

Resolution: When saving the Grid table, the data model should only refresh the parents that are the same as the selected row.

Verification:

1. Log in to Web Client.

2. Go to a Change with multiple affected items.

3. Highlight a row, e.g.P00001, to redline the BOM (i.e. QTY field) and Save.

4. Highlight another row, e.g. P00002, to go to another Affected Item's Redline Manufacturer's tab.

5. Go back to the original part, P00001, Redline Manufacturer's tab and update a field and Save.

6. Go to the Redline BOM tab.

Result: All the rows on the Redline BOM tab appear correctly.

12840461

SR 3-4146790711

Changes

Issue: AUDIT STATUS DOES NOT CAPTURE MISSING APPROVERS

Root Cause: The code logic does not handle this situation.

Resolution: If the setting for Pass Release Audit is set as Yes in workflow criteria, we also audit the release in addition to the audit status when executing the Audit Status action.

Verification:

1. Log in to Java Client as admin.

2. Go to Workflow > Default change orders > CCB status, open the criteria for CCB, and set its Pass Release Audit as Yes/warning.

3. Log in to Web Client as admin

4. Create a Change, C001, with a Part, P001, and select Default Change Orders as its workflow.

5. Route C001 to CCB status, fill in all required fields for both Change and Part, and add a few approvers for CCB status.

6. Click Audit release or click Next Status.

7 Click Action > Audit status.

Results:

6. A message that states that "Not all approvers responded." appears.

7. The system gives the warning message: Not all approvers responded.

12886570

SR 3-4234683581

Web Client

Issue: RELATIONSHIPS TAB ON DISCUSSION SUBCLASSES DOES NOT SHOW ALL RELATED OBJECTS

Root Cause: Discussion load relationships with rang 30 and pass the 30 required object rowids to server side, but the server query returns 30 object randomly. It does not display some objects which is not in the key set passed by UI.

Resolution: when query out results, it will compare with key set passed by UI. Then return them.

Verification:

1. Log in to Web Client as admin.

2. Import 100 Problem Reports: PR001 to PR100.

3. Create a Discussion, DIS1, then add all of the Problem Reports (original exists in the database and newly imported problem reports) to its Relationships table.

4. All Problems Reports (such as 130) were displayed in the DIS1.relationship table and sorted by Name by default.

5. Sort them by description or other columns.

Result: All related Problem Reports are displayed in the Relationships table and are sorted correctly by the selected column.

12909372

SR 3-4295430261

Web Client

Issue: DESELECTED SUPPLIERS ARE STILL LISTED ON RESPONSES TAB

Root Cause: The system gets the wrong value when the user clicks the checkbox.

Resolution: Add method to set the right value for the corresponding checkbox.

Verification:

1. Create a Sourcing Project.

2. Add an Item/Assembly.

3. Add 3 partners and check "Apply to remaining Records" in the Add Partners page.

4. Select all and create the RFQ. On the Add Suppliers page, uncheck 2 of the Partners.

5. Click on the Finish button.

6. Navigate to the Responses tab. Validate the Partners added.

Result: Responses lines are created for only the Partner selected in the wizard.

12938970

SR 3-4132904691

Changes

Issue: MAXIMUM NUMBER OF EXPRESSIONS IN A LIST IS 1000

Root Cause: This is an Oracle limitation issue, in a SQL list like table.column in (1,2,3,..) you cannot exceed 1000.

Resolution: Split the list into parts if it exceeds 1000.

Verification:

1. Create a user, usera, with all Changes related privileges.

2. Add usera to 1500 user groups.

3. Log in to Web Client as usera.

4. Search for certain Changes by doing a Quick Search or Advanced Search.

Result: The user can search for and find the Changes without error.

5. Log in Java Client as usera.

6. Search for certain Changes by doing a Quick Search or Advanced Search.

Result: The user can search for and find the Changes without error.

12958899

SR 3-2544309521, 3-4196347631, 3-6508447351

Web Client

Issue: LISTS ARE NOT SORTED IN ANY PARTICULAR WAY

Root Cause: If the count of the list values was more than the threshold limit, the list values would not be sorted.

Resolution: Remove the threshold limit.

Verification:

1. Log in to Java Client as admin.

2. Create a simple list and add 267 entries (245 active entries and 27 inactive entries, make sure that the active entries are not more than 250 because the list type will change to search automatically when it is more than 250).

3. Open the Change Orders class and go to the Page Two tab.

4. Enable a list, list11, for example and assign the newly created list value.

5. Log in to Web Client as admin.

6. Create or search for an ECO.

7. Click List11 in edit mode.

8. Check entries of list11.

Result: All list entries are sorted.

13019657

SR 3-4526843411, 3-4576839220

Web Client

Issue: GO TO BUTTON SOMETIMES CAN NOT FIND REF DES

Root Cause: The row which located at multiples of 30 has defective.

Resolution: Fix the defect.

Verification:

Precondition: Create an Item with child BOMs >30, make REF DES of child BOMs different. You can prepare this data through import.

Steps:

1. Click the Go to button in the BOM tab, then choose REF DES in the column list.

2. Try to fill the REF DES of 30th, 60th...(Multiple of 30) in the BOM grid, then click Find Next.

Issue: The row which is a multiple of 30 cannot be found.

Result: The row which is a multiple of 30 can be found.

13030595

SR 3-4462090671

Web Client

Issue: REDLINE EDIT INCORRECTLY APPEARS FOR CASCADING LISTS WHEN REDLINING OTHER ATTRIBUTES

Root Cause: We get an incorrect newValue and oldValue when creating the RedlineCellElement if the cell has cascade list value.

Resolution: Update the newValue and oldValue.

Verification:

1. Log in to Java Client as admin.

2. Open a subclass of Parts, Part, and enable Page Three.

3. Enable Date01, Text01, Money01, Numeric01, MultiText10 and make them as change-controlled.

4. Enable List01, MultiList01 and assign a cascading list, make them as change-controlled.

5. Log in to Web Client as admin.

6. Create a Part named Part1 and set the value for List01 and MultiList01 and leave others empty.

7. Log in to Java Client as admin.

8. Set Date01, Text01, Money01, Numeric01, List01 and MutiList01 as required.

9. Go back to Web Client as admin.

10. Create a Change Order against Part1, go to the redline Title Block tab, fill in only one of the above fields, for example, Text01, and leave the others blank.

11. Click Save and get an error stating that required fields need to be filled .

12. Check the above attributes.

Result: Nothing has the redlined indicator showing in List01 and Multilist01.

13354113

SR 3-4877395131

Web Client

Issue: PART TYPE ATTRIBUTE IS CHANGED WITHOUT SAVING ON EDIT PAGE

Root Cause: In the Web Client, when changing the object type (e.g. Part Type, Document Type, Change Type, PSR Type, QCR Type?), the system saves the object automatically, so at this time, if the user clicks Cancel, the system does not reset the object.

Resolution: As PM's confirmation, change the content of the warning message. <Changed file list> apcm\src\com\agile\resources\PCMessagesI18N.properties

Verification:

1. Log in to Java Client as admin.

2. Create a subclass: New part for Parts class.

3. Log in to Web Client as admin.

4. Create a new Part, P1, with part type.

5. Click Edit, then change its type to: New part.

6. Select Cancel.

7. Change its Type to: New part.

8. Select Continue.

9. Click Save or Cancel.

Results:

4. P1 with Part type can be created successfully.

5. Prompt a warning message "You are changing the subclass of the object. This change will be saved and cannot be rolled back. Do you want to continue using the same object name or number?"

6. It rolls back part for type field.

7. Warning message "You are changing the subclass of the object. This change will be saved and cannot be rolled back. Do you want to continue using the same object name or number?" is displayed again.

8. It prompts a message "Your changes have been successfully saved and the workflow list has been updated accordingly."

9. The modification is be saved successfully, since the modification took effect in Step 8.

13354443

SR 3-4837198421

Folders, Files & Attachments

Issue: FATAL ERROR : TREE GRID CANNOT RENDER - UNABLE TO CHECK OUT/CHECK IN, GET FILES

Root Cause: Additional attributes are considered while rendering the grid which results in an "Index out of range" exception.

Resolution: Exclude the attributes.

Verification:

1. Log in to Web Client.

2. Create a file folder/Design.

3. Add attachments to the Files tab.

4. Create a new table view. Save as the Base View without any customization.

5. Check out the File.

Result: The File Folder/Design checkout action was successful and the file downloaded successfully.

13361501

SR 3-4838979701

Web Client

Issue: NOT ABLE TO SEARCH THE LOV FOR AN ATTRIBUTE WITH ENTIRE STRING

Root Cause: There is a special symbol in the query string, such as "|".

Resolution: Use the disable/enable regular expression.

Verification:

1. In the agile.properties file, set the default regular expression value: disableRegularExpressions=no

2. In Java Client, create a simple list with the following values:

678T | Final Assy,Disk Drive,DVD (81001)

ASY | A784 | TSSOP 16 6000399 A PF

ASY | A784

A784

3. Assign this list to Parts.page two or part. page three list01, and check list display with search.

4. Log in to Web Client.

5. Go to Items > Part and create a part:p0001.

6. Click on the Edit button.

7. Go to the attribute Page Two or Page Three list01.

8. Click on the search button.

9. Enter any of the following values and search ASY \| A784 \| TSSOP 16 6000399 A PF

Result: ASY | A784 | TSSOP 16 6000399 A PF can be searched for and returned successfully. If searching for ASY | A784 | TSSOP 16 6000399 A PF, there is no result.

10. Go to the server and change disableRegularExpressions=yes and restart the application server.

11. Go to the Web Client and search p0001.

12. Modify the Page Two or Page Three list01, search ASY | A784 | TSSOP 16 6000399 A PF.

Result: ASY | A784 | TSSOP 16 6000399 A PF can be searched for and found successfully and added successfully.

13368223

SR 3-4840344611

Web Client

Issue: ERROR WHILE EXECUTING WHERE USED REPORT

Root Cause: The function to process the alpha character comparison is defective.

Resolution: Fix the defect.

Verification:

1. Create an item TC133682230010148382D with BOM item TC133682230010148382ER.

2. Open TC133682230010148382ER and create BOM Item 61.0266 & 61.0267.

3. Create an Item TC133682230020148382D with BOM item TC133682230020148382ER.

4. Open TC133682230020148382ER and add BOM Item 61.0267.

5. Run the Where Used Report with a layout that sorts Item number for Item 61.0267.

Result: There is no error. TC133682230010148382D & TC133682230020148382D are shown in the report result.

13551996

SR 3-5078427251, 3-6500028941

Workflow

Issue: A WORKFLOW HAS NOT BEEN ASSIGNED ERROR APPEARS FOR EVERY WORKFLOW WHICH IS ON HOLD

Root Cause: When executing the program business to get a historical hold before current status in workflows, because of the date format that was hard coded in the SQL script was US, if the language of the operating system that Weblogic server was running on was another language, it cause a SQL date conversion error.

Resolution: Change the date format from US to a common format.

Verification:

1. Log in to the server, go to Control Panel > Regional and Language > Regional Options > Standards and formats, set the Format as ENGLISH (CANADA).

2. Restart the Agile Service after making the change.

3. Log in to Java Client.

4. Create New > Change Order > ECO > Select the workflow as Default Change Order.

5. Move the Change Order to Submitted Status.

6. Move the Change Order to Hold Status.

7.Close the Change Order and open it again.

8. Go to the Workflow Tab.

9. Repeat the steps in Web Client.

Result: For both the Web Client and the Java Client, the workflow displays correctly on the Workflow table without any error.

13701071

SR 3-5276604081

Web Client

Issue: AGILE OOTB: ADVANCED SEARCH IS NOT LOADING THE CRITERIA ENTERED

Root Cause: This event is not fired when a list-based control exceeds the maximum threshold of 250 and a successful destruction/construction of a new equivalent search-based control has taken place.

Resolution: Code script. [PLEASE EXPLAIN--- ]

Verification: .

1. Log in to Java Client as admin.

2. Go to Admin > Workflow settings, add more than 10 new workflows, make sure that there are more than 250 values in the Workflow Status list.

3. Log in to Web Client as admin.

4. Do an Advanced Search: Changes > Workflow.Workflows status > Equal to > select one status list, such as Default change orders.CCB. Run the search.

Results:

An error message "Workflow Status can only be used in a criteria group along with other workflow attributes." appears.

14019984

SR 3-5498410881

Standard Reports

Issue: EFFECTIVE BOM EXPLOSION REPORT ONLY SHOWS ZERO LEVEL

Root Cause: The function to process canceled Change Orders in the Effective BOM Explosion Report has a defect.

Resolution: Just sweep the canceled Change Orders out.

Verification: .

1. Create a Part P001.

2. Create a Change, C001, against P001.

3. Add a Part, P002, as a redlined BOM of P001.

4. Release C001.

5. Create a Change, C002, against P001.

6. Add a Part, P003, as a redlined BOM of P001.

7. Change C002 status to CCB, then change C002's status to Cancel.

8. Go to Reports > Standard reports > Products Reports > Effective BOM Explosion Report, Add

P001 for the report.

9. Click Next, then click the Finish button.

Result: P002 should also appear in the report.

10. Create an SCO against P001.

11. Add a Part P005, as a redlined BOM of P001.

12. Release the SCO.

13. Create another SCO against P001.

14. Remove P005 from the redline BOM of P001.

15. Change the SCO's status to CCB, then change the status to Cancel.

16. Go to Reports > Standard reports > Product reports > Effective BOM Explosion Report, Add P001 for the report.

17. Click Next, then click the Finish button.

Result: P005 also appears in the report.

14044858

SR 3-5487709751, 3-5828988601

Changes

Issue: NO DEVIATION ABOUT TO EXPIRE NOTIFICATION RECEIVED ON RE-RELEASE

Root Cause: When the date value of the Effective To field is changed and the deviation is re-released, the notice flag is not reset, which would have prevented the expire notification from being sent again.

Resolution: Use a special handler for the deviation object. Reset the notice flag to 0 when the user changes the date value of the Effective To field.

Verification:

1. Log in to Web Client as admin.

2. Create a Deviation: D001, set its Effective From date as: 2013/01/22 and Effective To date as 2013/01/24 12:00AM (Note: current time: 2013/01/24 03:00AM).

3. Release D001.

4. Demote the Deviation, D001, and edit its Effective To value to another data/time, such as 2013/01/24 01:00PM.

5. Re-release D001.

Results:

3. The admin receives a Deviation About To Expire notification.

5. The admin can receive Deviation About To Expire notification on re-release.

14064750

SR 3-5654921581

Changes

Issue: UNABLE TO CREATE CAPA OBJECT, UNKNOWN NUMBER: OBJECT DOES NOT EXIST

Root Cause: When creating a new QCR, PSR, or Change object, the code checks whether the quality or change analyst has discovery privilege to create the object in the specific object category. The value of the object category attribute is retrieved from the server, so during the first attempt to create, this value is null, the privilege criteria could not be matched and the system threw the no-privilege exception.

Resolution: Change the logic to get the value of the object category attribute from the UI, instead of the server when creating a new QCR, PSR, or Change object.

Verification:

1. Log in to Java Client.

2. In Admin, open QCR > Corrective and Preventive Actions class.

3. In Attributes:Cover Page, set Required's value of Category and Quality Administrator to true.

4. Create a Criteria, e.g. test_criteria, with Object Type, CAPA, and the condition: Cover page.Category In Customer Complaint.

5. Create a Privilege, e.g test_privilege, with Privilege: Discovery and Criteria: test_criteria.

6. Create a User, e.g. test_user, with Lists: Quality Administrator List.

7. Create a Role, e.g test_role, with Privilege: test_privilege and Users/Groups: test_user.

8. Log in to Web Client as a super user.

9. Create a new QCR > Corrective and Preventive Actions with Category: Customer Complaint and Quality Administrator: test_user.

Result: When the user clicks the Save button, the content is saved successfully.

14072701

SR 3-5621210471

Changes

Issue: ERROR 'UNABLE TO SAVE YOUR CHANGES. YOU HAVE ONE ERROR.' IN THUMBNAIL NAVIGATOR

Root Cause: N/A

Resolution: N/A

Verification:

1. Log in to Web Client as admin.

2. Create a new change order, ECO001, then add a document, D001, as its Affected Item.

3. Open D001, then add an attachment, E.doc, to it.

4. Go to D001's.Title Block, check its Thumbnail window, it should show 1 of 1.

5. Go to ECO001's AI table, try to remove D001 from its AI table.

6. Select Continue > Finish.

7. Add D001 to ECO001.AI table again.

8. Open D001, check its Attachment table, there is no any file in the Attachment table.

9. Go to D001.Title Block, check Thumbnail.

10. Add another attachment file for D001, then check its Thumbnail.

11. Try to open the attachment file from Thumbnail Navigator.

Results:

5. It pops up awarning message window: Files that are attached to Document D001 of this pending revision will be removed as attachments.

9. No attachment was displayed in the ThumbnailNavigator window.

10. It shows 1 of 1.

11. The file can be opened successfully.

14107957

SR 3-5709117061, 3-6609951971

Web Client

Issue: AGILE PLM CUSTOM REPORT VARIABLE $ TODAY+XX NOT RETAINING

Root Cause: The character "+" was not handled well in our code.

Resolution: Added a special handler for date type attributes that have a value that contains "+".

Verification: .

1. Log in to Web Client to create an Advanced Search:

Changes - Change Orders - Object Search

Attribute Operator Value

DateOriginated Equal to $TODAY+10

2. Click Search button.

Result: It performs the search and + is valid in the search condition.

14115782

SR 3-5594290631

Web Client

Issue: WRONG DATE DISPLAYED IN THE EXPORT FILE AND PRINT OPTION FROM BOM TAB

Root Cause: Incorrect logic when printing and exporting date value.

Resolution: Change the logic, take Date Time format in consideration.

Verification: .

1. Set Effective From and Effective To attributes of class Deviations to DATE ONLY through Java Client.

2. Log in to Web Client, Set Time Zone to (GMT-07:00) Arizona.

3. Create a Deviation D00001, set Effective From to 01/16/2012, and set Effective To to 01/19/2012.

4. Click Action > Print.Result: When printed, the information is: Effective From: 01/16/2012 Effective To: 01/19/2012.

14198750

SR 3-5652371951

Item & BOM

Issue: STANDARD BOM EXPLOSION REPORT LOCKS IN DATE OF LATEST REVISION

Root Cause: The function to retrieve BOM attributes by Rev in the BOM Explosion Report has a defect.

Resolution: Fix the defect.

Verification: .

1. Log in to Web Client.

2. Create an assembly, P001, with the following structure in the BOM table:

Item Number Rev Rev Released Date

P001 C 12/20/2012 09:00:00 AM GMT

|__P0001 B 12/20/2012 07:32:44 AM GMT

| |__P00001 A 12/21/2012 01:00:00 AM GMT

|__P0002 C 12/26/2012 06:30:00 AM GMT

3. Open the BOM Explosion Report, click Execute at 12/26/2012 09:30:00 AM GMT.

4. Add P001 with the latest revision, C, to the report. Note the default value for Date As Of.

5.Click Finish, check the report result.

Result: The default value for Date As Of is 12/26/2012 09:30:00 AM GMT, which is the date and time the report ran. Rev A for P00001 and rev C for P0002, which are the latest revisions, appear in the report result.

14248693

SR 3-5859646151

Web Client

Issue: WORKFLOW STATUSES ARE NOT VISIBLE WHILE CREATING A REPORT (QUERY)

Root Cause: When doing an Advanced Search on an object Item, the status of the pending Change needs to get IDs of the Change not the Item.

Resolution: Add a special handler for this case on Item.pending change.status and Item.change history.status.

Verification: .

1. Log in to Java Client as admin.

2. Go to Admin > Workflow > Default Change Orders, and use Save As to create ECO_NEW, and add a new status, sri_new, for it. Enable the new workflow ECO_NEW.

3. Log in to Web Client as admin.

4. Do an Advanced Search: Items > Parts > Pending changes.status > In, and check listed values.

5. Create a Part, P001, then go to its Changes tab. Create a new Change Order, ECO001, with workflow ECO_NEW.

6. Route ECO001 to Pending status.

7. Do an Advanced Search, Items > Parts > Pending changes.status > In > ECO_NEW.Pending, run the search.

Results:

4. All the workflow statuses, including the customized status ECO_NEW.sri_new, are listed in the search dropdown.

7. P001 is returned as a search result.

14325559

SR 3-4511086219, 3-4511086219

Item & BOM

Issue: ERROR IN BOM COMPARISON REPORT

Root Cause: The function to process special characters in level 4 of a BOM Comparison Report has a defect.

Resolution: Fix the defect.

Verification: .

1. Log in to Java Client as admin.

2. Open the preference, Maximum BOM Compare Limit, set it to 1000000.

3. Log in to Web Client as admin.

4. Execute the BOM Comparison Report, set BOM level=4.

5. Add 1203433 and 1183403 to the report, click the Finish button.

Result: It returns the correct report result since the BOM nodes number less than 1000000.

14391019

SR 3-5260317751

Web Client

Issue: MULTIPLE ISSUES WITH SCHEDULE CUSTOM REPORTS SINCE UPGRADING TO 9.3.1.1

Root Cause: The function to view a historical report updates the report version.

Resolution: Remove the function.

Verification: .

1. Log in to Web Client as admin.

2. Go to Change Backlog Report > Historical Report Tab.

3. Select a row and click the View button. The historical report opens.

4. Select the row and click the Remove button.

Result: The user can remove the report successfully and gets the message "1 row has been removed."

14401106

SR 3-6019552391

Web Client

Issue: HISTORY TAB DOES NOT LOG CHANGED VALUES

Root Cause: The value of User Preferred Start Page attribute was not converted to a correct value when appended to the history detail.

Resolution: Added a special handler for this attribute to get the attribute's value from a new special User Preferred Start Page list.

Verification: .

1. Log into Web Client as admin.

2. Save this user as another admin user: create admin2 from admin.

3. Check its Preference.Preferred Start Page field.

4. Change its value to something else, e.g. Dashboard Resources. Then check details in the History table.

5. Log into Web Client as admin2.

6. Change its Preference.Preferred Start Page to be Notification, then check details in History table.

Results:

3. Workflow is displayed in this field.

4. <Preferences.Preferred Start Page>WAS<Workflow>IS<Dashboard Resources> is displayed.

5. Start page is the Dashboard Resources page.

6. <Preferences.Preferred Start Page>WAS<Dashboard Resources>IS<Notification> is displayed.

14464178

SR 3-6014478941

Item & BOM

Issue: ZEROS AFTER NUMBER REMOVED ON SAVE IN BOM TAB

Root Cause: The function to process number parsing has a defect.

Resolution: Fix the defect.

Verification: .

1. In Admin, Enable BOM Numeric01 under the BOM tab of Parts.

2. Set the numeric attribute scale to 5.

3. Go to Web Client, create Part1, add Part2 as its BOM.

4. Enter a value, e.g. 7.000000, for the BOM Numeric01.

5. Save.

Result: BOM Numeric01 has a value 7.00000.

14478649

SR 3-6045977751

Changes

Issue: STOP SHIP FAILS TO PROMOTE

Root Cause: When changing the workflow to a status with Released type, the object version of Affected Items are added 1, this program was run when released the lock of transaction, but the business was not correct, the object version would be added once in database, but twice in item cache, the version in these two places could not be matched, so the exception was thrown and the auto promote failed.

Resolution: Correct the object version in the Item cache and make sure that it increases by 1 only once.

Verification: .

1. Log in to Java Client with admin.

2. Go to Admin > Workflow, search out Default Stop Ships, save it as a new workflow with the name, Default Stop Ships_New.

3. Open workflow, Default Stop Ships_New, add a new Released type status, Released1, between Submitted status and CCB.

4. Edit the Released1 status, select all status for its Manual Valid Next Status field.

5. Edit the Submitted status, move the Released1 status to its Manual Valid Next Status field.

6. Make sure that the value of the Auto Promote attribute is set to Yes for the CCB status.

7. Create a new Change Status privilege, change status for ss with the new workflow, Default Stop Ships_New, and assign it to admin.

8. Log in to Web Client as admin.

9. Create a stop ship, SS1, with an Affected Item item, Part001, select Default Stop Ships_New as its workflow.

10. Enter the required fields, change the status of SS1 to Released1 status, then change its status to CCB.

Results: SS1 can be routed to CCB status without any errors and it can be auto-promoted to Released.

14557578

SR 3-6134500271

Web Client

Issue: COPY/PASTE FROM EXCEL FILE WITH DUPLICATE ITEM NUMBERS DOES NOT GET ALL ADDED IN WEB CLIENT

Root Cause: It is caused by the Blue One Change.

Resolution: Leverage 9.2.2 behavior.

Verification: .

1. Prepare a file, e.g. an Excel spreadsheet, that has a list of Item numbers that contain duplicates.

2. In Java Client, have the Smart Rule for DuplicateItemNumbers be set to Warning.

3. In Web Client, go to the redline BOM tab of an Affected Item and click the Add button.

4. Copy the values from the Excel file and paste them into the redline BOM table.

5. Paste the copied items again.

6. In Java Client, go to the redline BOM tab of an Affected Item and click the Add button. [IS THIS CORRECT?!]

7. Paste the copied items to redline BOM tab.

Results:

4. All the duplicate rows are added with the warning.

5. All the duplicate rows are added with the warning.

7. All the duplicate rows are added with the warning.

14633176

SR 3-6204749211

Item & BOM

Issue: COPY AND PASTE OF AFFECTED ITEMS FROM ONE CHANGE TO A CHANGE ON A DIFFERENT WINDOW/TA

Root Cause: The copy/paste functions generate bad data while crossing windows.

Resolution: Prevent the behavior while crossing windows.

Verification: .

1. Create a Part, P001, with BOM, P002 and P003.

2. Create a Change, C001, against P001.

3. Create a Part, P004, with BOM P005.

4. Create a Change, C002, against P004.

5. On this first session, go to C002's Affected Items tab, select row of P004, then go to redline BOM table.

6. Open the second session and go to the Redline BOM table of C001's P001.

7. Select a row of P002 and click More > Copy.

8. Go back to the first session, Click More > Paste on the redline BOM table.

Result: The warning "Performing copy/paste between multiple Agile PLM windows is not supported. Please perform copy/paste within the same Agile PLM window." appears.

9. Open C002 from the Recently Visited section and go to the redline BOM table of P004.

10. Click More > Paste.

Result: In Step 10 above, the user can paste successfully and P002 was added to the redline BOM table of C002's P004.

11. Go to the second session, select a row in P003 and click More > Copy.

Result: The warning "Performing copy/paste between multiple Agile PLM windows is not supported. Please perform copy/paste within the same Agile PLM window." is displayed.

12. Open C001 from Recently Vsited, then select the row from P003, click More > Copy.

Result: The user can copy successfully and a message "1 row has been copied" appears.

14657823

SR 3-6093818031

Item & BOM

Issue: UNKNOWN ERROR WHEN ADDING AN ATTACHMENT IF PARENT BOM CONTAINS A DUMMY ROW

Root Cause: The dummy row in the BOM table has class id 0, therefore it is unable to get the attribute from class id 0 and attribute id.

Resolution: Corrected the code to make sure that the blank row in the BOM table does not cause a null point exception.

Verification: .

Case 1:

1. Create Part P001, add P002 as component to P001's BOM tab.

2. In P001's BOM tab, click Add, and input a new Part number which does not exist in Agile, for example, HELLOPART001. Press Enter, Agile displays an alert like the following

Warning ? HELLOPART001

Items HELLOPART001 does not exist

Continue Cancel

-

3. Click Continue, HELLOPART001 is added to the BOM tab, but there is a red question mark in front of HELLOPART001.

4. Restart the Agile server and log in to Web Client

5. Go to P001's BOM table and open P002 to add an attachment.

Result: The attachment can be added successfully

Case 2:

1. Log in to Java Client.

2. Create a Part P00001.

3. Go to the BOM tab and add a blank row.

4. Go to the Title Block tab and then go back to the BOM tab. The BOM tab displays normally without any error.

5. Log in to Web Client and check P0001's BOM tab.

Result: The BOM tab displays normally.

6. Log in to Java Client, create a Change C0001, and add P0001 to the Affected Items tab.

7. Select P0001 and add a blank row for the Redline BOM.

8. Open P0001 and go to the BOM tab.

Result: The BOM tab displays normally.

9. Log in to Web Client and check P0001's BOM tab.

Result: The BOM tab displays normally.

10. Check the Redline BOM table of C0001.

Result: The Redline BOM table displays normally.

14688715

SR 3-6181749371

Searches

Issue: DUPLICATE REPLIES FIELD DISPLAY IN SEARCH AFTER APPLYING PATCH 9.3.1.1.177

Root Cause: This issue is caused by HF49. The tab 'replies' property is changed, and this affects the search replies field display. The tab 'replies' is added with a special handler, and then the tab is added again with the other normal tabs. Therefore it is added twice and resulting in the duplicate.

Resolution: Recommend the adding as other normal tabs.

Verification: .

1. Create 3 Discussions with a few replies.

2. Navigate to Advanced Search and select the subclass, Discussion, with Object search.

3. Click on the attribute search list and check for the duplicate data display of the Replies tab.

Deviation: Check the same in the Dashboard optional tab search criteria and Advance Search criteria.

Result: The Replies tab attributes are displayed only once in list.

14707991

SR 3-6211725411, 3-6367076771

Searches

Issue: ADVANCED SEARCH 'SAVE' FUNCTION OVERWRITES CRITERIA OF EXISTING SEARCH INSTEAD OF SAVING AS ANOTHER SEARCH

Root Cause: Design change

Resolution: Run a search to get the latest result after saving or using save as.

Verification: .

1. Log in to Web Client.

2. Do an Advanced Search for Items > Parts > Object Search, set the criteria as: Title Block.Lifecycle Phase In Production. Click the Save button to save the search as LC-P.

3. Do not leave the search page. Change the attribute and set the criteria as: Title Block.Product Line(s) Is Not Null.

4.Click Save >Save As o save the search as PL.

Result: The user is able to successfully save the search to another search by clicking Save As. The existing search does not get overwritten the search results are refreshed with the new criteria.

14722601

SR 3-6250208211

Standard Reports

Issue: AGILE CLASSES REPORT SHOWS MIN VALUE AS INFINITY

Root Cause: The Report server side uses the max value as the min value.

Resolution: Corrected the code so that it uses the min value.

Verification: .

1. Log in to Java Client as admin.

2. Go to Admin > Classes > Items > Part, set Min Value =1.0 for Numeric attributes Numeric5~10 on the Page Three tab.

3. Go to Admin > Classes > Items > Document, set Min Value =1.0 for Numeric attributes Numeric5~10 on the Page Three tab.

4. Log in to Web Client as admin.

5. Open the Agile Classes Report, click Execute, add the Items class for the report, click Finish.

6.Check the Min Value for Numeric attributes Numeric5~10 on the Page Three tab on the Part and Document subclasses.

Result: The Min Value appears as 1 in the Agile Classes Report result for the Numeric attributes, Numeric5~10, on the Part & Document Page Three tab.

14748795

SR 3-6424181446, 3-6256041211, 3-6897524461, 3-7038812591

Changes

Issue: UNKNOWN NUMBER: OBJECT DOES NOT EXIST

Root Cause: When removing a relationship in an object, there may be related data in table SUBSCRIPTIONS that need to be removed, but do not get removed successfully, which results in bad data. The bad data leads to this issue.

Resolution: Updated the logic for removing related data in table SUBSCRIPTIONS; provided a script to remove the bad data.

Verification:

1. Create 2 new Change Orders C00001 & C00002, and assign Default Change Orders to them.

2. Drag C00001 to the Relationships tab of C00002.

3. Select the row for C00001 in this tab and click Edit Rule, set it to: When C00002 is Submitted, set C00001 to Submitted, then click Save button.

4. Remove C00001.

5. Hard-delete C00001.

6. Select C00002, change its status to Submitted.

Result: The user can change C00002's status to Submitted successfully without any error.

14763697

SR 3-6310271771

Web Client

Issue: WHERE USED SEARCHES RETURN NO RESULTS

Root Cause: When a Where Used Search is executed, the code sets the incorrect value (name instead of id) to the object which is sent for a privilege check.

Resolution: Set the id instead of the name.

Verification:

1. Log in to Web Client as morganm.

2. Run a Where Used Search with the following criteria: Items > Parts > Where-used All Levels Latest Released Revision Only Title Block.Number Equal To 10-000002.

3. Click Search, check the search result.

4. Execute the Where Used Report.

5. Add Part 10-000002 to the report, check the report result.

Result: Agile returns all Where Used items for 10-000002 in the search and report result.

14805185

SR 3-6323121051

Web Client

Issue: MANUFACTURER TAB SEARCH IS NOT GIVING PROPER RESULTS.

Root Cause: This issue is caused by Base on Table/Base on Row behaviors, in 932.

Resolution: We have already handled both, so in 933, this issue will disappear from behavior Base on Row.

Verification:

1. Log in to Java Client as admin.

2. Go to the Preference setting and do search based on: row.

3. Log in to Web Client.

4. Create the following data:

3 parts and 3 Manufacturer (Mfr) names

Part p00583 with 3 manu1 (volvo), manu2 hyundai) and manu (Mahindra)

Part p00584 with manu1 (Volvo) and manu2 (hyundai)

Part p00585 with manu1 ( volvo)

Case 1:

1. Items > Parts Attribute: Mfr.Name contains Volvo AND Item.number contains p0058.

Result: 3 Rows are returned:p00583, p00584, p00585.

2. Move Mfr. Name into the Displayed field in the format options.

Result: 3 Rows are returned: p00583, p00584, p00585 with Mfr Name Volvo.

3. Remove Mfr.name from the Displayed field.

Result: 3 Rows are returned: p00583, p00584, p00585.

Case 2:

1. Items > Parts Attribute: Mfr.Name does not contain Volvo AND Item.number contains p0058.

2. Move Mfr.name into the Displayed field in the format options.

3. Click search

2 Rows returned--> p00583 with Mahindra and hyundai 1 row returned --> p00584 with Hyundai Remove Mfr.name displayed.

Result: 2 Rows returned--> p00583, p00584

Case 3:

1.Items > Parts Attribute: Mfr.Name does not contain Mahindra AND Item.number contains p0058.

2 Rows returned > p00583 with Volvo and hyundai

2 row returned > p00584 with Hyundai and Volvo

1 row returned > P000585 with Volvo

2. Remove Mfr.name from the Displayed field in Format:

Result: 3 Rows returned > p00583, p00584, p00585.

Case 4:

1. Items > Parts Attribute: (Mfr.Name does not contain Volvo AND Mfr.Name does not contain hyundai) AND Item.number contains p005 Click search button: Only P00583 is displayed in the search results.

14833939

SR 3-5630218036, 3-6141335031, 3-7189265881

Changes

Issue: AFFECTED ITEMS TAB HAS A GREY DOT INDICATING AN ACTIVE QUALITY ISSUE BUT THE QCR IS CLOSED

Root Cause: There is bad data in tables Item and Rev.

Resolution: For tables Item and Rev, update the PSR and QCR flags to 0 if there is no opening PSRs/QCRs.

Verification: .

1. Go to Web Client as admin.

2. Open C040512, go to its Affected Items tab, and check some Affected Items: QW00415 QW00512 QW00524 QW00562 QW00779

Result: All of the Affected Items, QW00415 QW00512 QW00524 QW00562 QW00779, are without an indicator since their related PSRs/QCRs were closed.

3. Create a related QCR for QW00415: Audit001 with workflow:CAPA-002, and route it to Verification closed status.

4. Go to C040512's Affected Items table, check the status of QW00415.

Result: QW00415 has the indicator that it still "Has Quality issue".

5. Close QW00415's related PSR/QCR. Check QW00415 in C040512's Affected Items table.

Result: The indicator is not there anymore.

14835608

SR 3-6361522871

Export (PC)

Issue: AN EXTRA ATTRIBUTE NAME APPEARS IN AXML OUTPUT

Root Cause: When an ECO is exported to AXML if the Affected Item's redlined attributes has no former value and export empty tags.

Resolution: We removed the empty tags, which allowed us to validate our AXML file.

Verification: .

Precondition: Enable MFR.tab Numeric01

Steps:

1. Create a Part, P00054.

2. Add a Manufacturer Part to the Manufacture tab.

3. Do not give any values in MFR.tabNumeric01.

4. Create a Change, C00013.

5. Select the Affected Items tab on the Change.

6. Do not give any values in redline Manufactures - MFR.tabNumeric01.

7. Export the change into AXML format in redline mode.

Result: In Manufactures, MFR.tabNumeric01, an empty tag is not displayed in AXML export format in redline mode.

15842026

SR 3-6408593241

Searches

Issue: CANNOT USE $TODAY IN ADVANCED SEARCH FOR CHINESE USER

Root Cause: $TODAY is translated into a local string, but the string is not recognized in our code.

Resolution: Ignore L10N translation for $TODAY.

Verification: .

1. Log in to Web Client as a Chinese user.

2. Create a Change Order,:ECO001, and release it.

3. Do an Advanced Search: Change > Change Orders > Cover page.Date Release > Equal to > $today.

4. Run the search.

Results:

2. $today can be input successfully.

3. Change Order, ECO001, meets the search criteria.

15864744

SR 3-6424181446

Workflow

Issue: UNKNOWN ERROR: "OBJECT DOES NOT EXIST" WHEN WE TRY TO CHANGE THE STATUS OF

Root Cause: When removing a relationship in an object, there may be related data in table SUBSCRIPTIONS that needs to be removed, but is not removed successfully. This generates bad data, which leads to this issue.

Resolution: Updated the logic to remove related data in table SUBSCRIPTIONS.Provided script to remove bad data.

Verification: .

1. Create 2 new Change Orders, C00001 & C00002, and assign Default Change Orders for them.

2. Drag C00001 to the Relationships tab of C00002.

3. Select C00001 and click Edit Rule, set it as: When C00002 is Submitted, set C00001 to Submitted, then click Save.

4. Remove the C00001 row from the tab.

5. Hard delete C00001.

6. Select C00002, change status to Submitted.

Result: The status is changed to Submitted successfully.

15931237

SR 3-6803286991, 3-5973184831

Web Client

Issue: SEARCH TYPE LISTS THAT INCLUDE AN EQUAL SIGN

Root Cause: N/A

Resolution: N/A

Verification:

1. In Java Client, create a list with Display Type of Search.

2. Add values that have an equal sign (=) and a non-numeric value following it. For example:

51027 - Mother = layers

51027 - Mother = 28

3. Add this list to an attribute. For example, Parts > Page Two > List01.

4. In Web Client, create an object that has the attribute from step #3..

5. Search for and add "'51027 - Mother = layers" to the attribute.

6. Click Save.

Result: The value can be saved successfully with selection of "51027 - Mother = layers".

15935038

SR 3-6416632881

Administration/Configuration

Issue: REPORT/SEARCH DATE ATTRIBUTE VALUES ARE NOT EXPORTED CORRECTLY

Root Cause: The DateFormat of export is written to date-time default, and is not controlled by Java Client.

Resolution: Added a condition to control dateformat for export.

Verification: .

1. Log into Java Client as admin.

2. Go to Admin > Classes > Parts, create a new subclass, Program Change Request Item.

3. Open Program Change Request Item, enable its Page Three, and enable the following attributes:

Date 13 - Compile Date

Date 14 - Target Date

Date 15 - Need By - P3. Set Date Only for their Date Time Format field

4. Create two privileges:

read Program Change Request Item(move all attributes to applied to field)

modify Program Change Request Item(move all attributes to applied to field)

5. Add these two privileges for admin.

6. Log in to Web Client as admin.

7. Click My Settings > Preferences, set Time Zone as (GMT-08:00) Pacific Time (US/Canada), Tijuana.

8. Create several Program Change Request Items, and set values for p3. Compile Date;Target Date;Need By - P3:

PCR1,04/08/2013; 04/20/2013;05/08/2013

pCR2,04/28/2013; 05/08/2013; 05/18/2013

9. Do an Advanced Search: Items > Program Change Request Item >Title block.Number > start with > PCR, and move p3. Compile Date; Target Date; Need By - P3 to the output field, run the search.

10. Export search results to an Excel file, check the search results in the Excel file.

Results:

9. PCR1 and PCR2 can be found and their p3. Compile Date; Target Date; Need By - P3 were displayed correctly in the search results table.

10. Search results in the Excel file are the same as they are in the UI. Values for date attributes are displayed correctly.

PCR1,04/08/2013; 04/20/2013;05/08/2013

pCR2,04/28/2013; 05/08/2013; 05/18/2013

16238888

SR 3-6717619161

Web Client

Issue: STOP SHIP INDICATOR STAYS ON ITEMS AFTER RESUMED STATUS

Root Cause: When releasing a stop ship/deviation, the Affected Item's flag will be updated accordingly, but there is a defect when the workflow is no Released status. This code defect leads to bad data.

Resolution: Fix the code for updating an Item's flag when releasing a stop ship/deviation. Provide a script to remove bad data.

Verification: .

1. Log in to Java Client.

2. Create a new workflow by using Save As on the Default Stop Ships workflow.

3. Delete the Released status in the new stop ships workflow and check the Resumed to be available in CCB next status option.

4. Create change status privileges for the newly created stop ships workflow.

5. Log in to Web Client.

6. Create a stop ship and use the newly created stop ships workflow.

7. Add an Item to Affected Items.

8. Change the stop ships to resume status.

9. Check the Item's Changes tab.

Result: The Stop Ships indicator (Red square) is no longer on the Item's Changes tab.

16561893

SR 3-3460136761

Web Client

Issue: CONSOLIDATED BOM REPORT DISPLAYS TWO RECORDS OF SAME BOM ITEM

Root Cause: There is a defect in the Consolidated BOM Report which made some records get displayed twice.

Resolution: Fix defect.

Verification: .

1. Log in to Web Client as admin.

2. Run a consolidated BOM report.

3. Add part 9604316-WT and go with the default layout, and display all levels.

Result: Consolidated BOM report displays one record for the BOM item.

16582040

SR 3-6783151261

Changes

Issue: PRINTING FROM AGILE DEFAULTS TO GMT RATHER THAN EASTEN LOCAL TIME

Root Cause: Incorrect logic is used to print the date value.

Resolution: Changed the logic to take Date Time Format into consideration.

Verification: .

1. Log in to Java Client as admin.

2. Go to Admin > Classes > Corrective and Preventive Actions > Cover Page.

3. Change the Date Originated, Date Assigned and Date Released, Final Complete Date, and Date Time Format from Date and Time to Date Only.

4. Click Save.

5. Log in to Web Client as admin.

6. Create a CAPA and release CAPA, ensure that the dates are as follows:

Date Originated:05/16/2013

Date Released: 05/16/2013

Final Complete Date:05/16/2013

7. Print the CAPA with Cover Page tab only.

8. Check the date attributes information.

Result: All the dates are as below:

Date Originated:05/16/2013

Date Released: 05/16/2013

Final Complete Date:05/16/2013

16770366

SR 3-6933795813

Java Client

Issue: AGILE LOGS GROW FASTER

Root Cause: Class WeblogicServerAdapter.java does not implement Serializable.

Resolution: Make WeblogicServerAdapter.java implement interface Serializable

Verification:

1. Create Part, add BOM & Manufacturer Parts.

2. Create an ECO against the part and redline edit BOM & Manufacturer Parts

3. Release ECO.

4. Run the BOM Explosion Report for the Part.

5. Export from the generated report.

6. Repeat for different parts with different BOM/Mfr Parts and different ECOs.

7. Check the application server console/log.

Result: There is no error like: java.io.NotSerializableException: com.agile.admin.vendor.weblogic.WeblogicServerAdapter

## 3.2 Product Governance & Compliance

10183262

SR 3-2163043821

Affected Objects/Admin

Issue: "UNKNOWN NUMBER: OBJECT DOES NOT EXIST?" ERROR IN PART GROUP

Root Cause: When you attempt to change Manufacturer Name, the code does not update the Manufacturer Name in the Parts tab of the Part family. When you load Manufacturer Parts and search the Manufacturer by the old Manufacturer Name, it throws the "object does not exist" error.

Resolution: If the system cannot search for and find the Manufacturer by the old Manufacturer name when loading Parts, set the same value from the Manufacturer Name of the Manufacturer Part object.

Verification:

1. Log into Web Client as admin.

2. Create a Manufacturer, MF1.

3. Create a Manufacturer Part, MFP1 with MF1.

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

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

6. Go back to PF1's Parts table.

7. Use Save As to save PF1 to a new Part family, then open PF1 again.

Results:

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

6. MFP1 with its related manufacture, MF1-new name, displays correctly in the Parts table.

7. PF1 can be opened successfully and its Parts table can be accessed successfully.

12978846

SR 3-2163043821

Standard Reports

Issue: ISSUE WITH OOB COMPLIANCE REPORT

Root Cause: This bug is reproducible when the report log is set as 'info', and you select multi-specifications. The error message is caused by the List overflowing when running the logItemInfo which logs some information. It is a code issue.

Resolution: Overwrite the function logItemInfo in the BOM compliance report and ensure that the list does not overflow when this function is run.

Verification:

1. Log in to Web Client as admin user. Set the BOM Compliance report log as 'info' on logging configuration.

2. Execute the BOM Compliance report.

3. Select one Item such as 1000-02.

4. Select two or more Specifications.

5. Finish the report.

6. Go to the report result page and notice there is more than one page.

7. Select page number or click the next page button to go to next page.

8. Check the result.

Result: There is no unexpected error such as "ERROR: An unexpected error has occurred. Please contact your system administrator. Error Detail: Index: 1, Size: 1' pop up."

14281969

SR 3-5852136311

Declaration

Issue: USER GROUP WITHOUT COMPLIANCE MANAGER LIST IS ADDED AS COMPLIANCE MANAGER VIA SDK

Root Cause: When setting the compliance manager via SDK, the code does not check if the User or User Group is in the compliance manager list.

Resolution: Now we check the Change Analyst. If the User or User Group are not added to the Change Analyst list, there are not sufficient privileges to add it. For the compliance manager, we follow the same behavior as the change analyst.

Verification:

1. Create one User Group, ug1.

2. Do not assign Compliance Manager List to Lists on ug1's General Info page.

3. Create one Declaration, decl1.

4. Run SDK to add ug1 as Compliance Manager for decl1.

Result: The User Group without a Compliance Manager List is not allowed to be set as Compliance Manager by SDK.

14636446

Standard Reports

Issue: BOM COMPLIANCE REPORT DOES NOT SHOW THE BOM ATTRIBUTE VALUES

Root Cause: Although the BOM's attributes can be selected, the code does not handle these attributes and does not show the BOM attributes' values.

Resolution: Add a function to handle BOM attributes.

Verification:

1. Log in to Web Client as admin.

2. Go to Standard Report > Compliance Reports.

3. Open the BOM Compliance report and click execute.

4. Create a new layout named abc, in format, and select BOM attributes under Item.

5. Click Next and add an Item.

6. Click Next and add a Specification.

7. Click Next and apply the following settings: BOM Level to All Levels, Display Excluded Items to No, Run Compliance Rollup (For Internal Specification Only) to No.

8. Finish the report and check the result.

Result: All of the BOM structures display fine with the correct value in the Compliance and BOM tables.

15846184

SR 3-6243563521

Averify

Issue: FIX FOR AVERIFY AGIL-00155025 TEST CASE

Root Cause: For one composition of a Part that uses the Substance name cannot judge if the part has a duplicate substance.

Resolution: Since Substance id is unique, we changed the code to use substance id to determine if a Part has a duplicate substance.

Verification:

1. In the 933 Agile database, make one composition of a Part to have the same substance_name with different substance_id.

2. Run Averify 1.7.5 on the datatbase.

3. Check if the AGIL-00155025 error exists in the oracle_averify_report.log.

Result: There is no AGIL-00155025 error in the oracle_averify_report.log.

16456230

SR 3-6893929861

Declaration

Issue: REACH/EXTERNAL ROLL UP DOES NOT SUPPORT DECIMALS AND DOES NOT PROVIDE MASS FIGURE

Root Cause: The quantity in fact_table (for ondemand) and fact_table_task (for task) do not support decimals.

Resolution: Change the quantity's type to number (18,2) to support 2 bit decimals.

Verification:

1. Log in to Web Client as admin.

2. Create two Parts, P1 and P2. Open P1 and add P2 as BOM. Set mass for P1=10g, P2.mass=1g.

3. Set Qty as 1.475 and Save.

4. Create an external Specification with Lead with Threshold PPM=1000.

5. Create a Composition for P2 against above external specification as follows:

Substance mass declared PPM

Lead 1100

Al 0.999999

6. Open P1 and add the external Specification and do an external rollup.

7. Check the Substance table for the external Composition.

Result: Support Qty as decimals. In this case, the mass was calculated for Lead=0.0011*1.47=0.001628g

## 3.3 Product Cost Management

7572442

SR 2-2001861, 7255965.992

Standard Reports

Issue: ASSEMBLY COST REPORT DOES NOT DISPLAY LIFECYCLE STATUS WHEN CONFIGURED IN LAYOUT

Root Cause: Does not correctly resolve Lifecycle Phase.

Resolution: Add method to resolve Lifecycle Phase correctly.

Verification:

1. Create an Assembly.

2. Create a Sourcing Project and add the Assembly.

3. Create an RFQ and open it to suppliers.

4. Get a response from suppliers.

5. Do Set As best and do a cost rollup.

5. Click on Sourcing Reports > Default Layout and add the Lifecycle Phase attribute.

6. Run the ACR Report and validate the Lifecycle phase field.

Result: The report displays all fields correctly.

13627519

SR 3-5178646691, 3-6241119301

Searches

Issue: NON-REDLINED PRICELINES ARE NOT DISPLAYED IN ADVANCED SEARCH RESULT ON ITEM.PRICES

Root Cause: When you do an Advanced Search against Object Item and display some attributes under Prices in the search result, only redlined prices are returned, because only the redlined price and the latest released PCO number is stored into column PRICELINE.CHANGE_IN. Otherwise, it's stored as 0.

Resolution: We changed the join condition from PRICE_RELATIONSHIP.DEFAULT_CHANGE =PRICELINE.CHANGE_IN(+) to PRICE_RELATIONSHIP.DEFAULT_CHANGE >= PRICELINE.CHANGE_IN(+). With the change, search lists all prices, not just the latest released. The behavior now is the same as Advanced Search against object Price. it also lists all the prices.

Verification:

1. Create a Sourcing Project Number of Periods: 3, Period Type: Quarterly.

2. Add a Part to the Sourcing Project.

3. Create an RFQ and open it to supplier1 for quoting.

4. Respond to the RFQ as the supplier1. Enter pricing as follows:

Q1 = 7.5;Q2 = 6.5;Q3 = 5.5

5. Submit responses back to the buyer.

6. Publish the prices to PCO and Release.

7. Create a search:

Items | Parts Number | Equal To | Part_Number

Format output fields to include: Number, Price Effective From Date, Price Effective To Date, Price Type, Supplier, and Total Material Price.

Note that all prices are displayed.

8. Perform a Save As from the Sourcing Project.

9. From Actions do Modify Price Scenarios.

10. In the Modify Price scenarios period, delete the Q1 price scenario and hit OK.

11. The number of periods is now 2.

12. Create an RFQ and open it to supplier1 for quoting.

13. Respond to the RFQ as the supplier1 entering pricing: Q2 = 6;Q3 = 5.

14. Submit responses back to the buyer.

15. Publish the prices to another PCO Redline mode: Only add and modify data (do not delete it) and Release the PCO.

16. Run the search in step 7.

Result:

Three pricelines appear in the search results with the Pricing (Q1=7.5,Q2=6 and Q3=5). It displays both redlined and non-redlined pricelines.

14199439

SR 3-5679482669

Sourcing Project

Issue: THE LIFECYCLE PHASE FIELD IN THE ANALYSIS TAB OF ONE PCM SOURCING PROJECT IS BLANK

Root Cause: An incorrect method is used to analyze the Lifecycle Phase, which is created at the class and subclass level.

Resolution: Use the correct way to analyze lcp, which is created in class and subclass level.

Verification:

1.Create a Sourcing Project.

2. Create Items with AML in the Sourcing Project.

3. Publish them to the Item Master.

4. Update from the Item Master.

Result: The Lifecycle Phase is pulled in for Items and AMLs.

5. Create an ECO and redline Items with a custom Lifecycle Phase. Redline the Manufacturer by adding an MPN with a new custom Lifecycle Phase and release the ECO with Rev1.

6. Navigate to sourcing and perform an update from the Item Master.

Result: The Lifecycle Phase values are pulled correctly into the Sourcing Project tab for Items and MPNs with the correct Rev.

14395814

SR 3-5992676121

RFQ/Response

Issue: VALID UNTIL AND MATERIAL PRICE MISSING FOR REQUIRED FIELDS

Root Cause: This issue was triggered when an attribute's name contained a semicolon. It was fixed in 932. A semicolon cannot be in an attribute name, so the semicolon was removed.

Resolution: Verify when update display name with the semi-colons in java client

Verification:

1. Create a Sourcing Project and save it.

2. On the General Information page, Notice the Response Required Fields: Valid Until and Material Price.

3. Edit the Response Required Fields by selecting the Check/Uncheck All to select all attributes and Save.

4. Edit the Response Required Fields again.

Result: By default, the Material Price and Valid Until date should be selected.

14415785

SR 3-5881601051

RFQ/Response

Issue: CREATION OF RFQS VIA SOURCING PROJECTS ERROR

Root Cause: This issue is related to the mapping of filed target cost. Although there are no mapping data set up for the target cost in the database, there is a bit of a gap there to cause the issue and errors are shown on subsequent operations.

Resolution: Change the following settings in Java Client as defined in the Sourcing Project class > Price Detail tab > Target Cost, then click the first blank option listed in the dropdown list and click Save.

Verification:

1. Create an Assembly, with an Item with AMLs and add it to a Sourcing Project.

2. Open the Sourcing Project.

3. Create an RFQ.

Result: The user is able to create an RFQ without any errors.

14573153

SR 3-6126336397

Price/PCO

Issue: ADDING PRICELINE NOTES IN THE FORMAT THROWS ERROR WHILE SEARCHING ITEMS

Root Cause: We currently use the wrong table in the where conditions for attribute ITEM.Prices.PRICELINE NOTES(2000007443). It should be 'PRICE_RELATIONSHIP' while not 'PRICELINE'.

Resolution: Correct to the table used for this attribute.

Verification:

1. Log in to Java Client and open Item > Prices tab.

2. Enable the Price line Notes attribute.

3. Log in to Web Client.

4. Create a Part and create a Price for it.

5. Add a Priceline and edit all the attributes.

6. Do a search on Item and add Prices tab > Price line notes in the Format tab.

Result: The user is able to add Price line notes to the Format tab.

14590137

SR 3-6145688641

Searches

Issue: PRICELINENOTES HAS NO VALUE BY SEARCHING

Root Cause: A property is missing for this flex text attribute.

Resolution: Add this property via script.

Verification:

1. Log in to Web Client.

2. Open a Published Price object and go to its Price Line tab.

3. Edit Price Line Notes and add some text into that field.

4. Go to Advanced Search.

5. Search Price > Published Price.

6. Format > Output, PriceLine.Notes. In the search results, no value is displayed in the PriceLine.Notes field. Export the search results to Excel. There is no value there either.

Result: Displays the PriceLine.Notes field with the data.

14643630

SR 3-6109012371

Searches

Issue: SEARCH FOR PCOS RETURNS NULL

Root Cause: BaseCacheUtil.isTheFlagSetForMultiSelectField may return a wrong result. It first defines an offset

with a default value zero. Then it tries to assign a correct offset value to it, but if none of the conditions matched, the offset will still be zero. Then it returns the flag according to the offset, but the flag in offset zero means it has an attachment. If a Change object has an attachment, it returns true, which is not correct.

Resolution: Modify the return value of the attachment flag so that it is correct.

Verification:

1. Create PCOs with and without attachments.

2. Perform a quick search and validate whether or not the PCOs are returned. Also validate for Advanced Search, as well.

Results: Results should return all of the PCOs (with or without attachments).

16006752

SR 3-6551479921

Price/PCO

Issue: REDLINE MATERIAL PRICE WILL ALSO UPDATE DATE CREATED DATA

Root Cause: On the database side, Agile creates a new priceline record when redline attributes and creation date is current time. The created date also gets changed.

Resolution: Although a new priceline is created, the created time should not change because the user just redlined on previous priceline.

Verification: .

1. Launch Web Client.

2. Create a new Price, PRICE00237.

3. Create a new Price line and Date created value is 12/13/2012 02:01:32 PM CST.

4. Create a new Price Change Order, PCO00040, with this Price line in Affected Prices.

5. Redline Material price from 50 to 30.

Result: The Date Created value should not be changed by the Price Change Order.

16063636

SR 3-6610756711

RFQ/Response

Issue: RFQ SEARCH ON RESPONSE STATUS PROGRESS RESULT 0 ROW

Root Cause: When an RFQ is in Draft status, the data of Response Status.Process does not exist in table RESPONSE_HEADER.

Resolution: Update SQL using left join and right join to avoid this issue.

Verification:

Preconditions: The pricing is done on Manufacturer Parts. The Manufacturer in the AML tab is listed on the Manufacturer tab of the corresponding Supplier.

Steps:

1. Create a new Sourcing Project.

2. Add Items to be quoted.

3. Create an RFQ against those parts. Do not open the RFQ.

4. Navigate to the Response tab and edit the response lines using Edit Response lines.

5. Go to the Response tab and verify that the progress shows 100.

6. Notice that the RFQ is still in Draft mode.

7. Create an Advance Search.

8. Criteria: Progress equal to 100.

Result: The search results should display all of the RFQ with progress equal to 100.

16582272

SR 3-6928908591

PCM SDK

Issue: AGILE PCM SDK ITABLE GETREFERENT FOR PRICES ALWAYS RETURNS PRELIMINARY REVISION

Root Cause: The change key of the referent Price object is not set correctly.

Resolution: Set the change key before retrieving the revision from referent Price object.

Verification:

1. Create one Item, p1, or Manufacturer Part, mfrp1.

2. Create one Published Price, price1, on p1/mfrp1.

3. Create one PCO on price1.

4. Release PCO with new version 1.

5. Load the Prices table on p1/mfrp1.

6. Using SDK, get revision on the referenced object for price1:

>IRow pricesTableRow = (IRow)pricesTableIter.next();

>IPrice price = (IPrice)pricesTableRow.getReferent();

>String refRevision = price.getRevision();

Result: SDK returns the correct revision "1" for the referenced object on Price.

## 3.4 Product Quality Management

13109574

SR 3-4722842691

Corrective Action

Issue: WRONG ERROR BANNER MESSAGE IN PROBLEM REPORT CLASS

Root Cause: The attribute name is hard-coded as Expected Resolution Date in the property file for notice messages.

Resolution: Parameterize the attribute name in the message since the user may update it.

Verification:

1. Log in to Java Client as admin.

2. Go to Classes > Problem Reports > Cover Page, open the attribute Expected Resolution Date, change its name to be Supplier Response Due Date.

3. Create a Problem, PR001, enter a date prior to today, such as:2011/12/31, click Save.

4. Enter a date greater than today, such as 2014/01/01, click Save.

Results:

3. The system prompts an error message: "Invalid Supplier Response Due Date. The Supplier Response Due Date must be later than the Date Originated."

4. The new date can be set successfully for Supplier Response Due Date.

## 3.5 Product Portfolio Management

10630389

SR 3-2571225811

Administration/Configuration

Issue: DEFAULT NOTIFIER COULD NOT BE DISPLAYED IN NOTIFY UPON ENTRY WINDOW

Root Cause: The subclass is not included when a request is passed for a criteria check.

Resolution: Find a way to carry over subclass information with the request.

Verification:

1. Log in to Java Client.

2. Navigate to WorkFlow and create a New Workflow with a new criteria > Gate Subclass.

2. Add User A in the Notify Upon Entry field for Open status of a New workflow.

3. Navigate to the Web Client and create a Program with some child objects.

4. Assign a newly created workflow for the gate object.

5. Change the status of the Gate to Open.

Result: In the Change status window, the Default notifier is displayed for the new criteria Gate subclass.

11724767

SR 3-2057117387

Web Client

Issue: LABOR COST - BUDGETED IS NOT UPDATED WHEN A DELEGATED OWNER IS ASSIGNED % ALLOCATION

Root Cause: The labor cost was not set while approving the delegated owner request.

Resolution: Set the labor cost appropriately while approving the delegated owner request.

Verification:

1. Create two resource pools: pool1 and pool2. Assign jenny1 to pool1 and jenny2 to pool2.

set pool 1 with labor cost: $60

set pool 2 with labor cost: $80

2. Log in as admin and create a one level project.

3. Add jenny1 to the Team tab as 100% resource.

4. Go to the Team tab, make sure jenny1 is assigned from pool1.

5. Go to the General Info page, see Budgeted Labor Cost: 480 USD.

6. Go to actions > delegate, add user jenny2 and delegate the owner to jenny2.

7. Log in as user jenny2, go to the My Assignment tab and accept the delegation.

8. Refresh the Team tab. Jenny2 is now added to the Team tab and auto-assigned from pool2, with the Product Manager role, add the Program Team Member role to jenny2.

9. Modify the % allocation to 100% for jenny2.

10. Expect to see the budgeted cost should rollup, but it does not.

11. Re-delegate the owner to admin user.

12. Log in as admin, go to the My Assignments tab and accept the delegation.

13. Go to the Team tab, remove jenny2 from the list.

14. Add jenny2 back to the list as a team member with 100% allocation.

15. Go to the General Info tab. The budgeted cost has been rolled up to Budgeted Labor Cost:1,120 USD.

11734045

SR 3-2873682071, 3-5133200091

Discussion & Action Items

Issue: UNABLE TO FILTER OR PRESENT DISCUSSION TYPES PROPERLY

Root Cause: The Discussion table's Type attribute was pointing to the incorrect list. Additionally, the discussions must be looked up by the ATT_ACTIVITY_DISC_NUMBER of the discussion and not by the Type attribute.

Resolution: Modified the code to use the ATT_ACTIVITY_DISC_NUMBER instead of the Type to look up the discussions. Also, point the ATT_ACTIVITY_DISC_NUMBER attribute to AdminType.LIST_DISCUSSION_REF.

Verification:

1. Go to project > Collaboration tab.

2. Click Personalize, a page of "Table Personalization" displays.

3. Click the Filter tab, select Type, In.

Result: The user is be able to select Type and save. The system allows the user to filter by type, and save the view with type.

12318807

SR 3-3313475201

Gantt Chart

Issue: PPM: DASHBOARD MANAGEMENT CONFIGURATION USING ADVANCED SEARCH BY GATE IS NOT WORKING

Root Cause: The delimiter is not used appropriately when handling the date type attribute.

Resolution: Refactor the delimiter usage for the BETWEEN operator.

Verification:

1. Log in to Java Client.

2. Configure Dashboard Management to create a new Dashboard General Info.Actual End Date Between check the Prompt.

3. Go to user privileges, click Dashboard Tabs to move the new Dashboard to AppliedTo.

4. Log in to Web Client.

5. Click the Dashboard Tab.

6. Go to the newly created Dashboard.

Result: The Dashboard should show the exact search condition and accurate search results.

12768751

SR 3-3997650481

Roles & Privileges

Issue: FIELDS DISAPPEAR WHEN USING ENFORCE FIELD LEVEL READ PRIVILEGE.

Root Cause: We need to pass the subclass for the user for a privilege check as the criteria is at the subclass level.

Resolution: Added code to pass the subclass of the user for a privilege check.

Verification:

1. Log in to Java Client.

2. Enable Page Two tab for Admin > Classes > Users Class.

3. Enable attributes from the Users Class > Page Two > User Interface Tab > Attributes: Page Two > List11 > Link to No Values List Name.

4.|Admin |Data Settings |Criteria |All Users List11 Test1 (User.PageTwo.List11 Ln Test1) (subclass level)

5.Create two privilege masks:

a. Discover All Users List11 Test1

b. Read AllUsers List11 Test1

6. Assign the Privilege masks to Role No Privilege.

7. Assign the role to users tpk, kgh.

8. Create a criteria as All Programs Subclass.

9. Create a privilege mask for Create using the criteria "All programs Subclass". Assign to No Privilege role.

10. Create a privilege mask for Discover using the criteria "All programs subclass". Assign to No Privilege role.

11. Create a privilege mask for Read using the criteria "All programs subclass" (Applied to field having all the values). Assign to No Privilege role.

12. Assign the Enforce Field level Read privilege and Display no privilege fields to the role No Privilege.

13. Log in to Web Client as user kgh/agile.

14. Create a Program named Program1.

15. Log in to Web Client as user tpk/agile.

16. Execute a Quick Search as Program1. Owner field shows no privilege.

17. Remove the Display No privilege Fields from the No privilege Role.

18. Log in to Web Client as user tpk/agile.

19. Quick Search program1.

20. The Owner field is not available.

Result: The Owner field should display the created user name.

13415935

SR 3-5688383277, 3-3741274611, 3-3741274611

Administration/Configuration

Issue: NOTIFICATIONS IN PPM UNRELIABLE

Root Cause: We did not check whether or not notifications are enabled when we sent the notifications.

Resolution: Modified the code to appropriately check if notifications are enabled while sending the notifications.

Verification:

Prerequisite: Navigate to Java Client > Admin > Server Settings > Database, and set Notifications to Yes.

1. In Web Client, navigate to a task and send the task to a user and check the email notification. A Notification should appear for the user.

2. Click Action > Delegate on that task and delegate it to a user. Delegation Notification should appear for the user.

3. From Java Client > Admin > Server Settings > Database: set Notifications to No

4. In Web Client, navigate to a task and try to send the same task to another user. The Send option is disabled.

5. Click Action > Delegate on that task and delegate to another user.

Result: The user should not receive any email notifications.

13971557

Dashboard

Issue: DASHBOARD CONFIGURED VALUES ARE NOT RETAINED WHEN WE MODIFY THE CHART

Root Cause: The Dashboard configured values are not retained in the Configure Chart wizard.

Resolution: Modified the code to retain the Dashboard configured values in the Configure Chart wizard.

Verification:

1. Click on Configure and configure with Display Type Chart on the Optional tab of the Dashboard.

2. Configure the Chart.

3. Navigate to some other program and make some changes and save them again. Navigate to Dashboard > Optional tab. The previously configured settings should be retained.

Result: Previous configuration values are retained.

13981935

SR 3-3313475201

Dashboard

Issue: ISSUE WITH CREATING DASHBOARD SEARCHES WITH 'CONTAINS', 'IS NULL', 'IS NOT NULL'

Root Cause: When configuring an Advanced Search with prompt and multiple conditions in a dashboard widget, and the user inputs these prompt values to execute this search, these values are sent to the server. Due to mismatched keys, however, the program is not able to read the corresponding values of the attributes and Save As criteria. Therefore, the correct result cannot be returned and displayed.

If we have "Is null", "Is not null", "Contains", or "does not contain" in the search, the system shows a warning and does not allow us to select that to go to next step. This warning states that these operators are performance-consuming and advises that the user execute this on off-peak time.

Resolution: Recode the key to confirm that we can read the correct and corresponding prompt value of the searched attributes. Then continue executing this search and return these rows to the client UI.

To be consistent between Java Client and Advanced Search the warning suggests that the user run a report on off-peak time, which is not applicable for the dashboard widget. Remove this warning to let a user continue to finish the configuration.

Verification:

CASE 1:

1. Log in to Web Client.

2. Create an Advanced Search, AS1, with multiple search conditions such as: Items with Title Block.Life cycle Phase In Preliminary and Title Block.Product Line(s) CONTAINS ANY with "PROMPT" selected and save this search as Personal Search.

3. Go to Dashboard > Optional tab, configure it to display the table using the new Saved search, enter the prompt value and finish.

4. Check the Dashboard widget to display the search results according to the search criteria prompt value.

5. Reconfigure the same Dashboard widget. Use the same personal search, change the prompt value from Value1 to Value2 and save.

6. Check the refreshed data in the new search result.

Result 1: Reconfiguring the Dashboard widget using the same saved search by giving different prompt values reflects the changed search results as per the new prompt value.

CASE 2:

Configure the Advanced Search with criteria Is Null and save it as Personal Search. Configure the Dashboard widget using the saved search from above.

Result 2: The user is able to configure the Dashboard widget using the saved search having criteria with Is Null operator. No warning is shown to the end user while configuring the Dashboard search. Search results are per the criteria set.

The same is true for the other operators "Is Not Null", "Contains" and "Does Not Contain".

14156044

SR 3-5735326561, 3-6164748551

Search

Issue: ISSUE WITH SIMPLE/QUICK SEARCH FEATURE IN AGILE

Root Cause: The regeneration of CTX indexes are bypassed on every tree update as name, number or description is not modified during the execution of the Health task. However if a SQL statement with any of the 3 columns is fired (which is fired when document is Saved), whether or not the values for these attributes have changed, the CTX indexes ignore these rows during the search unless CTX indexes are synchronized.

Resolution: After all of the tree's health information is recomputed and updated, the synchronization of CTX indexes is invoked. This will ensure that the CTX indexes are regenerated for all of the rows that got updated during the task execution.

Verification:

1. Select Search > Project Searches > Root Level Projects.

2. Select random Projects and Programs to use for a quick search.

Result: All programs get displayed in the quick search.

14194791

SR 3-5808507671

Web Client

Issue: UNABLE TO SET THE SCHEDULE START TIME FOR 12:00 AM

Root Cause: Working and Non-working time periods were not set correctly while configuring the calendar.

Resolution: Modified the code to set the Working and Non-working time periods correctly while configuring the calendar.

Verification:

1. Create a new Project

2. Set the scheduled start time to be 12:00 AM.

Result: The user should be able to set the start date as 12:00 AM.

14241770

SR 3-5879036761

Discussion & Action Items

Issue: REPLY TO DISCUSSION PAGE IS NOT PROPER WHEN WE HAVE MORE THAN 3 USERS IN THE NOTIFY LIST

Root Cause: The selected_container max-width is set to 810 px which is defined in multi_list.css.

Resolution: Added the selected_container max-width style in JSP to set he max-width to 425px.

Verification:

In a Safari browser:

1. Create a new discussion.

2. Enter the Subject and add a few Users to notify (more than 3).

3. Click Save.

4. From the Discussion page, click Reply and check the "Reply to Discussion UI".

Result: The Reply to the Discussion pop-up window displays the fields properly.

14265699

SR 3-5895028151

Administration/Configuration

Issue: USER CAN CREATE NEW ACTIVITIES ON SCHEDULE TAB WITHOUT CREATE PRIVILEGES IN AGILE

Root Cause: If the user is the activity owner, we allow him to create all types of activities, which conflicts with privilege design.

Resolution: If the user is an activity owner, he must accept privilege validation to create subclass of Activity or Gates though the Schedule tab, so comments the specific condition logic that the owner can create all types of activities.

Verification:

1. Log in to Agile as admin, create an activity1.

2. Log in to Agile as userA. UserA has Read/Discover/Modify Activities privilege.

3. Search for activity1.

4. Switch to the Schedule tab, click Add.

Result: UserA should not be able to add any type of activities in the schedule, since he does not have create privilege for any type activities.

14291798

SR 3-5899077034

Web Client

Issue: QUICK VIEW HAS A CLICKABLE AREA THAT IS SIGNIFICANTLY LARGER THAN THE SPEECH BUBBLE

Root Cause: The showQuickViewLink() defined in the ActivitySummaryPage.jsp does not include the 9312 fixes made around standard quick views.

Resolution: Fixed the issue by commenting out the function showQuickViewLink() that is defined in ActivitySummaryPage.jsp. Use the common function in ObjectInfoPalette.js to handle the PPM cases also.

Verification:

1. Log in to Web Client.

2. Go to the Recently visited section. Mouse over the links to produce a Quick View popup.

Result: The position of the Quick View is away from the click point, which allows the original link to be clicked.

14338569

SR 3-5909837171

Search (PPM)

Issue: RELATIONSHIP SEARCH ERROR

Root Cause: It is a SQL formation issue. A table name gets lost when searching the root parent of the Gate.

Resolution: Add a special handler for this solution as Activity.

Verification:

1. Log in to Web Client and create a Program with some child objects.

2. For a Gate object add a Document object in the Content tab.

3. Create an Advanced Search with Items > Documents > Relationship Search > Gate Object.

4. Select the criteria as LifeCycle Phase in Preliminary.

5. Click on the Search button. Search results appears.

6. Click on the Format button and move the Gates.General Info.Root Parent attribute from Hidden fields to the Displayed field and click on the Search button.

Result: Results related to the above search criteria are displayed.

14367357

SR 3-5966668724

Web Client

Issue: VALUE FOR DUE DATE FOR GATE IS NOT DISPLAYED IN UPCOMING ACTIVITIES

Root Cause: Incorrect CMObjectID gets passed for Read Privilege checks.

Resolution: We modified the code to pass the correct CMObjectID for Read privilege checks.

Verification:

1. Log in to Web Client.

2. Create a Program and add a Gate in the Schedule tab.

3. Open the summary view of the Program.

Result: In the Upcoming Activities and Action Items section, the Due Date field of the Gate displays the value as it does when we click on the Gate name. It does not show Insufficient privilege.

14387263

SR 3-5991667721

Web Client

Issue: UNABLE TO ADD ACTIVITY TO A TEMPLATE IN AGILE PPM

Root Cause: Overflow on the Dashboard attributes is not checked during insert of new activities from Gantt.

Resolution: Check the overflow and insert the values appropriately.

Verification:

1. Log into Web Client.

2. Create a template program. Open the Template > Gannt chart.

3. Add an Activity.

Result: The user is able to add the Activity.

14500069

Web Client

Issue: QUICK VIEW DOES NOT APPEAR ON OBJECTS AFTER NAVIGATING TO SUMMARY VIEW

Root Cause: JavaScript error, Used event is not defined.

Resolution: The event is defined in ActivitySummaryPage.jsp.

Verification:

1. Log in to Web Client.

2. Mouse over any object in the Recently Visited section.

3. Quick view appears.

4. Create a project as follows:

Project1

Task1

Task2

5. Navigate back to Project1.

6. Click the Summary, if the object is not already in Summary view.

7. Mouse over on any object link.

Result: Quick view appears as expected.

14516186

SR 3-5991667721

Content Management

Issue: HISTORY DOESN'T TRACK CHANGES TO CONTENT RULES

Root Cause: Update Related Object history is missing.

Resolution: Added the history for Update Related Object.

Verification:

1. Log in to Web Client.

2. Create a Program.

3. Add items in the Content tab.

4. Set a rule for the Item in the Content tab.

5. Edit the rule.

6. Delete the rule.

Result: Rule changes are recorded in the history.

14516354

SR 3-5991667721

Discussion & Action Items

Issue: REPLY BUTTON IS GRAYED OUT AFTER THE USER JOINS THE DISCUSSION

Root Cause: The replies span was not refreshed after the user joined the discussion.

Resolution: Modified the code to refresh the replies span after the user joins the discussion.

Verification:

1. In Java Client, give user1 and user2 privileges to be able to reply to notifications only if they are on the Notify List.

2. Log in to Web Client as user1.

3. Create a Change Order.

4. Create a Discussion and save it on the Change Order's Relationships tab.

5. Add user2 as an approver.

6. Log in as user2. From Workflow Routings, navigate to the Change Order > Relationships tab. open the discussion. Notice that reply button is grayed out. which is expected as the Notify List does not include user2.

7. Click Join to join the discussion. Notice that user2 now appears on the Notify List.

Result: The Reply button is enabled after the user joins the discussion.

14550921

SR 3-7192888681, 3-6065955751

Web Client

Issue: DEFAULT VALUE IS NOT PASSED FROM TEMPLATE WHEN CREATING A PROJECT FROM TEMPLATE

Root Cause: When the user creates a Project from the template or Save As, the required field values are not copied.

Resolution: Modified the code to copy the required field values during the creation of a project from template and Save As.

Verification:

1. Log in to Java Client, from the Classes node, Open Projects > Activities class.

2. Go to the User Interface tab, General Info, Attributes:General Info.

3. Make the Activity Division field visible and required.

4. Log in to Web Client.

5. Fill in the Division field in a project template.

6. Create New > Projects > From Template.

Result: The Division value is brought by default from the Template, in the Create New Project from Template window.

14551149

SR 3-6056485091

User/User Group

Issue: $USER DOES NOT WORK IN PROJECT MANAGER FIELD

Root Cause: $USER based criteria was not supported before. $USERGROUP is supported since 9.3.1.1.12

Resolution: Merged 9.3.1.1.12 to this hotfix and added support for $USER-based criteria in both Java Client and the search module.

Verification:

1. Activities Class > General Info, set Category 7 as Product Manager and point to Users list.

2. Create objects where the Product Manager field is populated.

3. Connect as the user assigned to Product Manager list.

4. Product Manager=$user, No results are returned.

5. When you change the product manager value to $user name, the search returns results.

14583451

Notifications & Subscriptions

Issue: TASK REMINDERS ARE SENT TO INACTIVE USERS

Root Cause: The code does not check whether the user is inactive/deleted. It also does not check the user's Receive Email Notification flag before sending an email for Reminder Tasks.

Resolution: Added the missing checks in the code.

Verification:

In Java Client:

1. Go to the Admin tab.

2. Navigate to Server Settings > Database and fill-in the fields:

Mail From Domain = us.oracle.com

Mail From User = server name

Mail Server External = internal-mail-router.oracle.com

Mail Server Internal = internal-mail-router.oracle.com

3. Edit the user, Demo1, and fill in the Email ID field. (For Ex: XXX@Oracle.com) and set Receive Email Notification as Yes in the Preferences tab in the Web client.

4. Log in to Web Client as Demo1 and create a Program, Project1.

5. In the Team tab, make Demo1 (owner) as a resource by editing percent allocation to 100.

6. From the admin log make demo1 as an inactive user.

In Java Client:

6. Server setting > Task Configuration > Activity Reminder task > Set Task start time. Once the time is set Server should be restarted.

Result: In Java Client, The Task Monitor (Admin tab > Server Setting > Task Monitor).Activity Reminder task Shows executed at the specified time. The Activity task Reminder notification is not received by an inactive user.

14646701

SR 3-6787505251, 3-6191523051

Import (PPM)

Issue: PPM FIELD(S) ARE MISSING WITH AGILE IMPORT

Root Cause: We do not support the import of some of Program's attributes like Category 11, Category 12, Category 13, and so on.

Resolution: Added support for the attributes Category11-Category24 and Project Keyword.

Verification:

1. Create a Program with all Category Fields enabled.

2. Export the Program to an Excel sheet.

3. Edit the Excel sheet to import the category fields with values and the Project Keyword field with values.

4. Import the file from Excel and map the attributes.

Result: The Category 11 to Category 24 Fields and their values get imported into the Program object.

14712314

SR 3-6253737531

Gantt Chart

Issue: UNABLE TO UPDATE ACTIVITIES CHANGES IN GANTT CHART ERROR JAVA.LANG.NULLPOINTER

Root Cause: The null case is not handled.

Resolution: Added code to handle the null case.

Verification:

1. Log in to Web Client.

2. Go to a Project and launch it in Gantt Chart.

3. Try to delete an Activity.

Result: No exception is thrown. The update is successful.

15873524

SR 3-6248461021

Custom Reports

Issue: PROJECT SUMMARY REPORT IN AGILE DASHBOARD IS NOT WORKING

Root Cause: This issue happens only on the Weblogic server. The GZipFilter throws the following exception: java.lang.IllegalStateException: getOutputStream() has already been called!

Resolution: All requests for PLMServlet go through the GZipFilter for compression. All of the Dashboard Chart requests should go through DashboardPLMServlet to avoid the GZipFilter compression. Fixed the issue to avoid the GZipFilter compression.

Verification:

1. Login to Java Client.

2. Create a new Dashboard tab called project summary.

3. Create a new table in the tab, Items Summary, and configure it with some query involving Items.

4. Give the user Dashboard tab read privilege.

5. Log in to Web Client.

6. Navigate to Dashboard > project summary.

Result: The table displays proper search results as per the query. It does not show any application error.

15997280

SR 3-6558296941

Gantt Chart

Issue: WHEN EXIT BUTTON IS CLICKED W/O ANY CHANGE IN GANTT CHART THERE IS WARNING MESSAGE TO SAVE DATA

Root Cause: The issue is reproducible when the Gantt Chart is launched only from the child activities, but not from the root activity. When the Gantt Chart is launched from the child activities, the serial number of the activities is getting reset while initializing the GanttDocumentModel and the activities are added to the DocumentTracker's Modified Activities.

Resolution: Modified the code to avoid adding the activities to DocumentTracker's Modified Activities while initializing the GanttDocumentModel as we do not persist the serial numbers from the Gantt Chart.

Verification:

1. Log in to Web Client.

2. Go to any Program and launch it in Gantt.

3. Close the Program in Gantt.

Result: It should not display any warning message.

16190811

SR 3-6683263131

Gantt Chart

Issue: DEPENDENT TASKS DO NOT GET UPDATED VIA GANTT CHART

Root Cause: The modified Activities list, which did not have all of the modified activities, was used during the update.

Resolution: Call getAllModifiedActivities on the document after calling UpdateCoverPage on the children to get the actual list.

Verification:

1. Create a dependency of Finish-to-Start between two tasks.

2. Change the schedule of the task via Web Client.

Result: The dependent task schedule also changes accordingly.

3. Change the schedule of the task via Gantt Chart.

Result: The dependent task schedule changes.

16279938

SR 3-6763916741

Schedule Management

Issue: ALL CHINESE NAMES OF PPM IN SCHEDULE TAB BECOME GARBAGE CHARACTERS

Root Cause: There is a double encoding in the ToDoListNameRenderer.preLink() method.

Resolution: We only needed to encode it in the entrance method.

Verification:

1. Log in to Web Client.

2. Create a Program and add Tasks and Gates in the Schedule tab.

3. Give names for the Tasks and Gates as special characters.

Result: Activity names are displayed properly in the Schedule tab and Navigator.

4. Add these Tasks in the Content tab for other activities.

Result: The Schedule tab displays the name.

16472017

SR 3-6703903641, 3-6845714431, 3-7154803941, 3-7403627697

Content Management

Issue: GET ERROR MESSAGE "RETRIEVING CONTENTS ADDED TO THE VIEW FAILED" WHEN CREATING NEW PROJECT BY SELECTING CONTENT IN THE OPTIONAL TAB

Root Cause: If the project template only contains 200 activities, the SQL statement is incorrectly built when saving deliverables.

Resolution: Correctly handle the situation of 200 activities.

Verification:

1. Use Create Project from XML File under Tools and Settings to publish the attached template.xml (it has more than 200 objects in the tree) as a new project template.

2. Create a New Project from the template.

3. In the Create New page, enter mandatory data and select the All Tabs option.

4. Click on the Save button.

Results: A Program is successfully created from the template.

16663593

Search

Issue: TARGET FIELD DOES NOT DISPLAY PROPERLY IN RELATIONSHIP SEARCH

Root Cause: When processing the related object attribute, the code uses the subclass of the main object, but it should use the related object class/subclass id.

Resolution: Corrected the code so that it uses the related object class/subclass id.

Verification:

1. Log in to Java Client as admin.

2. Open Class Parts and go to the PageTwo tab, enable MultiList01 or not, but must assign a dynamic list, e.g. Changes.

3. Open Class Activity and go to page tab, enable MulstiList01 and assign a cascading list, Location.

4. Log in to Web Client as admin.

5. Create a Part P001, a program Pro001, and assign values in Page2.MultiList01.

6. Open P001 and go to the Relationship tab and add Pro001.

7. Do an Advanced Search: Items:Parts:Relationships Search:Activities with condition:Relationships.name contain Pro0001 and select Activities.Page Two.MultiList01 as displayed fields in Format.

8. Check Relationships.Activities.Page Two.MultiList01 value in the search results.

Result: The value appears correctly.

## 3.6 Agile PLM Framework

7091505

SR 18993104.6, 19000376.6, 2-3596401, 2-3608530, 18996788.6, 2-3968985

Relationships

Issue: BOM ICONS LOOK LIKE PART ICONS ON WHERE USED TAB

Root Cause: N/A

Resolution: N/A

Verification:

1. Create two Parts: Part1 and Part2.

2. Add Part2 as a BOM of Part1.

3. Open Part2 and click the Where Used tab.

4. Check the Part1 icon.

Result: The icon for Part1 is the assembly icon on Part2's Where Used tab.

7388050

SR 2-1724453, 2-1973545, 2-1987494, 3-1352274551, 7155335.992, 3-1792023601

Web Client

Issue: APPLICATION ERROR WHEN CLICKING PRINT ACTION ON WORKFLOW ROUTINGS WINDOW

Root Cause: N/A

Resolution: N/A

Verification:

1. Open user admin > go to Users Preference > set Preferred Start Page to Workflow.

2. Log in to Web Client as admin.

3. Click the Print button on the Workflow Routings Tab.

Result: The user can print the Workflow Routings tab successfully.

8566151

SR 3-5968351221, 2-5854392, 7850967.992, 2-3199366, 7528040.993

User/User Group

Issue: IMPROPER HANDLING OF APOSTROPHE/TICK MARK IN NAME

Root Cause: The special character "'" cannot be escaped.

Resolution: Do a security check for those kinds of characters.

Verification:

1. Log in to Web Client as admin.

2. Create a Manufacturer named DAWLEY'S.

3. Create Manufacturer Parts, click the Search button in the Create New window.

4. Input DAWLEY and run the search.

5. Check the search results.

Result: DAWLEY'S displays in the results.

8812635

SR 2-3008434, 3-1112308961, 3-2199781231, 7657431.994

Web Client

Issue: NUMERIC FIELD WITH SCALE=0 ACCEPTS ANY NUMBER OF DIGITS AFTER THE DECIMAL POINT

Root Cause: N/A

Resolution: N/A

Verification:

1. In admin, enable Parts.Page2.Numeric01, and set its scale = 0.

2. Log in to Web Client.

3. Create a new Part.

4. Edit the Title Block Tab.

5. Change the value for numeric01 to 12.23456.

6. Click Save.

Result: The value displays as 12 for the numeric01 field.

8840816

SR 2-3027701, 7666778.994

Relationships

Issue: RELATIONSHIP ICON DOES NOT APPEAR AS EXPECTED

Root Cause: N/A

Resolution: N/A

Verification:

1. Log in to Java Client as admin.

2. Go to Admin > System Settings > Smart Rules, Set 'Many QCR per PSR to Allow.

3. Log in to Web Client as admin.

4. Create a PSR, PR001, with the Default problem report workflow.

5. Create a QCR, Audit001, from PR001.Action tab, and select Default Audits workflow.

6. Go to Audit001's Relationships tab. PR001should be displayed in its Relationships table.

7. Add a rule: When Audit001 is "Validated", setPR001 to Submitted.

8. Save As Audit001 to a new audit, Audit002, with default Audits workflow.

9. Go to Audit002's Relationships tab.

10. Add a rule on Audit002, check its Relationships tab.

Results:

9. PR001 was carried over to Audit002's Relationships table, and the Dot Icon appeared on Audit002's Relationship tab.

10. The Dot Icon appeared on Audit002's Relationship Tab.

9027682

SR 3-1585544601, 3-5884158011, 3-5902473171, 2-5869610, 21952114.6, 3-5685629621, 3-5856601831

Searches

Issue: SEARCH WITH LIFECYCLE PHASE NOT IN PRELIMINARY RETURNS PRELIMINARY ITEMS

Root Cause: This issue is caused by the bug fix for issue 7292870. The addition of one more criteria affected the search result for attribute Part.Title Block.Lifecycle Phase.

Resolution: Add a special handler to avoid the bug fix for issue 7292870 for attribute Part.Title Block.Lifecycle Phase.

Verification:

1. Log in to Web Client.

2. Select Advanced Search for Parts.

3. Specify the following criteria: Part.Title Block.Lifecycle Phase Not In Inactive, Obsolete, Preliminary

4.Click the Search button.

Result: The object of the Lifecycle Phase:Preliminary, Inactive, Obsolete cannot be displayed.

Note: Some Preliminary values are displayed, because the user did not assign the lifecycle values in the Affected Items tab.

9446605

SR 3-3993877361, 3-1467894371, 3-2339599471

Standard Reports

Issue: CHANGE CYCLE TIME REPORT WITH PROMPTED RELEASE DATE SAVED SEARCH

Root Cause: Parameter values cannot be transferred in the next or previous page of the report execution wizard.

Resolution: Fix the defect.

Verification:

1. Log in to Web Client.

2. Create an Advanced Search with the following criteria: Changes->Object Search Cover Page.Date Released->Between-> Prompt

3.Save the search as search001.

4.Open Reports > Standard Reports > Process. Reports > Change Cycle Time Report, click Execute.

5. In Step 2, select the saved search, search001, click Next.

6. In Step 3, define the report parameter, click Finish.

Result: The correct report results are returned without error.

10113214

SR 3-2097565381

Standard Reports

Issue: ISSUES WITH "SHARE W/USERS" FUNCTIONALITY ON STANDARD REPORTS

Root Cause: The function to view a historical report allows a user to see other users in Share W/ User even though the current user does not have the discover User privilege. This defect is a security issue and is the same as issue 10113233.

Resolution: Fix the defect.

Verification:

1. Create 2 Users, usera and userb, with the Report manager role.

2. Ensure that the Users do not have read privilege on each other..

3. Log in to Web Client as admin.

4. Create a standard report schedule, then add usera and userb to Share W/ Users.

5. Wait until the schedule has executed, log in to Web Client as usera (or userb) and read the report.

Result: Usera can only find himself in Share W/Users on the Schedule and Historical report.

10113233

SR 3-2097917591

Standard Reports

Issue: SECURITY ISSUE WHEN USER SHARES REPORT WITH MULTIPLE EXTERNAL USERS

Root Cause: The function to view a historical report allows a user to see other users in Share W/ User even though the current user does not have the discover User privilege.

Resolution: Fix the defect.

Verification:

1. Create 2 Users, usera and userb, with the Report manager role.

2. Ensure that the Users do not have read privilege on each other..

3. Log in to Web Client as admin.

4. Create a standard report schedule, then add usera and userb to Share W/ Users.

5. Wait until the schedule has executed, log in to Web Client as usera (or userb) and read the report.

Result: Usera can only find himself in Share W/Users on the Schedule and Historical report.

10115496

SR 3-1858145021

Searches

Issue: DUPLICATE ROWS ARE RETURNED BY ADVANCED SEARCH DUE TO DUPLICATE ATTACHMENT_MAP

Root Cause: Filter algorithm for duplicate rows is only for adjacent rows.

Resolution: 932 CCB002 improves the algorithm and provides another algorithm which filters all duplicate rows.

Verification:

1. Create an Item, P00001.

2. Add two file attachments to P00001.

3. Create a change against P00001. Select option with:"The latest revision of Part P00006 has attachments. These attachments can be referenced to the new revision." and then go to P00001's Attachments tab with two attachments.

4. Create an Advanced search against Parts, choose criteria: Title Block.Number starts with P00001.

5. Go to the Format field, add Attachments.Folder Number and Attachments.Filename.

6. Click the Search button.

Result: The part displays correctly with two rows with different attachments in the search results.

7. Export into the XLS files.

Result: The values display correctly as UI.

10139509

SR 3-5324202061, 3-5709117061, 3-2129493771, 3-5229066531, 3-5452014895, 3-5569557721

Searches

Issue: WHEN PLUS SIGN (+) IS USED AS PART OF A VALUE IN AN ADVANCED SEARCH IT IS REMOVED IN ERROR

Root Cause The character "+" is not escaped well in our code.

Resolution: Added a special handler for date type attributes whose values contain "+".

Verification:

1. Create a Part and create an ECO against the Part.

2. Go to the Affected Items table and set the Effective Date with a date less than 7 days from today and set the Obsolete Date with a date greater than 5 days from today..

3. Set the Part version and release ECO.

4. Go to the Advanced Search table and execute the following search:

Changes:ECO:object search

Effective Date between: $today -7 and $TODAY

5. Click the Search button. The ECO is returned as a search result successfully

6. Save the search into the Saved Search field and name it Effective date.

7. Click the saved search for Effective date.

8. Check the search criteria for $TODAY-7.

9. Go to the Advanced Search table, and execute the following search:

Changes:ECO:object search obsolete Date between: $TODAY and $today +5

10. Click the Search button. The ECO can be found successfully.

11. Save the search into the saved search field and named Effective date.

12. Click saved search for Effective date.

13. Check search criteria for $TODAY+5

Result:

8. $TODAY-7 displays correctly and the search works correctly, as well. 13. $TODAY+5 displays well and the search works correctly, as well.

10217959

SR 3-2201426091

Searches

Issue: JAPANESE DOUBLE WIDTH SPACE IS NOT TREATED AS DELIMITER IN SEARCH

Root Cause: FTS does not support DOUBLE WIDTH SPACE in the search string.

Resolution: Code changed to support this. Treat double width space as a single width space.

Verification:

Case 1 for Japanese:

1. Log in to Web Client as a Japanese User.

2. Create two Parts with different character settings, like full-width or half-width for character.

3. Set two part descriptions, as shown below:

P00094 with description 説明

部品

P00095 with description

説明　部品

4. Do a simple search with "説明　部品" with full-width.

5.Check the search results.

Result: P00094 and P00095 can be searched for successfully.

Case 2 for Chinese:

1.Log in to Web Client as a Chinese User.

2.Create two Parts with different character settings like SBC case (全角) and DBC case (半角).

3. Set two part descriptions, as shown below:

P00096 with description

部件测试　文&#

21270; (SBC case)

P00097 with description

部件测试

文化(DBC case)

4. Do a simple search with "部件测试　文& #21270;" with the SBC case.

5. Check the search results.

Result: P00096 and P00097 can be searched for successfully.

10428046

SR 3-2471404781

Searches

Issue: DASHBOARD TABLE GENERATES WRONG RESULTS

Root Cause: For Multilist attributes, the code to compute the counter was not correct.

Resolution: Corrected the code to compute the counts for Multilist attributes.

Verification:

1. 1. Log in to Java Client and click on the Admin tab.

2. Go to Classes > Problem report subclass > User Interface > Page Three.

3. Enable a multilist field, such as Multilist31 or Multilist32.

4. Name the field: BiWEEKLY, and create/assign a new list: Bi Weekly, with values like: 01, 02, 03, 04, 05, 06, 07

5. Create approximately 10 PSRs with Page Three multilist values, select random values, single value or multiple values.

6. Go to System settings > Dashboard management > create a new dashboard "Test", and two tables: Summary and BiWeekly.

7. For table Summary, configure it as Advanced Search, on Problem Report subclass, with search condition: Page Three. BiWeekly is not null, and add Page Three. BiWeekly to the output field.

8. For table BiWeekly, configure it as Advanced Search, on Problem Report subclass, with search condition: Page Three. BiWeekly is not null, and add Page Three. BiWeekly to the output field. Click Display type, select table. For data: select X-Axis: PageThree.BiWeekly; Y-Axis:Cover Page:PSR number; Function: Count.

8. Go to Privileges, Dashboard view, make Test Dashboard visible.

9. Log in to Web Client, go to Dashboard: TEST. check and compare the count. For example: 05 has only appeared twice, but the count says 5.

11654917

SR 3-2713251081

Searches

Issue: SEARCH RESULT DISPLAYING TEAM NAME AND ROLES IS WRONG

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 a Program with some child objects.

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

3. Add the Program's name in Advanced Search and format the output to display Team.Name and Role attribute.

4. Click on the Search button.Result: Duplicates are not displayed in the search result.

11668954

SR 3-2499172951

Searches

Issue: SEARCHES DO NOT RESPOND TO $CURRENTSTATUS - REMOVE FROM PICKLIST

Root Cause: Design change

Resolution: Remove the additional list entry "$CURRENTSTATUS".

Verification:

1. Log in to Web Client as admin.

2. Do an Advanced Search: Changes > Change Orders > Cover page.status > In > $statustype.released, run the search.

3. Change the search criteria as follows: Changes > Change Orders > Cover page.status >In, try to select $currentstatus.

Results:

2. Change Orders meet the criteria and are successfully searched.

3. Cannot find $currentstatus, this selection has been removed from the list options.

11673387

SR 3-2511518701, 3-5229066531, 3-5569557721

Searches

Issue: UNABLE TO USE DATE VALUE OF $TODAY+N (ANY NUMBER) IN SEARCH

Root Cause: The character "+" is not handled well in our code.

Resolution: Add a special handler for date type attribute.

Verification:

1. Log in to Java Client as admin.

2. Go to Classes > Parts > Page two, enable p2.Date01.

3. Log in to Web Client as admin.

4. Do an Advanced Search: Items > Parts > page two.Date01 > Equal to > $today+2, run the search.

Results: The user can successfully use date value of $today+2 in the search criteria. Parts that meet the search criteria are successfully returned in the results.

11673470

SR 3-2753083071

Administration/Configuration

Issue: GET ERROR IF TRY TO DELETE 1000 ENTRIES OF A SIMPLE LIST

Root Cause: There is a resource leak (ps and rset) in ADDAO.listEntryInUsed.

Resolution: Fix the resource leak. Takes less than 1 min to delete 1000 entries from the list.

Verification:

1. Log in to Java Client as admin.

2. Create a simple list named List_A and create 1000 entries in this list and save it.

3. Highlight all list values and try to delete them at once.

Result: All of the selected values should be deleted at one time without any error message.

11775952

SR 3-2704909101

Security

Issue: SHUTDOWN AGILE SCRIPTS IS PROMPTING FOR USERNAME AND PASSWORD EVEN BOOT.PROPERTIES

Root Cause: The stopAgile script needs plain text superadmin's password in the command line, which is a security issue.

Resolution: Use Weblogic boot.properties file contains encrypted username and password. The stopAgile script extracts the username and password from boot.properties and uses them to stop Weblogic server.

Verification:

1. Install Agile933 with windows service.2. Go to $AGILE_HOME/agileDomain/bin.3. Run the stopAgile script.Expected Result: 1. The superadmin password is not required.2. The Agile server successfully stops when you execute the stopAgile script.

11795861

SR 3-2985472731

Performance

Issue: RUNNING BOM EXPLOSION REPORT FOR LARGE BOMS (230K) HANGS

Root Cause: The report server side loads all attributes for chosen objects when running the report. When too many attributes are loaded, the server crashes.

Resolution: Only load the attributes in the selected report layout.

Verification:

1. Run BOM explosion report against a large BOM, 075-0504 with over 230K rows.

Result: The Report generated in 59 minutes 55 seconds.

11830086

SR 3-2994766431

Searches

Issue: UNABLE TO EXECUTE ADVANCED SEARCH DUE TO UNNECESSARY TRANSLATION OF AND/OR LOGIC OPERATOR

Root Cause: With some languages, the following two messages in PCResources.properties do not get translated:

Dlg.AdvancedSearch.LogicOpAnd

Dlg.AdvancedSearch.LogicOpOr

Resolution: Dlg.AdvancedSearch.LogicOpAnd=AND Dlg.AdvancedSearch.LogicOpOr=OR

to Dlg.AdvancedSearch.LogicOpAnd=And Dlg.AdvancedSearch.LogicOpOr=Or.I18N team would translate the messages.

Verification:

1. Log in to Java Client as a Japanese user.

2. Do an Advanced Search: Change Orders > Cover page.Change Analyst > In > admin > And (Note: Operator And/OR has been translated) > Cover page.Number > start with > ECO, run the search.

3. In the search criteria, note that Operator And/OR also has been translated, change the search criteria to be: Change Orders > Cover page.Change Analyst > In > agile (choose another user) > And > Cover page.Number > start with > ECO, and run the search again.

Result:

2. All Change Orders that meet the search criteria are returned in the search results.

3. The search criteria can be modified successfully, and all Change Orders that meet the search criteria are returned in the search results.

11855292

SR 3-3136887071

Web Client

Issue: UNABLE TO CREATE NEW OBJECT FOR CERTAIN SUBCLASS AFTER UPGRADE

Root Cause: a. The double quotation included in the name of the multi-list attribute creating this issue.

b. There is a " in json data.

Resolution: Escape " with "

Verification:

1. In Admin, rename Parts.Page2.MultiList01 to "I" part number.

2. Point the MultiList to a simple list, and set it as Required.

3. Go to Web Client.

4. Create a Part, and select a list value for the MultiList, click Save.

Result: The user is able to select values for the MultilList attribute which contains double quotes in its name,and is able to finish the creation.

11872874

SR 3-3103366751

Software Development

Issue: INCONSISTENCY IN HANDLING THE "BETWEEN" AND "NOT BETWEEN" OPERATORS FOR SAVED SEARCH

Root Cause: This particular issue is due to the fact that SDK does not support the between operator in its code.

Resolution: Updated SDK code to support the between operator.

Verification:

The Query object created through the SDK client inserts two rows into the database Criteria table when 'between'/'not between' operators are used. One row is for the 'less than' operator and the other one for the 'greater than' operator as shown below:

QUERY_ID ATTR_ID RELATIONAL_OP VALUE

6115485 12468 6

6115485 12468 8

In this case, getQuerySession().loadTable() in apibean loads two rows and thus constructs a criteria string for example as '([12468] greater than or equal to %0) and ([12468] less than or equal to %1)'

Whereas saved searches created though Web client inserts only one row into the database Criteria table as follows:

QUERY_ID ATTR_ID RELATIONAL_OP VALUE

6115413 12468 22 2

4

Here is a code snippet to use the BETWEEN operator with IQuery. It will search for Parts having P2.Numeric01 value between 15 and 30.

String criteria=

"["+ItemConstants.ATT_PAGE_TWO_NUMERIC01+"]"+ "between " +"(%0, %1)";

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

query.setCaseSensitive(false);

query.setCriteria(criteria);

ITable results = query.execute(new Object[]{new Integer(15), new Integer(30)});

11879728

SR 3-3181630311, 3-6352859491

Notifications & Subscriptions

Issue: CANNOT MODIFY OR ADD NOTIFICATION TEMPLATE

Root Cause: "Priority" list can be modified and deleted.

Resolution: Make "Priority" list read only.

Verification:

1. Log in to Java Client as admin.

2. Go to Admin > Lists, search for a simple list: Priority, try to delete it.

3. Try to add some values to it and delete some old values.

4. Go to System Settings > Notifications, open a notification, modify the notification template, try to save it.

Results:

2. Cannot delete this list, delete button is grayed out.

3. List entries are uneditable, New and Delete buttons are all grayed out.

4. The notification template is saved successfully.

11939637

SR 3-2907596031

Standard Reports

Issue: ERROR MESSAGE WHEN DELETING HISTORICAL REPORTS

Root Cause: The function to view historical reports updates report version.

Resolution: Remove the function.

Verification:

1. Log in to Web Client as admin..

2. Go to BOM Explosion Report > Historical Report Tab.

3. Select a row and click the View button. The historical report opens.

4. Select the row and click the Remove button.

Result: The user is able to remove the historical report successfully and get the message "1 row has been removed".

12331828

SR 3-3228584601

Web Client

Issue: CANNOT SEE THE ENTIRE LINE OF CRITERIA WHEN ADDING/EDITING TRANSFER OF AUTHORITY

Root Cause: This is an Internet Explorer (IE) specific issue: select cuts off options. If you set a static width on the <select> element and the width of the text in the <option> are wider than that, the text gets cut off in IE 6-8.

Resolution: When moused over in IE, change the width to "auto" to accommodate the width and then change it back to static width when the user is done.

Verification:

1. Log in to Web Client with IE8/IE9.

2. Create a Transfer Authority.

3. Check the Criteria drop down list.

4. Edit an existing Transfer Authority and check the criteria drop down list.

5. Repeat the case for Firefox/Safari.

Results:

3. The user can see the entire line of criteria in the drop down list.

4. The user can see the entire line of criteria in the drop down list.

12347533

SR 3-3337287351, 3-3959983541, 3-5451742446, 3-5922208581, 3-3959839471

Export

Issue: AGILE DATE DISPLAYED VS EXPORTED EXCEL DATE

Root Cause: Date type attributes' values are set to DataOnly in the output file, but are different within Web Client.

Resolution: Changed the code to make sure that the attributes' values in the output file are the same as in the Web Client.

Verification:

Precondition:Enable all Page Two and Page Three date (Date01-15) attributes. Select dates only in Java Client and save the settings.

Steps:

1. Create a Part.

2. Enter the date in Page Two and Page Three date fields (Date01-15) and Save.

3. Export the Part in all export formats.

4. Repeat the steps for other objects such as Document, Model, Option Class, MFR, MFR Part, PSR, QCR and Changes.

Result: All Page Two and Page Three date (Date01-15) attributes should display properly for all Agile objects. It should not display time with all export formats (Excel, text, aXML,PDX). For aXML format, the Date Only format is displayed as 2013-05-30T0:00:00Z and with only the Date value shown in the format.

12536741

SR 3-3499926671, 3-3499926671, 3-3288819491, 3-5524259491, 3-5556089501, 3-6172842511

Administration/Configuration

Issue: AGILE PLM NOT SHOWING TIME IN EDT; SHOWS IN EST INSTEAD

Root Cause: This is caused by JDK's TimeZone change. Our metadata is not updated to follow JDK's change.

Resolution: Check-in the updated scripts.

Verification:

1. Log in to Java Client.

2. Set User's TimeZone to "(GMT-05:00) Eastern Time (US/Canada)".

3. Enable Parts.Page2.Date01 and Date02.

4. Create a Part, set Page2.Date01 = 2013/1/8, and Set Page2.Date02=2013/7/8, click Save.

5. Check the date that was saved.

Result: Date01 appears as EST and Date02 appears as EDT. It considers DST.

12544133

SR 3-3551964111

Java Client

Issue: LDAP MAPPING OF LONG FIELD NAMES

Root Cause: The current limit of 20 characters is not long enough to satisfy the customer's use case.

Resolution: Change the maximum length of LDAP id to 100, as suggested by the LDAP developer.

Verification:

1. Go to the LDAP configuration node in Java Client.

2. Double-click the LDAP Server.

3. Navigate to User-LDAP attributes mapping.

4. Click on the Plus sign.

5. Select the Agile ID of mutli text, text, etc.

6. Put in the LDAP id as "physicalDeliveryOfficeName".

Result: The system should allow the user to enter the LDAP field name as physicalDeliveryOfficeName.

12570689

SR 3-3633744221

Standard Reports

Issue: ITEM ATTRIBUTE HISTORY REPORT SHOWS DIFFERENT TITLEBLOCK ATTRIBUTES NAME WITH JAVA CLIENT

Root Cause: The related function does not process the inherit attributes of the Item subclass.

Resolution: Fix the defect.

Verification:

1. Log in to Java Client, set the Smart rule RedlineAttribute as Allow.

2. Go to Admin > Classes > Items > Part.

3. On the Title Block, rename attributes like Number, Description, and Part Category. For example, change the attribute name, "Number" --> "Number111", "Description" --> "Description111", and "Part Category" --> " Part Category111".

5. Set Parts.Title Block.Part Category as a change-controlled attribute.

6. Log in to Web Client.

7. Create one Part, P0001. The attribute names have changed and show as Number111, Description111, and Part Category111. Set the Part Category attribute to Electric.

8. Create one change,ECO001, against the Part, leave it as Pending status. Set Rev as 1. Change the Part Category attribute from Electrical to Software.

9. Run the "Item Attribute History Report" from the Action menu, choose Part P0001.

Result:

1. The attributes names display as "Number111", "Description111", and "Part Category111".

2. This report display correct values.

12633823

SR 3-326648032

Standard Reports

Issue: EFFECTIVE BOM REPORT IS NOT NOT DISPLAYING CORRECT RESULT

Root Cause: The function to process Item rev/cat/Rel Date fields is defective..

Resolution: Fix the defect and explain the business logic of Range Date in the Effective BOM Explosion report.

Verification:

1. Create a part, P001, with BOM P002 and P003.

2. Create a change, C001, against P001, add P004 to redline BOM table then release this change.

3. Create a change, C002, against P001, remove P002 from redline BOM table then release this change.

4. Create a change, C003, against P001, remove P003 from redline BOM table then cancel this change.

5. Create a change, SCO001, against P001, add P005 to redline BOM table then release this change.

6. Create a change, SCO002, against P002, remove P005 from redline BOM table then cancel this change.

7. Create a change C004 against P001, add P006 to redline BOM table, set effective date as 02/22/2012 then release this change (Current date is 02/20/2012).

8. Run the Effective BOM Explosion Report, add P001 for the report, leave other fields with default values.

Result: The report displays the correct results without error.

12695703

SR 3-2713251081

Searches

Issue: DO NOT DISPLAY TEAM.ASSIGNED FROM IN RESULT OF ADVANCED SEARCH WHEN TEAM.% ALLOCATION AND TEAM ASSIGNED FROM ARE SELECTED AS OUTPUT FIELDS

Root Cause: The display value of the Assigned From attribute is based on the value of Team Resource, and if there are not any resources, the value of Assigned From will be null.

Resolution: Remove the relationship between Assigned From and isresource.

Verification:

1. Open a Program which is assigned some members from the resource pool user group.

2. In the Team tab, edit the % allocation from the resource pool to 0 %.

3. Perform an Advanced Search for the Program with the output format including Team.% Allocation and Team.Assigned From.

Result: The Team.Assigned From field of the Program is displayed.

12712056

SR 3-3883826981, 3-4713435641

Searches

Issue: PERFORMING A SAVE AS ON A SEARCH DOES NOT OPEN THE NEW SEARCH

Root Cause: The display value of the Assigned From attribute is based on the value of Team Resource, and if there are not any resources, the value of Assigned From will be null.

Resolution: Remove the relationship between Assigned From and isresource.

Verification:

1. Log in to Web Client as admin.

2. Open an existing search, such as S1.

3. Use Save As to save S1 as a new saved search,:S2, and click the Save button.

4. Check the active search in the right pane.

Results:

3. S2 can be saved successfully.

4. The active search in the right pane shows the new search, S2.

12715622

SR 3-3792040377

Standard Reports

Issue: BOM EXPLOSION REPORT SHOWS INCORRECT QUANTITY

Root Cause: The function to retrieve the BOM attributes by Revision in the BOM Explosion Report has a defect.

Resolution: Fix the defect.

Verification:

1. Log in to Web Client as admin.

2. Create an Item as follows:

Item Number | Quantity | Find Num

P01

-P001 | 3 | a1

--P0001 | 2 | b1

-P002 | 2 | a2

3. Go to Reports > Standard Reports > Product Reports > BOM Explosion Report.

4. Execute and select the object as P01.

Result: The attribute Find Number and Quantity for P01 are blank. The values 3 and a1 are displayed in the attributes "Quantity" and "Find Num" for P001.

12754591

SR 3-3977179591

Standard Reports

Issue: FIND NUMBER IS INCONSISTENT BETWEEN WEB UI AND BOM EXPLOSION REPORT

Root Cause:The function to retrieve the BOM attributes by Revision in the BOM Explosion Report has a defect.

Resolution: Fix the defect.

Verification:

1. Change the server time to 2012-12-01.

2. Log in to Web Client as admin, and create a BOM with the structure below:

P1 rev A - C00001, change release date

2012-12-01

--P2 QTY: 2 Find Number: 2

----P3 QTY: 3 Find Number: 3

3. Change the server time to 2013-01-01.

4. Log out and log in to Web Client as admin, and create a change C00002 against P2, and change the P3 Qty & Find Number from 3 to 9, and release C00002 with date 2013-01-01.

Result: When the user runs the BOM Explosion Report against P1 with all levels, the system shows P3 with the Qty 9.

12801451

SR 3-4130685581

Searches

Issue: ADVANCED SEARCH FOR CHANGES CHANGE TYPES SHOWS PCO EVEN WITHOUT PCM LICENSE

Root Cause: A proper license check is not done.

Resolution: We added a license check before returning the subclass list.

Verification:

1. Log in to Java Client as admin.

2. Click the Admin tab.

3. Expand Server Settings.

4. Double-click Licenses.

5. Click Modules tab.

6. Note Product Cost Management is not enabled, it is set to No.

7. Expand Classes.

8. Note Price Change Orders Class are not enabled.

9. Click on Advanced .

10. Object Type: Select Changes.

11. Field: Select Change Type.

12. Click in Value box.

13. Scroll down and notice that the choice list includes all values.

Result: "PCO" is not listed here.

14. Log in to Web Client as admin.

15. Execute Advanced Search the same as in Java Client.

16. Scroll down notice choices list all values.

Result: "PCO" is not listed here.

12912039

SR 3-4204354581

Searches

Issue: WRONG ATTRIBUTE GROUPING / SORTING IN RELATIONSHIP SEARCHES

Root Cause: This is caused by a flexible attributes design issue. (Inherit information which is used to find the correct tab name is lost.)

Resolution: For search, the resolution is a workaround as it is not feasible to fix in the Admin side. Fetch the correct tab name instead of the wrong one.

Verification:

1. Enable Part.PAGE_THREE and create flexible attributes like MultiText86, MultiText87.

2. Enable FileFolder.Page_Three and create flexible attributes like MultiText86, MultiText87.

3. Assign read privilege on the new flex attributes.

4. Log in to Web Client.

5. Create an advanced relationship search on Part and File Folder.

6. Open the attribute selection drop down list.

7. Check the attributes under Relationships.FileFolder.PageThree.

Result: The attributes in Relationships.FileFolder.PageThree are grouped the same as on the GUI.

12938961

SR 3-4375997691

Searches

Issue: REPORT RESULTS CUT OFF AT 50,000 ROWS WHEN THE USER HAS FULLSEARCHDISPLAY PRIVILEGE

Root Cause: The FullSearchDisplay privilege affects Custom reports, but the Where Used Report is not controlled by this privilege.

Resolution: Change the behavior after 9312.

Verification:

1. Log in to Java Client as admin.

2.Go to Admin > Server Settings > Preferences, set Maximum Report Results as 5,000.

3.Assign the FullSearchDisplay privilege to user userA.

4.Log in to Web Client as user userA.

5.Create a custom report, CR001, and set the query as: Object Search -- Items {Title Block.Number Is Not Null }.

6.Make sure there are more than 5,000 items in the system, execute the report and check the report result.

Result: Displays all the Items which are more than 5,000 in the custom report CR001's result when the user has the FullSearchDisplay privilege.

12954482

SR 3-4452764461

Web Client

Issue: NOT ABLE TO SORT TRANSFERS OF AUTHORITY BY SELECTED COLUMN

Root Cause: Transfer Authority table can not be sorted.

Resolution: Make the Transfer Authority table sortable.

Verification:

1. Log in to Web Client as admin.

2. Go to My Settings > Transfer Authority, then add several rows to the Transfer Authority table.

3. Click the From user column to sort all rows in Transfer Authority.

4. Click the From user column again

5. Click the Start Date to sort all Transfer Authority rows again.

6. Click the Start Date again

Result: All Transfer Authority rows should be correctly sorted by the selected column.

12983950

SR 3-3646568561

Searches

Issue: SEARCH FOR BOM ITEMS STARTING WITH XXXX DISPLAYS THE BOM.ITEM NUMBER AS THE ASSEMBLY'S

Root Cause: This issue is on search result is based on the table. The customer expects the search result to be based on the row.

Resolution: 932 CCB008 handles both.

behaviors.

Verification:

1. Create a Part, P001, with BOM, P002 and P003.

2. Created an Advanced Search for Items: Part - Object Search, Bom.Item number | Starts With | P002

3. Format the output to include the BOM Item Number.

Result: Only P001 with BOM P002 shows in the search result.

13091000

SR 3-4673567721

Java Client

Issue: ISSUE WHILE CREATING NEW USER GROUPS

Root Cause: Attributes of P3 of User Group are incorrectly using class id instead of subclass id for resolving possible values of lists.

Resolution: Use subclass id when resolving list values for User Group P3 attributes.

Verification:

1. In Java Client > Classes > User Group subclass, enable P3.Multilist01.

2. Select a simple list for P3.Multilist01.

3. Go to User Settings > User Groups, click New to create a new User Group.

4. On the User Group creation dialog, check the values of Multilist01.

Result: The user is able to see the multilist values in the selection window during creation.

13247598

SR 3-4659289441, 3-4874748042, 3-4906002767, 3-5546480163

Searches

Issue: COM.AGILE.ADMIN.CLIENT.VALUE.ADMINEXCEPTION: NODE DOES NOT EXIST IN THE CACHE

Root Cause: There is a Print exception when debug enabled.

Resolution: Comment out the print stack trace code.

Verification:

1. Log in to Web Client.

2. Perform a Quick Search with * to search for all objects.

3. Go to the server where PLM is installed, monitor the backend log info.

Result: There is no exception like COM.AGILE.ADMIN.CLIENT.VALUE.ADMINEXCEPTION.

13375597

SR 3-4887628901, 3-7185352081

Administration/Configuration

Issue: HOME ORGANIZATION DOES NOT APPEAR IN ADVANCED SEARCH FOR USERS

Root Cause: Search Web Client does not support showing the customer itself in the Home Organization list.

Resolution: Modify view ORGANIZATION_P2P3 to support this and also add code to support this in the java file.

Verification:

1. Log in to Java Client as admin.

2. Go to Admin > System Settings > CompanyProfile, make sure that the customer is Oracle Corporation.

3. Log in to Web Client as admin.

4. Do an Advanced Search: Users > User > GI.Home Organization > not in, try to search for value: Oracle Corporation.

Results: Oracle Corporation can be selected successfully.

13495334

SR 3-5009579301

Standard Reports

Issue: TAB DISPLAY CONFIGURATION DISPLAYS THE CURRENT OBJECT IN THE CONFIG WINDOW

Root Cause: The function to process header text in the popup window is defective.

Resolution: Fix the defect.

Verification:

1. Log in to Web Client as admin.

2. Go to Tools and Settings > Administration, open Tab Display Configuration.

3. Close the Tab Display Configuration window, then open any object such as part01.

4. Go to Tools and Settings > Administration, open Tab Display Configuration again, check the Tab Display Configuration window.

Results:

2. The Tab Display Configuration window pops up. It displays Tab Display Configurations assigned to admin.

4. The Tab Display Configuration window pops up. It displays Tab Display Configurations assigned to admin. The object opened previously can not be displayed at the top.

13592378

SR 3-4603434821

Import

Issue: PREVIOUS REV DOCUMENT CLASS ATTACHMENTS ARE BEING RENAMED WHEN IMPORTING A PDX

Root Cause: The parameter of method versionAttachToObj passes the wrong file name fileid, instead of filename.

Resolution: Pass the correct filename instead of fileid.

Verification:

Precondition: In the Preference tab, set Smart Rules Warning Violation Behavior as " Accept" and Redline Mode Behavior = All Items onto the change.

Note: This issue can be reproduced only when the attached file has no file extensions.

1. Create an Item, P00001.

2. Create a Change, E00001, and add P00001 into the Change.

3. Add an attachment with a file called, test, without any file extensions (e.g. create a txt file and remove the extension).

4. Release the Change and get the rev 001 P00001 with attachment.

5. Export the rev 001 P00001 with attachment to a pdf file.

6. Click the tab attachment of rev 001 P00001, click the folder name of attachment test.

7. Check the file out and check in a new rev attachment test (Version 2).

8. Click the tab attachment of rev 001 P00001, select version 2 for the attachment test,click save.

9. Import the pdf file, which was previously exported, to a new change E00002.

Result: The previous rev of attachment name is not changed, and is imported correctly and the file name details on new change are correct.

13623958

SR 3-3230896621

Relationships

Issue: HISTORY TAB OF USER PROFILE SHOWS

Root Cause: This is as designed before 932.

Resolution: Request a new flag in the User object to store the Relationship used tag and maintain the flag in the server side.

Verification:

1. Log in to Web Client as admin.

2. Create a new User, U001, then go to its Relationships tab. Add several objects to its Relationships table.

3. Go to U001's History tab.

4. Check U001's Relationship tab.

Results:

3. The Add relationships actions have been recorded into the History table with the correct information.

4. The Radio button/bubble can be found on U001's Relationships tab when the user is related to any object.

13630511

SR 3-5199383291

Agile Content Services

Issue: UNABLE TO CREATE DESTINATIONS UNDER AGILE, WHICH IS INSTALLED ON WEBLOGIC SERVER

Root Cause: Initial context environment variable Context.URL_PKG_PREFIXES is not correctly set when looking up the resource from the OAS server. There is rack of OAS-related jar files.

Resolution: 1. Set the context environment variable to "oracle.oc4j.naming.url" when looking up the resource from OAS Server.

2. Copy the following 8 jar files from OAS_HOME to \Agile_HOME\agileDomain\lib, then restart the server.

OAS_HOME\lib\dms.jar;

OAS_HOME\j2ee\home\oc4jclient.jar;

OAS_HOME\j2ee\home\jazncore.jar

OAS_HOME\j2ee\home\lib\oc4j-internal.jar;

OAS_HOME\j2ee\home\lib\adminclient.jar;

OAS_HOME\j2ee\home\lib\bcel.jar;

OAS_HOME\j2ee\home\lib\pcl.jar;

OAS_HOME\j2ee\home\opmn\lib\optic.jar;

Verification:

1. Install Agile on WLS12C.

2. Log in to Agile Java Client.

3. Create a new AQ JMS Destination that is configured on OAS 10.1.3.4 (Set it per Implementation guide for D2R 2.5, where in the customer case, the AQ is on same OAS where AIA is deployed).

4. Test the connection.

5. Observe that the connection test fails with the following error:

The remote server returns the following error message: While trying to look up comp/resource/EcoRP/QueueConnectionFactories/QCF in /app/ejb/acs.jar#com.agile.acs.destination.Destina tionSession.

6. Configure the foreign server on the WLS12C as per the relevant document.

7. Test the connection

Result: The test is successful.

13711385

SR 3-5305260501

Searches

Issue: SEARCH RESULT IS INCORRECT

Root Cause: During the process of SQL formation, it only adds the latest UserID, the old one is overwritten.

Resolution: Add multi UserIDs in SQL.

Verification:

1. Create two users User1 & User2 with Approve / Reject; Change Analyst role.

2. Create one ECO, ECO001, and add User1 & User2 as CCB.approvers.

3. Create one ECO, ECO002, and add User1 as a CCB.approver.

4. Run an Advanced Search from Agile Web Client.

5. Search criteria like: Approver contains "User1,User2".

Result: It returns 2 search results, including ECO001 & ECO002.

13804893

SR 3-5364995101

Standard Reports

Issue: BOM EXPLOSION REPORT SHOWS INCORRECT RESULT IN PRODUCTION ENVIRONMENT

Root Cause: The parent Item fetches the first child's information and displays it in the BOM table.

Resolution: Changed the code so that we do not fetch the child information when we load the parent Item in the BOM table.

Verification:

1. Log in to Web Client as admin.

2. Create an Item as follows: Item Number | Quantity | Find Num | Ref Des | BOM Notes

P01

-P001 | 3 | a1| R1-R3 | note001

--P0001 | 2 | b1| b1,b2 | note0001

-P002 | 2 | a2| a1,a2 | note002

3. Go to Reports > Standard Reports > Product Reports > BOM Explosion Report.

4. Execute and select the Item, P01, for the report.

Result: It should display the following value for the attributes Qty, Find Num, Ref Des and BOM.

Notes on P001 in the report result:

Level Item Number Qty Find Num Ref Des BOM Notes

0 P01

1 P001 3 a1 R1-R3 note001

2 P0001 2 b1 b1,b2 note0001

1 P002 2 a2 a1,a2 note002

13868789

SR 3-5466169681, 3-6000385341, 3-6164409941

Searches

Issue: CANNOT SET SORT ORDER FOR REPORT LAYOUT

Root Cause: The function to collect sorting column has a defect.

Resolution: Fix the defect.

Verification:

Preconditions:

- Set Java Client > Preferences > Search All.

- Set Records for Duplicates to "Yes".

Steps:

1. Test with Change class, create a custom report.

2. Click on the Layout tab.

3. Click on the Layout Name.

4. Click on the Sort tab.

5. In the Attribute row, select Cover Page.Status for the first row.

6. In the second row, select Cover Page.Number.

7. Click on the Save button.

8. Issue: When you open the layout again, the first row shows Cover Page.Number instead of Cover Page.Status

9. Run the report.

Result:

Step 8: When you open the layout again, the first row shows Cover Page.Status, instead of Cover Page.Number.

Step 9: The report returns the correct value as same the result from Advanced Search.

13932243

SR 3-5380710631

Searches

Issue: DUPLICATED ENTRIES/ROWS WHEN EXPORT SEARCH RESULT TO EXCEL

Root Cause: The filter algorithm of duplicate rows is only for adjacent rows.

Resolution: CCB002 improve the algorithm. It provides another algorithm which filters all duplicate rows.

Verification:

1. Log in to Java Client as admin.

2. Enable PSR > Cover page > Product lines with a simple list such as: test01, test02.test03, test04, test02

3. Log in to Web Client as admin.

4. Create PSR objects with the following setting:

Product lines: test02

Customers with more customers values from DB like (CUST2 (CUST00004); Cust1 (CUST00003); RONALD

(DEMO CUSTOMER 1); SAMPLE (CUST00001); SAMPLE

(SAMPLE_CUST01))

5. Create an Advanced Search with the following search criteria:

Product Service Requests Object Search

Attribute: Operator: Prompt : Value Join

Product Line(s): Contains Any ::test02 And

Customers In CUST2 (CUST00004); Cust1

(CUST00003); RONALD (DEMO CUSTOMER 1); SAMPLE

(CUST00001); SAMPLE (SAMPLE_CUST01)

6. Click the search button.

Result 6: Search Results display correctly.

7. Select More > Export(xls).

Result: The export result is the same as the UI and there are no duplicated results.

13945425

SR 3-5939117781, 3-5993496784, 3-6142942841, 3-5551721481

Custom Reports

Issue: ISSUE WITH REMOVING REPORTS FROM HISTORICAL REPORT

Root Cause: The function to view historical report updates the report version.

Resolution: Remove the function.

Verification:

1. Log in to Web Client as admin.

2. Go to Change Backlog Report > Historical Report Tab.

3. Select a row and click View, the historical report opens.

4. Select the row and click Remove.

Result: The user can remove the report successfully and gets the message "1 row has been removed."

13975379

SR 3-5589435841

Admin Config Propagation

Issue: ISSUE WITH REMOVING REPORTS FROM HISTORICAL REPORT

Root Cause: When propagating the LCP attribute for the Part subclass, the possible values are taken for the Parts class, but should be taken for the Part subclass.

Resolution: This issue was fixed in AdminCriteria.java by getting all of the possible values of LCP from the Part subclass instead of the Parts class.

Verification:

1. Create a Lifecycle Phase on a Subclass level.

2. Create a criteria on a subclass (Parts || Title Block.Lifecycle Phase In <newly created Lifecycle Phase>).

3. Export using ACP.

4. Create the same Lifecycle Phase in a new environment.

5. Import using ACP.

6. Check the Import.err file.

Result: There are no errors.

14020895

SR 3-5495904471

Searches

Issue: UNABLE TO VIEW THE MULTILIST ATTRIBUTE WITH MANY VALUES FROM SEARCH RESULT

Root Cause: The server saves the multiple list entry to MSAtt table if the entry is more than 250. The search server does not handle cases for these.

Resolution: Create a special handler for this case to correctly fetch a multiple list entry.

Verification:

1. Log in to Web Client.

2. Search for 2 documents using the following search parameters: Items > Other Specifications > Name/Number/Description > Contains Phrase > qx-074

OR

Name/Number/Description > Contains Phrase > fe-00333. Click Format, and add Page Two.Supplier Release List to the Format tab so that it appears in the search results.

4. Run the Search.

5. View the Page Two.Supplier Release List in the search results.

Result: The value of Page Two.Supplier Release List can be reviewed with the customer DB upgrade.

14057919

SR 3-5605658501

Admin Config Propagation

Issue: PAGE TWO OF SUBCLASSES ARE NOT CORRECTLY PROPAGATING

Root Cause: Page Two attributes of subclass are not considered when propagating a subclass.

Resolution: Fixed by implementing SubclassWrapper.getUserInterfaceTabs() to propagate P1 & P2 attributes of a subclass.

Verification:

1. Change attributes' visibility features of Page Two attributes on the Subclass level.

2. Propagate via ACP. Everything comes up correctly.

4. Change it again in the Source and propagate again. Visibility changes to what is configured in the Class level.

Result: Page Two of subclasses can be propagated successfully.

14065145

SR 3-5680966721

Folders, Files & Attachments

Issue: NO PRIVILEGE ERROR WHEN VIEWING FILE ATTACHMENTS

Root Cause: There is a bug in the code.

Resolution: Fixed the case while viewing the file from the "View Versions" window.

Verification:

1. Log in to Web Client.

2. Create an Item, add attachments.

3. Create a Change and add the Item.

4. From Affected Items select Item > Attachments tab.

5. Select a File, select View Versions from the More menu.

6. Click the View button without selecting the View drop down.

Result: The file can be viewed without any error message.

14083014

SR 3-7675118871, 3-5470837131, 3-7258554558, 3-7293992141

Web Services

Issue: AGILE ABS SERVICE FAILS WHEN PROCESS EXTENSION (PX) IS MODIFIED AND DEPLOYED

Root Cause: When WSX are deployed, need to clear the AxisEngine's Session cache.

Resolution: Fixed in WsxDeployHandler.

Verification:

Deployed the WSX and made some changes in the WSX Code. Deployed the WSX again without restarting the server. It gave an updated response per the changes made.

14107658

SR 3-5741685861

Administration/Configuration

Issue: APOSTROPHE NOT APPEARING IN ALL AGILE OBJECTS NAMES

Root Cause: MessageFormat.format removes the single quote "'", we must use '' instead of '.

Resolution: Remove the MessageFormat if we use the French language.

Verification:

Case: On the left hand-side, under "Recherches",Result1: "Recherches de l'ingenieur decomposants"

Result 2: "Recherches de l'analyste modifications"

Case 2: In the dropdown list, the apostrophe is displayed correctly.

Result: "Type d'annexe"

14118058

SR 3-5748421271

Notifications & Subscription

Issue: SPELL CHECK NEEDED IN SUBJECT LINE FOR URGENT MARKED CHANGE APPROVER NOTIFICATION

Root Cause: There is a Subject string format issue.

Resolution: Add a blank space between notification subject and "URGENT:".

Verification:

Preconditions: Do configuration for notifications and set notification type as email or inbox and email.

Steps:

1. Log in to Web Client.

2. Open an ECO.

3. Change Status from Pending to Submitted, change Status window opens.

4. Select users to notify of the status change.

5. In the bottom of the window, select option to Send notification as urgent.

Result: Users receive the email notification, having subject line as URGENT:Your ***

6. Forward this email to others and click the Spell check button.

Issue: The subject line is having a spell check error when forwarding this email to others.

Result: There is a space after "URGENT:'" ==>. URGENT: Your ***

14156149

SR 3-5657617951

Database Installation

Issue: ERROR UNABLE TO EXTEND TABLESPACE TEMP

Root Cause: TEMP's datafile does not autoextend

Resolution: Add AUTOEXTEND ON clause for TEMP's datafile in the CREATE DATABASE statement

Verification: 1. Run the 933 database installer to create an instance.

2. Log in to sqlplus, check if the tempfile is autoextensible. select file_name, tablespace_name, autoextensible from dba_temp_files.

Result: The tablespace TEMP's datafile is autoextensible.

14169115

SR 3-5589695201, 3-5694795951

Admin Config Propagation

Issue: EVENTS ARE NOT PROPAGATING WITH ACP

Root Cause: Unable to resolve Class, Workflow and its statuses in target system.

Resolution: Added new APIs to resolve them.

Verification:

1. Create a new workflow in Java Client.

2. Create a new Event on the new workflow.

3. Create a new Event Handler.

4. Create a new Event Subscriber to bind the Event and the Event Handler.

5. Use ACP to export all the newly created objects.

6. Use Java Client to delete all of the newly created objects.

7. Use ACP to import all of the deleted objects above.

8. Verify the objects in Java Client.

Result: The propagate event is successful. There are no error messages in the console and import.err.

14182287

SR 3-5797341171

Notifications and Subscriptions

Issue: THE USER NAME FIELD INSERTS THE TO FIELD VALUE INSTEAD OF THE USER ON EVENT NOTIFICATIONS

Root Cause: ProgramMsg is used in the Event Notification. In the notification, user name is generated from the context passed to it, which is the receiver context.

Resolution: Set the user on the ProgramMsg based on who is sending the notification, instead of generating it from the receiver context.

Verification:

1.Create an event named Complete task:

Event Type: Change Status for Workflow

Workflow: Default Activities (All Activities)

Object Type: Activities

Status - From: <ANY>

Status - To: Completed

2. Create an Event Subscriber named Complete task notification.

Event: Complete Task

Event Handler: "Activities - Project Status Promotion, Observers/Notifiers PX" (which is a notification saved from "Activities - Project Status Promotion,Observers/Notifiers")

a. Both notifications have the field "[User Name]" as shown below:

[General Info.Activities Type] [General Info.Name] has been moved by [User Name] to [General Info.Status] for the [General Info.Workflow] workflow. Comments from [User Name]:[Comments] Moved to [General Info.Status] by: [User Name]

b. The PX notification has the To field set to "$NOTIFY".

3. Log in to Web Client as admin.

4. Create a Program, Program-1.

5. Add a user to the team, e.g. user A.

6. Log in as User A.

7. Change the status to Completed.

8. Log in as Admin and go to Notifications tab and see that both notifications were triggered and sent to respective users.

9. Check the [User Name] field display for Notifications:

Activities - Project Status Promotion, Observers/Notifiers PX and Activities - Project Status Promotion, Observers/Notifiers.

Deviation 1: Change the notify to field for the PX notification from $NOTIFY to "User B" and reproduce steps 3-7. Log in as User B and check the notifications for the [User Name] field.

Deviation 2: Check the [User Name] field value display for Gate objects.

Result:

[User Name] field should display the "User A" for the above Activities/Gate objects.

[User Name] field should display "User B" after changing the To field.

14183847

SR 3-5792833441

Searches

Issue: IQUERY FOR SEARCHING ALL CHANGES WHERE [WORKFLOW.APPROVER] IS AN USERGROUP DOES NOT WORK

Root Cause: The workflow.approver refers to the User list. When using a nested query with the User Group attribute, the server can not resolve the User Group attribute.

Resolution: Validate the attribute belonging to the User or User group. Then pass the correct class id to the search server.

Verification:

Use the Nested Criteria to Search for Values.

[Workflow.Approver] contains ([" +

UserGroupConstants.ATT_GENERAL_INFO_NAME + "] == 'ug')

>>>

session = connect();

IQuery query

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

hangeConstants.CLASS_CHANGE_BASE_CLASS);

query.setCaseSensitive(false);

String criteria = "([Workflow.Approver] contains

([" + UserGroupConstants.ATT_GENERAL_INFO_NAME +

"] == 'ug'))";

query.setCriteria(criteria);

ITable results = query.execute();

System.out.println(results.isEmpty());

System.out.println(results.size());

Iterator it = results.getTableIterator();

while(it.hasNext()){

IRow row = (IRow) it.next();

String changeNum = row.getValue(ChangeConstants.ATT_COVER_PAGE_NUMBER).toString();

System.out.println(changeNum);

}

Result: The query is executed successfully and the search results are correct.

14184143

SR 3-5695284761

Standard Reports

Issue: UNABLE TO RUN THE ATTRIBUTE HISTORY REPORT IF AN ASSOCIATED CHANGE IS CANCELED

Root Cause: The function to filter canceled Change Rev Data in the Item Attribute History Report has a defect.

Resolution: Fix the defect.

Verification:

Preconditions:

1. Log in to Java Client as admin.

2. Click Admin > Workflow Settings > Workflows, open Default Change Orders.

3. Open Pending status, add Canceled to Manual Valid Next Status.

4. Open Change status privilege for Change Orders. Make sure that the user has the privilege to change status from pending to canceled for the Default Change Orders workflow.

Steps:

1. Log in to Web Client as admin.

2. Create a Document D0001.

3. Create a change, C0001, add D0001 to its Affected Items tab, set rev=1, and route it to Released status.

4. Create a change, C0002, add D0001 to its Affected Items tab, set rev=2, and route it to Canceled status directly (key step).

5. Open the Document, D0001, click Actions > Attribute History Report.

6. Select default layout and PDF/Excel/Word/HTML output format, open the PDF/EXCEL/WORD/HTML file and check the result.

Result: The user is able to open the PDF/Excel/Word/HTML file without error message, and the correct value is shown in the report result.

14186288

SR 3-5811296681

Standard Reports

Issue: USER USAGE REPORT FAILS WHEN SELECTING USERS FROM A USER GROUP

Root Cause: A NumberFormatException happens when parsing User information from User Group.

Resolution: Fix the defect.

Verification:

1. Log in to Web Client as admin.

2. Execute Standard Reports > Administrator Reports > User Usage Report.

3. Click the User icon to launch the palette..

4. Select User Groups in the dropdown list.

5. Enter wild card * and click Search to select some User Groups.

6. Click Finish.

Result: Users in the selected User Groups display in the report result without error message.

14193085

SR 3-5788204101

Web Client

Issue: ADD FILES WINDOW DROPS WHEN ADDING ATTACHMENTS VIA SEARCH THEN ADVANCED SEARCH

Root Cause: Add by Custom Search is not implemented.

Resolution: Due to the large amount of work needed to implement the functionality, remove the Custom Search button instead.

Verification:

1. Log in to Web Client.

2. Open any Agile object's Attachment tab.

3. Select Add > By Search.

4. Verify the Custom Search button.

Result: The Custom Search button is removed from Attachment tab's Add > By Search window.

14199944

SR 3-5834592341, 3-7185352081

Searches

Issue: THE SAME LIST SHOWS A DIFFERENT NUMBER OF VALUES IN THE WEB AND IN JAVA CLIENT IN SEARCH

Root Cause: Search in Web Client does not support the display of the customer itself in the Home Organization List.

Resolution: Modify view ORGANIZATION_P2P3 to support this and also add code supporting it in the Java file.

Verification:

1. Log in to Java Client as admin.

2. Go to Admin > System Settings > CompanyProfile, make sure that the customer is Oracle Corporation.

3. Go to Lists > Organizations, check values in this list. The user can find the value of Oracle Corporation.

4. Do an Advanced Search: Users > User > GI.Home Organization > not in, select value: Oracle Corporation.

5. Log in to Web Client as admin.

6. Do an Advanced Search: Users > User > GI.Home Organization > not in, enter value: Oracle Corporation, or try to search value: Oracle Corporation.

Result:

4. The user can select the value of Oracle Corporation successfully in Java Client.

6. Oracle Corporation can be selected successfully

14213207

SR 3-5847862911

Standard Reports

Issue: DISPLAY STATUS DATE FORMAT PROBLEM IN QUALITY CYCLE TIME REPORT

Root Cause: The function to process Date format transformation in the Change/Quality Cycle Time Report has a defect.

Resolution: Fix the defect.

Verification:

1. Log in to Web Client as admin.

2. Go to My Settings > Preference, set "Preferred Date Format" as "MM/dd/yyyy".

3. Create a Problem Report, PR001, route it to CCB status. Its Date Submitted is 01/16/2013 09:05:20 PM EST.

4. Run the Agile Quality Cycle Time report with the defined query: Product service requests > Problem reports > GI.Date Submitted > Less than > 01/17/2013 and status change from pending to CCB, execute the report.

5. Back to Preference, Change the "Preferred Date Format" to be "MM-dd-yyyy", run the Quality Cycle Time report with the same query criteria, check report results.

Results:

4. PR001 was returned as a result and displays the correct date format for both start status date: 01/16/2013 09:05:16 PM EST and end status date: 01/16/2013 09:05:27 PM EST.

5. PR001 was returned as a result and displays the correct date format for both start status date: 01-16-2013 09:05:16 PM EST and end status date: 01-16-2013 09:05:27 PM EST.

14213577

SR 3-5440733441

Admin Config Propagation

Issue: ACP IMPORT FAILS WITH ERROR "PLEASE CANCEL THIS OPERATION..." (CRITERIA)

Root Cause: The criteria object is not refreshed after its properties are saved during import.

Resolution: Refresh criteria object before updating it.

Verification:

1. Log in to Java Client as admin.

2. Create the criteria roletest.

3. Prepare the XML file:

<copy>

<criteria>

<include>

<pattern>testrole</pattern>

</include>

</criteria>

</copy>

4. Execute an export action in ACP: acp export golden -debug

5. Update some attribute for criteria.

6. Execute import action: acp import golden dev -debug

Result: Imports successfully. There is no error message like "This is not really an exception. This error message should never be displayed." displayed in the console or import.err.

14213609

SR 3-5440733441

Admin Config Propagation

Issue: ACP IMPORT FAILS WITH ERROR "PLEASE CANCEL THIS OPERATION..." (CRITERIA)

Root Cause: The error is thrown even though it was not an error condition.

Resolution: This issue was fixed by throwing a warning instead of an error since the import completes successfully, and the message indicates "This is not really an exception."

Verification:

1. Log in to Java Client as admin. 2. Config: <copy> <subclass> <include> <pattern>User group</pattern> </include> </subclass> </copy> 4. Execute an export action: acp export golden -debug 5. Update some attributes for the user group object. 6. Execute and import action: acp import golden devResult: The import is successful. There is no error message like "This is not really an exception. This error message should never be displayed." displayed in the console or import.err.

14213638

SR 3-5440733441

Admin Config Propagation

Issue: ACP IMPORT FAILS WITH ERROR "THIS IS NOT REALLY AN EXCEPTION..." (ROLE)

Root Cause: The error is thrown even though it was not an error condition

Resolution: This issue was fixed by throwing a warning instead of an error when the system is unable to resolve the user, user group, and privilege.

Verification:

1. Log in to Java Client as admin.

2. Create a new cascade list, caslist1, and add some list entries.

3. Config:

<copy>

<role>

<include>

<pattern>testrole</pattern>

</include>

</role>

</copy>

4. Do an export action: acp export golden

5. Update some attribute values of ttestrole.

6. Do an import action: acp import golden dev

Result:

Import completes successfully. No error message like "This is not really an exception. This error message should never be displayed." displayed in the console and import.error.

14242164

SR 3-5854469571

Searches

Issue: PROMPT WINDOW FOR SEARCH COULD NOT DISPLAY CHINESE ATTRIBUTE NAME

Root Cause: The Chinese name's length is larger than the value we defined.

Resolution: Introduce a jquery plugin to solve the problem.

Verification:

1. Log in to Java Client as admin.

2. Go to Classes > Parts > Title block, open attribute Description, and change its name to be Chinese words.

3. Create a new part with a Chinese name, such as: 遥控器， and input value: abc for its attribute: 描述

4. Log into Web Client as admin.

5. Do an Advanced Search: Items > Parts > Title block.遥控器 > Equal to, enable prompt, run the search.

6. The Enter Search Values window appears, check the attribute name in this window.

7. Input value, abc, in the prompt search window, run the search.

Results:

6. The Chinese attribute name:描述 is displayed correctly in the prompt search window.

7. The value can be set successfully, and Part, 遥控器, can be found.

14247685

SR 3-5883883681, 3-6320685101, 3-7179807801

Web Client

Issue: EXPORT TOOL - ADDING ITEMS USING ADVANCED SEARCH ADDS INTRODUCTORY REV

Root Cause: Drag & drop with Custom Search does not pass the revision to the server. The PDXDataModel then uses the Introductory revision (rev) as default, which is the problem.

Resolution: If no rev is provided, use the default rev. Normally this is the latest rev.

Verification:

1. Log in to Web Client as admin.

2. Go to Tools and Settings > Export.

3. Click on Add button.

4. Use the Advanced Search. For example, search for the Items with multiple revisions.

5. Drag the search results into the Selected Objects to Export pane.

Result: The Items should get added correctly with the latest released revision.

14351476

SR 3-5967962608

Searches

Issue: VALUE OF THE LIST ATTRIBUTE IN DASHBOARD TABLE IS NOT SORTED IN CORRECT ORDER

Root Cause: Currently, we only support sorting in the database (DB) by the SQL order clause. Some attributes are stored in the DB with id. For these attributes, it does not make sense to sort according to id, it should sort by their values.

Resolution: Adding the sorting process in memory.

Verification:

Case 1:

1. Create some Parts and assign values to the Size and Product Line fields.

2. The created values are as below:

Number,Size,Product line

P00004,F,Taurus;

P00007,F,Pisces;

P00169,D,Capricorn;

P00171,B,Leo;

P00172,F,Capricorn;

P00174,E,Capricorn;

P00176,G,Capricorn;

3. Go to the Advanced Search table and enter the following search criteria:

Items:Part:Object Search

Size is not null and Product lines is not null

4. Go to the Format table and click sort, Make Size Descending as primary sort and Product line Ascending as the secondary sort.

5. Move these two attributes into the Displayed field.

6. Click the search button and check the search results.

Results:

Number,Size,Product line

P00176,G,Capricorn;

P00172,F,Capricorn;

P00007,F,Pisces;

P00004,F,Taurus;

P00174,E,Capricorn;

P00169,D,Capricorn;

P00171,B,Leo;

Case 2:

1. Log in to Java Client as admin.

2. Modify the list used in the ECR.Cover Page.Change Category with the following values:

Mandatory

Quick Phase-In

Standard Pase-In

3. Log in to Web Client.

4. Create 5 ECRs as follows:

Number Status Change category

R00002 CCB Mandatory

R00003 CCB Quick Phase-In

R00004 CCB Standard Phase-In

R00005 Submitted Mandatory

R00006 Submitted Quick Phase-In

5. Configure the table with the following search, and Next:

For: Change Requests

Type: Object Search

Criteria: Cover Page.Status.Is not null And

Change category is not null

6. Add the following fields to the output files:

Cover Page.Change Category

Cover Page.Status

7. Configure the sort order as below and Finish:

Cover Page.Change Category Descending

Cover Page.Status Ascending

8. Check the search results.

Results:

Number Status Change category

R00004 CCB Standard Phase-In

R00003 CCB Quick Phase-In

R00006 Submitted Quick Phase-In

R00002 CCB Mandatory

R00005 Submitted Mandatory

14397019

SR 3-5761919890

Software Development Kit

Issue: HOW TO GET EXISTING CRITERIA AND ITS CONDITION USING SDK GETCRITERIA() METHOD

Root Cause: SDK did not have the Is released and Is Introductory operators.

Resolution: Added SDK support for the Is released and Is Introductory operators.

Verification:

1. Create criteria with criteria condition = [$LATESTREV] Is Introductory And [Title Block.Lifecycle Phase] In Inactive And [$CURRENTREV] equal to '$INTRODUCTORY_NOCHANGE'.

2. Get criteria via SDK getCriteria().

Result: The return criteria should be: [$LATESTREV] Is Introductory And [Title Block.Lifecycle Phase] In Inactive And [$CURRENTREV] equal to '$INTRODUCTORY_NOCHANGE'.

14492323

SR 3-6048005991

Searches

Issue: PART-RELATIONSHIP-DOCUMENT SEARCH DOES NOT SHOW RELATIONSHIP DATA

Root Cause: When there is a process-related object attribute, it uses a subclass of the main object, but it should use the elated object's class/subclass id.

Resolution: Correct the code so that it use the related object's class/subclass id.

Verification:

1. Log in to Java Client and set the following subclass configuration Document (subclass), in Page Two, rename multilist01 to Customer Release List, assign Customers to List Part (subclass), in Page Three, rename list01 to "Customer" and assign Customers to List.

2. Create Parts P00350, P00351, assign customer001 to their PageThree.Customer field Create Documents: D00030, D00031, assign customer001 to their PageTwo.Customer Release List field. Add D00030 as P00350's relationship. Add D00031 as P00351's relationship.

3. In Web Client do the following Advanced Searches.

3.1 Items, Part, Relationship Search, Document, do not input any criteria, click Format and select PageThree.Customer and Relationships.Document.PageTwo.Customer Release List into Displayed Fields, make sure PageThree.Customer is on top of Relationships.Document.PageTwo.Customer Release List.

Issue: Run the Advanced Search and there is no value for Relationships.Document.Page Two.Customer Release List in the search result.

Results:

3.1 Run the Advanced Search and see that the correct value for Relationships.Document.Page Two.Customer Release List is in the search result.

14506225

SR 3-6080947144

Web Client

Issue: AGILE - HARD-CODED NAMES IN POP-UP WINDOWS

Root Cause: The label name is from the constants instead of the object attribute.

Resolution: Use the object attribute name instead of the constants.

Verification:

1. Log in to Java Client and go to Admin > Classes > Manufacture Part > General Info > Manufacture Name.

2. Rename the attribute name from Manufacture Name to Manufacture Site.

3. Log in to Web Client, create a new Manufacture Part, the Create New window appears.

4. Complete the popup window and check Manufacture Part's General Info tab.

Results:

3. In the popup window, the field name should be displayed as Manufacture Site.

4. In the newly created Manufacture Part's General Info tab, the attribute displays as Manufacture Site.

14511150

SR 3-5385117741

Admin Config Propagation

Issue: ACP DOES NOT PROPAGATE TITLE PAGE AND PAGE 2 SUBCLASS SPECIFIC HIDDEN FIELDS

Root Cause: Page Two attributes of the subclass are not considered when propagating a subclass.

Resolution: Propagate P1 & P2 attributes of a subclass.

Verification:

1. Open subclass Part

2. Go to its P1 and make attribute Product Line invisible.

3. Go to its P2 and make attribute Notes invisible.

4. Go to its P3 and make attribute Date01 invisible.

5. Use ACP to export subclass Part.

6. Change all three attributes to visible.

7. Use ACP deep compare.

Result: The attributes are reported to be different in the report.

8. Use ACP to import subclass Part back.

Result: The attributes are invisible.

14552877

SR 3-5486909601

Folders, Files, & Attachments

Issue: ATTACHMENT COPY - WRONG VALUES POPULATED ON PASTE

Root Cause: Attachment Type value is not copied from the source row to the destination row.

Resolution: Added code to ensure that the Attachment Type value is copied over to the new row.

Verification:

Precondition: Enable the Attachment Type attribute on the Parts Class, Assign read and Modify privileges of Attachment Type attribute.

1. Create a Part, P1, add an attachment and set a value for Attachment Type.

2. Create a Part, P2.

3. Copy the Attachment row from P1.

4. Paste the Attachment row to P2.

5. Verify the Attachment row on P2.

Result: The Attachment Type attribute value from P1 is pasted to P2.

14621649

SR 3-5995618051

Folders, Files, & Attachments

Issue: UNABLE TO CONTROL TASK INTERVAL OF ATTACHMENT PURGING TASK

Root Cause: When a user changes the configuration from the Java Client UI, the database is updated with the new values (Referred in the code as Node for the Attachment purge task). When you restart the server, however, the values of the interval, frequency, etc. are picked up from elsewhere (Referred in the code as Root Node for the Attachment purge task). The values here are set to an interval of 24 hours, which results in the task being run every 24 hours despite changing its interval from the UI. The design is such that once the task is run for the day, it will not run again. So even modifying the code to pick up the right values would not work.

Resolution: After discussing this bug with product management and internal developers, it was agreed that the interval under Task Configuration should be read-only (grayed out). This would convey to the user that the task interval is non-editable, but at the same time we display the default task interval value.The admin guide will be updated accordingly.

Verification:

1. Log in to Java Client.

2. Navigate to Admin > Server Settings.

3. Verify the Task Interval field.

Result: The Task Interval is set to 1440 by default and the field is read-only.

14713055

SR 3-6277224121

Web Client

Issue: OBJECTS THAT DO NOT MATCH THE CRITERIA CAN BE ADDED TO DYNAMIC LISTS USING DRAG

Root Cause: Criteria based list validation is not included in the code.

Resolution: Enhance the validation process for criteria-based lists.

Verification:

1. In Java Client, create two subclasses of User Groups: Internal UG and External UG.

2. Create two criteria:

InternalUG - User groups General Info.Type In Internal UG

External UG - User groups General Info.Type In External UG

3. Create two dynamic lists with Search type:

InternalUG list - point to criteria: InternalUG

ExternalUG list - point to criteria: ExternalUG

4. Enable two multi-list attributes on Change Orders.Page Two:

MultiList01 - point to InternalUG list

MultiList02 - point to ExternalUG list

5. Add the attributes to the Read/Modify privileges.

6. Log in to Web Client as a user with the above privileges, e.g. Admin.

7. Create a User Group, In_UG1, for Internal UG and create a user group, Ex_UG1, for External UG.

8. Create a new ECO, C001.

9. Click on the MultiList01 search icon and search for all Internal UG - there is only In_UG1 in the search results table.

10. Drag & drop In_UG1 to MultiList01.

Result: The user can successfully drag & drop to MultiList01.

11. Drag & drop In_UG1 to MultiList02.

Result: The user cannot drag & drop to MultiList02.

12. Click on the MultiList02 search icon and search for all External UG. Only Ex_UG1 is in the search result table.

13. Drag & drop Ex_UG1 to MultiList01.

Result: The user cannot drag & drop to MultiList01.

14. Drag & drop Ex_UG1 to MultiList02.

Result: The user can drag & drop to MultiList02.

14728099

SR 3-6166790761

Software Development

Issue: LOCK RFQ RESPONSES

Root Cause: There is no SDK API for lock and unlock RFQ responses rows.

Resolution: Added 2 new API on IRequestForQuote.

Verification:

1. Create one Sourcing Project sp1.

2. Change it to Open status.

3. Add multiple items with BOMs and AMLs into the Items table.

4. Select Items and create an RFQ.

5. Assign Item and AML rows to a supplier.

6. Open the RFQ to a supplier.

7. Lock RFQ response lines by IRequestForQuote.lockResponses().

8. UnLock RFQ response lines by IRequestForQuote.unlockResponses().

Results: SDK is able to lock and unlock responses.

14731209

Internationalization

Issue: COMPLIANCE MANAGER UNTRANSLATED

Root Cause: The Compliance Manager is hard coded in Comments.jsp.

Resolution: Use the I18N tag.

Verification:

1. Log in to Web Client as a Spanish user.

2. Create an IPC 1752-1 declaration and add one Part, P1.

3. Click on the Comment button.

Result: The Compliance Manager is translated into the Gestor de conformidad.

14752311

SR 3-6862539111, 3-6237794121

Notifications & Subscriptions

Issue: APPROVAL REQUIRED NOTIFICATION IS OVERRIDDEN BY NOTIFICATION OF CHANGE RELEASE

Root Cause: Notify user is unique in the Notify list now. Even the user is with a different user group. Only one notification is sent when the user is an approver and acknowledger.

Resolution: Use the user id and user type as a unique key.

Verification:

1. Create a User, user001, with Approve Change Order privilege.

2. Create a User Group, UG001, and add user001 to UG001.

3. Create an ECO, C001, and change the status to Submitted.

4. Click the Next Status button. The Change Status window appears.

5. Add UG001 as an approver and select any.

6. Add user001 in the Notify field.

7. Click Finish.

8. Go to Home > Notification and check notifications.

Result: User001 should receive two notifications - ECO Status Promotion for Observers/Notifiers and ECO Status Promotion for Approvers

14755268

SR 3-5698701261, 3-6286264911, 3-7348415261

Notifications & Subscriptions

Issue: DEVIATION ABOUT TO EXPIRE NOTIFICATION DOES NOT WORK WHEN THE DEVIATION IS IN ANY WORKFLOW STATUS BEFORE EXPIRED

Root Cause: Deviation About To Expire notification can be sent when CCB status is changed from Promoted to Released.

Resolution: Not considering Status condition, in one word, even the Status of Deviation, if it approaches the Effective Date, it sends Expire notification.

Verification:

Note: pcm.notification.deviation.expiry.forwarn.period=48 in the agile.properties by default.

1. Log in to Java Client.

2. Set the Deviations About To Expire Notifications to Email and Inbox in Admin > Server Settings > Database > Notification.

3. Log in to Web Client, and create a Deviation and set it to expire at 2 hours.

4. Check Email Notification.

Result: The Email notification is sent before the expiration.

14811937

SR 3-3575953621

Custom Reports

Issue: FAILED TO DEFINE REPORT QUERY WITH INPUT PARAMETER

Root Cause: There is a defect when defining a query with Relationships Search for custom report.

Resolution: Fix the defect.

Verification:

1. Log in to Web Client.

2. Create a Custom Report CR0001.

3. Define the query as below:

Items > Part > Relationships Search > Part2 Relationships.Part2.Page Three.List01 in a

[IS THIS QUERY COMPLETE?]

4. Edit the query as below:

Items > Part > Relationships Search > Part2 Relationships.Part2.Page Three.MultiList15 Equal To (b;c)

5. Define the query with List01 and MultiList01 on Page Two.

6. Execute the Custom Report, CR0001.

Result: The user can successfully define a query with List/MultiList attribute on Page Two/Page Three when creating a Custom Report. The query returns correct report results.

15876576

SR 3-6432026381, 3-6712276231

Agile Content Services

Issue: EXCEPTION [SECURITY:090398]INVALID SUBJECT: PRINCIPALS=[WEBLOGIC, ADMINISTRATORS

Root Cause: In the ACS extract thread, two user contexts are created. ctx1 is first created to lookup JMS resource which is located on the SOA server. Then, ctx2 is created to lookup the JDBC data source. When call ctx2.lookup(), ctx1 is not closed and the current context in ACS extract thread is ctx1, that causes the error.

Resolution: Minimized the context variable scope and closed the context after it is used.

Verification:

1. Connect to an AIA setup from Agile.

2. Test if the destination is successful.

3. Release an ECO.

4. Verify the server logs.

Result: The ATO is successful to Complete. There is no SecurityException logged in the stack trace.

15893095

SR 3-6298847441, 3-6416127731

Searches

Issue: FTS TASK CONFIGURATION DOES NOT WORK

Root Cause: Active is not considered when we try to save the configuration.

Resolution: Include active for full text search task.

Verification:

Precondition:

1.Make sure that the FTS search works properly. If FTS is not working, please run FTS scripts with the latest version and restart the application server.

2. Make sure that the file types are supported by FTS.

Steps:

1. Log in to Java Client as admin.

2. Go to System Settings > Full Text Search.

3. Set the Indexing: Scheduled Recurrence: Every 1 hours starting at 1:00pm Ending at:5:00 PM on sunday, Monday, Tuesday, Wednesday,...

4. Click OK. Save it.

5. Go to Task Configuration in the Server Setting.

6. Open the Full Text Search. Set the Task Interval:5 or other values(small) Set the Task Lookback Windows: 30

7. Save.

8. Log in to Web Client or Java Client.

9. Create some objects like Parts and add some attachments including content: shanghai.

10. Wait until schedule time has passed.

11. Go to the Task monitor. You will see the Full Test Search record on the finished filter.

12. Log in to the server and do a full search on the Advanced Search: File Document Text contains shanghai.

Result: The Parts can be searched successfully with attachment files.

15901823

SR 3-6451442021

Software Development

Issue: UOM (UNIT OF MEASURE) CONVERSION RELATED APIS MENTIONED IN THE AGILEPLM9.3.1.2 ARE NOT WORKING

Root Cause: There is no implementation for these APIs in the server.

Resolution: Mark these APIs as internal from 9.3.3. The customer can use the workaround as below:

double convertFrom = 1234.21;

com.agile.api.IUnitOfMeasureManager uomManager =

(IUnitOfMeasureManager)session.getManager(IUnitOfMeasureManager.class);

fromUOM = uomManager.createUOM(0, "Kilogram");

toUOM = uomManager.createUOM(0, "Gram");

IUnit fromUnit = fromUOM.getUnit();

IUnit toUnit = toUOM.getUnit();

double conversionFactor =fromUnit.getConversionFactor()/toUnit.getConversionFactor(); => in above example return 1000/1 =1000

double convertedValue = convertFrom *conversionFactor;

Verification:

1. Open the Indext.html under SDK_AIS_Sample\sdk\documentation\html

2. Go to Class List under AgileAPI in leftPane

3. Open IUnitOfMeasure

Result: There is no IUnitOfMeasure convertTo (IUnit unit) throws APIException IUnitOfMeasure convertTo (String unit) throws APIException

4. Open IUnitOfMeasureManager

Result: There is no IUnitOfMeasure convert (double value, IUnit from, IUnit to) throws APIException.

15955140

SR 3-6303076691

Folders, Files & Attachments

Issue: OPENING AN ATTACHMENT VIA GET SHORTCUT THROWS !NULL ERROR

Root Cause: There is a bug in the code that does not handle the case when there are no subclasses for File Folder and Design.

Resolution: Fixed the code to handle the situation when there are no subclasses, in case the subclasses from the Agile out-of-box database were deleted.

Verification:

1. Log in to Web Client.

2. Create a Part, add an attachment.

3. Select a file, from the More menu GetShortcut.

4. Paste the URL into the browser.

5. Log in with proper user credentials.

Result: The file downloads successfully.

16027365

SR 3-6569142881

Admin Config Preparation

Issue: UNABLE TO PROPAGE USER GROUP WHEN ACP USER IS NON-ENGLISH USER

Root Cause: In the case of the non-English user node, id is not found, so the ACP code fails to find a User Group object.

Resolution: Modified the SQL script in the code to handle the missing user id.

Verification:

1. Log in to Java Client as admin.

2. Create a new User Group,Group1.

3. In ACP, configure project.properties, set the ACP user as a Non-English user, e.g. an Japanese User, and make sure that the user has privilege to propagate.

4. Configure:

<copy>

<user_group user_association_rule="replace"/>

</copy>

5. Run ACP export: acp export golden.

6. Delete User Group Group1.

7. Run ACP import: acp import golden dev.

8. Check import.err log.

Result: No error message.

9. Check the new group in Java Client.

Result: The group has been imported successfully.

16044709

SR 3-6569142881

Admin Config Preparation

Issue: APPLIED TO OF MANAGE REPORT PRIVILEGE FAILS TO PROPAGATE THROUGH ACP

Root Cause: TheManage Report privilege is not considered as an object-level privilege while propagating Applied To attributes.

Resolution: Include the Manage Report privilege into object-level privileges.

Verification:

Precondition: Set the golden instance and dev instance as the same URL.

Steps:

1. Log in to Java Client as admin.

2. Select Privileges - Manage Report - Manage All Reports.

3. Choose all nodes in Applied to.

4. Config in ACP:

<copy>

<privilege objects_per_file="1000"/>

</copy>

5. Export golden property: acp export golden.

6. Import golden to dev: acp import golden dev.

Result: There is no change in the Applied To area.

16095111

SR 3-6633137781

Internationalization

Issue: CHINESE WARNING MESSAGE IS INCORRECT WHILE DELEGATE THE OWNER OF A PROGRAM

Root Cause: Messages.properties MSG_Delegate_Activity_Not_Accepted = Delegation of this activity has not been accepted by {0}. The translation is not correct.

Resolution: The correct translation should be like: MSG_Delegate_Activity_Not_Accepted={0}\u672a\u63a5\u53d7\u6b64\u6d3b\u52a8\u7684\u59d4\u6258

Verification:

1. Log into Web Client as a Traditional Chinese user (Language is Traditional Chinese).

2. Try to delegate a Program to others like (sammi, we).

3. Go to the Team tab.

Result: It shows a Chinese message like "sammi, we 未接受此作業&# 30340;授權 "

If you log in to Web Client as an English user, in the same case, it shows an English message like "Delegation of this activity has not been accepted bysammi, we".

16219218

SR 3-6713888711

DB Upgrade/AUT for RMW

Issue: OOB, PL/SQL PACKAGE MM_UTILS_SP DOES NOT COMPILE, TABLE D_INT_WEBSERVICE_OPERATION

Root Cause: N/A

Resolution: N/A

Verification: N/A

16313161

Software Development

Issue: SUPPORTING API TO VALIDATE ITEM ON AML TAB

Root Cause: This feature was not supported in SDK.

Resolution: New API IProject.validateItems(List itemRows,List amlRows) was added to support this feature.

Verification:

1. Create a Sourcing Project.

2. Import items with BOM and AML containing invalid Items, Manufacturers and Manufacturer Parts (not found in the Item Master) into the Sourcing Project.

3. Run the following sql2 scripts for Item, Mfr and Mfr Part.

4. Create the Items, Manufacturers and Manufacturer Parts in Item Master.

5. Using SDK, do a validation by IProject.validateItems().

6. Run below sql1 and sql2 scripts for Item, Mfr and Mfr Part.

***************************

==>Item sql1>SELECT ID FROM ITEM WHEREITEM_NUMBER='<Item Number>';

sql2>SELECT SCI_ITEM_SRC_FK from sc_item WHERE

SCI_PROJECT_FK IN(SELECT PJ_PK FROM PROJECT

WHERE

PJ_NUMBER='<SP Number>') and

SCI_ITEM_NUMBER='<Item Number>;

==>Mfr and Mfr Part

sql1>SELECT ID, MANU_ID FROM MANU_PARTS WHERE

MANU_ID IN(SELECT ID FROM MANUFACTURERS WHERE

NAME='<Mfr Name>') AND part_number = 'MfrPart

Number';

sql2>SELECT SCI_MANUFACTURER_PART_FK,

SCI_MANUFACTURER_FK from sc_item WHERE

SCI_PROJECT_FK IN(SELECT PJ_PK FROM PROJECT

WHERE

PJ_NUMBER='<SP_Number>') and

SCI_ITEM_NUMBER='<MfrPart Number>' AND

sci_manufacturer='<Mfr Name>';

Result:

1. Before the validation, the returned value for SCI_ITEM_SRC_FK, SCI_MANUFACTURER_PART_FK and SCI_MANUFACTURER_FK in sql2 is null.

2. After the validation, the returned values for SCI_ITEM_SRC_FK, SCI_MANUFACTURER_PART_FK and SCI_MANUFACTURER_FK in sql1 and sql2 should be same, not null.

16313166

Software Development

Issue: SUPPORTING API FOR UPDATE CONTENT FROM ITEM MASTER

Root Cause: Agile SDK API does not exist to support this functionality.

Resolution: Enhanced Agile SDK by adding new API IProject.updateContentFromItemMaster(Map Params) to support the ability to update content from Item Master.

Verification:

1. Create one Sourcing Project, sp1.

2. Add an Item with BOMs and AMLs into sp1.

3. Add/Delete/Update BOM Items in Item Master.

4. Add/Delete/Update AMLs in Sourcing Project By SDK.

5. Choose All Content and Synchronized AMLwith Item Master.

6. Do Update by IProject.updateContentFromItemMaster().

Result: The BOM and AML in the Sourcing Project should be the same as the Item Master after the update.

16313173

Software Development

Issue: SUPPORTING API FOR UPDATE AML FROM ITEM MASTER

Root Cause: Agile SDK API does not exist to support this functionality.

Resolution: New API IProject.updateAMLfromIM() added to support this feature.

Verification:

1. Add an Item with AMLs into a Sourcing Project.

2. Update AML values in Item Master.

3. Using SDK, do an Update AML from Item Master by IProject.updateAMLfromIM() with the following combination.

>Update the Approved Manufacturer List--- checked

>>>Overwrite changed mande in this Sourcing project --- selected

>Update the approved Manufacturer List Attributes ---checked

>>>Overwrite changed made in this Sourcing project -- Selected

Result: The AML changes in the Item Master are updated to the Sourcing Project.

16338994

SR 3-6798654301

Averify Issues

Issue: ADDING ITEMS TO SOURCING PROJECT THROWS ERROR

Root Cause: Added a new case to Averify.

Resolution: Fixed the script.

Verification:

1. Import 9312 demo DB and SELECT DISTINCT VALUE FROM PROPERTYTABLE WHERE PROPERTYID=625 AND VALUE IS NOT NULL;

2. SELECT * FROM NODETABLE WHERE OBJTYPE=21 AND ID IN ( <VALUE FROM 1>);

3. If Step 2 returns a null value, set OBJTYPE=21 to the records in Step 1.

4. Run Averify.

5. Check oracle_averify_report.log.

Result: The following error appears in the report:

AGIL-00025150 : E : PROPERTYTABLE table has bad data (NODETABLE ID: XXXXX was assigned to wrong PROPERTYTABLE Values.) XXXXX is the ID you set in step 3.

16530517

SR 3-6928155401

DB Upgrade/AUT

Issue: MANUFACTURER OBJECT WHERE USED TAB - WEB CLIENT NULL & JAVA CLIENT UNKNOWN ERROR

Root Cause: The data is incorrect in the database before the upgrade.

Resolution: Corrected the value when upgrading to 9.3.3 or later during the upgrade.

Verification:

1. Import 9312 demo DB.

2. Set all attributes on the Where Used tab of the Manufacturer to visible.

3. Set P2 List 14 of Manufacturer Part to visible.

4. Create a Manufacturer, M4, and Manufacturer Part, MP4, with M4. Set the value of MP4's P2 List14. Create a Part, P4, and add MP4 into P4's Manufacturer.

5. Generate bad data with the developer's script.

6. Go to M4's Where Used tab and an "Unknown Error" appears.

7. Upgrade with AUT.

8. Check M4's Where Used tab again.

Result: No error appears and the value of Mfr.Part List14 displays correctly.

16539357

SR 3-6968778691

Process Extension (PX)

Issue: WORKFLOW PX AT CCB IS NOT GETTING EXECUTED DURING AUTO PROMOTION

Root Cause: The customer configured Change Status Event for the workflow, and also configured PX at the CCB status. The Change Status Event updates a Page Two attribute at CCB status, which also automatically triggers auto promotion (updated status from CCB to Validate). The PX at CCB status does not run at all.

Resolution: Add a flag into the SDK session, so that customization users can control whether to auto promote when updating attributes for routable objects.

Verification:

1. Log in to Java Client as admin.

2. Create a Change Status Event on a Change Order workflow which will get executed when there is a status change (Submit to CCB). The event will modify Change.Page Two.Date Attribute.

3. Set up a PX at status CCB of Change Order, which will get executed and print the name of the Change Order.

4. Set Auto Promote = Yes at CCB status of Change Order.

5. Log in to Web Client as admin.

6. Create a Change Order and change status to CCB.

7. Validate the change and the History table.

Result: The change status is auto-promoted to Released. The action about the triggered PX and event are logged in the History table.

16635666

SR 3-6923451441

Web Services

Issue: CHANGESTATUS SERVICE DOES NOT SET DEFAULT APPROVERS

Root Cause: When a Change Status action is triggered by a web service, the system does not add the default reviewers that were set in Java Client.

Resolution: Add default reviewers when the request is from web service.

Verification:

1. Go to Java Client for a Change Order like ECO and Add Default Approvers for the next Status,

like Review Status.

2. Through the Change Status Webservice, change the Status of the ECO.

3. Verify that the Default Approvers are added when the status is changed to Review.

16686545

SR 3-7080256351

DB Upgrade/AUT

Issue: GETTING ERRORS WHILE RUNNING AUT EXECUTE-FTS-POST-TASKS-921 ON 9.2.2.4.110

Root Cause: This was unsupported in previous version, 1.7.5 new feature.

Resolution: Support 9.2.2.4.110 in AUT 1.7.5.

Verification:

1. Go to ..\AUT\bin folder.

2. Run update_content_url.bat/sh.

3. Check the update_content_url.log in logs folder.

Result: Update_content_url.bat and update_content_url.sh are added in the bin folder. The log shows "BUILD SUCCESSFUL".

16716380

SR 3-6624739471

Folders, Files, & Attatchments

Issue: SUPPORT SSL MODE (HTTPS) FOR CONNECTION BETWEEN FILE MANAGER AND APP SERVER

Root Cause: There is a bug in the custom axis implementation where the WebLogic specific Session ID is not recognized.

Resolution: Fixed the issues in axis.jar.

Verification:

1. Configure the application server in SSL mode.

2. Configure the File Server in SSL mode.

3. Start the application server.

4. Start the File Server.

Result: The application server and the File Server started successfully without any errors.

16752369

SR 3-7124641071

Standard Reports

Issue: WHEN RUNNING USER USAGE REPORT, RETURNS INVALID INFORMATION

Root Cause: A NumberFormatException occurs when parsing User information from User Group.

Resolution: Fix the exception.

Verification:

1. Log in to Web Client as admin.

2. Create a User Group, UG0001, and add 3 users to the User Group.

3. Log in as these 3 users and do some actions.

4. Log in to Web Client as admin.

5. Execute the User Usage Report.

6. Add the User Group, UG0001, to the report and click the Finish button.

Result: The 3 users in the User Group, UG0001, are displayed in the report result