Skip Headers
Agile Product Lifecycle Management Readme
Release 9.3.4
E52160-02
  Go To Table Of Contents
Contents

Previous
Previous
 
Next
Next
 

3 Resolved Issues

This chapter lists issues that were resolved during this release.

3.1 Product Collaboration

10038556

Changes

Issue: BULK CHANGE WIZARD ON THE AFFECTED ITEMS TAB SHOWS WRONG ITEM STATUS

Root Cause: When the user used the "Add an item to multiple assemblies" action in bulk change, the system showed an "Introductory" value of the Item's revision as the default value in the Status column in the Add table.

Resolution: Change the code to show the value of the Item's latest life cycle phase.

Verification:

  1. Log in to Web Client as admin.

  2. Create an Item, P1.

  3. Create an Item, P2, and release it with Lifecycle Phase = Production.

  4. Create an Item, P3, and release it with Lifecycle Phase = Prototype.

  5. Create a Change Order, ECO1, and do a BOM Bulk Change.

  6. Select to Add an item to multiple assemblies in the BOM Bulk Change tab

  7. Click Next.

  8. Add a new Part to the Item to add filed. Click Next.

  9. Click Add.

  10. Add P1,P2, andP3 into it.

Result: Check the status of P1, P2, and P3. All of the statuses are displayed as previously set.

13340887

Web Client

Issue: PLANNING AND EXECUTION WORDING DOES NOT DISPLAY CORRECTLY ON THE WORKFLOW SCREEN

Root Cause: The status name is trimmed to 20 characters.

Resolution: Trim the name to 50 characters.

Verification:

  1. In Admin, open Default Change Orders, and change the CCB status name to PLANNING AND EXECUTION.

  2. In Web Client, create an ECO.

  3. Move to PLANNING AND EXECUTION status, and check the status title for the ECO.

Result: The status name is shown completely when the length is less than 50. The words PLANNING AND EXECUTION are showing completely.

14242408

Item & BOM

Issue: ERRONEOUS DISPLAY OF REDLINE ITEMS IN REDLINE BOM TAB

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

Resolution: Make the Redline BOM table refresh after rows are added.

Verification:

  1. Create a Part, P1.

  2. Add more than 50 parts as P1's children.

  3. Create an ECO for P1.

  4. Add one more redline child by add search.

  5. Go to the next page to display the Affected Item's redline BOM values.

    Result: The values are displayed properly. There are no duplicated rows.

  6. Click Add by Create New.

  7. Go to the next page to display the Affected Item's redline BOM values.

    Result: The values are displayed properly. There are no duplicated rows.

  8. Drag one Part from the Recently Visited field.

  9. Go to the next page to display the Affected Item's redline BOM values.

    Result: The values are displayed properly. There are no duplicated rows.

14505722

Folders, Files, and Attachments

Issue: BATCH PRINT FROM JAVA CLIENT DOES NOT PRINT PAST 10 PRINTS

Root Cause: The bug is specific to JDK6.

Resolution: Resolved with Java SE 7u45. https://bugs.openjdk.java.net/browse/JDK-8000555

Verification:

  1. In any text editor or word-processing application that can save a text file, type the Item's type and a comma.

    Note: The entries you type in steps 1 and 3 are case-sensitive. For example, if the item you want to batch print is Rev B, Rev b will not print

  2. Type the 15 Item numbers that have attachments and a comma.

  3. Type the Item's Rev and a comma.

    Example: Part,015016,B (Should not have spaces)

  4. Select Java Client > File menu > Batch Print.

  5. Browse Input File.

  6. Click Print.

Result: Batch Print prints files in the Attachment tab of BO which are listed in the input file.

14546449

Mfr/Mfr Parts

Issue: DISCOVERY PRIVILEGE DOES NOT WORK WITH MANUFACTURER PARTS

Root Cause: There is a special handling for Object MfrPart to check privilege. If a user has the privilege to discover manufacturers, he is also able to discover the corresponding Manufacturer Parts.

Resolution: Access to Manufacturer Parts will not check the privilege of Manufacturer.

Verification:

  1. Log in to Java Client as admin.

  2. Create a new user, u001, with the following privileges:

    - discover all Manufactures

    - discover Manufacturer Parts with criteria CR1:Manufacturer Parts > General Info.Lifecycle Phase > In > Active

    - read Manufacturer Parts with criteria CR1

  3. Log in to Web Client as user u001.

  4. Do a quick search: Manufacturer Parts >*.

Result: Only Manufacturer Parts in GI.Lifecycle Phase In Active can be found.

14580639

Web Client

Issue: PROBLEM WITH AGILE ADVANCED SEARCH FOR CHANGE

Root Cause: When the count of list (Workflow status) entry is over 2500, the display type is set from list to search. An error is thrown when saving the value.

Resolution: Fix the defect when saving the value.

Verification:

  1. Log in to Web Client as admin.

  2. Do an Advanced Search: changes >change orders > Workflow.workflow status > Equal to/Not Equal to > Default change orders.CCB, run the search.

    Result: It prompts an error message: Workflow Status can only be used in a criteria group along with other workflow attributes.

  3. Change the search criteria: changes > change orders > Cover page.Number > start with > try to input value.

    Result: The user can change the search criteria and enter values successfully.

14611663

Item & BOM

Issue: MISSING SUB-ASSEMBLY WHEN ADDING PARENT ASSEMBLY TO SOURCING PROJECT

Root Cause: This is caused by bad data. The system des not have a special handler for this situation.

Resolution: Added a constraint clause in procedure "addBomRowEx" to get the correct BOM flag. With this change, the customer can use the Edit > Update from Item Master action to recall the procedure to update the BOM tree for existing Sourcing Project objects.

Verification:

  1. Create 3 parts: P00001, P00002, P00003.

  2. Add P00001 to P00002's BOM tab, add P00002 to P00003's BOM tab.

  3. Create a change order C00001, add P00002 to C00001's Affected Items tab, set the new Rev value as 1.

  4. Release C00001.

  5. Create a Deviation D00001, add P00002 to D00001's Affected Items tab, set Revision value as 1.

  6. Use Actions > Save As from D00001 to create a new Deviation, D00002.

  7. Release D00001, then release D00002.

  8. Create a Sourcing Project, PRJ00001.

  9. Add P00003 to PRJ00001's Item tab.

Result: P00002 displays as an assembly under P00003 in the Sourcing Project's Items tab.

14753590

Web Client

Issue: CHANGE METRICS REPORT - DATE/TIME ON THE REPORT IS SHOWING 7 HOURS OFF

Root Cause: Transfer of the status date two times caused the time to be off.

Resolution: Correct the transfer.

Verification:

  1. Log in to Web Client as admin.

  2. Set the Preference field Time Zone to (GMT-08:00) Pacific Time (US/Canada), Tijuana.

  3. Create a Change Order, then change the status to Submitted.

  4. Go to Reports and Analytics > Standard Report > Process Reports > Change Metrics Report, and choose this Change Order.

  5. Click Execute.

  6. Compare the submit date with the submitted date in the Change History tab.

Result: The two dates are the same.

14808619

Java Client

Issue: CHECKING IN DESIGNS WITH STRUCTURES/WHERE USED PURGES OLD VERSIONS-SIGNIFICANT

Root Cause: In the auto-purging version, it purges without checking if it can be purged, as is the case in manual purging.

Resolution: Force checking in case of auto-purge.

Verification:

Precondition: In Viewer & Files set Auto Purge Enabled to Yes. File Version Keep to 3

  1. Create several Design objects with Structure.

  2. Open a component design and check it out and back in though MCAD adapter or Manually checkout/checkin.

  3. Repeat this for the component until several versions are created, and the number of versions exceeds auto-purge rules for attachment versions.

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

Result: The AutoPurge task does not purge the versions of Designs if the design is a component of another design.

14826061

Performance

Issue: TAKES LONG TIME TO ADD HUNDREDS OF DESIGNS TO DESIGN STRUCTURE

Root Cause: There are unnecessary calls of marchalTable() during the append rows process. There was a similar performance issue with delete rows, too. Also, when a structure row was added to another one, the parent row did not show up under the Where Used table of the appended row.

Resolution: Resolved in AttachmentService.java and DesignServiceStructure.java by eliminating unnecessary calls to marchalTable() and by preventing refresh object during append/delete row actions. We also forced the WhereUsed table of an appended object to be reloaded, so a parent object will show up under the Where Used table.

Verification:

  1. Log in to Web Client.

  2. Open the existing design structure.

  3. Search and add 100 design objects.

    Result: This process now completes within 5 secs.

15829839

Item & BOM

Issue: CHANGE-CONTROLLED ATTRIBUTE IS REDLINED UPON REDLINE OF THE OTHER ATTRIBUTE

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

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

Verification:

  1. In Admin, set RedlineAttributes = Allow.

  2. Set Parts.Page2.Text11 and MultiText31 as Redline Controlled.

  3. Log in to Web Client using Internet Explorer browser.

  4. Create Part01, edit Page2.MultiText31 with at least 2 rows.

  5. Create Part01, edit Page2.MultiText31 with at least 2 rows.

  6. Log in to Web Client using FF browser.

  7. Open ECO01 and go to Part01's Redline Title Block tab.

  8. Redline edit Page2.Text11 with a new value, click Save.

Result: Page2.MultiText31 is remaining its value. Only Page2.Text11 is redlined.

15841564

Java Client

Issue: UNABLE TO CREATE A DYNAMIC LIST FOR USER BELONGING TO PARTICULAR USER GROUP

Root Cause: Currently, we do not support it in the search module.

Resolution: Remove the attribute from criteria selection list with Bug15841564.sql.

Verification:

  1. Log in to Java Client as admin.

  2. Open Criteria > Create Criteria.

  3. Enter the name, for example, users, and select the Object Type: Users.

  4. Click Add, check the Attributes.

    Result: The user Groups: Group Name is removed from the attributes list.

15858424

Changes

Issue: BOM VALUES WITH DECIMALS IS DIFFERENT WHEN SEEN UNDER ECO REDLINE

Root Cause: There is an incorrect configuration for numeric value for BOM redline table in TableConfig.xml.

Resolution: Update the configuration.

Verification:

  1. In Admin, enable a numeric attribute, that is, a BOM.NUMERIC01, with scale = 3.

  2. In Web Client, create a Part with a BOM and add a value to the above field, for example. 0.123.

  3. Create a new Change and add the Part to the Affected Items tab.

    Result: In the ECO's Affected Items-> Redline BOM table, the numeric is showing with leading 0, 0.123.

  4. Create a new Change and drag/drop that same Part onto the Affected Items tab and say OK to the warning that it is on another Change.

    Result: In the new ECO's AI > Redline BOM table, the numeric is showing with leading 0, 0.123.

15878794

Standard Reports

Issue: LOGIN FAILURE REPORT - ADMIN REPORT DOES NOT WORK IN CLUSTER ENVIRONMENT

Root Cause: Login failure does not need to be recorded into AUTH_FAILED in the WLS environment.

Resolution: Add.

Verification:

  1. Log in to Java Client as admin.

  2. Create 2 different user accounts:

    test1/agile

    test2/agile

  3. Log in to Web Client as test1/test.

    Log in to Web Client as test2/test.

    Log in to Web Client as test3/test.

    Log in to Web Clientas admin/agile.

  4. Execute the Standard Reports > Administrator Reports > Login Failure Report.

  5. Check the result.

    Result: The results show the user with invalid passwords (test1,test2) and the user with an invalid username (test3).

15902198

Standard Reports

Issue: CHANGE PACKAGE REPORT FAILS FOR ECO WITH DESCRIPTION OF MORE THAN 3K CHARACTERS

Root Cause: This is a code defect. The dead loop is caused when the description of the Change covered the full page.

Resolution: Fix it.

Verification:

  1. Log in to Web Client.

  2. Go to Reports and Analytics > Standard Reports > Process Report > Change Package Report.

  3. Execute the report.

  4. Select an ECO with a description of more than 3k characters, finish.

    Result: The user is able to execute the report and see the results of the report without any issue.

16064533

Standard Reports

Issue: USAGE REPORT IS OVER-REPORTING USER SYSTEM USAGE

Root Cause: LDAP user usage is over-reported.

Resolution: Fixed the problem.

Verification:

  1. Log in to Web Client as ldapdemo1/Oracle2011 at 10:00.

  2. Log out of Web Client at 10:05.

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

  4. Log out of Web Client at 10:35.

  5. Log in to Web Client as admin.

  6. Go to Standard Report > Administrator Report > User Usage Report.

  7. Execute User Usage Report with user ldapdemo1 and Date Range from 10:00 to 10:40, Finish.

  8. Check the result.

    Result: Duration of the report should be 10 mins.

16180963

User Group

Issue: CANNOT ASSIGN USERS TO USER GROUPS USING ADD DROPDOWN SELECTION

Root Cause: When updating the values hidden for the auto-complete function, a map used to keep selected values holds values as their keys, but the keys used to fetch values are not correct from the second key. Some blank spaces are still appended in front of these keys, and no values can be retrieved.

Resolution: Trim keys before getting values using them.

Verification:

  1. Log in to Java Client as admin.

  2. Go to Admin > Server Settings > Preference, set Display UserID to No.

  3. Log in to Web Client as admin.

  4. Search for a User Group, go to its Users tab, and try to add 3 users to it by clicking the Add button

  5. Type one character such as A and allow auto-complete to select one user, Type one or several character(s) such as test, and allow auto-complete to select one user. Type one or several character(s) and allow auto-complete to select one user and press Enter.

    Result: All selected users can be added to the Users table successfully.

16199174

Item & BOM

Issue: UNABLE TO VIEW REDLINE OF BOM EXCEPT FOR ITEM NUMBER AND ITEM REV

Root Cause: When the user clicks one Affected Item in a Change object, the system sets this change as the current revision in the context, so when the read privilege of the related redline BOM is checked, the system evaluates this change as the current rev of the redlined BOM, but this rev was always not equal to the latest rev of the redlined BOM. It blocks the user to see all the values under the redline BOM tab.

Resolution: Get the latest rev of the redlined BOM as the current rev.

Verification:

  1. Log in to Java Client, set the value of DisplayBOMTables to Display with just Part Num and Rev in SmartRules.

  2. Create a criteria, All items Pending and Latest Rev Only, with the condition, Items $CURRENTREV Equal To $INTRODUCTORY_PENDINGCHANGE Or $CURRENTREV Equal To $STATUSTYPE.PENDING Or $CURRENTREV Equal To $STATUSTYPE.REVIEW Or $CURRENTREV Equal To $STATUSTYPE.SUBMIT Or $CURRENTREV Equal To $UNASSIGNED Or $CURRENTREV Equal To $LATEST, and create a read Item privilege, Read Unrestricted Items Pending and Latest Rev Only, with this criteria.

  3. Create a user with the new read Item privileges, then add other privileges Discover Items, Discover Changes, Read Changes to this user.

  4. Log in to Web Client as admin. Create a Part with one BOM, then add this Part to a pending change object which with the workflow Default Change Order.

  5. Log in to Web Client as the user created in step 3.

  6. Open the ECO and check the Part's Redline BOM table.

    Result: The user is able to read all values from the Redline BOM table, just like the BOM table.

16428591

Administration/Configuration

Issue: RECEIVING ERROR 'UNKNOWN NUMBER: OBJECT DOES NOT EXIST' WHEN CREATING TRANSFER AUTHORITY

Root Cause: There is a NumberFormatException that occurs when parsing User information from User Group.

Resolution: Fix the exception.

Verification:

  1. Log in to Web Client as admin.

  2. Create a new User Group, UG1, and add user, tommyhuang, as a member.

  3. Create a Transfer Authority as below and select the user, tommyhaung, from user group UG1 as the To User in the TA creation window.

    To User 'tommyhuang'

    Criteria: Global.All Activities

    Start Date: 2013-10-15 12:00:00 AM PST

    End Date: 2013-10-27 12:00:00 AM PST

    Affected Changes: All Changes

  4. Save the change.

    Result: The TA is created successfully without error.

16456341

Web Client

Issue: ERROR LOOKING UP SESSION WITH ID

Root Cause: Same classes do not implement interface Serializable, so it failed to replicate the object across the servers.

Resolution: The classes now implement serializable.

Verification:

  1. Create 2 Items, P00001 & P00002, in a clustering environment

  2. Create a Change, C00001.

  3. Add P00002 to the BOM tab of P00001.

  4. Add P00001 tab of C00001.

  5. Add P00002 to the BOM tab of C00001

  6. Specify the Excel sheet: Item,Change,affected item,BOM,Qty P00001,C00001,P00001,P00002, 4

  7. Import the Excel sheet and do the redline BOM.

  8. Refresh the redline BOM after 5 minutes.

    Result: The redlined BOM is available. Refreshed after 5 minutes and verified the server side files (java.io.NotSerializable Exception ) like the agilePCWeblogic.log and Agile server log and there is no error message.

16486717

Notifications and Subscriptions

Issue: APPROVAL EMAIL NOT SENT WHEN USER BELONGS TO USERGROUP BEING NOTIFIED

Root Cause: The notified user is unique in one notify action. When the same user is in a different user group - one group is in the Approver list and another one is in the Notifier list, the notification only sends one notification randomly to either the approver or notifier.

Resolution: Combine user id and user type as a unique key.

Verification:

Precondition: Configuration of Notification setting in JavaClient

  1. Create a User, UserA, with the following roles: Approve/Reject and Acknowledge, Change Analyst, Component Engineer

  2. Add UserA to a User Group, UG1.

  3. Create a Change and route it to Review status. Add the User Group as Notify and UserA as Approver.

    Result: UserA receives the change status notification and the Approval Required notification.

16496098

Web Client

Issue: DATE ORIGINATED VALUE IS DIFFERENT WHEN THE SERVER TIME HAS A DELAY

Root Cause: At code level, we set our current server time for Date Originated, but there is also a trigger on the database side which set the value to the current DB server time when inserting a new Change.

Resolution: Update the trigger to only use DB server time when it is not set in the application server time.

Verification:

  1. Re-set the application server's date & time to one day later than the current date (make sure the application server and DB server are different machines).

  2. Log in to Web Client as admin.

  3. Create an ECR and check the value of Date Originated.

    Result: It is the same as the application server's date & time.

16546175

Administration/Configuration

Issue: WHEN PERFORMING A SAVEAS ON A CRITERIA THAT CONTAINS THE ATTRIBUTE TITLE BLOCK.LIFECYCLEPHASE WE GET ERROR

Root Cause: N/A

Resolution: N/A

Verification:

  1. In Admin, go to Items > Documents > Lifecycle Phases and add a new Lifecycle Phase named Active.

  2. Go to the Criteria node and create a new criteria "Test DJK 7" that has the Documents object type, and the condition Title Block.Document Type In Documents.

  3. Click Save As to create a second criteria.

  4. Edit the Test DJK 7 criteria again and put the condition as below: Documents Title Block.Document Type In Document And Title Block.Lifecycle Phase In Active.

  5. Click Save As to create a new criteria.

    Result: The user is able to create the new criteria.

16595640

Item & BOM

Issue: CANNOT EDIT BASE MODEL ATTRIBUTE

Root Cause: Max System Length is less than Max Length.

Resolution: Make Max System Length equal to Max Length with Bug 16595640.sql.

Verification:

  1. Go to Java Client > Admin tab > Data Settings > Classes >Parts >User Interface Tabs > Title Block > Base Model attribute.

  2. Try to change the name from "Base Model" to" Base".

    Result: The value can saved successfully.

  3. Modify "Base" to be "Base_testing".

  4. Click Save.

    Result: The value can be saved successfully.

16635869

Folders, Files & Attachments

Issue: WHEN USING THE OPEN ATTACHMENTS COMMAND, IT INCORRECTLY LAUNCHES CREO TO OPEN PDF CREATED BY EC 3.1.0.1

Root Cause: The filename of the first row in the File table of File folder is incorrectly chosen for the OPEN file action.

Resolution: Choose the correct filename for the corresponding open file.

Verification:

Precondition: In A9 Java Client > Admin > System Settings > Preferences > Allow Download of Productivity Components should be set to Yes or No.

Steps:

  1. Log in to A9.

  2. Create a File Folder or Design and upload 3 files to it in this order: JPG, an XLS file and a PDF file and check in.

  3. Create a Part and navigate to the Attachments tab.

  4. In the Part's Attachments tab, click the Add > Add By Search button.

  5. Search for the File Folder or Design created in step 2 and add the files to the Part object in the same order as before.

  6. Select the PDF file row and click on Open.

    Result: The PDF file is opened in its native application (Adobe reader).

  7. Select the XLS file row and click on Open.

    Result: The XLS file is opened in its native application (Microsoft Excel).

  8. Select the JPG file row and click on Open.

    Result: The JPG file opens in its native application (Windows photo viewer or MS Paint).

16721531

Web Client

Issue: URLS CREATED FOR ATTACHMENTS DO NOT WORK FOR GENERAL USERS

Root Cause: If a user does not have access privilege, the fold name he get will be null, which leads to this issue.

Resolution: 1. Do not provide a URL if the user clicks "Get Shortcut" without access privilege. The application throws an appropriate error "You do not have access to download the selected attachment. A URL cannot be generated." 2. If a user without the access privilege tries to download a file using the complete URL, throw the following error "Insufficient privilege to get file(s)"

Verification:

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

Admin User:

  1. Log in to Agile as admin.

  2. Navigate to an Item that has an Attachment, then click on the Attachments tab.

  3. Select one of the file attachments. Go to More > Get Shortcut. Copy the Complete URL from the dialog box.

  4. Paste the URL on Safari and the file is successfully downloaded.

General User:

  1. Log in to Agile as a general user.

  2. Navigate to an Item that has an attachment, then click on the Attachments tab

  3. Select one of the file attachments. Go to More > Get Shortcut. Copy the URL from the dialog box.

  4. Validate the URL in dialog box for General User for GetShort Action.

    Result: The complete URL is shown in dialog box for General User.

  5. Paste the URL on Safari and validate the message shown in the browser.

    Result: The ”Insufficient privilege to get file(s)" error is shown on Safari browser.

16756815

Java Client

Issue: ADDRESS BOOK ALWAYS SORTS USERS IN USER GROUP BY FIRST NAME

Root Cause: The application always sorts the users in a User Group by first name regardless of how the user names are displayed. JavaClient > Admin > Preference >Default User Name

Resolution: UserGroupService.java public VOUserBasic[] getOrgUsers(IClientContexticc, int orgID,String queryString, int sortOrder, boolean needCheckDiscoveryPriv)In sort order is VOUserBasic.SORT_DEFAULT, sort the users by setting Preference > Default User Name.

Verification:

  1. Log in to Java Client as admin.

  2. Go to System Settings >Preference >Default User Name: Lastname fistname

  3. Create a Change Order and submit it.

  4. Add an Approver

  5. Select User Groups.

  6. Open a User Group with many users in it.

    Result: Check the users sorted by lastname firstname. Afftected cases: check firstname lastname and lastname,firstname

16836909

Changes

Issue: AUDIT STATUS REQUIRED FIELD HYPERLINK SENDS USER TO WRONG PLACE

Root Cause: A BOM's attribute of an Item can only be modified on the redline tab if it is in the Affected Items tab of an ECO or SCO.

Resolution: Link to the redline tab for such an attribute.

Verification:

  1. Log into Agile.

  2. Go to a Change Order that has a required field that is on the Item, for example, BOM.QTY.

  3. Change the status and see that the warning pop up that says that Item.BOM.QTY is a required field.

  4. Click on the hyperlink in the warning "Item.BOM.QTY is a required field."

    Result: This link should take the user to the Item.BOM.QTY redline tab of the change.

16865217

Changes

Issue: UNABLE TO ADD AFFECTED ITEMS ON CHANGE ORDER

Root Cause: Some Items have bad data for field "encode_name" (redundant space char at tail) in the database.

Resolution: Provided SQL script to remove bad data.

Verification:

  1. Generated bad data for a Part.

  2. On the server, try to create an ECO and add the Part with bad data to the Affected Items table.

    Result: It shows error as customer encountered

  3. Run the provided scripts. Update item set encode_name = trim(encode_name) where length(item_number)<>length(encode_name); commit;

  4. Restart the server.

  5. Repeat Step 2.

    Result: The part is added into the ECO's AI table.

16918830

Web Client

Issue: CHANGE NUMBER NOT DISPLAYED, MESSAGE

Root Cause: Have not set object's subclass when checking privilege for pending changes, which will lead to that issue.

Resolution: Set object's subclass.

Verification:

  1. In Admin, create a Role, Role02, with the following privileges:

    • Discover Items

    • Discover ECOSubclass with criteria: only ECO (subclass of Change Orders)

    • Enforce Field Level Read

    • Modify Eng Changes

    • Read ECO Subclass with criteria: only ECO (subclass of Change Orders) and with applied to all fields

    • Read Items

  2. Create a User, User02, and add Role02 to the user

  3. Log in to Web Client as admin.

  4. Create a Part, Part02, and create an ECO, ECO01, against this Part, and create ECO02.

  5. Log in to Web Client as User02.

  6. Run Quick Search to search for Part02.

  7. Run Quick Search to search for ECO02 and go to its Affected Items table.

  8. Drag Part02 from the left pane and drop it into ECO02's AI table

    Result: The warning message shows the pending change number: Part Part02 is already on pending changes: ECO02.

16940890

Folders, Files, & Attachments

Issue: FILE FOLDER REFERENCE ON WHERE USED TAB RESULTS IN ERROR

Root Cause: Sourcing Project Line items are being treated as Agile objects.

Resolution: Associate the Sourcing Project line items with the parent Sourcing Project so that the first class object can be resolved.

Verification:

  1. Create a Sourcing Project.

  2. Add an Item.

  3. Open the Item. In the popup window, select Attachment tab, add an attachment to the File Folder.

  4. Run a search for the File Folder. Sort by the Name or Date and open.

  5. Go to the Where Used tab.

  6. Click on the link Project number-Item number link.

    Result: No error is displayed. The Sourcing Project opens where the Item is present.

16975236

Changes

Issue: REMOVE CHANGE CONTROLLED FROM ONE SUBCLASS REMOVES VALUE OF ALL SUBCLASSES

Root Cause: In Java Client, when the user changes the Change Controlled field's value of a subclass's/class' attribute that is in P3/P2 to No,, the system removes the redline information for all of the subclass's/class's attributes that had the same base id.

Resolution: Added a subclass/class constraint condition in the Remove program, when performing the above change action. Only remove the redline info of the self-subclass's/class's attribute.

Verification:

  1. Log in to Java Client as admin.

  2. Create two subclasses: subPart001, subPart002

  3. Set Page Three Visible for subPart001 and subPart002.

  4. Set Page Three.List01 Visible and associate to Users list for subPart001 and subPart002.

  5. Set Page Three.List01.Change Controlled to Yes for subPart001 and subPart002.

  6. Log in to Web Client as admin.

  7. Create two Parts, P001 based on subPart001 and P002 based on subPart002.

  8. Create a Change Order, CO001 and add P001 to the Affected Items (AI) tab; create another Change Order, CO002 and add P002 to AI tab.

  9. Open CO001 and redline P001, select a user, like admin, to Page Three.List01.

  10. Open CO002 and redline P002, select a user, like yvonnec, to Page Three.List01.

  11. Go to Java Client and set subPart002.Page Three.List01.Change Controlled to No.

  12. Go to Web Client and open CO001, go to the AI tab and check P001's redline information.

  13. Open CO002, go to the AI tab and check P002's redline information.

    Result: Redline on CO001 for P001.Page Three.List01 remains, as nothing changed for the subclass subPart001. On CO002 for P002.Page Three.List01 is no longer change-controlled, so it does not appear in the Redline Title Block tab.

17006241

Administration/Configuration

Issue: ACS DEFAULT PROVIDER URL LIMITED TO 100 CHARACTERS

Root Cause: The URL provider is limited to 100 characters.

Resolution: Extends the attribute length to 500 characters.

Verification:

  1. Log in to Java Client.

  2. Set up a JMS destination for ACS.

  3. Fill the Default Provider URL with 500 characters.

    Result: The user is able to fill 500 characters for Default Provider URL in the ACS JMS destination.

17021138

Item & BOM

Issue: P2 ATTRIBUTES GET ALLIGNED TO THE RIGHT SIDE WHEN INPUTTING MORE CHARACTERS IN FIREFOX

Root Cause: The long characters stretched the container more than usual and lead to this problem.

Resolution: Break the long chars to the next line.

Verification:

  1. Ensure that Preference.MultiColumn Display is set to One Column.

  2. Enable Parts.Page2.MultiText10 and set its MaxLength to 250.

  3. Log in to Web Client.

  4. Create Part01, edit MultiText10 with about 200 characters (without space) and click Save.

    Result: Characters are displayed in multiple lines, and the Page2 attributes are aligned to the left side.

17076026

Notifications & Subscriptions

Issue: ACTIVITY NOTIFICATIONS GO OUT WHEN NOTIFICATIONS ARE TURNED OFF FROM DEV INSTANCE

Root Cause: The code does not check if the notification is disabled before the PPM notification is sent.

Resolution: Do not send an email if notification is turned off.

Verification:

  1. Log in to Java Client.

  2. Go to Admin > Server Settings > Task Configuration.

  3. Open the Activity Reminder Task.

  4. Set Field Disabled to Yes and Save.

    Result: When the Notifications Enabled option is set to No, then all other settings should be overridden and no email or inbox notification should be sent. When the Notification option in switched off, no notification should be sent out no matter if it is from the Notification framework or Event framework.

17085496

Web Client

Issue: NOT ABLE TO EDIT THE NAME OF A BOOKMARK CREATED FOR A STANDARD REPORT

Root Cause: The code treats the standard report's bookmark as standard report object when it checks to see if the name if is editable.

Resolution: Correct the check function.

Verification:

  1. Log in to Web Client as admin.

  2. Go to any report and bookmark it.

  3. Edit the name of the bookmark.

    Result: The user is able to edit the name.

17087924

Import

Issue: PROBLEM WHILE IMPORTING DATA IN AGILE

Root Cause: There is a lack of Part Type validation while creating objects.

Resolution: Add Part Type validation.

Verification:

  1. Log in to Java Client as admin.

  2. Open Parts.Title Block.Number under Classes, set the MaxLength equal to 5.

  3. Open Documents.Title Block.Number under Classes, set the MaxLength equal to 30.

  4. Log in to Web Client.

  5. Import a file with a Level template similar to below:

    Level Item Number Type Description Quantity

    0 P0001 Part Test 0

    1 Doc-A001 Document Test 1

    1 A0001 Part Test 0

    2 Doc-A002 Document Test 1

  6. Map all of the above columns and import.

    Result: The user is able to import the Parts and Documents at the same time.

17161067

Changes

Issue: COPY PASTE OF ITEMS ONTO AFFECTED ITEMS TAB OF CHANGE DOES NOT WORK

Root Cause: When the user added Affected Items, if they pasted the value to the popup field in the new grid row, the pasted value replaces the old value in the field.

Resolution: Instead of replacement, append the pasted value to the old value.

Verification:

  1. Log in to Agile Web Client.

  2. Create a Change Order.

  3. Click on the Affected Items tab.

  4. Click on Add.

  5. In the search box, type or copy an Item number that needs to be added. The first item in the search box is appended with a semicolon.

  6. In the same search box, trying pasting another Item.

    Result: The Item number is added after the 1st item.

17168275

Java Client

Issue: DEFAULT VALUE FOR GROUP SIGNOFF EXPANSION SHOULD BE ANY

Root Cause: A new property was introduced in 932 code that causes this issue.

Resolution: Set the Group Signoff Expansion to Any for all workflow CCB and Released criteria.

Verification:

  1. Create a 932 schema and link to a 932 application server.

  2. Log in to Java Client as admin. See the criteria of each status in the workflow.

    Result: The Group Signoff value is set to ”All” or ”N/A”.

  3. Use AUT176 to upgrade 932 to 934.

  4. Link the upgraded schema to a 934 app server.

  5. Log in to Java Client as admin. See the criteria of each status in the workflow.

    Result: Group signoff value set to ”Any” or ”N/A”.

  6. Create a new workflow and add review status. Add criteria.

    Result: Group signoff value is set to ”Any”.

17171551

SDK

Issue: SDK QUERYCRITERIA SHOWS WRONG CRITERIA RESULT

Root Cause: Criteria with Relational operators (Contains ALL, Contains None, Contains Any, In and Not In) was unable to be interpreted from SDK as related constants were missing in cases.

Resolution: Updated SDK code to get the criteria with Contains All, Contains Any, Contains None, In and Not In operators.

Verification:

  1. Go to Java Client and create a new criteria for object Change with multiple conditions:

    [Cover Page.Workflow] in 'Default Change Orders' and (

    [Cover Page.Workflow] is not null or

    [Cover Page.Product Line(s)] contains all words 'Capricorn' ) and

    [Cover Page.Product Line(s)] contains any 'Leo' and

    [Cover Page.Product Line(s)] contains none of 'Scorpio' and

    [Page Two.Money01] greater than '10.0' and

    [Page Two.Money01] less than '111.12' and

    [Cover Page.Number] contains '00' and

    [Cover Page.Number] does not contain 'jj' and

    [Cover Page.Number] does not starts with 'n' and

    [Cover Page.Number] starts with 'C0'

  2. Get the criteria condition of testCriteria1 via SDK.

    Result: The criteria condition output via SDK is correct.

17192252

Standard Reports

Issue: AGILE PRODUCT WHERE USED REPORT IS NOT POPULATING VALUE OF BOM NOTES FIELD

Root Cause: BOM Notes field is not displayed in the Where Used Report.

Resolution: Correct this issue in processing the function of this report.

Verification:

  1. Log in to Web Client as admin.

  2. Create a Part, P001, and add Part P002 as its BOM.

  3. Add BOM Notes on P002.

  4. Execute the Where Used Report on P002 with the default layout that includes BOM Notes.

  5. Check the result.

    Result: The BOM Notes in the report result are the same as in the UI.

17219877

Workflow

Issue: SIGNOFF DURATION IS NULL IN WORKFLOW ROUTINGS TAB FOR SOME ECO REQUEST

Root Cause: In 9.3.1 we had enhanced PPM to support time in Schedule dates. The duration computation was enhanced to consider the working time and working hours defined in agile.properties, however, there is no such design for duration computation. Additionally, there is a defect in the code.

Resolution: Use the exact time difference (include weekends) and a 24-hour period for a day.1. Include Sunday and Saturday. 2. Round the integer down when the value is not an integer. For example, when the value is 0.9, take the value as 0; when the value is 1.1, take the value as 1.

Verification:

  1. Set admin time zone as (GMT-08:00) Pacific Time (US/Canada).

  2. Create a Change Order, C00030, and change status to CCB.

  3. Add admin as approver for CCB status and create the server date with the current Date/Time.

  4. Wait for three days more and include the weekend and < 4 days

  5. Open C00030 and check Signoff Duration which displays 3 days.

  6. Click the Approve button of CCB status and check Signoff Duration.

  7. Check approve the time which is 2013-11-05 06:42:27.

    Result: The signoff duration value is 3 days as user setting rules(3<duration time <4) and also follows the new rule based on an exact cycle with 24 hours as a day.

17242898

Administration/Configuration

Issue: TPO TECH NO PRIVILEGE TO NOTIFY USER WHEN EXITING PENDING STATUS ON A QE

Root Cause: The code check discover privilege for signoff user with user class in this case, but actually it can be user/user group.

Resolution: Check discover privilege with actual class.

Verification:

  1. In Admin, create a User User01 with the following privileges:.

    • Discover changes

    • ChangeStatus for All Workflow

    • Read changes

    • Discover user groups

  2. Create a User Group Usergroup01, and add a privileged user into it, say, Yvonnec.

  3. Open Default Change Orders and set Submitted.Notify Upon Entry with Usergroup01, set CCB.Approver with Usergroup01.

  4. Log in to Web Client as admin user.

  5. Create an ECO ECO01, set workflow Default Change Orders, and set Change Analyst.

  6. Log in to Web Client as User01.

  7. Open ECO01, click Next Status.

  8. Check on the Change Status popup whether the User Group appears or not:

    Result: The User Group, Usergroup01, appears in the Notify box. Click Finish on the dialog. It goes to Submitted status

  9. Click Next Status. Check whether the User Group appears as Approver.

    Result: The User Group, Usergroup01, appears in the Approver box. Click Finish on the dialog, it goes to CCB status.

17275507

Import

Issue: IMPORTING USERS TO USERGROUPS DOES NOT WORK

Root Cause: Previously, the server did not support the addition of users one by one, so that we can know the details of any errors. Additionally, if one user failed, all other users failed, as well.

Resolution: Added a method that supports the addition of users one by one.

Verification:

  1. Log in to Web Client.

  2. Import a source file with User Groups and Users, on of which is inactive.

  3. Check if the Users have been imported to the User Groups.

    Result: All active users are imported to user groups.

17301752

Item & BOM

Issue: REDLINES ARE INDICATED IN THE AFFECTED ITEMS FOR DATA THAT IS IDENTICAL AND NOT

Root Cause: When saving a redlined Title Block table, if the old value of multiText attributes containedspecial chars "\r\n", the system would convert "\r\n" to "\n" automatically. In this case, the new value from the UI could not match to the old value from severe even if these 2 values looked the same in the Web Client.

Resolution: Use a special handler in this case. Convert "\r\n" to "\n" for old values when matching the old value and the new value.

Verification:

  1. In Admin, set RedlineAttributes = Allow.

  2. Set Parts.Page2.Text11 and MultiText31 as Redline Controlled.

  3. Log in to Web Client using an Internet Explorer browser.

  4. Create Part01, edit Page2.MultiText31 with at least 2 rows.

  5. Create ECO01 against Part01.

  6. Log in to Web Client using Firefox browser.

  7. Open ECO01 and go to Part01's Redline Title Block tab.

  8. Redline edit Page2.Text11 with a new value, click Save.

    Result: Page2.MultiText31 keeps its value. Only Page2.Text11 is redlined.

17314705

Custom Reports

Issue: REPORT USING RELATIONSHIP SEARCH NOT RETURNING RESULTS

Root Cause: There are some defects in preparing the report header for relationship search.

Resolution: Fix them.

Verification:

  1. Log in to Web Client as admin.

  2. Create a Custom Report, CR001.

  3. Define its query as Suppliers > Suppliers > Relationships Search >Audit Category in product issue Status in Default Audits.Audited Lifecycle Phase in Active.

  4. Execute CR001 with the default layout and standard output format.

    Result: The user gets the correct results.

17362063

Java Client

Issue: AGILE PLM ATTACHMENT FILE INCORPORATION STATUS FLAG ERROR

Root Cause: In an Item's Where Used tab, the classid for parent-item's default Change is incorrect.

Resolution: Set the classid for the parent Item's default change.

Verification:

  1. Create Part01 and add Part02 as its BOM.

  2. Create ECO01 against Part01 and release it.

  3. Open Part01 and make it Incorporated on the latest Rev.

  4. Create MCO01 against Part01 and release it.

  5. Open Part01 directly, check whether it is Incorporated.

    Result: Part01 appears as Incorporated.

  6. Open Part01 from the Where Used Tab of Part02 and check if it is Incorporated.

    Result: Part01 appears as Incorporated.

17403070

Java Client

Issue: USERID IS ABLE TO BE VIEWED FROM QUICKVIEW AND SHOULD BE MASKED

Root Cause: In Quick View, the User Id is not masked.

Resolution: Masked the User Id.

Verification:

  1. Log in to Java Client as admin.

  2. Go to Admin > System settings > Preference, set No for Display User ID, and choose User ID for Signoff user Dual Identification Type.

  3. Create a new User, u001, with Discover Users and Read Users privileges.

  4. Log in to Web Client as u001. Search for a User. Its user ID in the GI tab is displayed as xxxxxx.

  5. Go to the Recently visited panel, click Quick View above the user, check user ID in the Quick View window.

    Result: It displays User.xxxxxx in the top left of the Quick View window, and displays xxxxxx for the user id attribute.

17432661

Java Client

Issue: FIX CODE FOR ROOT CAUSE OF AVERIFY AGIL-00025103 E PROPERTYTABLE 0 DUPLICATE PRO

Root Cause: There are duplicate Add property 925 for new the notification template.

Resolution: Remove the null value row in the property table when creating a new notification template.

Verification:

  1. Connect a 934 app server to a 934 demo db and start.

  2. Create a Notification in Java Client.

  3. Run Averify to check the schema.

    Results: 1. No AGIL-00025103 in the Averify report. 2. Run the following sql scripts: select * from propertytable a where a.PROPERTYID=925 and a.parentid in (select parentid from propertytable where PROPERTYID=925 group by parentid having count(*)>1) and a.parentid in (select id from nodetable where objtype=213) and value is null; The script returns no records.

17446142

Web Client

Issue: REPORT SAVE JS ERROR

Root Cause: There is a JS error that blocks the next server operation which sets the source to an inexistent image in Report Control Pane.

Resolution: Solve the related JS error.

Verification:

  1. Stop the File Manager server.

  2. Log in to Web Client as admin.

  3. Go to Standard Report >Product Report >BOM Explosion Report.

  4. Execute the BOM Explosion Report. The application generates a report result.

  5. Click Save.

    Result: The following error message pops up: "The preferred file server : http://bej301255.cn.oracle.com:8080/Filemgr/services/FileServer for current user is down. Please contact the system administrator."

17634682

Changes

Issue: 9.3.1.1 HF 239 SURPRISING BEHAVIOR: DETAILS COLUMN IN HISTORY TAB NOW WRAPS

Root Cause: Some Details in the History tab wrap.

Resolution: Correct the text displaying in Text Rendering.

Verification:

  1. Log in to Java Client, enable Page Two, enable a MultiText31, and set its Include Characters to 'All'.

  2. Add the related Read/Modify privilege to MultiText01.

  3. Log in to Web Client, create a Change, C1, and route its status to Submitted.

  4. Edit C1, press 'ab' to MultiText01, move the cursor to the middle of the 'ab', press enter, then make sure 'ab' to be

    'a

    b'.

  5. Go to the History tab.

    Result: The Details column shows: <Page Two.MultiText31>WAS<>IS<a b>.

17712876

Standard Reports

Issue: UNABLE TO LAUNCH - AGILE USER USAGE REPORT WHEN YOU SELECT ONLY A USER GROUP

Root Cause: There is a NumberFormatException that occurs when parsing User information from User Group.

Resolution: Fix the exception.

Verification:

  1. Log in to Web Client as admin.

  2. Go to Standard Report >Administrator Report > User Usage Report.

  3. Execute the User Usage Report with any user group, Finish.

    Result: The user gets the correct report results.

17824833

Item & BOM

Issue: CREATE DATE DOES NOT GET AUTO-POPULATED WHEN A NEW PART IS CREATED

Root Cause: When the user creates an object and saves page two info, if a field was visible in the subclass level, but not visible in the class level, the system does not save it.

Resolution: In this case, save this field.

Verification:

  1. In Admin, open Parts.Page Two.Date01, and set DefaultValue = $Today, set Visible = No.

  2. Open Part.Page2.Date01, set Visible = Yes.

  3. Log in to Web Client.

  4. Create a new Part.

  5. Check the default value for Page Two.Date01.

    Result: The Date is generated automatically.

17825836

Searches

Issue: SEARCH DISCUSSIONS WHERE RELATED TO FIELD IS NULL.DISCUSSIONS ARE RETURNED WITH THE RELATED TO FIELD NOT NULL

Root Cause: If there is a value in a Discussion's Related To attribute, the data should exist in view 'DISCUSSION_RELATED_TO', but it loses the RFQ object.

Resolution: Unite all the data in RFQ object.

Verification:

  1. Create a Discussion for an RFQ. The Related To attribute shows the RFQ.

  2. Create a few more Discussions with Null value for the Related To attribute.

  3. Run an Advanced Search on Discussions where the Related To field is null. Validate the result.

  4. Run an Advanced Search on Discussions where the Related To field is not null. Validate the result.

    Result: The Discussion related to the RFQ appears in the Advanced Search result where the Related To field is not null. Advanced search shows the proper result.

17832084

Item & BOM

Issue: WEB CLIENT SHOWS INCORRECT ITEM DESCRIPTIONI IN REDLINE BOM TAB

Root Cause: The HTML special char "<" was not replaced correctly when rendered Item description is filled in the BOM redline table.

Resolution: Replace "<" by correct way.

Verification:

  1. Log in to Web Client, create Parts P1 and P2, edit P2 and set P2's Description to "<M40", then add P2 into P1's BOM.

  2. Create an ECO and add P1 as an Affected Item, and check the value of P2's Description under BOM redline tab.

    Result: "<M40" appears as the Description.

  3. Do a Remove Redline action on P2, and check the value of P2's Description under the BOM redline tab.

    Result: "<M40" remains as the description.

17852854

SDK

Issue: CELL [ATTACHMENTS.REVISION STATUS] IS READ ONLY

Root Cause: UserContextManager.getUserContext(IAgilePrincipal agPrincipal), tries to use case the sensitive user name to retrieve Process Extension context, but this context was stored with case insensitive user name. This returns the wrong context.

Resolution: Convert the user name into lower case.

Verification:

  1. Set up the LDAP server with the Agile system and create two LDAP users: TESTDEMO1(all upper case) & TESTdemo2 (both upper case & lower case).

  2. Compile the Process Extension code and put pxroletest.jar under %AGILE_HOME%\integration\sdk\extensions.

  3. Create a new role: pxrole and give it the Discover, Read, Modify, Create Item & Change privileges.

  4. Log in to Web Client and create a new Part named PX_PART001.

  5. Create a new PX named pxtest, make it initiate from the Tools menu.

  6. Assign Role: pxrole to PX:pxtest.

  7. Log in to Web Client as LDAP user, TESTDEMO1, click pxtest under the Tools menu.

  8. Log in to Web Client as LDAP user, TESTdemo2, click pxtest under the Tools menu.

    Result: Add validation to check visibleCells."

17866173

Item & BOM

Issue: MISSING ATACHMENTS

Root Cause: When displaying an Item object by clicking a link to it from another Item's where Used tab, the default rev class is the change base class and is not translated to the specific class, so the related system business is mismatched.

Resolution: Translate the default rev class from base class to the specific class.

Verification:

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

  2. Create MCO01 against Part01 and release it.

  3. Create MCO02 against Part01 and release it.

  4. Create MCO03 against Part01.

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

    Result: The file attachments remain in the Part of the pending MCO Rev.

17941797

Administration/Configuration

Issue:AGILE PPM RESOURCE POOL OWNER CANNOT ACCEPT OR DECLINE A PHASE

Root Cause: Use the parent's Activity ID to create all children's notifications.

Resolution: Use the children's Activity ID to create the children's notifications.

Verification:

  1. Log in to Web Client as User A and create a User Group, UG. Make it a resource pool. Add users, admin and User A, in it.

  2. Log in to Web Client as admin. Create a Program and add a phase and task in the Schedule tab.

  3. In the Team tab of phase and task, add admin and User A of user group UG as resources and give % allocation.

  4. Change the status of the phase and task to In Process.

  5. Log out and log in as User A. Go to Home> My assignments.

  6. Rows should be there for phase and task which will be pending for acceptance.

  7. Select the row for phase and task and click on Accept.

    Result: User A is able to accept/decline the phase and task without getting any error.

17950771

SDK

Issue: AGILE 9.3.2 ITABLE FETCHES ONLY 5000 RECORDS

Root Cause: This issue was caused by 9310.69 which limits the number of results. The maximum number of results that was set in Java Client is 5000. That HF also limits the number of results in SDK.

Resolution: Check if it is called by SDK. If yes, return all results. The number of results are not limited if the user gets the Part table through SDK.

Verification:

  1. Log in to Java Client > Admin > Preferences > set Maximum Query Results Displayed as 5000.

  2. Create a commodity, Create 200,000 Parts (more than 5000) and add all of the Parts as the commodity's BOM.

  3. Get the total number of Parts in the commodity's BOM.

    Results: The user gets the total number of Parts, which is not 5000.

  4. Sort Parts in a certain order.

  5. Get the total number and names of the Parts in commodity's BOM.

    Result: The user gets the total number of Parts, which is not 5000. The Parts are returned in sorted order.

18036662

Standard Reports

Issue: MODIFY BOM EXPLOSION REPORT

Root Cause: The P2/P3 attributes can not be shown when the BI static template is used in the BOM Explosion Report.

Resolution: Correct the wrong key string in the report buffer stream.

Verification:

  1. Create a new RTF template for BOM Explosion Report.

  2. Create an XML file to load into Microsoft Word (use BI Publisher Template Builder).

  3. Load the XML File into Microsoft Word.

  4. Try to add a field in the header section.

  5. Add other fields from Page Two, Title Block, and so on.

  6. Finalize and run the report.

    Result: No errors are reported during the process. The report is produced correctly.

18043536

Standard Reports

Issue: BOM COMPARISON TOOL REPORT FAILS WITH '0' BYTE FILE

Root Cause: Reports cannot handle the special character '"" and always throws an exception.

Resolution: Add a special handler for character '""'.

Verification:

  1. Log in to Web Client.

  2. Create a Manufacturer Part, MFP123, with the Description 'LBL BLNK THERM 3"X1" W/PERF'.

  3. Add this Manufacturer Part to a Part P0001.

  4. Run the BOM Comparison Report.

  5. In Step 2, check the BOM and AML as compare structure.

  6. In Step 3, add P0001 for the report, click Finish

    Result: It generates the correct report results.

18049995

Changes

Issue: WARNING ERRORS IN CHANGE ORDERS ARE CREATING A HARD STOP

Root Cause: The warning id used in "...conflicting redline in AML...will become non-displayable..." is incorrect.

Resolution: Update with correct warning id.

Verification:

  1. Log in to Web Client, and create Part01 with AML

  2. Create ECO01 against Part01, redline edit AML.

  3. Create MCO01 against Part01, redline edit AML.

  4. Release ECO01.

  5. Open MCO01, go to Redline AML tab, check warning message.

    Result: The following message appears: "Change Order C00227 with conflicting redlines in AML has been released. Redlines conflicting with a released change will no longer be visible." Click Continue, and the user sees that the AML is rebased to latest revision.

18109688

Export

Issue: EXPORT AN ECO "AN ERROR OCCURRED DURING EXPORT"

Root Cause: Change the subclass type of Item, there are dirty data in DB.

Resolution: Skip to process attribute can not be found in the database for MSRedlineAttribute table.

Verification:

  1. Log in to Web Client.

  2. Open the Change ECO 016095.

  3. Click Actions > Export, select the default change filter and CSV/XLS/AXML/PDX format, check the result.

    Result: The Change ECO 016095 is exported successfully with the correct result.

18127165

Searches

Issue: GROUPING () IN QUALITY CHANGE REQUEST SEARCH IS NOT WORKING AS EXPECTED

Root Cause: If the user searches by workflow.Action related attributes, the application checks the existence of Approver/Observer, and parentheses do not work correctly in this process.

Resolution: Set Workflow.action attributes and check the existence SQL in one grouping.

Verification:

  1. Log in to Web Client as admin.

  2. Create a QCR as below. Set the Quality Administrator as yourself.

    Audit00001 -> In Review status, and approved by yourself.

    Audit00002 -> In Review status, and acknowledged by yourself.

    Audit00003 -> In Submit status.

    CAPA00008-> In Review status, and approved by yourself.

    CAPA00011 -> In Review status, and awaiting for approval.

  3. Run an Advanced Search with the following condition:

    CAPA & Audit Object Search

    [( Workflow Status Equal To $CURRENTSTATUS And

    Status In $STATUSTYPE.REVIEW And

    Approver Action Equal To Approved ] Or

    [ Workflow Status Equal To $CURRENTSTATUS And

    Status In $STATUSTYPE.REVIEW And

    Approver Action EqualTo Acknowledged ]) And

    Quality Administrator In $USER

  4. Run the search.

    Results: The search results appear correctly as followsAudit00001 -> In Review status, and approved by yourself.Audit00002 -> In Review status, and acknowledged by yourself.CAPA00008-> In Review status, and approved by yourself.

18152537

Import

Issue: CAN NOT GET ITEM GROUP ATTRIBUTE OF PART TITLE BLOCK TO MAP DURING IMPORT

Root Cause: The application does not add the Part Group into itemimportinfo before the import.

Resolution: Add the Part Group into itemimportinfo.java.

Verification:

  1. Log in to Web Client.

  2. Import the source file with Item Group to Item in Excel, CSV, aXML or PDX format.

  3. Check if Item Group(s) attribute is available in the mapping.

    Result: Item Group(s) attribute is available in the mapping.

18191009

Standard Reports

Issue: JAVA HEAP ISSUE FOR CHANGE PACKAGE REPORT ON ONE PARTICULAR ECO

Root Cause: There is a code defect. A dead loop is caused when the the Description of the Change covers the full page.

Resolution: Fixed issue.

Verification:

  1. Log in to Web Client.

  2. Go to Reports and Analytics > Standard Reports > Process Report > Change Package Report.

  3. Execute the report.

  4. Select an ECO with a Description of more than 3k characters and Finish.

    Result: The user is able to execute the report and see the results without any issue.

18205450

Import

Issue: COMMODITY CODE IS NOT AVAILABLE FOR IMPORT

Root Cause: Commodity is disabled when the customer does not have a PCM licence. Web UI users can modify & read commodity objects, however, even if the user does not have a PCM licence. It is inconsistent.

Resolution: Removed the limitations so that a user can import a commodity even if they do not have a PCM licence.

Verification:

  1. Log in to Java Client as admin.

  2. Enable the Commodity attribute on the Items Title Block.

  3. Disable the PCM license.

  4. Restart the server.

  5. Log in to Web Client.

  6. Click Tools and Settings >Import to import Items with commodity.

  7. Define the mapping in the wizard.

    Result: The commodity is listed under Items Title Block when defining the mapping and it is imported to Items.

18245047

Changes

Issue: UNABLE TO RELEASE CHANGES IN WEB CLIENT FOR VERY LARGE BOMS

Root Cause: 1. During an audit release, Web Client invokes doAuditStatus 3 times. Each doAuditStatus invokes a BOM check 3 times recursively. 2. When releasing a large BOM with recursive data, there is an additional complete scan in the BOM recursive check, which takes a lot of time.

Resolution: 1. Invoke doAuditStatus one time (along with 1a time recursive BOM check) 2. If there is recursive data and the BOM tree size exceeds a defined number (default 24million), stop the transaction and throw an error message to let the customer know that we cannot support this recursive BOM check in "sync mode."We have to inform the administrator to identify (execute a script) and remove the recursion, and then release the change.

Verification:

  1. Create a Change Order.

  2. Assign a workflow.

  3. Add Items (that have large structures) to the Affected Item tab.

  4. Click on the next status until the Change Order gets released.

    Result: The Change Order gets release as expected and in an appropriate amount of time.

18363532

Administration/Configuration

Issue: PROJECT NAME MAXLENGTH ISSUE WHEN THE USER CREATES PROJECT FROM TEMPLATE

Root Cause: The MaxLength parameter is missing when a project is created from a template.

Resolution: Add MaxLength parameter when creating a project from a template.

Verification:

  1. Set MaxLength to '30' for Activities.general Info. Name attribute.

  2. Create a new Project and it only allows user to input 30 characters for Activities.generalInfo. Name attribute in project creation wizard.

  3. Create a new Project from template

    Result: New Project or Project is created from template- It does not allow user to input more than 30 characters for Activities.general Info. Name attribute in project creation wizard.

18422146

Changes

Issue: AGILE 9312 CRITERIAL FAILED

Root Cause: The logic for checking Lifecycle Phase in criteria has a defect, which can lead to such error if there are multiple Affected Item rows.

Resolution: Correct the logic.

Verification:

  1. In Admin, create a criteria TC as follows: Change Orders Affected Items.Item Number Starts With P And Affected Items.Lifecycle Phase Is Not Null Or Affected Items.Item Number Starts With A.

  2. Set the Default Change Orders workflow, set TC as the only criteria for CCB status.

  3. Create Change Order C01, Add P01 and A01 to C02, fill Lifecycle Phase for P01, change C03 to CCB status.

    Result: The user is able to successfully change status to CCB status.

18459849

Folders, Files, & Attachments

Issue: USERS CANNOT SEE ATTACHED FILES UNLESS THEY REFRESH THE PAGE

Root Cause: When loading the Relationships table of an Item object, the data model of the Relationships table is stored in the action context, so at this time, if the user clicked the Item object from the left tree panel, the system would use the old data model of the Relationships table which was already existing in the action context.

Resolution: Added a special handler for item objects, so that if the user clicks the Item object from left tree panel, the data model of the Item object is refreshed first.

Verification:

  1. Create P/N Part01, attach file(s) as attachment and release it to create rev A.

  2. Assign Part01 to a new ECO: current rev is (B). Do not release this ECO.

  3. Go to the Attachment tab of rev (B). You can see the attachment file.

  4. Click on Part01 from the Recently Visited section. You get the Attachment tab of rev A.

    Result: The Attachment tab of rev A has a dot and all the files are displayed.

18641543

Standard Reports

Issue: OUT OF RANGE AND DUPLICATE DATA REPORTED IN RESULTANT EXCEL LIST FROM AN ITEM ACTIVITY REPORT

Root Cause: There is some duplicate and out of date range records in Item Activity Report.

Resolution: Added the code for no revision changes, such as ECR.

Verification:

  1. Create a Part.

  2. Create an ECO against this Part.

  3. Create an ECR against this Part.

  4. Run the Item Activity Report.

    Results: 1. If the ECR is in the date range, ECO1 before the date range, the result gets records from before the date range.

    2. If the ECR is in the date range, ECO2 after the date range, the result gets records from after the date range.

18815232

SDK

Issue: READ VALUE USERCONSTANTS.ATT_GENERAL_INFO_DISPLAY_NAME RET INCONSISTENT RESULT

Root Cause: When visibleCells was checked, there were some errors in the logic.

Resolution: Add validation to check visibleCells.

Verification:

  1. Create two users in Java Client, named testa and testb.

  2. Run SDK code to return the value of the attribute User.General Info.Display Name.

  3. Check the user display name.

    >>>

    IUser agileUser = (IUser)m_session.getCurrentUser();int attribute = UserConstants.ATT_GENERAL_INFO_DISPLAY_NAME;IDataObject obj = (IDataObject) agileUser;ICell cell = (ICell) obj.getCell(new Integer(attribute));Object value = null;value = cell.getValue();System.out.println("value.toString display= "+value.toString());

    Result: The display name is the same as the login User.

18859056

Workflow

Issue: WEB CLIENT DOES NOT AUTOMATICALLY ADD $APPROVER VARIABLE ON THE WORKFLOW

Root Cause: The logic for parsing default reviewer setting in workflow has a defect which leads to such issue.

Resolution: Update the logic.

Verification:

  1. In Admin, go to Workflows, save as Default Change Orders to DefaultECO2, add CCB2 after the first CCB status and add a criteria for it, make sure CCB2.Auto-promote = No, Ad-hoc Reviewers = Yes.

  2. Set Notify Upon Entry on Released status = $APPROVER, enable the workflow DefaultECO2.

  3. Create ChangeStatus privilege to allow the user to change status on the newly created workflow, and assign the privilege to the Administrator role.

  4. Log in to Web Client, create ECO01.

  5. Move to CCB and add approver #1.

  6. Move to CCB2 and add approver #2.

  7. Move to the Released status, and on the Change Status dialog, check the users in the Notify box.

    Result: The approvers in CCB and CCB2 are added into the Released.Notify box.

18960383

Web Client

Issue: HOW TO DISABLE EFFECTIVE FROM AND TO FIELDS ON DOCUMENTS

Root Cause: The customer wants flexibility in enabling/disabling effective information in the object header.

Resolution: Switch on/off the display of effective information based on the Title Block Effective Date Visibility setting.

Verification:

  1. Log in to Java Client as admin.

  2. Go to Classes > Parts >Title Block.

  3. Set the Effectivity Date to No.

  4. Save.

  5. Log in to Web Client as admin.

  6. Create a Part.

    Result: Check the Title Block header of Part. The Effectivity Date has disappeared.

18997914

Notifications & Subscriptions

Issue: AGILE SENT AN 'ALL APPROVED' E-MAIL TO ANALYST WHILE THE STATUS WAS IN SUBMIT

Root Cause: N/A

Resolution: N/A

Verification:

  1. Log in to Java Client.

  2. Create User, U001, with related privileges.

  3. Add U001 to $CHANGEANALYST list.

  4. Add $CHANGEANAYST to Approvers of Workflow Default Change Orders.CCB.

  5. Enable Notifications.

  6. Log in to Web Client as admin.

  7. Create an ECO, C0001.

  8. Promote C001 to CCB status.

  9. Move back the workflow of C001 to Submitted status.

  10. Click the Next Status button.

  11. Check the approval box with the names already populated.

  12. Remove any of the existing approvers from that listing.

  13. Check Admin's email and U001's email.

    Result: No All Approved email on C001 in Admin's email, and No All Approved email on C001 in U001's email.

19046899

Standard Reports

Issue: BOM COMPARISON REPORT IS EMPTY EVEN THOUGH THERE ARE DIFFERENCES

Root Cause: There is an encoding issue in the BOM Comparison Report.

Resolution: Fix the problem.

Verification:

  1. Log in to Web Client as admin/agile9.

  2. Select from Reports > Standard Reports > Product Reports.

  3. BOM Comparison > Execute

    Select Layout: Default Layout

    Output Format: PDF

    Compare Level: All Levels

    Compare Structure: BOM

  4. Add a BOM with a description that contains special characters.

  5. Finish.

    Result: It generates a report with correct values.

19298151

Searches

Issue: EXPORT WHERE USED SEARCH CONTAINS NO DATA

Root Cause: Functional code is skipped and we do not add the row value in rowlist.

Resolution: Add the row value in the correct way.

Verification:

  1. Log in to Java Client as admin.

  2. Go to Admin > Server Settings > Preferences > Maximum Database Records to Process for Searches, set 0 for this preference.

  3. Log in to Web Client as admin.

  4. Do an Advanced Search:Items > Parts > Where Used One Level All Released Revisions > Title Block.Number > Is not null, run the search.

  5. Export search result to CSV or XLS file, then open the file to check the search result.

    Result: All parts that meet the search criteria are displayed in the exported file.

19485903

Standard Reports

Issue: ERROR OCCUR WHEN SAVE A CUSTOM REPORT

Root Cause: Document building request parameters is not using UTF-8 format.

Resolution: Change to use UTF-8 as encoding type.

Verification:

  1. Install Agile on a Simplified-Chinese Windows box.

  2. Log in to Java Client, enable the Simplified-Chinese language, and restart Agile.

  3. Log in to Java Client and make sure the appropriate privileges are enabled.

  4. Set the admin preference to use Simplified-Chinese. Log off and log in again.

  5. Create a custom report, create new query with Changes > Change Orders > ECO, Cover Page.Date Originated equals something.

  6. Press Next or Finish.

    Result: No error occurs and the user can go to the next page or get the correct report.

19539518

Standard Reports

Issue: ITEM ATTRIBUTE HISTORY REPORT SHOWS SAME DATA FOR BOTH PARTS/DOCUMENT FIELDS

Root Cause: The report result does not filter layout attributes by inputting data subclass.

Resolution: Add the related logic.

Verification:

  1. Log in to Java Client, and make sure that Smart Rules > Redline Attributes is set to Allow.

  2. Enable List11 of Parts and Documents. Enable Change Control for them.

  3. Log in to Web Client. Create a Part. Create a change to change List11.

  4. Create a Document and create a Change to change list11.

  5. Go to Standard report > Products Reports > Item Attribute History Report.

  6. In the Layout tab, Add both Parts.Page TWO. List11 and Documents.Page Two.List 11 from Hidden Fields to Displayed Fields to default layout.

  7. Execute the report, search for the Part and add it.

  8. Click Finish to generate the report.

    Result: In the generated report, under Page Two, Attribute List11 has been listed only once. The same result is returned when the user runs the report against a document.

19547265

Searches

Issue: ERROR ORA-00904 WHEN DEALING WITH INCLUDE INACTIVE LIST VALUES VARIABLE IN USER

Root Cause: Some of the newly added attributes do not exist in the agileuser_p2 view.

Resolution: Fixed the script.

Verification:

  1. Log in to Web Client as admin.

  2. Do an Advanced Search: Users > Users > General Info.User ID > contains > Prompt, click Format button, move Preference. Include Inactive List Values in the output field and run the search.

  3. Input value "ad" in the Enter Search Values window, run the search.

    Result: All users' User IDs that contain "ad" are returned in the search results and their Preference.Include Inactive List Values is displayed correctly in the search results table.

3.2 Product Governance & Compliance

14344697

Custom Reports

Issue: PARENT-CHILD RELATIONSHIPS & BILL OF SUBSTANCES APPEAR INCORRECTLY IN CUSTOM REPORT

Root Cause: The Join condition that is defined between Material Declaration and Substance is incorrect.

Resolution: Correctly join Material Declaration and Substance. The relationship should be 'Material Declaration - Mfr Part - Substance'.

Verification:

  1. In Web Client, create a Substance Declaration

  2. Add at least two Manufacturer Parts.

  3. Associate a Specification to the Declaration.

  4. Add different BOS substances to each Manufacturer Part. For example:

    Mfr Part 1

    * Lead

    * Lead Compounds

    - LEAD TRI-OXIDE

    - Lead Oxide

    Mfr Part 2

    * Cadmium

    * Lead Compounds

    - Cadmium

    - LEAD TRI-OXIDE

    - Lead Oxide

    * Test Group

    - Test Child

  5. Run a Custom Report to include the above fields, that is Manufacturer Part Composition.Substance Name, with the following query: Query Definition: Object Search -- Substance Declarations {Cover Page.Name Contains MD00017}

    Result: The data under Mfr Part1 and Mfr Part2 is shown correctly.

16981712

Declaration

Issue: AGILE PG&C: SPECIFICATIONS WITH ZERO-PPM NOT SHOWING CORRECT COMPLIANCE STATUS

Root Cause: When the Threshold PPM is zero, the external rollup engine rolls it up as compliant. The current behavior does not make sense.

Resolution: Set the correct value, which should be non-compliant, when the Threshold PPM is zero.

Verification:

  1. Log in to Web Client as admin user

  2. Create an external specification and add substance: Lead, set Threshold PPM as Zero.

  3. Create a Part and set Mass is 1g and create a substance declaration against it.

  4. Add the external specification.

  5. Add Lead with Declared PPM is 200, Al with Mass 1g and release the declaration.

  6. Open the Part and go to Compliance tab and click the Calculate Compliance button.

  7. Check the calculated compliance of the specification.

    Result: The user gets the Non-Compliant value in Calculated Compliance of the specification.

17021457

Rollup

Issue: AGILE PG&C SPECIFICATION MAPPING WITH EXTERNAL ROLL UP

Root Cause: Does not support the external specification mapping in 9.3.2 & 9.3.3.

Resolution: Add this function.

Verification:

  1. Log in to Web Client as admin.

  2. Create an external specification: SP1_External and add substance with Threshold Mass PPM.

  3. Log in to Java Client as admin.

  4. Open Parts Class and go to Page Two, enable List01 and assign Calculated Compliance.

  5. Go to System Settings >Product Governance & Compliance > Specification Mapping.

  6. Open SP1_External and assign list01.

  7. Log in to Web Client as admin.

  8. Create a Part and create a declaration against it.

  9. Add the external specification and add BOS for the Part.

  10. Release the Declaration.

  11. Open the Part and go to Compliance tab, click Calculate Compliance button to get the calculated compliance value.

  12. Go to Title Block tab and check List01 value.

    Result: The user gets the same calculated compliance value from step 11.

17060364

Export

Issue: SUBSTANCE TYPE ELEMENT MISSING FROM AXML OUTPUT SINCE UPGRADING TO 9.3.1.2

Root Cause: Substance type is not a real read through attribute.

Resolution: Treat substance type as table attribute.

Verification:

  1. Log in to Web Client as admin.

  2. Create a Manufacturer Part.

  3. Create a Declaration against the Manufacture Part, add specification and add some substance.

  4. Release the Declaration.

  5. Open the Manufacturer Part and export with the Compliance tab in AXML format.

  6. Check the agile.xml file.

    Result: Substance Type appears in the file.

17584025

Substance/Spec/Part Group

Issue: PART FAMILY | PART NUMBER: NO PRIVILEGES

Root Cause: The Part number value is stored as "no privlege" if the user does not have the Discover All Items privilege. Even if another user has the Discover All Items privilege, the name is also no privilege.

Resolution: The Part number in Part family > Part table must be stored with the correct name, not as "no privlege".

Verification:

  1. Log in to Java Client as admin.

  2. Create a subclass for Parts named New Part.

  3. Create Discovery privilege for all New Part.

  4. Open the Role-Compliance Manager and do a Save As to New Compliance Manager. Remove the Discover All Items and Discover All New Part privileges.

  5. Create a User named New User and assign the New Compliance Manager role.

  6. Create a New Part named Part_New1.

  7. Log in to Web Client as New User and search Part_New1 >>User can read.

  8. Search for Part Family and add Part_New1.

    Result: Part_New1 appears correctly on the tab.

17976541

Administration/Configuration

Issue: AGILE PC -UNABLE TO INACTIVATE 1ST ADDED SUPPLIER CONTACT USERS (NO PCM LICENSE)

Root Cause: We check if the supplier user is used in Default RFQ recipient if there is no PCM License.

Resolution: Do not check if the supplier user is used in Default RFQ recipient if there is no PCM License.

Verification:

  1. Log in to Java Client as admin.

  2. Go to Admin > Server Settings > License, disable the PCM license, restart server.

  3. Log in to Web Client as admin.

  4. Create a Supplier user, sup1, add two supplier users: su1 and su2 to it.

  5. Contact user su1 was set as Default Declaration Recipient.

  6. Open su1, try to inactive it, prompt an error message.

  7. Set su2 as Default Declaration Recipient, then try to inactive su1.

    Result: The contact use that was added first, su1, can be inactivated successfully.

18252723

Web Client

Issue: ERROR "FOR INPUT STRING:" APPEARS WHEN ADDING SUPPLIER TO MANUFACTURER PART

Root Cause: The Supplier resolution does not work for numeric number and Suppliers whose Number field has been modified.

Resolution: Use the supplier id directly instead of resolving Supplier Number while adding to the Item's tab. Update the cached number-based map when a Supplier's Number is modified.

Verification:

  1. Install Agile Application with Setup DB.

  2. Create an active Supplier whose Supplier Number is 1002.

  3. Create an active Supplier whose Supplier Number is 1001.

  4. Create a Part, Document, Manufacturer Part, and Part Family.

  5. Try to add the Supplier 1002 to the Part.

    Result: The user can add Supplier 1002 to the Part successfully.

  6. Try to add Supplier 1001 to the Part.

    Result: The user can add Supplier 1001 to the Part successfully.

  7. Try to add Supplier 1001 and Supplier 1002 to Document/Manufacturer Part/Part Family object.

    Result: The user can add Supplier 1001 and Supplier 1002 to those objects successfully.

3.3 Product Cost Management

13061072

RFQ/Response

Issue: MODIFYING PRICE FOR AN ALTERNATE PART CLEARS OUT THE RESPONSE LINE DATA

Root Cause: Bid alternate part is deemed to NO bid, so that all response data is cleared out.

Resolution: Disable to show bid alternate part for buy edit.

Verification:

  1. Create Sourcing Project and assigned Items.

  2. Assign Supplier and request for an alternate bid.

  3. Create an RFQ and send it to the Supplier.

  4. Log in as a Supplier.

  5. Go to Responses > Propose Alternate Part.

  6. Fill out the data.

  7. Submit response line.

    Note: Supplier edits the price and saves the record for an alternate part and the responses are updated with the new data.

  8. Log in as buyer and edits the price for the alternate part bid (RFQ > Responses > Edit > Response Lines).

  9. Save.

    Result: Bid-Alternate option should not be available for the buyer user. Editing the response lines should save the values correctly.

15987733

RFQ/Response

Issue: BUYER SIDE EDIT RESPONSES ON RFQS DOES NOT WORK WHEN EDIT MODE IS ADVANCED TABLE

Root Cause: No appropriate message is shown if a user is in Table Edit mode, as it was not supported so far.

Resolution: If user is in Table Edit mode, display proper message.

Verification:

  1. Create an Item with AML, Assembly and add to Sourcing Project.

  2. Add the Items to the Sourcing Project and create an RFQ.

  3. Open the RFQ and get responses from the Supplier.

  4. Log in as buyer user.

  5. Navigate to the RFQ and lock the RFQ.

  6. Edit the table.

    Result: The following message is displayed on DMS: To Edit Response Lines, Select Edit > Response Lines.

17030895

Administration/Configuration

Issue: MAP DATA TO ONLY SELECT ATTRIBUTES FROM P3 AND NOT P2 & P3 AS DOCUMENTATION STATES

Root Cause: P3 did not follow the logic of P2.

Resolution: Added the logic of P2 attributes to P3 as follows:

  • When the list attributes of item.P3 has been assigned to the 'Item_Sites Quote_As' List, only then can it be mapped to the PCM attribute Quote As.

  • When the list attributes of item.P3 has been assigned the 'Yes/No Cost List' List, only then can it be mapped to PCM attribute Cost.

Verification:

  1. Enable Item.P2 list1 and P2 list 2 attributes and assign them to Item_Sites Quote_As List" and Yes/No Cost List.

  2. Enable item.P3 list1 and P3 list2 attributes and assign them to Item_Sites Quote_As List" and Yes/No Cost List.

  3. Navigate to the Sourcing Project's AML tab Item attributes, open Quote As and click on map data.

    Result: Displays item.p2 list1 and item.p3 list1 (assigned to to Item_Sites Quote_As List). Similarly for Sourcing Project's AML tab item attributes open Cost.

17425396

Administration/Configuration

Issue: INCORRECT LIST FOR AUTHORIZED SHIP TO DEFAULT

Root Cause: EditorListItemChooser.java 258th line:The code passes the wrong parameter to admininterface.getAdminList.Currently the code is:tmpList = ai.getAdminList(classID,adminList.getID());

Resolution: Changed to be: tmpList = ai.getAdminList(classID, attributeID);

Verification:

  1. Log in to Java Client as admin.

  2. Go to Admin > Data Settings > Classes > Users > Users Interface Tabs > General Info tab > Attributes:General Info tabs > Authorized Ship-To.

  3. Click drop-down arrow of Default Value.

  4. Check the values in Choose From:

    Result: The application displays the values from the List: Ship To Location List.

17562068

Searches

Issue: COLUMN AMBIGUOUSLY DEFINED ADDING MANUFACTURER PART NUMBER TO SEARCH RESULTS

Root Cause: SQL incorrectly generates the same two tables in from clause.

Resolution: The code was fixed to remove the duplicate table from the clause.

Verification:

  1. Log in to Web Client as admin.

  2. Do an Advanced Search: Changes > PCO, click Format button, move the Affected Prices.Manufacturer Part Number attribute to the Displayed Fields, run the search.

    Result: Displays the search results row correctly with values and the values for Manufacturer Part Number attribute.

17571863

Administration/Configuration

Issue: WORKFLOW EXIT REQUIRED FIELDS CHECK IS NOT WORKING AS EXPECTED

Root Cause: When the user does a change status action on a related change object, the system loads the Part's suppliers information with the introductory rev as default and checked the Required Fields for the Affected Items' Suppliers tab.

Resolution: Load the Suppliers information with the Rev of the current change.

Verification:

  1. In Admin, enable Parts.Suppliers.List01 and point it to any list.

  2. Set Default Change Orders.Pending.Exit Required field as Parts.Suppliers.List01.

  3. Log in to Web Client, create a Part, Part01, and add a Supplier, without adding a value to List01.

  4. Create an ECO, ECO01, against Part01, select Default Change Orders workflow

  5. Click Audit Status, it shows the following error/warning for the missing required field: The following required fields are missing: Part01: Suppliers.List01.

  6. Click on the row, and it will locate to Part01's Supplier.List01. Edit the cell with a value and click Save.

  7. Go back to the Audit Status dialog, and click Audit.

    Result: The warning/error of the missing required field for list01 does not appear as the value is provided.

  8. Try to release the ECO.

    Result: The user is able to release the ECO.

17757274

Supplier

Issue: ITEM.P2.MULTILIST01 IS CLEARED WHEN ADDING SUPPLIER

Root Cause: If the ASL that is mapped to the attribute in Item.Suppliers.Supplier points to a MultiList, when the list attribute of the MultiList is changed from Supplier list to other lists, the relation between the ASL mapped to the attribute and the MultiList is not destroyed.

Resolution: Destroy the relation and set the value of the ASL mapped to the attribute to the initial value.

Verification:

  1. In Admin, enable Parts.Page Two.MultiList01 and associate the List attribute with User Group list.

  2. Enable Parts.Suppliers.Supplier and associate the ASL mapped to attribute with Parts.Page Two.MultiList01.

  3. Go back to Parts.Page Two.MultiList01, the List attribute was auto-changed from User Group list to Supplier list, then change the List attribute back to User Group list and save.

  4. Log in to Web Client.

  5. Create a Part and select one or more User Groups for the Page Two.MultiList01 field, click Save.

  6. Go to the Suppliers tab and add a Supplier. Go back to see the value(s) in the Page Two.MultiList01 field.

    Result: The value(s) in the Page Two.MultiList01 field remain.

17838950

Administration/Configuration

Issue: WE CAN NOT CHANGE SUPPLIER USERS

Root Cause: We cannot inactivate the Default RFQ Recipient user. It prompts an error message, and if you follow the message guild, the operation is successful.

Resolution: Do not check if the supplier user is used as the Default RFQ Recipient if there is no PCM License.

Verification:

Prerequisite: User has only a PCM license.

  1. Create Supplier.

  2. Add contact user.

  3. Make the contact user inactive.

    Results: The following error message is displayed: ”Cannot make the user inactive since this user is the default RFQ recipient.”

17963781

Price/PCO

Issue: MPN ERROR DURING MPN PRICE OBJECT CREATION

Root Cause: In the current code, the equal sign "=" is the delimiter char between name and id in a list item, so it does not support "=".

Resolution: Update the parsing method with lastIndexOf().

Verification:

  1. Create a Manufacturer Part name as SLEEVE 4.0KV, ID=1MM.

  2. Create a Price object against Manufacturer Part and use the SLEEVE 4.0KV, ID=1MM from list of values.

  3. Finish the creation of the Price object.

    Result: The Price can be created with a Manufacturer Part number that contains an equal sign.

18076469

Sourcing Project

Issue: EXPANDED DISPLAY OF ITEMS TAB IN SOURCING PROJECT DISPLAYS DATA IN WRONG COLUMNS

Root Cause: The logic for getInnerTableMaxRowCount() is incorrect.

Resolution: Overwrite the getInnerTableMaxRowCount() method.

Verification:

  1. Add an assembly that has Documents to a Sourcing Project.

  2. Select the Assembly and add Partners.

  3. Select the Assembly and perform Expand Display.

    Result: The BOM structure displays correctly.

18377150

Export

Issue: ITEM NUMBER NOT SHOWING UP IN PCO EXPORT

Root Cause: Missing validation for item privilege.

Resolution: Add item privilege validation.

Verification:

  1. Log in to Web Client.

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

  3. Create a PCO for the Price.

  4. Export the PCO in Excel format using default filter.

  5. Validate the Item number in Excel file >Affected Prices tab.

    Result: The Item number is displayed correctly in the Affected Prices tab (Export file).

3.4 Product Quality Management

16959843

SDK

Issue: FAILURE IN ADVANCEDSEARCH WEB SERVICE WHEN PRIVILEGES ARE MISSING

Root Cause: The code does not support invalid attributes when doing Advanced Search via Web Services (WS).

Resolution: In WS client, the customer needs to put a flag as follows to notify the WS server whether we need to skip the invalid attribute or not.

invalid attribute or not.

ParamListType plt= new ParamListType();

String[] ignoreInvalidAttr= new

String[1];

ignoreInvalidAttr[0]="ignoreInvalidAttr";

plt.setParameter(ignoreInvalidAttr);

ParamListType[] plta = new

ParamListType[1];

plta[0]=plt;

advancedSearchRequestType.setParams(plta);

Verification:

In WS client, pass the flag to notify WS server if we need to skip the invalid attribute or not, as per resolution and should provide the proper response with error.

17271099

Web Client

Issue: DATE ONLY PRINTING ERROR

Root Cause: N/A

Resolution: N/A

Verification:

  1. Log in to Java Client as admin.

  2. Go to the class Problem Reports > Enabled Page two >Date attributes.

  3. Enable date01, date02, date03 to yes, also set the format from Date and Time to Date Only.Enable date04 to yes with default format.

  4. Save.

  5. Log in to Web Client as admin.

  6. Create a PR and set Page Two dates with new values with Date Only.

  7. Save.

  8. Go to Action >Print.

  9. Click preview values.

Result: The date attributes are displayed in Date Only format.

17430669

Web Client

Issue: PROBLEM REPORT CREATION SHOWS UP IN THE GMT TIME ZONE WHEN EVEN THE PHYSICAL SERVER IS PST

Root Cause: This is a Date Only issue in the print action.

Resolution: The issue was fixed in 932.

Verification:

  1. In Admin, set Problem Reports.Cover Page.Date Originated.Date Time Format = Date Only.

  2. In Web Client, create a Problem Report.

  3. Click Actions > Print, and click Preview.

    Result: On the Print Preview page, the value of Date Originated appears as Date Only without time/timezone.

3.5 Product Portfolio Management

14338659

SDK

Issue: CONTENT NOT CREATED CORRECTLY ON PROJECT CREATED BY EXECUTING IPROGRAM SAVEAS

Root Cause: There is a lock on Program deliverables which is only released after the entire "Create from template" transaction is finished. Therefore, this operation cannot be executed simultaneously. However, using the option "do in background" could solve the issue.

Resolution: Enhanced saveAs API in SDK to pass a flag to execute Create From Template operation in background. A new parameter ProgramConstants.DO_IN_BACKGROUND was added and should be used in the customer sample code ThreadTest.java in order to solve the issue.

Verification:

  1. Log in to Java Client as admin.

  2. Create a project template with some structure.

  3. Fill the template name as SDK code.

  4. Run SDK code

Result: No error message is shown on the SDK side. Five Programs are created successfully.

14401071

Administration/Configuration

Issue: HOW TO DISABLE THE JOIN BUTTON ON TASK OBJECT

Root Cause: No Privilege check for Join/Reply of Discussion

Resolution: 1. "Join" will be available if the user has the Modify privilege for Discussion.Notify List.2. "Reply" will be available if the user joined the discussion. To reply to the discussion, the user should also have Modify privilege for Replies.Notify List /Replies.Message / Replies.Subject.

Verification:

  1. Log in to Java Client and remove the following attributes:

    "Discussion.Cover Page.Notify List,Discussions.Replies.Message,Discussions.Replies.NotifyList,Discussions.Replies.Subject" from belowPrivileges.Modify All DiscussionsModify My DiscussionsReply to All Discussions I am Notified About(Restricted) Reply to Discussion(Restricted) Modify My Discussions

  2. Log in as Admin and create a Program with some child objects and add Discussions to the child objects.

  3. Log in as user "robertb" and try to join the discussion.

    Note: "1 of 1 discussions cannot be joined due to insufficient privilege." error message is displayed.

  4. Add the attributes removed from the Privilege and try to Join and Reply to the discussions.

    Result: The ability to join and reply to a discussion is controlled based on privileges.

16212836

Standard Reports

Issue: PPM USER TIME REPORT SHOWS INCORRECT ACTUAL TIME

Root Cause: The User time report uses the value of attribute Activity.GI.Actual Time.

Resolution: Change Activity.GI.Actual Time to Activity.Team.Actual Hours.

Verification:

  1. Execute PPM User Time Report.

  2. Edit DEFAULT LAYOUT.

  3. Switch to tab Format.

  4. Move Actual Hours from Hidden Fields to Displayed Fields and save.

  5. Click Next.

  6. Click Finish.

    Result: The value of the Actual Hours field comes from tab Team of the activity.

16382327

Web Client

Issue: THIS FEATURE DID NOT PERFORM AS EXPECTED.PLEASE CONTACT YOUR AGILE ADMINISTRATOR

Root Cause: The UI does not handle the case when the Days Effort attribute is set to invisible.

Resolution: Handle the case when Days Effort is set to invisible.

Verification:

  1. Set Days Effort to invisible in the Activity General Info tab in Java Client.

  2. Create a Program in Web Client.

  3. Validate the data in the General Info tab. Try to open an activity.

    Result: The General Info tab displays the data correctly.

16399675

Discussion & Action Items

Issue: DISCUSSION REPLIES ARE NOT SORTED IN ORDER OF CREATION

Root Cause: The DISCUSSION.CREATED_DATE attribute is a date type attribute. The milliseconds information is not stored in the database. When many replies are added quickly, replies of the Discussion are not sorted in order of creation.

Resolution: Sort the replies by created Id instead of by created date.

Verification:

  1. Run HistoryTest. This will create a new Discussion, and add 50 replies.

  2. Log in to Web Client, and search for the Discussion created for the last time.

  3. Open the Discussion.

    Result: The replies are sorted by created Id instead of created date.

16400071

Administration/Configuration

Issue: DELETED PROJECT RECYCLE BIN SEARCH DOES NOT EXECUTE

Root Cause: The DISCUSSION.CREATED_DATE attribute is a date type attribute. The milliseconds information is not stored in the database. When many replies are added quickly, replies of the Discussion are not sorted in order of creation.

Resolution: Sort the replies by created Id instead of by created date.

Verification:

  1. Log in to Web Client.

  2. Create a few Projects and then soft delete them.

  3. Search the Recycle Bin searches for deleted Projects.

    Result: Recycle bin searches for deleted projects shows the projects that were soft-deleted.

16428173

Gantt Chart

Issue: UNABLE TO SET ACTIVITIES.PAGE TWO.NUMERIC ATTRIBUTE TO NULL FROM GANTT CHART

Root Cause: The Null numeric value is ignored in Gantt when saving the attribute.

Resolution: Save null numeric value when saving the attribute.

Verification:

  1. Log in to Java Client as admin.

  2. Enable Activities.Page Two.Numeric01.

  3. Log in to Web Client.

  4. Create Project01 and add Task01.

  5. Go to the Schedule tab of Task01 and edit Page Two.Numeric01 attribute. Change the value from the default of 0 to null and Save.

    Result: The user is able to save the value to null.

  6. Launch Gantt Chart from Project01.

  7. Select the row of Task01 and right click > Properties.

  8. Go to the Page Two tab. Notice that Numeric01 has value 0 set.

  9. Remove 0 so that the value will be null and Save.

  10. Select the row of Task01 and right click > Properties.

  11. Go to the Page Two tab. Notice that Numeric01 has its value set as Null.

  12. Save the changes and close Gantt.

  13. Go back to Web Client and open Task01 of Project01.

  14. Check Page Two.Numeric01.

    Result: The value is set to Null.

16693530

Search

Issue: CANNOT SEARCH FOR USER GROUPS BY THE TEAM.NAME FIELD

Root Cause: The menu for attribute Team.Name does not contain Usergroup in search criteria.

Resolution: Added a special handler to support Usergroup.

Verification:

  1. Log in to Web Client as admin.

  2. Create a User Group, UG1, and set Yes in the Resource Pool field.

  3. Create a Program, P1, and add UG1.

  4. Do an Advanced Search for Projects > Activities > Object Search with criteria: Team.Name In Value.

  5. Click the Value field and click the icon to search.

  6. Select the User Group in the drop down list and input UG1 as value.

  7. Select UG1 and finish the search.

  8. Check the search result.

    Result: Program P1 appears in the search result.

16739501

Export

Issue: IMPORTED MSP XML IS MISSING RESOURCES

Root Cause: The error method to check the relationship between parent and child.

Resolution: Correct the method to check the relationship between parent and child.

Verification:

  1. Log in to Web Client of Environment1.

  2. Create a task with one Resource and one Resource Pool in the Team tab.

  3. Go to Actions > MSP > Save as XML (in either Edit or Read Only mode).

  4. Open this XML in MSP 2010, remove the values in TEXT 30 field, and save as XML;

  5. Import this XML in Environment2, During the import steps map the resource with a User/User Group from our demo environment.

  6. Check the Team tab to see if the newly mapped resource is displayed.

    Result: Importing Project's XML from one environment to another with resource mapping shows the newly mapped resources (Users and User Groups) in the Team tab of the imported project.

16800825

Web Client

Issue: INVALID DATE ERROR WHEN USING SAVE AS FROM PROGRAM (PPM)

Root Cause: The wrong date format is used when saving a Program as another one.

Resolution: Use the correct date format when saving a Program as another one.

Verification:

  1. In Java Client, set the field, Estimated Start Date, as a required field. It will appear as a required field in the Save As window.

  2. Create a Program and fill in the Scheduled and Estimated dates.

  3. Go to Actions > Save As, fill in the information in the Save As window.

  4. When you save, the system should not generate the error massage saying that the date you put is an invalid date.

    Result: The new project is saved successfully.

17061558

Web Client

Issue: KEYWORDS ATTRIBUTE IN CONTENT TAB OF AGILE PPM MODULE

Root Cause: The default value of Keyword is not added when import MSP XML project.

Resolution: Add the default value of Keyword when importing an MSP XML project.

Verification:

  1. Create a Program using Create New. Create new from template and importing project using xml.

  2. In the Content tab of the Program, add another Program/Task/ECO/ECR.

  3. The user is able to edit the Keywords attribute if he has required privileges. When the user double-clicks the Keywords column, a new window opens.

  4. Click on Search to add. The Keywords window pops up,

  5. Double-click the value Important Content so that it gets selected and then click Save. Keywords column should show the value Important Content.

    Result: It should not display any error message.

17189640

SDK

Issue: APPENDING ROLES TO THE USER ON THE TEAM TAB CAUSES EXCEPTION

Root Cause: When the user ran a Process Extension (PX) action, the PX roles did not replace the user's roles.

Resolution: To run a PX action, use PX roles to replace the user's roles.

Verification:

  1. Create a PX: UpdateTeam.

  2. Create Program and assign a user in the team table with Role: Program Team Member.

  3. Log in to Web Client as a user who does not have role: Program Manager and run the PX in the Program action menu.

    Result: The user in the Team table is assigned with an additional Role: Program Manager.

17278975

Web Client

Issue: PPM TIME SHEET SEARCH RETURNS AN ERROR WHEN ADDING USERS FROM A USER GROUP

Root Cause: The User ID is not split from the User Group when the User comes from a User Group.

Resolution: Split the User ID from the User Group if the User comes from a User Group.

Verification:

  1. Log in to Web Client.

  2. Go to the Timesheet tab.

  3. More > select Timesheet search.

    Result: It works for a one user search.

  4. Select from a User Group - Users.

    Result: Results display for Users added from the User Group.

17348351

Web Client

Issue: REPLY BUTTON CANNOT BE ENABLED IN QUICK VIEW OF DISCUSSIONS

Root Cause: The code uses the wrong method to get edited information from the Discussion Quick View.

Resolution: Design a new method to get edited information from the Discussion Quick View.

Verification:

  1. Log in to Web Client.

  2. Create a Discussion.

  3. In the Discussion page, click on the Reply button. The Reply to the Discussion window opens.

  4. Enter a reply and click Send.

  5. Search for Discussions and from the search results, click on the Quick View for any Discussion and try to reply.

  6. Open the Quick View for any Discussion from the Recently Visited section and try to reply for that Discussion.

    Results: 1. The user is able to submit a reply to a Discussion from the Quick View of the Discussion irrespective of where that discussion is opened. 2. The Reply button is enabled in the Quick View of Discussions.

17452097

Discussion & Action Items

Issue: DISPLAY WRONG DISCUSSION OBJECT STATUS UNDER ECR RELATIONSHIP

Root Cause: The Discussion's version is not increased when it is updated, so the Relationship table is not reloaded in cache.

Resolution: Update the Discussion version when it is updated, then the Relationship table will be reloaded in the cache.

Verification:

  1. Create an ECR, create a discussion, D00001.

  2. Go to the ECR's Relationship tab, drag the Discussion into the ECR's relationship, the current status of D00001 is Open.

  3. Change D00001's status from Open to Closed. Go to the ECR's relationship, the current status of D00001 is Closed.

  4. Change D00001's status from Closed to Open. Go to the ECR's relationship, the current status of D00001 is Open.

    Result: It displays the proper status of the Discussion.

17626022

Web Client

Issue: COPY URL TO CLIPBOARD IS INTERMITTENTLY CREATING BAD URLS

Root Cause: This is a code issue. The regex that is used to strip the jsessionid is not correct.

Resolution: Strip the jsessionid which supposed to end with ? or #.

Verification:

  1. Log in to Web Client.

  2. Create a Program, Part, ECO, MCO, and User Group.

  3. For each of the newly created objects, go to Actions > Copy URL to clipboard.

  4. In the new window where the URL is copied, verify that there are no extra characters between 'PLMServlet' and '?'.

    Result: There are no extra characters between 'PLMServlet' and '?' in the URL. The URL opens the correct object in a new window.

17972796

Web Client

Issue: A932 PPM MODULE: CONTENT TAB FIELD VALUE IS NOT DISPLAYED IN TEMPLATES

Root Cause: The application is hard-coded to set the first column to null for template content.

Resolution: Set the criteria met column to null by attribute id.

Verification:

  1. Create a new Program of type template.

  2. Add an Item to the Content tab of this Program.

  3. Modify the first column, for example, "required" or "rule". (This will depend on the View settings.) Click Save.

  4. Open the template > Content Tab; Required field is blank, double-click on it. It displays a dropdown value with yes/no options

  5. Select either option, Save.

    Results: The value (Yes/No) for Required field is saved and displays correctly after saving. When changing the View's display order the columns and their values appear correctly.

17941797

Administration/Configuration

Issue: AGILE PPM RESOURCE POOL OWNER CANNOT ACCEPT OR DECLINE A PHASE

Root Cause: When displaying an Item object by clicking a link to it from another Item's Where Used tab, the default revision class is the Change base class and is not translated to the specific class, so the related system logic is mismatched.

Resolution: Translate the default rev class from base class to the specific class.

Verification:

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

  2. Create MCO01 against Part01 and release it.

  3. Create MCO02 against Part01 and release it.

  4. Create MCO03 against Part01.

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

    Results: The file attachments remain in the Part of the pending MCO Rev.

18007973

Gantt Chart

Issue: MODIFICATION OF LIST VALUE IN GANTT LEADS TO BAD DATA IN AGILE DB

Root Cause: This is a simple list initial issue on PAGE_TWO of activity in Gantt.

Resolution: To be consistent with Web Client, convert ?? to null on PAGE_TWO of activity in Gantt.

Verification:

  1. Create a List with values as Yes/No/0/blank.

  2. Assign the list to the Page Two attribute of Activity.

  3. Create an Activity in the following structure in Web Client:

    P1-----T1-----------G1with attribute value as 'Yes'

  4. Go to Gantt and edit the Page Two attribute value to blank and Save.

  5. Check the attribute value at the database level.

  6. Go to Web Client and Change the Value from blank to No. Click on Save.

  7. Edit the value back to Blank and Save.

  8. Check the attribute value at the database level.

    Deviation: Try changing the list value from Yes/No/0 to blank in Gantt and verify the same in DB. The following query is to be used to verify in DB assuming List11 is the PageTwo attribute assigned with the list value: Select list11 from page_two where id in (select id from activity where activity_number = 'PGM00001') and class=18022;

    Results:

    >> The user is able to create a list and assign the list to the Page Two attribute.>> The user is able to log in to Web Client and create an activity with the attribute value as Yes.>> The user is able to launch Gantt chart and edit the value to Yes/blank/No.>> If the value of the PageTwo List attribute in Web Client and Gantt is blank, then in the DB, the value is null. For a blank value in Gantt, the DB value is not 0; it is always null.

18055224

Searches

Issue: WORKFLOW SEARCHES WITH ADVANCED SEARCH AGILE 9.3.2 ARE NOT WORKING CORRECTLY

Root Cause: The count of Prompt Search times are not recorded in the workflow's related attribute.

Resolution: Pass a parameter to cover workflow issues.

Verification:

For Activities:

  1. Create a Program with some child objects and move the status of child objects to In process with Approve as User A.

  2. Click on Advanced Search and set the criteria:

    Projects Gates Object Search

    Activity Type In Prompt Value

    (Workflow status Not Equal To Prompt value Approver Action Equal To Prompt Value)

    Note: Brackets symbol indicates Grouping the criteria.

    {Grouping: Select the radio buttons from the left and right and then select option Add() from grouping menu.}

  3. Click on the search button.

  4. Enter the prompted search criteria:

    Activities Type in (prompt) Program, Phase, Task

    [Workflow Status Not In $StatusType.Complete

    Approver Action Equal To (Awaiting Approval)

    Approver Contains (prompt) ]

    Results: Search results display the correct values.

For Gates:

  1. Create a Program with some child objects and move the status of child objects to In Review with Approve as User A.

  2. Click on Advanced Search and set the criteria:

    Projects Gates Object Search Gate Type In Prompt Value

    (Workflow status Not Equal To Prompt value

    Approver Action Equal To Prompt Value)

    Note: Brackets symbol indicates Grouping the criteria.

    {Grouping: Select the radio buttons from the left and right and then select option Add() from grouping menu.}

  3. Click on the search button.

  4. Enter the prompted search criteria:

    Activities Type in (prompt) Gate

    [Workflow Status Not In $StatusType.Complete Approver Action Equal To (Awaiting Approval)]

    Result: The search results display correct values.

18327990

Gantt Chart

Issue: UNABLE TO MAKE CHANGES TO THE RESOURCEVIEW UNTIL USER RETURNS TO THE GANTT VIEW

Root Cause: Set uneditable when initializing resource view chart in Gantt.

Resolution: Set editable when initializing resource view chart in Gantt.

Verification:

  1. Create a Program with some child objects and add few resources with percent allocation from the Team tab.

  2. Launch the Gantt chart for the Project and navigate to Resource view.

  3. Select a Resource that is assigned to a task with Percent allocation and drag the task from chart towards left.

    Results: Dragging the Task is moving to the respective date.

18420374

Web Client

Issue: UNABLE TO ARCHIVE PROJECTS - GET ERROR REGARDING MISSING IN OR OUT PARAMETER AT INDEX

Root Cause: The SQL string is incorrect when attempting to archive a project with over 100 tasks on its Schedule tab.

Resolution: Correct the SQL string.

Verification:

  1. Log in to Web Client.

  2. Create a Template program, Prg1 with 180 Tasks, in the Schedule tab.

  3. Create a new Active project from the template created in Step 2.

  4. Edit the Project's Description and some other attributes of General Info tab.

  5. Add a subtask under one of the 180 subtasks of the root program.

  6. Navigate to the root program and click Action > Archive

    Result: 1. The user is able to modify the root program. 2. The user is able to Archive/Unarchive the root project. 3. When attempting to archive a project with over 180 tasks on the Schedule tab, it does not fail with Missing In or Out parameter.

18336123

Roles & Privileges

Issue: USER W/O MODIFY PRIVILEGE FOR THE TASK CAN MARKUP COMPLETE FROM MY ASSIGNMENTS

Root Cause: Privileges are not checked when completing an Action Item from "My Assignment".

Resolution: When attempts to complete an ActionItem from My Assignment, we check Modify privilege on Activities.Action Items.Status.

Verification:

  1. Log in to Java Client as admin user.

  2. Create user ynakano1, and grant a role with the following privileges to this user. Do not grant modify program privilege: Discover All Projects, Programs, Phases, Tasks and Gates Read All Projects, Programs, Phases, Tasks and Gates

  3. Log in to Web Client as admin.

  4. Create Project, go to Schedule tab, and add Task1.

  5. Open Task1, go to Collaboration tab > Action Items, and add an Action Item.

  6. Add an Action Item, and set Assigned to: ynakano1.

  7. Log in to Web Client as ynakano1.

  8. Go to My Assignments.

  9. Open Program from the Related To link of the task

  10. Go to Collaboration tab > Action Items, and confirm that the user cannot select complete the task as he has no privilege. This is an expected result.

  11. Go back to My Assignments. Select the Action Item and Mark Complete.

    Results: A user without the modify privilege for this Project should not be able to mark complete. It shows an insufficient privilege message.

18750943

Web Client

Issue: ISSUE WITH BOOKMARKS OPTION FROM PROJECT ACTION MENU

Root Cause: Do not set the default bookmark name on the activity summary page.

Resolution: Set the default bookmark name on the activity summary page.

Verification:

  1. Go to any Project and add documentXYZ on the Content tab.

  2. Search for documentXYZ and open it.

  3. Navigate to the Relationships tab.

  4. Click on the Project.

  5. Go to the Actions menu and click on Bookmark.

  6. Validate the text in the Add to Bookmarks window in Name text box.

  7. Click on the "Details View" of the Project and validate the same.

    Results: The text that is present in the Name field of the Add to Bookmarks window is the Project name, not Document name.

18857833

Gantt Chart

Issue: REQUEST TO HAVE OWNER ATTRIBUTE EDITABLE FROM GANTT

Root Cause: The functionality to edit the Owner attribute behavior in Gantt is restricted.

Resolution: Change the modification limitation of the Owner attribute and send the notification.

Verification:

  1. Create a Program with some child objects.

  2. Launch Gantt chart and launch the Program Information window for a child object.

  3. Edit the Owner attribute and change the user.

    Results: The Owner field is editable. After the new value is saved, it is updated.

3.6 Agile PLM Framework

12400499

Roles & Privileges

Issue: CANNOT GETFILE FOR ATTACHMENT FROM ECN AFFECTED ITEMS

Root Cause: N/A

Resolution: Only give Item Get file privilege to be able to download while looking at the Change Affected Items > Redlines > Attachments tab in order to simplify user privilege requirements.

Verification:

  1. Create a user cy. The user only has the Cy Role and default My User Profile ROLE.

  2. Assign the following privileges to the Cy Role: Read Doc/Changes, Discover Doc/Changes, Getfile for Doc

  3. Log in to Web Client as admin. Create Doc1, add an attachment to Doc1, and create ECO1 against Doc1.

  4. Go to ECO1's Affected Item tab > Redline Attachment.

    Result: The Get files button is enabled and the user can get the files.

  5. Log in to the system as the cy user.

  6. Open Doc1 and open ECO1.

  7. Go to the Affected Item's tab and redline the attachment.

    Result: The Get files button is enabled and the user can get the files.

12970719

Java Client

Issue: WHEN USING A COLON IN A CASCADE LIST VALUE, THE VALUE DISPLAY IS SHORTENED WHEN EDITING

Root Cause: The character "\" is allowed in list name and entry names.

Resolution: Do not allow "\" in list name and entry names.

Verification:

  1. Log in to Java Client as admin.

  2. Create a cascade list that contains the following values:

    List001=TEST

    List002<TEST

    List003-TEST

    List004"TEST"

  3. Assign the cascade list to Part.Page Two.List01.

  4. Log in to Web Client as admin.

  5. Create a Part P001.

  6. Assign a value for Page Two.List01 then save.

    Result: List001=Test appears as List001=Test;

    List002<TEST appears as List002<TEST;

    List003-TEST appears as List003-TEST;

    List004"TEST" appears as List004"TEST".

  7. Click Edit and check list01.

    Result: List001=Test appears as List001=Test;

    List002<TEST appears as List002<TEST;

    List003-TEST appears as List003-TEST;

    List004"TEST" appears as List004"TEST".

    Note: Special characters ; \ are not allowed in list values for cascade list (special character : is allowed).

13988154

Searches

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

Root Cause: Lack of class/subclass filter when generating attachment SQL

Resolution: Added class/subclass filter in attachment SQL.

Verification:

  1. Create File Folder1 with description - testword.

  2. Create Markup Object1 with description - testword.

  3. Create File Folder2 with attached text file containing text testword.

  4. Create Markup Object2 with attached text file containing text testword.

  5. Basic Search for File Folders Contains Phrase testword (checked to Include Attachments Text).

    Results: Search returns 4 objects (File Folder1 & 2 and Markup Object1 & 2)

  6. Basic Search for File Folders|File Folder Contains Phrase testword (checked to Include Attachments Text).

    Results: Search returns 2 objects (File Folder1 & 2).

  7. Basic Search for File Folders|Markup Contains Phrase testword (checked to Include Attachments Text).

    Results: Search returns 2 objects (Markup Object1 & 2).

Note: Validated with options: Manual Indexing - selected Index Attachment Now. Synchronous - files get indexed automatically in minutes.

14008186

Administration/Configuration

Issue: ATOS ARE NOT BEING GENERATED BY EVENT

Root Cause: The search server does not support $CURRENTREV.

Resolution: Changed code to support $CURRENTREV.

Verification:

  1. Log in to Java Client as admin.

  2. Create a Scheduled Event to run every 5 minutes.

  3. Create the following criteria: Part type in Part and ( Title Block*.Lifecycle Phase Equal To Preliminary And $CURRENTREV EqualTo $INTRODUCTORY_PENDINGCHANGE ).

  4. Create a Subscriber with the scheduled event and criteria, and select the default part filter.

    Result: The user is unable to select the criteria created in Step 3 when defining the subscriber.

  5. Create another subscriber with the scheduled event and the criteria, All Parts, and select default part filter.

  6. Enable the subscriber.

    Result: New ATOs are automatically generated every 5 minutes.

14119874

Searches

Issue: SEARCH RETURNS INCOMPLETE RESULTS BASED ON STATUS TYPE

Root Cause: If create PSRs/QCRs with default workflow, the "statustype" field in table psr/qcr should be "0" when at pendng status, but the actual value is "NULL", which leads to the search issue.

Resolution: Set the correct value for statustype when creating PSRs/QCRs with default workflow.

Verification:

  1. Log in to Java Client as admin.

  2. Go to Classes- > Corrective and Preventive Actions- >User Interface tab -> Cover Page, open attribute:workflow, set Default CAPAs as its default value.

    Go to Classes >Audits >User Interface tab > Cover Page, open attribute:workflow, set Default Audits as its default value.

  3. Log in to Web Client as admin.

  4. Create three CAPAs and two Audits.

    QCR Number, Status, Workflow

    ---CAPA00001,Identified,Default CAPAs

    ---CAPA00002,Identified,Default CAPAs

    ---CAPA00003,Implement,Default CAPAs

    ---Audit00001,Prepared,Default Audits

    ---Audit00002,Audited,Default Audits

  5. Do an advanced search: Quality Change Requests > Corrective and Preventive Actions > Status > In > $STATUSTYPE.pending, run the search.

  6. Do an advanced search: Quality Change Requests > Corrective and Preventive Actions > Status >In > $STATUSTYPE.review, run the search.

  7. Do an advanced search: Quality Change Requests > Status > In > $STATUSTYPE.pending, run the search.

  8. Do an advanced search: Quality Change Requests > Corrective and Preventive

    Actions > Status > In > $Default CAPAs.pending, run the search.

Results:

CAPA00001 and CAPA00002 are returned in the search results.

CAPA00003 is returned in the search results.

CAPA00001, CAPA00002 and Audit001 are returned in the search results.

CAPA00001 and CAPA00002 care returned in the search results.

14272626

Standard Reports

Issue: SCHEDULED CUSTOM REPORT GIVES NULL POINTER EXCEPTION

Root Cause: NullPointerException occurs when 2 custom reports of the same type are run together with same user.

Resolution: Use the left one to get correct transaction info to avoid NullPointerException error.

Verification:

  1. In Java Client, make sure Maximum Reports Executed Simultaneously > 1.(Multiple Report Restriction can be ignored here since in a cluster environment it has no effect). In Server Settings > Task Configuration > Report Task, set Interval to 1 (minutes).

  2. Log in to Web client as admin. Create a custom report CR001 which will run for a while to show the result (It is better if the report can run > 1 minute).

  3. Add a schedule for the report.

  4. Manage to manually run the report:

    - at the same time as the scheduled time.

    - just before a scheduled start.

    - just after a scheduled start.

Result: You may encounter 3 kinds of behaviors, all of which are acceptable:1. The manual reports and scheduled reports all finish successfully..2. The manual report failed with error ”Someone is working on this object. Please try again later.” message, while the scheduled report succeeds.3. The manual report finished, while the scheduled report failed. Wait for 5 minutes or so and the scheduled report will re-run and finish without error.

14296045

Administration/Configuration

Issue: ERROR WHEN ENTERING DEFAULT TEXT: THE DEFAULT VALUE IS GREATER THAN THE MAX LENGTH

Root Cause: Currently, 1333 characters (4000/3) is put to cover all the single/multiple byte languages when validation is done. Actually, we should compare the byte count of input characters with 4000 to see if it exceeds the maximum length.

Resolution: Calculate the byte count of input characters and then compare it with the max length (4000 bytes) to see if it exceeds that.

Verification:

  1. Log in to Java Client as an English user.

  2. Go to Admin > Classes, open any object, for example, ECO, and open the description and notice that the ”max length” and ”max system length” are both set as 4000.

  3. Enter a text value that is 1327 characters in length in ”Default value”.

  4. Save.

14341331

Directory Access Protocol

Issue: NAVIGATION BETWEEN THE TABS SLOW IN AGILE DUE TO LDAP CALLS

Root Cause: 1. Group unique member is queried when querying a user group. 2. A9 server is chatty when working on LDAP users and user groups.

Resolution: 1. Do not query user group's unique member. 2. Use LDAP caching API in A9 server.

Verification:

  1. Configure the LDAP server in Java Client.

  2. Configure LDAP authentication in the Weblogic console.

  3. Enable auth.ldap.group.enabled property in agile.properties file.

  4. Configure the log.xml file by enabling the LDAP log file(adminLdap.log) generation as per the steps mentioned by DEV in progress update and restart the server. A log file adminLdap.log should be created in agileDomain\servers\<AgileServer>\logs.

  5. Migrate the user and usergroup from LDAP to Agile.

  6. Log in to Web Client as an LDAP user and open the current user.

  7. Switch between tabs of current user.

  8. Open the adminLdap.log file and verify the logged information.

Result: Logs related to LDAP calls are not printed each time when switching between the tabs.It prints only once.

14344697

Custom Reports

Issue: PARENT-CHILD RELATIONSHIPS & BILL OF SUBSTANCES APPEAR INCORRECTLY IN CUSTOM REPORT

Root Cause: The Join condition that is defined between Material Declaration and Substance is incorrect.

Resolution: Correctly join Material Declaration and Substance. The relationship should be 'Material Declaration - Mfr Part - Substance'.

Verification:

  1. In Web Client, create a Substance Declaration

  2. Add at least two Manufacturer Parts.

  3. Associate a Specification to the Declaration.

  4. Add different BOS substances to each Manufacturer Part. For example:

    Mfr Part 1

    * Lead

    * Lead Compounds

    - LEAD TRI-OXIDE

    - Lead Oxide

    Mfr Part 2

    * Cadmium

    * Lead Compounds

    - Cadmium

    - LEAD TRI-OXIDE

    - Lead Oxide

    * Test Group

    - Test Child

  5. Run a Custom Report to include the above fields, that is Manufacturer Part Composition.Substance Name, with the following query: Query Definition: Object Search -- Substance Declarations { Cover Page.Name Contains MD00017 }

Result: The data under Mfr Part1 and Mfr Part2 is shown correctly.

14747537

Internationalization

Issue: AGILE-9.3.2:4461:PARTIAL TR: COMPARE BY SEARCH

Root Cause: It was hard coded in the JS file.

Resolution: Do not hard code it, use I18N tag.

Verification:

  1. Log in to Agile as Japanese user.

  2. Create an Action using File Folders > Designs > Action.

  3. Click View All Versions.

  4. Click Comparison Report.

  5. Check the Compare By Search.

    Result: The Compare By Search results are translated into the Japanese language.

14753008

Internationalization

Issue: WPTG_TMS_LT_T13Y: AGILE-9.3.2: STUDLYCAPS:CHANGESTATUSNORESPONSEFROMACKNOWLEDGER

Root Cause: There is some studlycaps word in Smart Rule of Java Client.

Resolution: Separate the studlycaps words by one space.

Verification:

  1. Log in to Java Client as admin.

  2. Go to System Setting > Smart Rule > check CHANGESTATUSNORESPONSEFROMACKNOWLEDGER.

    Result: The attributes are added space for Smart Rule: CHANGE STATUS NO RESPONSE FROM ACKNOWLEDGER. Other Smart Rules are changed successfully.

14754329

Internationalization

Issue: AGILE-9.3.2:4461:LINE WRAPPED UNDESIRED FOR "LAYOUT TYPE:

Root Cause: Label is too short.

Resolution: Increase the width of the label.

Verification:

  1. Log in as traditional Chinese user.

  2. Go to Compliance Report > Parts with Substances.

  3. Go to the Schedule tab.

  4. Click Add.

  5. Click the Edit button for default Layout for Item.

    Result: The label and value are aligned.

16001509

Administration/Configuration

Issue: ATTRIBUTE NAME OF FLEX FIELD DEFINED BY NON-ENGLISH USER GETS LOST

Root Cause: when creating new flex attributes with non-english user, record is not inserted into langtable.

Resolution: Insert the record into langtable when creating new flex attributes with non-english user.

Verification:

  1. Log in to Java Client as admin. Change the user's language preference to Japanese, and then log in again to Java Client.

  2. Go to Settings > Data Setting > Class, and create a new Part subclass, part_test.

  3. Go to Page Three tab of part subclass, part_test.

  4. Create a new list attribute, and define an attribute name for Japanese language users, for example, JapaneseAttName.

  5. Change the admin user's language preference to English, and login again to Java Client.

  6. Update the name of the attribute created in step 4 to define the English attribute name, for example, EnglishAttName.

  7. Log out from Java Client.

  8. Restart Agile Application Server.

  9. Log in to Java Client as admin. Change the language preference to Japanese, and log in again to Java Client

  10. Check the attribute name of the attribute created in step 4.

    Result: The values are kept the same as JP lanaguage setting.

16052059

Java Client

Issue: DEFAULT VALUE CONFIGURED FOR USER'S CURRENCY IS NOT REFLECTED WHEN CREATING A NEW RATE

Root Cause: When creating a user, the application does not use the selected currency as default value.

Resolution: Use the selected currency as the default value when creating a user.

Verification:

  1. Log in to Java Client as admin.

  2. Go to Admin tab > System Setting > Currency Exchange Rate.

  3. Add the new currency rate, for example, JPY.

  4. Go to Data Settings > Classes, and open property of User Class.

  5. Open the property of Preference tab, and change the default value of Preferred Currency to currency created in step 3, for example, JPY.

  6. Create a new user.

  7. Check the Preferred Currency that is set for the newly created user.

    Result: The default Preferred Currency appears as JPY.

16234036

Internationalization

Issue: CHINESE WARNING MESSAGE IS INCORRECT WHEN DELEGATING THE OWNER OF A PROGRAM

Root Cause: Incorrect Simplified Chinese translation.

Resolution: Retranslate the message.

Verification:

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

  2. Try to delegate a Program to others.

  3. Go to the Team tab.

    Result: User ID with Chinese about Delegation of this activity has not been accepted.

16246915

Web Client

Issue: ERROR WHEN TRYING TO IMPORT FILE WITH INFORMATION RETRIEVED

Root Cause: When exporting reports data as Excel, the format is not Excel format.

Resolution: Correct to Excel format.

Verification:

  1. Log in to Web Client as admin.

  2. Create a Part, P001, and add the Manufacturer Part XIAMEN MICFEX RUBBER to it.

  3. Go to Standard Report >Product Report >Item Manufacturer Report.Define Query > Advanced Search Items > Parts Attribute >Title Block Number, equal to P001 >Finish.

  4. Preferred Status and Manufacturer Part Lifecycle Phase select all, click Finish.

    Result: The report is generated with few data.

  5. Export the report with Microsoft Excel Workbook format.

  6. Modify the Excel to have only 3 columns: Manufacturer name, Manufacturer Part number and Manufacturer Part Lifecycle Phase.

  7. Go to Tools and Settings > Import.

  8. Import file selects the saved Item_Manufacturers_Report.

    Result: The user is able to import the file successfully.

16360226

Roles & Privileges

Issue: VIEW HISTORICAL REPORT ROLE IS NOT VISIBLE IN JAVA CILENT

Root Cause: The View Historical Report Role is a specific role that is only for report use. It should not visible to users, but the admin server side does not filter it out.

Resolution: Filter out the View Historical Report Role from the User/User Group cover page, address book and role assign list.

Verification:

  1. Log in to Java/Web Client as admin.

  2. Open a User/User Group.

  3. Double-click on the Role field on the General Info Tab.

  4. Check if the View Historical Report Role is displayed on the Choices window

    Result: The View Historical Report Role is not displayed in the Java Client or the Web Client.

16498045

Web Client

Issue: CTO (TRANSFER ORDER) ATTRIBUTE PAGE_TWO.MULTILIST01 VALUE IS NOT SHOWN ON COMPLETION

Root Cause: Workflow uses the 3rd bit of flags, but P2.MULTILIST01 also uses this bit for value overflow, which causes the issue.

Resolution: P2.MULTILIST01 now uses the eighth bit of the flags.

Verification:

  1. Log in to Java Client as admin.

  2. Enable Page Two.Multilist01 on CTO and set it to required.

  3. Apply Page Two.Multilist01 to Read CTO privilege.

  4. Log in to Web Client.

  5. Create a CTO, CTO0001, edit the multilist01 attribute to input less than, greater than or equal to 250 values.

  6. Move CTO0001 to Released status, then it is automatically routed to Complete status.

    Result: CTO.Page Two.MultiList01 with less than, greater than or equal to 250 values are shown up in Released and Complete status.

16543853

Web Services

Issue: F-3213 THAT CLEARS THE AUTONUMBERSRFIELDS FOR ITEM & ECO SHOULD SHOW PROPER MESSAGE

Root Cause: Web Services (WS) does not handle the null point exception that is thrown from WS code. so we need to catch the situation when an Item or Change is created without a number or AutonNmber source.

Resolution: When a user creates an Item or a Change without the parameter number or AutoNumber source, return an exception message "Invalid request."

Verification:

  1. Creating a Part/ECO without providing value to number field gives response -<statusCode>FAILURE</statusCode>- <exceptions> <id>0</id> - <exception> <identifier /><exceptionId>WS_1</exceptionId><message>Invalid request</message></exception>

  2. Creating a Part/ECO without providing the number field gives response: <statusCode>FAILURE</statusCode> - <exceptions> <id>0</id>- <exception> <identifier /> <exceptionId>WS_15</exceptionId> <message>Required data missing</message></exception>

    Result: Clearing the AutoNumber source fields for Item and ECO shows the proper message.

16588348

Folders, Files, & Attachments

Issue: ATTACHMENT FILES DO NOT OPEN WHEN FILENAME CONTAINS # CHARACTER

Root Cause: The special character, #, in the filename is not decoded on the server side before trying to open the file.

Resolution: Code changed to decode the "#" in the filename before trying to open the file.

Verification:

  1. Log in to Web Client.

  2. Create a Part, add an attachment with filename MII-4253_App#1.pdf.

  3. Select the attachment and select file MII-4253_App#1.pdf to open.

    Result: When Allow Download of Productivity Components is Yes, the PDF file with "#" in the filename opens in native mode. When Allow Download of Productivity Components is NO - pdf file file with # in filename downloads without any error.

16620724

Web Client

Issue: CHANGE OBJECT - HISTORY TAB-PERSONALIZATION PALETTE-FILTER-USER(S) NOTIFIED

Root Cause: The default properties of this attribute are incorrect.

Resolution: Fix the incorrect meta data.

Verification:

  1. Log into Web Client.

  2. In Change object > History tab > Personalization palette > Filter tab- > User(s) Notified columns - Equal To - Click Search for users.

    Result: The user is able to search for users and filter with the specified criteria.

16746002

Directory Access Protocol

Issue: LDAP QUERY PERFORMANCE IN PLMAP PRODUCTION SERVERS

Root Cause: Group uniquemember is queried when querying a user group. A9 server is chatty when working on LDAP users and usergroups.

Resolution: Do not query usergroup's uniquemember and use the LDAP caching API in the A9 server.

Verification:

  1. Configure the LDAP server in Java Client.

  2. Configure LDAP authentication in WebLogic console.

  3. Enable auth.ldap.group.enabled property in the agile.properties file.

  4. Configure the log.xml file by enabling the LDAP log file(adminLdap.log) generation as per the steps mentioned by DEV and restart the server. A log file adminLdap.log should be created in agileDomain\servers\<AgileServer>\logs.

  5. Migrate the User and User Group from LDAP to Agile.

  6. Log in to Web Client with an LDAP user and open the current user.

  7. Switch between tabs of current users.

  8. Open the adminLdap.log file and verify the logged information.

    Result: Logs related to LDAP calls are not printed each time when the user switches between the tabs.It only prints once.

16888147

Java Client

Issue: JAVA CLIENT FAILS TO OPEN WHEN WHEN USING A LINK IN NOTIFICATION EMAIL

Root Cause: The pcclient.jnlp file that is created is empty.

Resolution: Use apache specific XML parser implement instead of XML factories.

Verification:

  1. Log in to Web Client, open a Part.

  2. Press the F12 key, click the Network tab.

  3. Click the opened object again by clicking the object number in the left pane (Recently Visited).

  4. Select the first row, click the Params tab, find out the classid & objid, and copy them out.

  5. Replace the server URL/classid/objid with following format: http://[ServerURL]:7001/JavaClient/start.jsp?action=OpenEmailObject&classid=[classid]&objid=[objid]

  6. Open IE/FF/Chrome browser, paste the URL.

  7. Launch the URL.

    Result: The user is able to open the object in Java Client.

16954269

Export

Issue: RDO VALUE IS NOT BEING EXPORTED TO EXCEL WHEN THE EXPORT ACTION IS PERFORMED ON A CHANGE

Root Cause: The application exports all user for user group regardless of whether the user is Active or Inactive.

Resolution: Do not export the inactive user for User Group's User tab.

Verification:

  1. Log in to Web Client as admin.

  2. Create an Item, P00001.

  3. Create an ECO against P00001 named C00001.

  4. Make the Item Size attribute in the title block point to theUser Group list.

  5. Set the size attribute to change control.

  6. Use C00001 add value to the size attribute.

  7. Release C00001.

  8. Enable the item size attribute in the Change's Affected Items tab.

  9. Export C00001 to Excel, aXML,and PDX.

    Result: The value of the item size attribute is exported.

16987351

Export

Issue: GROUP SIGNOFF EXPANSION SET TO ALL CAUSING PROBLEM AFTER UPGRADE TO 9.3.2

Root Cause: The new property was introduced in 932 code. and has been fixed in 933. The fix sets the Group Signoff Expansion to Any for all workflow CCB and Released criteria.

Resolution: Fixed script, changed setting value from All to Any.

Verification:

  1. Create a 932 schema and link to a 932 application server.

  2. Log in to Java Client as admin. See the criteria of each status in the workflow.

    Result: The Group Signoff value is set to ”All” or ”N/A”.

  3. Use AUT176 to upgrade 932 to 934.

  4. Link the upgraded schema to a 934 app server.

  5. Log in to Java Client as admin. See the criteria of each status in the workflow.

    Result: Group signoff value set to ”Any” or ”N/A”.

  6. Create a new workflow and add review status. Add criteria.

    Result: Group signoff value is set to ”Any”.

16994351

Directory Access Protocol

Issue: JAVA.LANG.NULLPOINTEREXCEPTION WHEN ATTEMPTING TO LOG IN AS LDAP USER

Root Cause: The Hash utility class throws an unnecessary exception.

Resolution: Adjust the logic so it does not throw that exception.

Verification:

  1. Setup LDAP in Java Client.

  2. Setup LDAP in WebLogic admin console, and restart Agile Application Server by starting WebLogic in a command console.Log in to Java Client as an LDAP user ldapuser1. The user can successfully log in to the system.

  3. Check for the error in the WebLogic command console.

    Result: No errors are displayed.

17065025

Software Development Kit

Issue: PROBLEM IN RETRIEVING MONEY ATTRIBUTE TYPE VALUE

Root Cause: The BigDecimal value that is retrieved via SDK-API is initialized with proper scale.

Resolution: Use the default scale 6 for all the moneyattributes.

Verification:

  1. Create a Program.

  2. Create a List attribute for Project object. Make it a criteria-based dynamic list which points to Project object.

  3. Select a value for Page2.List11.

  4. Through the LoadProject WS, load that List attribute.

  5. Verify that the Project gets loaded without any error.

    Result: The Project gets loaded without any error.

17241491

Searches

Issue: ADVANCED SEARCH RETURNS ERROR USING COMBINATION OF PROMPT AND NON-PROMPT ATTRIBUTES

Root Cause: The number of Duration days is converted to milliseconds, but the validation is based on days.

Resolution: Convert from milliseconds to days before validation.

Verification:

  1. Create an Advanced Search on Projects with criteria: Root Parent Equal To and check Prompt and Scheduled Duration and check Prompt.

  2. Run the search.

  3. Enter a valid Root Parent and Schedule Duration values when prompted.

  4. Schedule duration value should prompt in days before validation. Click on search button.

    Result: Search Results should display all activities that satisfy the criteria.

17279418

Event Java PX

Issue: CELL [AFFECTED ITEMS' EFFECTIVE DATE] IS READ ONLY

Root Cause: In UserContextManager.getUserContext(IAgilePrincipalagPrincipal), try to use case sensitive user name to retrieve process extension context. This context, however, was stored with the case insensitive user name, which results in the wrong context getting returned.

Resolution: Convert user name into lower case.

Verification:

  1. Setup LDAP server with Agile system and create two LDAP users: TESTDEMO1(all upper case) & TESTdemo2(both upper case & lower case).

  2. Compile PX code and put pxroletest.jar to under %AGILE_HOME%\integration\sdk\extensions.

  3. Create a new role: pxrole and give discover, read, modify, create Item & change privileges.

  4. Log in to Web Client and create a new Part named PX_PART001.

  5. Create a new PX named pxtest, and make it initiate from the Tools menu.

  6. Assign Role: pxrole to PX:pxtest.

  7. Log in to Web Client as LDAP user: TESTDEMO1, click pxtest under the Tools menu.

  8. Log in to Web Client as LDAP user: TESTdemo2, click pxtest under the Tools menu.

    Result: The Affected Items.Effective Date attribute is updated and the update log is recorded in History table, e.g. <Affected Items.Effective Date>WAS<2013-07-26 06:53:18 GMT>IS<2013-07-26 07:10:47 GMT>.

17297504

Webs Services

Issue: LOAD PROJECT WEB SERVICE THROWS EXCEPTION WHEN PLM REFERENCE ATTRIBUTE IS NULL

Root Cause: After deploying HF9312.6, the DB column PLM_REFERENCE becomes CLOB type. When a PLM reference field has no value the DB column returns a "" instead of null. The "" value was incorrectly handled in DocumentToProjectTypeVOConverter.setValue()->ProjectWSUtil.getProjectListTypeVO(subClsId,attrId,tableId,(String)getData).

Resolution: According to the code history, this issue was already fixed by 934.

Verification:

  1. Load Project for General Info tab through WS.

  2. The Content tab PLM ref attr values were added, deleted.

    Result: No exceptions are thrown when PLM Reference attribute is null.

17353348

Application Server

Issue: LOAD PROJECT WEB SERVICE THROWS EXCEPTION WHEN PLM REFERENCE ATTRIBUTE IS NULL

Root Cause: Disabled the Item.Title Block.Part Family Attribute; while trying to update the Part's description to Part Family, but cannot find the column info.

Resolution: Do not throw an error for this case.

Verification:

  1. Create a Part, and set a value for Item.Title Block.Part Family.

  2. Go to Java Client, disable the Item.TitleBlock.Part Family.

  3. Create an ECO on the Part.

  4. Release this ECO.

17367474

Web Client

Issue: JAVA.IO.NOTSERIALIZABLEEXCEPTION: COM.AGILE.UI.PCM.COMMON.TREEGRID.RENDERER

Root Cause: Class IndicatorImageRender does not implement the Serializable interface.

Resolution: Implement the Serializable interface and transition the fields.

Verification:

  1. Log in to Web Client as admin.

  2. Create a Part, Part003, and add two BOMs and Mfrs to Part003.

  3. Create a Change, ECO001, against Part003, redline modify an existing BOM, redline delete an existing BOM, redline add a new BOM, redline modify an existing Manufacturer Part, redline delete an existing Manufacturer Part, and redline add a new Manufacturer Part

  4. Change ECO001's status to Released.

  5. Open server log to check the information

    Results: There is no similar error message:"<Error> <Cluster> <BEA-000126> <All session objects should be serializable to replicate. Check the objects in your session. Failed to replicate non-serializable object."

  6. Do some sanity checks for function.

    Results: There is no similar error message.

17399629

Averify Issue

Issue: AVERIFY ERROR REPORTED INCORRECTLY ON USER_GROUP TABLE

Root Cause: AGIL-00025047 and AGIL-00025048 don't cover functional Team class since this class is introduced in 932.

Resolution: Need to modify AGIL-00025047 and AGIL-00025048 in order to cover functional team class.

Verification:

  1. Enable the Functional Teams class on the server, create a Functional Team.

  2. Run Averify on the database, and check the oracle_averify_report.log

    Result: There is no bad data. The AGIL-00025047 and AGIL-00025048 error on USER_GROUP table are not reported.

17451736

Dataload

Issue: DATA LOAD 932: DATABASE ERROR(ORA-01000: MAXIMUM OPEN CURSORS EXCEEDED), WHEN LOADING RECORDS

Root Cause: Connection, result have not been closed.

Resolution: Fixed code.

Verification:

  1. Prepare more then 1000 records in SOURCE_Rev table and set the CHANGE_NUMBER of those records that do not exist in the database.

  2. Start Dataload.

  3. Load the SOURCE_Rev table.

    Result: In the command console window, there are no ORA-01000: maximum open cursors exceeded errors. Those incorrect records are not loaded into the target DB. Those incorrect records are logged into the ERROR_Rev table in the source DB.

17479592

Web Client

Issue: INFORMATION IN THE IMPORT WIZARD DOES NOT SHOW XLSX AS A SUPPORTED FILE TYPE

Root Cause: The xlsx file type is supported in 932, but is not listed.

Resolution: Change the menu item to "xls / xlsx".

Verification:

  1. Log in to Web Client as admin.

  2. Go to Tools and Settings > Import.

  3. Check the information in the import wizard.

    Result: It says:"Select a file to import. The following file types are supported; Excel(xls/xlsx), Text (txt / csv), Product Data Exchange (pdx) and Agile XML(axml)."

17511851

Searches

Issue: THE PARAMETRIC SEARCH AND ADVANCED SEARCH DO NOT GIVE THE SAME RESULTS

Root Cause: Archived Project cannot be found through search due to some special handling.

Resolution: Comment out the special code which blocks the search of archived projects.

Verification:

  1. Log in to Java Client as admin.

  2. Click Admin tab.

  3. Expand Data Settings.

  4. Double click Classes.

  5. Under Projects > Activities double-click Project.

  6. Click the User Interface Tabs.

  7. Double-click the General Info tab.

  8. Click Attributes > General Info tab.

  9. Sort by Name.

  10. Double-click Archived

  11. Set Visible to: Yes.

  12. Set Enable for Search Criteria to: Yes.

  13. Click Save.

  14. Log in to Web Client.

  15. Click Create New button > Projects > New Type: Project Fill in the required fields and note the Name you created, example:TestProject.

  16. Click Save.

  17. Click Actions > Archive.

  18. In Quick Search type: TestProject. Project TestProject is returned.

  19. Open an Advanced Search.

  20. Object Type: Activities Search Type: Object Search, Search Condition: Field: Match: Value: And/Or General Info.Name Starts With TestProject. Click Search. Returns Modify Advanced Search to include: Search Condition: Field: Match: Value: And/Or General Info.Name TestProject. Click Run. Returns project: TestProject.

    Result: Based on the criteria given, the parametric search and Advanced Search give the same results.

17585883

Averify Issues

Issue: CHARACTER 1333 ARE ACTUALLY ALLOWED THOUGH 4000 IS SHOWN

Root Cause: The maximum string length of Comments in the client side does not match the size defined in the server side.

Resolution: Use charset UTF-8 to calculate the string length to ensure that the client side matches the server side.

Verification:

  1. Log in to Web Client.

  2. Create a Program.

  3. Change the status to In Process.

  4. In the Change Status window, there is a Comments text field. The number, 4000, is displayed on the side of the text box, which means it allows an entry of 4000 characters.

  5. Validate the actual number of characters allowed.

    Result: 4000 characters are allowed.

17615028

Averify Issues

Issue: ROOT CAUSE FIX FOR AGIL-00025024 PROPERTYTABLE: TABLE HAS BAD DATA AT ID

Root Cause: When removing criteria from the field Matching Criteria in the Workflow.GI tab, the properties of the criteria are not removed.

Resolution: Remove the properties when removing the criteria.

Verification:

  1. On Agile 934 environment, log in to Java Client.

  2. Go to Admin > Workflow Settings > Workflows, open a workflow, add/remove criteria of Matching Criteria field in the GI tab.

  3. Run Averify 1.7.6 on the database.

  4. Check the Averify report.

    Result: There is no AGIL-00025024 error in the Averify report.

17617046

Admin Config Propgation

Issue: ACP FAILS TO PROPAGATE ACS EVENTS TIED TO A WORKFLOW WITH A "."

Root Cause: ACP cannot resolve workflow status from the qualified status, when the workflow name has more than one dot.

Resolution: Resolve status from the qualified status via workflow name.

Verification:

  1. Log in to Java Client as admin.

  2. Go to Admin > Settings > Workflow Settings > Workflow.

  3. Create a workflow with a name that contains ".", for example, "acp.test".

  4. Add Pending, submit status to the workflow.

  5. Go to System Settings >Agile Content Service > Events.

  6. Create an event tied to the workflow from Step 3.

  7. Go to ACP and configure as follows:

    <copy>

    <acs_event/>

    </copy>

  8. Do an ACP export: acp export golden.

  9. Go to Java Client, delete the event created in step 6.

  10. Do an ACP import: acp import golden dev.

    Result: The user can import the ACS Event successfully. No error message is displayed.

17623245

Process Extension

Issue: UNABLE TO SCROLL THROUGH THE EXTENDED TOOLS MENU EVENT TYPE PXS

Root Cause: If a user sets a lot of Process Extensions (>30) on the Tools menu, there is no down scroll arrow at the bottom of the list in Web Client.

Resolution: Follow the Action menu. If the browser does not have enough height to display all the PX settings on the Tools menu, show the down scroll arrow at the bottom of the list.

Verification:

  1. In Java Client, create a lot of Extended Tools Menu type of Event PXs (over 30).

  2. In Web Client, open the Tools Menu to check the PXs.

    Result: There is a down scroll arrow at the bottom of the list to show PXs.

17772280

Agile Content Services

Issue: EVENT GROOVYSCRIPT ERROR ON ATO COMPLETE STATUS

Root Cause: The Process Extension's user context in thread local variable is a stack object, but it is treated and cast to object com.agile.pc.cmserver.base.UserContext in method com.agile.admin.security.weblogic.WeblogicPrincipalExtractor#extractPrincipal().

Resolution: Return the object com.agile.pc.cmserver.base.UserContext when retrieving PX user context for method com.agile.pc.cmserver.util.CMLibrary#ifContainsIpx Session().

Verification:

  1. Create Event Handler Script.

  2. Copy and paste text from the groovyscript file and save the Event Handler.

  3. Create anEvent on Default ATO Workflow From Any status to Complete.

  4. Create Event Subscriber that uses new Event and Event Handler that is Post, Synchronous.

  5. Create ACS File destination for ACS.

  6. Create ACS Event when ECO releases using Default Change Order workflow.

  7. Create ACS Subscriber that uses Event.

  8. Add Subscriber Detail that sends AXML file to destination with roles, language, and filters.

  9. Enable Subscriber.

  10. Create the ECO using the default Change Order.

  11. Add a new Part.

  12. Set New Rev, LCP, and Effective Date.

  13. Move the ECO to Released status.

    Results: ATO is created.

    ATO is moved to Complete.

  14. Check ATO history and check Event Handler Monitor.

    Result: The Event is triggered and it shows [ATO Event Handler Called] in ATO history table and Event Monitor.

17843286

Averify Issues

Issue: LOST FILE ATTACHMENTS AFTER INPLACE LOAD SUCCEEDS

Root Cause: N/A

Resolution: N/A

Verification:

  1. Open the following cases in Averify:

    Averify\scripts\testcases\AGIL-00025151.sql

    Averify\scripts\testcases\AGIL-00025153.sql

  2. Check the output error message in AGIL-00025151.sql and AGIL-00025153.sql.

    Result: In step 2, the output error messages are changed to following:Please log an SR with Support ASAP to resolve the issue and avoid risk of system down time.

    Note: The fix for this bug is only the change in the output message from Averify.

17939605

Searches

Issue: INACTIVE LIST VALUES NOT REFLECTED IN SEARCH

Root Cause: This function is not supported since 9311 CS04. This feature is only for Search.

Resolution: Code was fixed by CS04.

Verification:

  1. Log in to Java Client as admin.

  2. Click View/Edit current user button, and ensure that the preference "Include Inactive List Values In Search" is set to Yes.

  3. Create a cascade list, cas1, with the following structure:

    ---cas1A

    -----cas1A-1

    -----cas1A-2

    ---cas1B

    -----cas1B-1

    -----cas1B-2, and assign list cas1 to parts.P2.list01

  4. Create a Part, P001, and select cas1A-1 for P001.p2.list01.

  5. Open list cas1, set its value cas1A-1 as inactive.

  6. Log into web client as admin

  7. Do an Advanced Search: Items > Parts >Page Two.list01 > In > Check values can be selected.

    Result: All list values that contain cas1A-1(Inactive) are listed.

  8. Set search criteria as Items > Parts >Page Two.list01 > In > cas1A-1(Inactive), run the search.

    Result: P001 is returned as a result.

17962276

Searches

Issue: ADVANCED SEARCH RELATIONSHIP OBJECT DOES NOT SHOW RESULT

Root Cause: A join condition is missing.

Resolution: Added the join condition.

Verification:

  1. Log in to Web Client.

  2. Do an Advanced Search for Changes >L1 Qualification >Relationships Search > Manufacturer Part with the following criteria: Relationships.Manufacturer Part.General Info.Manufacturer Part Number Is Not Null.

  3. Click the Search button.

    Result: Search results are returned in a short time.

18029417

Averify Issues

Issue: LISTENTRY TABLE HAS BAD DATA (CASCADE LIST ITEM)

Root Cause: 'Country' list (list ID is 365) is special.

Resolution: Change the test case in latest 9.3.4 to handle it differently to avoid the error.

Verification:

  1. Create a new listentry on Country List in Java Client.

  2. Run Averify 1.7.6 on the database.

  3. Check oracle_averify_report.log.

    Result: The AGIL-00025085 error does not occur.

18045203

Web Client

Issue: ERROR SAID JRE6 REQUIRED FOR JAVA CLIENT ON 9.3.2 BUT JRE 7 IS THE CORRECT VERSION

Root Cause: If JRE is not installed, in start.html page it requests the user to install JRE 6.x, but per the Platform Matrix or Capacity Planning Guide, in 9.3.2.0 JRE 7 is supported and in 9.3.4 it supports JRE 8.

Resolution: Change the warning messages.

Verification:

  1. Try to launch 9.3.4 Java Client on a server without installing JRE.

    Result: The following error message appears: The Agile 9 Java Client requires that you install Java 2 Platform, Standard Edition, JRE 8.x. You do not need to install NetBeans IDE, the J2SE SDK or Itanium. Please click on the icon below to go to the download location for the required software. Download Now Once you have installed Java 2 Platform, Standard Edition, JRE 8.x, you may return to the previous page to install and run the Agile 9 Java Client.

18106873

Internationalization

Issue: TRANSLATION OF JAPANESE ERROR MESSAGE IS INCORRECT

Root Cause: Incorrect Japanese translation.

Resolution: Retranslate the message.

Verification:

Precondition: Set the package name and package.p2.text01 with AlphaNumeric Upper Case setting

  1. Log in to Web Client as Japanese user.

  2. Create New > Packages.

  3. For Package Name enter a character other then an alphanumeric upper case character and save.

    Result: Only "Alpha Upper Case" values are allowed for Package Number. The translation is done correctly.

18115507

Searches

Issue: IN ADVANCED SEARCH WHEN INCLUDING P3 FLEX ATTRIBUTE

Root Cause: For a flexible attribute, it gets the column name from table 'AGILE_FLEX', which is different from common attributes.

Resolution: Added a way to handle flexible attribute for multilist.

Verification:

  1. Log in to Java Client as admin.

  2. Open subclass Problem Report, make Page Three visible, add a Multilist named Site using pre-defined list Sites, and make Site visible and searchable.

  3. Assign Admin with appropriate privileges to read and modify attribute Site.

  4. Log in to Web Client as Admin.

  5. Create an Advanced Search as follows:

    Product Service Requests Problem Report Object Search

    [ Workflow.Workflow Status Equal To

    efault Problem Reports.Review And

    Workflow.Approver Action Contains

    Awaiting Approval ] And

    Page Three.Site Contains Any

    India

    Note: The first two conditions are grouped with "[]".

  6. Click Search.

    Result: There is no error and the user gets the correct results.

18142993

Administration/Configuration

Issue: CAN NOT SAVE THE VALUE AT FAILOVER LINK IN LDAP CONFIG

Root Cause: The wrong class type is used.

Resolution: Use the correct class type.

Verification:

  1. Add an LDAP configuration which points to a working LDAP server, say its ID is Agile001.

  2. Modify Agile001's Failover Links to Agile002, which does not exist.

  3. Save Agile001 and check.

    Result: A message dialog popup is displayed with the following message: LDAP Agile002 is diabled or not found.

  4. Modify Agile001's Failover Links to Agile003, which does exist.

  5. Save Agile001 and check.

    Result: It is saved without any errors.

18173383

Admin Config Propogation

Issue: FAILED TO MIGRATE EVENTS VIA ACP

Root Cause: Unable to resolve source object properties when referenced objects are newly created on the source system.

Resolution: Fixed this issue in ACP to import Events properly.

Verification:

  1. Log in to the Java Client as admin.

  2. Create a new Workflow.

  3. Create a new Event. (refer to step11 for event type).

  4. Create a new Event handler.

  5. Create a new Event Subscriber to bindworkflow, event and event handler.

  6. In ACP, configure the following:

    <copy>

    <em_event/>

    <em_event_handler/>

    <em_event_subscriber/>

    <workflow/>

    </copy>

  7. Using ACP, export all the above newly createdobjects.

  8. Delete all of the newly created objects in the Java Client.

  9. Using ACP, import all the above deletedobjects.

  10. Verify the objects in Java Client.

  11. Repeat 2~9 to test different event types (9 total) as follows:

    1. Approval for Workflow

    2. Audit for Workflow

    3. Change Approvers or Observers for Workflow

    4. Change Status for Workflow

    5. Comment for Workflow

    6. Escalation for Workflow

    7. Promotion Failure for Workflow

    8. Reject for Workflow

    9. Reminder for Workflow

    Result:

    10. Import Workflow Event is successful. There is no error message in the console or log files (import.err, import.log)11. Import Workflow Event is successful. There is no error message in the console or the log files (import.err, import.log) for each kind of event type.

18185312

SDK Import & Export

Issue: SDK IS READING DATA FROM A DISABLED TABLE

Root Cause: We do not do the necessary validation for the privilege.

Resolution: Added the privilege validation.

Verification:

  1. In Java Client, enable the Visible attribute in Page Two and disable the Visible attribute in Page Three.

  2. Use SDK code:

    1. Create a new Item.

    2. Get Page Two table and use table.isVisible(); to see if it is visible.

    3. Get Page Three table and use table.isVisible(); to see if it is visible.

    Result: When the Visible attribute is enabled, then table.isVisible(); returns true, Otherwise, it is false. So, step 2 > true, step 3 > false.

18189354

Web Client

Issue: NO APPROPRIATE MESSAGE IN AGILE PLM WEB CLIENT AFTER PASSWORD EXPIRY

Root Cause: We do not do the necessary validation for the privilege.

Resolution: Added the privilege validation.

Verification:

  1. Log in to Java Client as admin.

  2. Go to Admin > User Settings > Account Policy, set password expiry to 1 day.

  3. Create a new user, u001, with the same Time Zone as the server.

  4. Set the server time to the next day.

  5. Log in to Web/Java Client as u001.

    Result: The following message displays: ”Your login password has expired. Please provide a new password should be prompted in both Web and Java Client.”

18252904

Administration/Configuration

Issue: USER INTERFACE THROWS -1 ERROR WHEN OPENING PRICES TAB ON MANUFACTURER PART TAB

Root Cause: This is an IndexOutOfBounds issue. When the column information of the Manufacturer Price table does not contain the attribute ”effectivity date,” we should not set value for it.

Resolution: Check whether the Manufacturer Price table contains the attribute ”effectivity date” before setting a value for it.

Verification:

  1. .Log in to Web Client.

  2. Search for any Manufacturer Part and go to the Prices tab.

    Result: It displays the list of Prices which are associated with the Manufacturer Part.

18449626

Averify Issues

Issue: AVERIFY MISSING RECORD IN ADMINMSATT NOT DETECTED

Root Cause: N/A

Resolution: Checked in New Averify Case AGIL-00025154.sql

Verification:

  1. Create a 934 schema and link to the application server.

  2. Log in to Java Client as admin. Create a privilege with criteria named Test_Privilege_00, and create a workflow with Matching Criteria named Test_WF_00.

  3. Get the new privilege's ID from table nodetable, get the new workflow's ID from table nodetable.

  4. Delete reference data in ADMINMSATT table with "delete from adminmsatt where parentid=(got from 3)". and get the matching criteria data in ADMINMSATT table. The id is stored in NODETABLE table with hierarchical structure. The user can get it by "select id from nodetable where parentid in(select id from nodetable where parentid in (got from 3) and description='Matching Criteria')").Delete reference data in ADMINMSATT table with "delete from adminmsatt where parentid=(got from 4)".

  5. Relaunch the application server and Java Client, find the detail info for Test_Privilege_00 and check workflows.

  6. Run Averify176 to check this schema with a specific testcase.

    Result: Averify reports AGIL-00025154 Error Missing adminmsatt data reference at nodetable id.

18454845

DB Upgrade/AUT

Issue: QUANTITY & FINDNUM OF SUB CLASS DESIGNS SCALE VAL CHANGED 2 TO 0 in 9.3.3, CANNOT MODIFY SCALE VALUE OF QUANTITY AND FINDNUM IN STRUCTURE TAB

Root Cause: 933 is rounding Quantity and FindNum value to integer value

Resolution: Accept a scale of 2 for Quantity and FindNum value.

Verification:

  1. Log in to Java Client.

  2. Navigate to Admin > Data Settings > Classes > Designs > Structure tab.

  3. Verify the default scale value for Quantity and Find Num.

    Result: The default value of scale should be 2 for Quantity and Find Num.

18454896

DB Upgrade/AUT

Issue: AUT CREATES NEW VISIBLE ATTRIBUTES WHICH ARE NOT MANDATORY

Root Cause: There is a less rigourous upgrade script

Resolution: Set the introduced attributes to appropriate states.

Verification:

  1. On AUT 1.7.6, set dest.version = 9.3.4 in aut.properties.

  2. Run AUT to upgrade the database from 9311 to 934.

  3. Start up 934 Agile server, log in to Java Client, check if the default setting of the following attributes/tabs are same as follows:

    Specifications.General Info.Rollup Engine - Visible

    Items.Compliance.Specification.Rollup Engine - Invisible

    Part Groups.Compliance.Specification.Rollup Engine - Invisible

    Declaration.Specification.Rollup Engine - Invisible

    Manufacturerparts.Compliance.Specification.Rollup Engine - Invisible

    Gates.General Info.Enable Stationary Gate - Invisible

    Activities.Schedule.Schedule Status - Invisible

    Activities.Schedule.Functional Team(s) - Invisible

    Items.Where Used.Functional Team(s) - Invisible

    Manufacturer parts.Where Used.Functional Team(s) - Invisible

    Reference object Class - Disabled

    User Groups.Discussion Tab - Visible

    User Groups.News Tab - Visible

    Discussion.Replies Tab - Visible

    Activites.General Info.MSP Import Date - Invisible

    Gates.General Info.MSP Import Date - Invisible

    Result: The Default setting of those attributes/tabs are displayed as expected.

18459315

Administration/Configuration

Issue: VALUES OF MULTILIST ATTRIBUTE MISSING IN RELATIONSHIP SEARCHES

Root Cause: When process related object attribute, it uses subclass of main object, but it should use related object class/subclass id.

Resolution: Correct to related object class/subclass id.

Verification:

  1. Go to the Admin client as admin

  2. Enable Page3.multilist01 on Document subclass and add list Users

  3. Enable Page3.multilist01 on Part subclass and add list User Group

  4. Go to the Web client as admin

  5. Create a new Document and select some values from list Users in Page3.multilist01

  6. Create a new Part and select some values from list User Groups in Page3.multilist01

  7. On the new Document create a relationship to the new Part

  8. Run a relation ship search between Document and Part and attribute Relationships.Part.Page3.Multilist01 in the output

    Result: Search result appears correctly.

18475427

DB Upgrade/AUT

Issue: DISCUSSIONS CLASS REPLIES TAB VISIBILITY HAS BEEN CHANGED TO YES DURING THE UPGRADE

Root Cause: CCB 12

Resolution: CCB 12

Verification:

  1. Upgrade the database from 9311 (9312 prior) to 934.

  2. Log in to Java Client, check the Discussions.Replies tab.

    Result: The replies tab is enabled.

18477516

DB Upgrade/AUT

Issue: PARTS.TITLE BLOCK.BASE MODEL -> ATTRIBUTE PEROPERTY

Root Cause: Max System Length is less than Max length.

Resolution: Make Max System Length equal to the Max Length with Bug 16595640.sql. Affected Area: Can save successfully.

Verification:

  1. Stop the 933 server.

  2. Run the following scripts to the database schema to which the 933 server is connected:

    create table propertytable_18477516 as select * from propertytable where parentid = 2000009494 and propertyid = 3;

    update propertytable set value = '100' where parentid = 2000009494 and propertyid = 3;

    commit;

  3. Start the 933 server.

  4. Log in to Java Client.

  5. Open Classes > Parts > Title Block.Base Model, check the values for MaxLength & Max System Length.

    Result: Both are 100.

18665484

DB Upgrade/AUT

Issue: AUT ISSUE: INSERT STATEMENT FAILURES WHILE UPGRADING FROM AGILE 9.3.1.1 TO AGILE 9.3.2

Root Cause: The Insert statement does not cover null value.

Resolution: A sanity check was added before the insert script.

Verification:

  1. Create a 9311 schema.

  2. Delete rows in the database as in customer-offered log. For example:

    delete from nodetable where parentid = 13098 anddescription like 'Example - Read All Projects, Programs, Phases, Tasks and Gates';

  3. Upgrade the schema from 9311 to 933 using AUT176.

    Result: There is no insert error in the AUT.log.

  4. Create a 9311 schema.

  5. Delete rows in the database as in customer-offered log. For example:

    delete from nodetable where parentid = 13098 and

    description like 'Example - Read All Projects, Programs, Phases, Tasks and Gates';

  6. Upgrade the schema from 9311 to 934 using AUT176.

    Result: There is an insert error in the AUT.log

18727866

Database Install

Issue: ORA-00959: TABLESPACE 'AGILE_DATA5' DOES NOT EXIST

Root Cause: The agile9_check.sql file does not check tablespace AGILE_DATA5.

Resolution: Added check logic in agile9_check.sql to verify that the following tablespaces that we require are present in the database:AGILE_DATA1AGILE_INDX1AGILE_DATA2AGILE_INDX2AGILE_DATA3AGILE_INDX3AGILE_DATA4AGILE_INDX4AGILE_DATA5AGILE_INDX5

Verification:

  1. On a 9.3.4 Agile database, run agile9_check.sql on agile user.

  2. Log in to sqlplus as dba,alter tablespace AGILE_DATA5 rename to TestData5, then run agile9_check.sql; Or run agile9_check.sql on an Agile 9.3.1 database (before 9.3.2).

    Result: There is no error in agile9_check.log

    Result: It shows error message as follows: ERROR: Missing tablespace AGILE_DATA5.

18740708

DB Upgrade/AUT

Issue: AUT1753 REPORTS ERROR ORA-01722: INVALID NUMBER

Root Cause: A more rigorous script is needed.

Resolution: Fixed script.

Verification:

  1. Import 9224 Clarion database and upgrade to 934 by AUT 1.7.6.

  2. Check if there are any ORA-01722 errors in the AUT.log.

    Result: There are no ORA-01722 errors in the AUT.log.

  3. Check the script in 932/933/934 upgrade path.

    Result: The following updated script is updated in the 932/933/934 upgrade paths.update relationship set criteriamet=1 where criteriamet <> 1 and subscription <> -1 and subscription in ( select id from subscriptions where trigger_event_ids='976' and id in ( select subscription from relationship where ctr_objtype in (9000, 10000) and eff_objtype in (18022, 18387) and ctr_objid in (select id from item where latest_released_eco=0) ));

18897952

DB Upgrade/AUT

Issue: ERRORS REPORT IN LOG OF AUT 1753

Root Cause: The script does not cover all situations.

Resolution: Make the fields transient.

Verification:

  1. create a 9311 schema

  2. Delete rows in the database as in the customer-offered log. For example:

    delete from nodetable where parentid = 13098 and description like 'Example - Read All Projects, Programs, Phases, Tasks and Gates';

  3. Upgrade schema from 9311 to 933 using AUT176.

    Result: There is no insert error in the AUT.log.

  4. Create a 9311 schema.

  5. Delete rows in the database as in the customer-offered log. For example: delete from nodetable where parentid = 13098 and description like 'Example - Read All Projects, Programs, Phases, Tasks and Gates';Upgrade the schema from 9311 to 934 using AUT176.

  6. Check if there are error messages in the server log.

    Result: There is no insert error in AUT.log.

19010420

Web Client

Issue: WEB CLIENT COLUMN MISSING AFTER ADJUSTING COLUMN WIDTH

Root Cause: If the user resizes the width of a column to be smaller (like 4px or 5px around), they are not able to resize the width to be larger again.

Resolution: For the columns whose width < 10, show it with width 10px. All the columns of all of the tables must have MinWidth 10px.

Verification:

  1. Log in to Web Client.

  2. Go to Home page > Workflow Routings tab.

  3. Adjust the Column Width of Workflow to make it small (less than 4px).

    Result: It shows the column width with 10px.

19060795

Administration/Configuration

Issue: [JP TRANSLATION] SOME SMARTRULES ARE NOT TRANSLATED

Root Cause: The translation team did not know what the words exactly mean, like word ChangeStatusNoResponseFromAcknowledger.

Resolution: Explain what the words mean and translate them, for example, ChangeStatusNoResponseFromAcknowledger means Change Status No Response From Acknowledger.

Verification:

  1. Log in to Java Client as a Japanese user.

  2. Go to Admin tab > System Settings > SmartRules.

  3. Check how the following SmartRules are displayed:

    ChangeStatusNoResponseFromAcknowledger

    ChangeStatusNoReponseFromApprover

    DeleteInstanceWithBOM

    DemotionReviewersRemoval

    RedlineAttributes

    Result: All the values are translated into Japanese.

19141123

Web Client

Issue: INTERNET EXPLORER 11 SUPPORT/ CERTIFICATION FOR AGILE 9.3.3

Root Cause: No support for IE11 Native mode in 933.

Resolution: There was no code change since 934 already supports the native (standard) mode of IE 10 & 11.

Verification:

  1. Log in to the 934 server with IE10 or IE11 as admin.

  2. Do some UI Testing of an object.

  3. Check that the object displays everything correctly like icons, fields, columns, and rows.

    Result: Everything displays correctly.

19167986

Internationalization

Issue: [JP TRANSLATION] FROM/TO ARE WRONG TRANSLATION TO JAPANESE IN TRANSFER AUTHORITY

Root Cause: There is a translatability issue misleading vendor for translation.

Resolution: Add a comment for the related string to resolve translatability issue.

Verification:

  1. Log in to Java Client with a Japanese session.

  2. Menu bar: Settings->Transfer Authority.

  3. Click New.

  4. Users: From/To translation.

    Result: It is translated correctly.

19191459

Web Client

Issue: FAILED TO RUN USER HISTORY REPORT

Root Cause: There is an issue in an early version of JDK7.

Resolution: Use the user's preferred locale/language to retrieve the localized time zone id.

Verification:

  1. Set the default locale of the Agile server JVM aszh_TW, by:

    a. specifying the user.country and user.language system properties in the start script (startAgile.cmd) -Duser.country=TW -Duser.language=zh OR

    b. changing the system's locale/language of the Agile server to zh_TW if it has an Asian support package installed.

  2. Select the Taipei time zone for the tested user.

  3. Select English as the preferred language for the tested user.

  4. Run the User Usage Report.

    Result: Get the correct report.

19208450

Software Development Kit

Issue: COM.AGILE.UTIL.EXCEPTION.CMAPPEXCEPTION: ATTRIBUTE ”PAGE TWO.XXX” NOT FOUND

Root Cause: The data in the cache is different than what is in the database.

Resolution: Change some data in the query result.

Verification:

  1. Connect to Agile.

  2. Configure a Java Program in Eclipse.

    This program should query Parts and find those Parts which have a Page Two field called Compliance Flag set to Yes.

  3. Create such a Page Two in the generic system and also create 2 Parts with the value of this attribute set to Yes.

  4. Execute the Java Program in Step 2.

    >>>

    IQuery query = (IQuery)session.createObject(IQuery.OBJECT_TYPE, ItemConstants.CLASS_PART);

    String criteria = "[Page Two.Compliance flag] == 'yes'";

    query.setCriteria(criteria);

    Iterator it = query.execute().iterator();

    while(it.hasNext()) {

    IRow row = (IRow)it.next();

    IDataObject

    iu=(IDataObject)row.getReferent();

    System.out.println(iu.toString());

    }

    Result: The system queries out the Parts with Compliance Flag = Yes. The Parts created in Step 4 are displayed in the query result.

19271520

Export

Issue: EXPORT OF WHERE USED ONE LEVEL LATEST RELEASED REV IS BLANK

Root Cause: Functional code is skipped and we do not add the row value in rowlist.

Resolution: Add the row value in the correct way.

Verification:

  1. Log in to Java Client as admin.

  2. Go to Admin > Server Settings > Preferences > Maximum Database Records to Process for Searches, set 0 for this preference.

  3. Log in to Web Client as admin.

  4. Do an Advanced Search:Items > Parts > Where Used One Level Latest Released Revisions > Title Block.Number > Does not Contain > P00002, run the search.

    Result: All parts that meet the criteria are returned.

  5. Export the search result to CSV or XLS file, then open the file to check the search result.

    Result: All parts that meet the search criteria are displayed in the file.

19346839

Averify Issues

Issue: NEED A CLEANUP SCRIPT TO REMOVE 3 BAD RECORDS

Root Cause: The REV table has bad data (find duplicate site $site_id in table rev for item $item_id in change.)

Resolution: AGIL-00075102.sql is added.

Verification:

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

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

  3. Insert bad data with the following SQL statement: insert into rev(id, item, change, site) values($ID,$item_id,$change_id, $site_id); make $site_id is duplicated with the one existing in the Part.

  4. Run Averify against the database.

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

19442156

Export

Issue: WHEN EXPORTING AN ITEM WITH CHANGES TO PDX RELEASED DATE OF THE CHANGE IS INCORRECT

Root Cause: The error java.text.ParseException: Unparseable date: "2014-06-25T12:42:39Z" is thrown in the console when the exported Item has released a Change.

Resolution: Removed the error output from the code.

Verification:

  1. Log in to Web Client.

  2. Create an Item, P0001.

  3. Create a Change, C0001, against the Item.

  4. Release the Change with Revision A.

  5. Open the Item, P0001, click Actions > Export to export it to PDX.

    Result: The Item is exported to the PDX file with the correct Rev Release Date without any error message in the server log.

3.7 Autovue for PLM

11854880

2D Pro Integration

Issue: AGILE 9.3.0.1 - AUTOVUE - LANGUAGE SETTING MIXED ENGLISH AND DANISH

Root Cause: Original Agile implementation does not include multi-languages due to lack of support in Autovue's early releases.

Resolution: Add this support to Agile user's locale for the Autovue viewer applet.

Verification:

  1. Navigate to the user's Format Preferences, update Language: to Japanese/German and Save. Log out and Log in again.

  2. Access a BO with files.

  3. View a file.

  4. From the Viewer window select view source.

  5. Verify that the PARAM NAME="LOCALE" VALUE

    Result: PARAM NAME="LOCALE" VALUE is updated with the respective language.

    document.write('<PARAM NAME="LOCALE" VALUE="ja">');document.write('<PARAM NAME="LOCALE" VALUE="de">');

17548020

2D Pro Integration

Issue: WATERMARK AND BANNER TIMEZONE IN AUTOVUE IS DIFFERENT FROM WEB CLIENT

Root Cause: Date and time is not converted to the user defined timezone.

Resolution: Changed code to convert the watermark/banner time to the user date format/timezone.

Verification:

Preconditions:

  1. Navigate to Admin > System Settings >Viewers & Files >WaterMark.

  2. Open Change Orders Banner & Watermark, set Print Watermark to Yes and Save.

  3. Open Change Orders Banner & Watermark from Banners, set Bottom Right Banner to Cover Page.Date Released Bottom Right Banner Text ECO Released Top Left Banner Cover Page Number.

  4. Set user's Time Zone Preference to CST.

Steps:

  1. Log in to Web Client.

  2. Create a Change Order, add Attachments.

  3. Release the Change Order.

  4. Select File to view.

  5. Select Print, validate Time Zone displayed in Viewer WaterMark/Banner for Cover Page.Date Released.

    Result: Displays timezone in CST for Cover Page Date Released attribute.

3.8 Agile Engineering Collaboration

16842140

EC Services

Issue: SLOW PREFORMANCE ON AGILE-PRO\/E CONNECTOR

Root Cause: In 9.3.3 and earlier, EC Services used an API that triggered too many method calls and SQL queries.

Resolution: Since 9.3.4, bulk APIs have been used or newly introduced, which speed up server side processing.

Verification: The Save/SaveAs performance has been increased by 40% in 934 when compared to 933. There was some amount of performance improvement reported in the load use case, as well.

16955932

EC Services

Issue: MCAD/AGILE EC PERFORMANCE ISSUES AND MONITORING TOOLS

Root Cause: In 9.3.3 and earlier, EC Services used an API that triggered too many method calls and SQL queries

Resolution: Since 9.3.4, bulk APIs have been used or newly introduced, which speed up server side processing.

Verification: The Save/SaveAs performance has been increased by 40% in 934 when compared to 933. There was some amount of performance improvement reported in the load use case, as well.

19365496

EC Services

Issue: PUBLISHING TO A RELEASED ITEM GIVES A SUCCESS MESSAGE, WHEN IT SHOULD NOT

Root Cause: The error that a Design is published to a previously released Item without a new pending Change was only reported as a warning to the client, which is ignored and not reported to the user.

Resolution: Changed the warning message to an error message when trying to publish to a previously released Item without a pending change

Verification:

  1. In Agile Web Client, create an Item, P001.

  2. Create a Change, C001, against P001 and release C001.

  3. Launch the CAD system and create a testing model Part1.SLDPRT and save to local.

  4. Click Agile > Save preview.

  5. In Agile Save preview, highlight the component and double-click.

  6. In the Details tab, type P001 in the Item Number field and click the Search button. P001 is returned as a result.

  7. Click the 123 button near Design Number, a new design number will be generated.

  8. Click the Save button in the Details table.

  9. Click the Continue button to save it to Agile.

    Result: There is an error in save result - Not Published, Change is already released.

  10. Log in to Agile Web Client and check the Design and Item object.

    Result: In Agile Web Client, the Design's files should not be published to the Item Attachment table.