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

Previous
Previous
 
Next
Next
 

2 Issues Resolved by Hot Fix Releases

Hot fixes included in this product release are:

2.1 PLM Release 9.3.1.0

This section includes Hot Fixes included in Agile PLM 9.3.1.0.

2.1.1 9310_146

Bug ID 19870258: UNABLE TO IMPORT ITEM SUPPLIER DATA WITHOUT SITES LICENSE ENABLED

Root Cause: Import side uses supplier id:::site id as unique id to identify one supplier row. If site license is disabled, the unique id will be supplier id:::, and import side will always execute the add operation. For some supplier rows, import side should do an update operation.

Resolution: If the site license is disabled, change site id to common site id.

2.2 PLM Release 9.3.1.1

This section includes Hot Fixes included in Agile PLM 9.3.1.1.

2.2.1 9310_319

Bug ID 20174988: ATO FAILING TO COMPLETE

Root Cause: Item does not have privilege check.

Resolution: Add code to check privilege.

2.2.2 9311_322

Bug ID 20635300: NOTIFY AT APPROVAL OF ROUTING SLIP ON FILE FOLDERS

Root Cause: There is no OOTB notification template defined for FileFolders approval.

Resolution: Added notification templates for file folder & design object per PM's requirement.

2.2.3 9311_324

Bug ID 21559688: CREATE CHANGE WORKFLOW CRITERIA USING AN ITEM PAGE2 DYN. LIST $USERGROUP FAILS

Root Cause: $USERGROUP is not handled specially for admin criteria.

Resolution: Specially handle for $USERGROUP.

2.3 PLM Release 9.3.1.2

This section includes Hot Fixes included in Agile PLM 9.3.1.2.

2.3.1 9312_297

Bug ID 19544784: COMPLIANCE CALCULATION IS INCORRECT

Root Cause: The different order of adding spec to declaration have different order of composition id when already a mfn part is added, so it leads to random picking up of compositions.

Resolution: Changed the code to sort the composition by the spec name (ASCII order). The user can modify the spec name that they want to reuse.

2.3.2 9312_298

Bug ID 19715310: USER PERFORMS A SAVED SEARCH AND RECEIVES ERROR

Root Cause: We did not support multiple search windows before, so when the customer launched multiple windows from MCAD it caused inconsistent/NullPoint issues.

Resolution: Refresh search Criteria if there are different BaseClassId/ClassId between Cache and UI. Set a flag to indicate search launched from MCAD URL or others. Use a special handler for the MCAD case; it should not read last session criteria.

2.3.3 9312_299

Bug ID 19732368: ATTRIBUTES NOT CORRECT AFTER SUBCLASS CHANGE THROUGH PROCESS EXTENSION

Root Cause: The attributes in the title block and Page Two do not change according to the Part type change when edited in the Item.

Resolution: When Part type changes, save the new subclass and return to view the model with attributes refreshed.

2.3.4 9312_300

Bug ID 19826176: QUICKVIEW WINDOW DOES NOT DISPLAY ALL INFORMATION

Root Cause: In general, Quick View only looks at Rev information stored in the changeKey of VO rows, but for Quick View from search results, the changeKey does not have set values.

Resolution: Set the correct Change Key for query result rows from Search, and make the Rev consistent in the UI side.

2.3.5 9312_302

Bug ID 20048703: IMPORT OF XLSX FILE CAUSES ERROR BUT XLS FILE IMPORT IS OK

Root Cause: The logic used to parse Excel is wrong and some special formats are mishandled.

Resolution: Change the parsing logic to consider the special format.

2.3.6 9312_303

Bug ID 20093294: AFTER THE 9312_298 PATCH, DASHBOARD WIDGET CONFIGURATION SEARCH- NO CRITERIA DISPLAYED

Root Cause: The undefined form causes the problem.

Resolution: Catch the empty form when loading the search criteria.

2.3.7 9312_304

Bug ID 20075954: LINK IN THUMBNAIL ON ITEMS OPENS THE WRONG FILE IN AUTOVUE

Root Cause: Those attachment rows added by Search from the same File Folder or Design object share the same thumbnail from the corresponding File Folder and Design object. URLs generated to view the corresponding file of this thumbnail uses incorrect file information from the first row of File Folder or Design object. That is the reason why the 2nd row is set as Master thumbnail and the 1st row file is incorrectly displayed in viewer applet.

Resolution: Fixed in code to pick up the correct file information by examining the row with the same thumbnail id and its file name against the thumbnail caption.

2.3.8 9312_307

Bug ID 20367752: WHERE USED REPORT THROWS UNEXPECTED ERROR

Root Cause: A special handler is missing. The Where Used Report uses relationship search, which uses $CURREV and $LATESTREV. The code does not handle the two variables very well in some situations. In this case, there is a special privilege configured with special criteria.

Resolution: A special handler for $CURREV and $LASTESTREV.

2.3.9 9312_308

Bug ID 20333682: UNABLE TO MODIFY THE CURRENT PRICE PERIOD OF A SOURCING PROJECT AF

Root Cause: Date format is not passed as parameter, so in the calendar it only gets the default.

Resolution: Show the proper date depending on the passed date format.

2.3.10 9312_309

Bug ID 20378079: FATAL EXCEPTION OCCURED JAVA HEAP SPACE WHEN IMPORTING ITEMS

Root Cause: Wrong parameter is used for dummy table row.

Resolution: Use the right parameter to create dummy BaseRow.

2.3.11 9312_310

Bug ID 19060190: AGILE SDK API ISSUE - II - PCM MODULE UNABLE TO ADD SOME ITEMS TO

Root Cause: In the sc_item table, PCM converts all small letters to capital letters for Part Number, but PC does not. Therefore, Agile can not find the proper Item even it existed in the PC side when the RFQ was created.

Resolution: Convert all small letters to capital letters when retrieving Part Number in sc_item.

2.3.12 9312_311

Bug ID 20671443: TITLE BLOCK PAGE DOES NOT RENDER PALLETS CORRECTLY WHEN USING IE11

Root Cause: IE compatability issue.

Resolution: Enforce IE into IE7 mode, and fix the UI issues.

2.3.13 9312_312

Bug ID 20596790: EC RELINKS WRONG CAD FILES ON LOAD

Root Cause: For an internal object cache, to avoid loading more than one duplicate, the ID's hash code was used, which could have generated duplicate hash values although it should not.

Resolution: The internal object cache's key value was changed from the hash code to the ID string and now we cannot have duplicate values anymore, which could cause an incorrect object to be loaded.

2.3.14 9312_314

Bug ID 20605650: MANUFACTURER WHERE USED FIELDS ARE NOT POPULATING IN EXPORT COMPLETE

Root Cause: There is no code to output the itemP2 attribute for the manufacturer Where Used table.

Resolution: Added code for it.

2.3.15 9312_315

Bug ID 20606980: ACCESSING PRICE TAB FOR ASSEMBLIES WITH HIGH REVISIONS AND MORE NU

Root Cause: Duplicate manufacture part id is included in list.

Resolution: Exclude the duplicate manufacture part id.

2.3.16 9312_317

Bug ID 20735706: THE RECENT DISCUSSIONS REPORT IS NOT RUNNING AUTOMATICALLY

Root Cause: When multiple scheduled reports are attempted to be scheduled, some of them may fail due to some reason. The correct behavior is re-scheduling the failed reports to the next scheduling cycle, but the code doesn't handle it very well.

Resolution: Correct the related behavior.

2.3.17 9312_318

Bug ID 19595950: AUTOVUE FOR AGILE TAKES MUCH LONGER TO OPEN FILES COMPARED TO STAN

Root Cause: Two factors - 1. Pinging DFM costs a lot of time. 2. When replicating and checking if a file exists, the W S call costs a lot of time.

Resolution: 1. Ping action correctly to normal ping servlet approach.2. Remove file exists WS call, instead use get file size WS call.

2.3.18 9312_319

Bug ID 21425766: AGILE CORE WEB SERVICES NOT WORKING ON 9.3.1.2

Root Cause: HF 9.3.1.2.179 introduced a NullPointerException error while getting the API name of list Item of Lifecycle Phase.

Resolution: Added a null object check and converted the list Item name to API name if the API name is null.

2.4 PLM Release 9.3.2.0

This section includes Hot Fixes included in Agile PLM 9.3.2.0.

2.4.1 9320_139

Bug ID 19424273: RECEIVED MESSAGE STATING YOUR CHANGES HAVE BEEN SUCCESSFULLY SAVED, BUT CHANGES NOT SAVED

Root Cause: When cover page info is edited on object1 in window1, the object id in action context was object1, then if switched to window2 (in one HTTP session) and the user executes some actions on object2, at this time, the object id in action context changes to object2, so if the user comes back to window1 and the user clicks the save or validate button, the current object id in window1 could not match the object id in action context, so the cover page info which the user edited was lost.

Resolution: Handle this multiple windows case on the objects which in PC, PGC, PCM, PPM and common modules, check the object id in current request and in action context when the user clicks the Save or Validate buttons in the Cover Page tab, if these 2 object ids can not be matched, throw the block error message.

2.4.2 9320_143

Bug ID 19658167: LEGACY BOM COMPARISON REPORT DOES NOT DETECT DIFFERENCES IN FIND NUM

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

Resolution: Corrected the code to use correct data type.

2.4.3 9320_144

Bug ID 19690151: 'HAS ATTACHMENTS' EMPTY IN CHANGE AI TAB AS ADDING ATTACHMENT MODI

Root Cause: The system caches a wrong row of the pendinglist. When adding a new attachment, it sets the flag value to 1 in the wrong row. So the Has Attachment attribute in the Affected Items (AI) tab show empty

Resolution: Forced Refresh the cache before add the attachment. The affected area is the ¿Has Attachment¿ attribute in AI tab of change.

2.4.4 9320_145

Bug ID 19513662: THE WINDOW COULD NOT BE CLOSED(ADVANCED SEARCH )

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

Resolution: Fixed the defect that occurred when the value is saved.

2.4.5 9320_147

Bug ID 19790432: SUBSTANCES ROLLUP DOES NOT HANDLE A THRESHOLD OF 0 (ZERO) PPM CORRECTLY

Root Cause: External rollup does not handle a threshold of 0 PPM correctly when calculating rollup result.

Resolution: Update the logic to take 0 in such a scenario.

2.4.6 9320_150

Bug ID 19645659: SCALE CANNOT BE CHANGED ON SOME PART COMPLIANCE ATTRIBUTES

Root Cause: Scale, Min Value and Max Value properties of the following 15 attributes are disabled and not editable: Parts.Compliance.Substances.Numeric01~Numeric10 Specifications.Substances.Numeric01~Numeric05

Resolution:Scale, Min Value and Max Value properties of the above 15 attributes are enabled and editable.

2.4.7 9320_152

Bug ID 20003697: EXTERNAL ROLLUP RETURNING INCONSISTENT & INCORRECT CALCULATED CONC RESULTS ON SP

Root Cause: There are duplicated rows in SPECIFICATION_SUBSTANCES table, which is generated during external rollup. The duplicated rows look like bad data resulted from multiple threads of external rollup.

Resolution: The DISTINCT keyword can be used to resolve the problem

Related bug:

Bug 20003697: PPM ASSIGNS THE INCORRECT UNIT OF MEASURE (GRAM INSTEAD OF KILOGRAM

Bug 19878897: PPM ASSIGNS THE INCORRECT UNIT OF MEASURE (GRAM INSTEAD OF KILOGRAM

2.4.8 9320_154

Bug ID 19421515: PARTS IN PART GROUP DO NOT SHOW SAME COMPLIANCE AS PART GROUP

Root Cause: When the Declaration has no supplier the SUPPLIER in the database is stored as NULL, but in the SQL generated in Java we use NVL(supplier,0) which turns NULL to 0. Therefore, in the search query we should use 0 to indicate the case of no supplier instead of NULL or, the composition cannot be returned so the view substance table will not be published to objects(item/mpn) under Part Group.

Resolution: Change the SQL accordingly.

2.4.9 9320_155

Bug ID 20078454: SCHEDULED SPECIFICATION MANAGEMENT TASK FAILS

Root Cause: There is an incorrect attribute id when performing specification management task.

Resolution: Update with the correct attribute id.

2.4.10 9320_156

Bug ID 19873397: SCHEDULE STATUS REASON IS NOT REFLECTED CORRECTLY IN CASE OF USING

Root Cause: When a project is created, the reason stored in Schedule Status Reason of the root project is Children are Off Track which is in English. After the language is switched to Japanese and completed Phase 1, the status of its parent changes from Off Track to Need Attention which is correct. Before overriding the value of Schedule Status Reason in the parent, the system checks if it's been modified by customer by comparing the value stored in the Schedule Status Reason field with the default reason of status "Off Track".The first value is Children are Off Track in English, but the second one is Children are Off Track in Japanese. They are different although they have the same meaning. Therefore, in this case the system treats the situation as if the user has changed the default value of Schedule Status Reason and keep the user specific value.

Resolution: 1. Add a locale check before the Schedule Status Reason attribute is updated;2. Compare the existing value with all enabled languages and update the reason attribute with current user's preferred language except the existing value does not equal to any of the enabled locales.

2.4.11 9320_161

Bug ID 20216218: CURSOR FOCUS NOT IN FIRST EDITABLE FIELD

Root Cause: 934 ME-001 project (Two Columns project), fields have new CSS classes assigned.

Resolution: The code to set focus on fields honors the Two Column mode.

2.4.12 9320_162

Bug ID 20260062: DISPLAYS JAVA.NET.PROTOCOLEXCEPTION ON AGILE SSO ENVIRONMENT WHEN ADDING ANY OBJECT TO RELATIONSHIP TAB OF ITEM

Root Cause: The response buffer flush for adding object by search is not correct.

Resolution: Set correct response string length, and fresh buffer.

2.4.13 9320_164

Bug ID 20255774: PPM PROJECT IS CREATED FROM PROJECT TEMPLATE THE CONTENT RULE IS NOT TRANSFERRED

Root Cause: The system retrieves the wrong subscription when creating from template with affected relationship

Resolution: Update the Get Subscription method.

2.4.14 9320_166

Bug ID 20419123: FAIL TO RUN WORKFLOW JOB FUNCTIONS WITHOUT USERS REPORT

Root Cause: When the customer does not have a license for some base classes, the system generates a NullPointerException when sorting with Null value.

Resolution: Sort while filtering out Null value.

2.4.15 9320_167

Bug ID 20448203: CALCULATED PPM IS INVALID

Root Cause: PGC uses float type for returned results from external rollup, but the customer's use case involves many decimals so the precision is decreased.

Resolution: Change float to double when appending result rows in server layer.

Related Bug 20447116: PGC DECIMALS WRONG

2.4.16 9320_168

Bug ID 20533983: REPLACE SPECIFICATION FEATURE DOES NOT REPLACE AFTER SPECIFICATION

Root Cause: The status is hard-coded as Default Declarations' Pending status when getting pending declaration for specification management task, which leads to the issue.

Resolution: Replaced the Status id with status type of Pending.

2.4.17 9320_169

Bug ID 20583495: COMPOSITIONS.DECLARATION LIFECYCLE PHASE IS BLANK ON ADVANCED SEARCH RESULT

Root Cause: The attribute, Parts.Compliance.Declaration Lifecycle Phase, is a special list. It is not handled properly.

Resolution: Added special handling for Parts.Compliance.Declaration Lifecycle Phase, Manufacturer parts.Compliance.Declaration Lifecycle Phase, and Part groups.Compliance.Declaration Lifecycle Phase

2.4.18 9320_171

Bug ID 20508162: INVALID CALCULATIONS DUE TO MULTIPLICATION AND/OR ROUNDING RESULTS

Root Cause: The decimal precision at in the database is 2 for Calculated PPM in external rollup logic when calculating the value. For example, if calculated PPM is 0.001, it will be rounded to 0 and regarded as an invalid substance. The Whole Substances view is ignored if invalid substance exists.

Resolution: Remove decimal precision limitation in the database for Calculated PPM.

2.4.19 9320_172

Bug ID 20675200: GLOBAL REPLACE CAN NOT REPLACE ACKNOWLEDGERS

Root Cause: The Replace All function became missing with the introduction of acknowledger in 932.

Resolution: Add this function to system.

2.4.20 9320_174

Bug ID 20732886: ACP IMPORT ERROR: UNABLE TO RESOLVE THE VALUE

Root Cause: When migrating the default value of the list attribute, we need a special handler.

Resolution: Added a special handler for the default value of list attribute via ACP.

2.4.21 9320_175

Bug ID 20774469: EC RELINKING WRONG CAD FILES ON LOAD

Root Cause: The cache uses the hashCode of a string, which is generated by concatenating the class ID and the Design numbers. In such cases, the hash is computed as identical, which it should not.

Resolution: The internal object cache's key value was changed from the hash code to the ID string and cannot have duplicate values anymore. This can cause the wrong object to be loaded.

2.4.22 9320_176

Bug ID 20759265: ACP IMPORT ERROR: DUPLICATE NAME ENTERED

Root Cause: The way to generate hidden sub-cascade list name is like 'UOM00', 'UOM01', 'UOM02' when migrating cascading list from source to target, which causes duplicated names in the database side.

Resolution: Changed the method of generation with UOM plus nano seconds of current time.

2.4.23 9320_177

Bug ID 20691530: MATERIAL PPV(%) DOES NOT SHOW IN PERCENTAGE FOR ITEM OBJECT PRICE

Root Cause: We do not filter the money attributes that include the currency.

Resolution: Made the Item.Price tab money attribute always show as numeric without currency regardless of the money type so that it will look the same as Price.Priceline.

2.4.24 9320_178

Bug ID 20550124: PC - BOM/BOI READ PRIVILEGE DOES NOT FLOW TO BOM/BOI OF A PARENT PART

Root Cause: The BOM children's BOM attributes' privilege check are only based on the direct parent level. For example, a level 3 object only follows the level 2's attributes privileges.

Resolution: For the BOM object on level N, we should enforce the code logic to check BOM attributes privilege for all parent objects from level 0,1,...to N-1. It should be an intersection of all parent objects' BOM privileges.

2.4.25 9320_180

Bug ID 20814351: IMPORT SHOULD NOT ALLOW THE OBJECT CONTAINS CHARACTER

Root Cause: There is a lack of number validation while calling createMultiListValue.

Resolution: Add number validation.

2.4.26 9320_181

Bug ID 20680887: AGILE SCHEDULED REPORTS IS FAILING

Root Cause: When multiple scheduled reports are attempted to be scheduled, some of them may fail due to some reason. The correct behavior is rescheduling the failed reports to next scheduling cycle.

Resolution: Correct the related behavior.

2.4.27 9320_182

Bug ID 21162497: EXTERNAL ROLLUP DOES NOT CHECK FOR SHIPPABLE ITEMS

Root Cause: QTY with decimal is not supported in fact_table_task. Scheduled task and On Demand Calculate use two tables to store the object data to be externally rolled up.

Resolution: Change the QTY column of the fact_table_task property at the DB level.

Related Bugs:

21164947: PATCH 9.3.2.171 NEEDS TO BE APPLIED TO EXTERNAL ROLLUP BATCH JOB

21165056: PART OF PATCH 9.3.2.167 NEEDS TO APPLIED TO EXTERNAL ROLLUP BATCH JOB

2.4.28 9320_183

Bug ID 20901466: CANNOT SELECT VALUE FOR DECLARATION LIFECYCLE PHASE IN ADVANCED SEARCH

Root Cause: The list of statuses for Compositions.Declaration Lifecycle Phase is special, and not handled properly.

Resolution: Fetch the list of statuses from Declarations.Cover Page.Status list

2.4.29 9320_186

Bug ID 21228608: CANNOT UPDATE SUPPLIER INFORMATION BY IMPORTING A SPREADSHEET

Root Cause: Import side use supplier id:::site id as unique id to identify one supplier row. If the site license is disabled, the unique id will be supplier id:::, and import side will always do add the operation. For some supplier rows import side should do update operation

Resolution: If site license is disabled, change site id to common site id.

2.4.30 9320_187

Bug ID 21290555: RELATIONSHIP TAB DOES NOT SHOW THE CORRECT SUPPLIER TYPE

Root Cause: There are two columns in DB to store the supplier object subclass value and when it's modified in cover page only one of them is changed in DB. However the relationship table is generated based on another one.

Resolution: For the relationship table we used the column which always stores the latest subclass value.

2.4.31 9320_188

Bug ID 20359771: AGILE LDAP USER SYNC IS NOT WORKING FOR GENERIC LDAP CONFIGURATION

Root Cause: For generic LDAP server, it needs map objectGUID atribute to entryGUID in groovy script. but the map value is not saved into agile user.

Resolution: Added code to save the values.

2.4.32 9320_190

Bug ID 21454680: THE HOME DISPLAY ERROR WHEN A USER LOG IN TO THE AGILE

Root Cause: This is caused by a code defect. The NULL pointer is not handled for this case.

Resolution: Need to handle null pointer exception.

2.4.33 9320_193

Bug ID 21497037: REDLINE FOR PART P3 ATTRIBUTES ON ECO SYSTEM DOES NOT SHOW CORRECT

Root Cause: In redline edit mode, the system does not hide the fields which the current user had no privilege to read.

Resolution: Hide the fields that the user does not have read privilege for in redline edit mode.

2.4.34 9320_195

Bug ID 21630515: "WORKFLOW ALREADY IN USE ERROR" WHEN CREATING NEW WORKFLOW

Root Cause: When the user adds a new status in workflow, we need to check if the workflow is in use (value of some criteria of query equals to id of workflow). In the current code, it only checks for value, not for attribute id.

Resolution: When validating if the workflow is in use, we need to check for both value and attribute id of criteria of query.

2.5 PLM Release 9.3.3.0

This section includes Hot Fixes included in Agile PLM 9.3.3.0.

2.5.1 9330_35

Bug ID 20065993: VIN: LOADING TO VIN WITH A9 OBJECTS IS TAKING VERY LONG TIME

Root Cause: The performance issue is resolved from the A9 side. This bug can be resolved directly or transfer to Fusion IM for further follow up from the Fusion IM side.

Resolution: The issue is resolved on the A9 side by providing batch creation, need Fusion IM to uptake the new method.

2.5.2 9330_104

Bug ID 19424458: NEED TO HAVE USERID PASSED IN WEB SERVICE REQUEST FROM REF OBJECTS

Root Cause: There is no user login ID in the Reference Object request.

Resolution: Add the user login ID into the Reference Object request.

2.5.3 9330_109

Bug ID 19206503: CHECKOUT LOCATION ON THE ATTACHMENT TAB DOES NOT POPULATE

Root Cause: Modern web browser security limitations do not allow us to populate this information or read this directly from the user system. As we removed Java technology from the application for file transfers to simplify deployments, this capability became obsolete. There is no HTML 5 capability to enable this capability on a Web Browser.

Resolution: Hard code in WebClient to disable check location in following places:1. Item table,Attachment tab, Checkout Location field2. File table, Title Block tab, Checkout Location field3. File table, Files tab, Checkout Location field

2.5.4 9330_118

Bug ID 19530388: EXPECTED ALL EVENT MESSAGES TO DISPLAY HTML AFTER PATCH 16932062

Root Cause: Security encodes HTML entities in the messages.

Resolution: Does not encode HTML entities.

2.5.5 9330_119

Bug ID 19559430: TIMESHEET SEARCH RESULT DISPLAYS SAME SET OF DATA MULTIPLE TIMES

Root Cause: Each page returns all table rows in the timesheet search data model.

Resolution: Overwrite the getdata method in the timesheet search data model to return the right rows in each page.

2.5.6 9330_124

Bug ID 18704328: EXPORTS ITEM DATA EXCEPT THE MFR/MFR. PARTS COLUMNS APPEAR BLANK

Root Cause: The PCO Affected Price tab price does not check the privileges for Price, Item, Manufacturer Part, and Manufacturer privilege.

Resolution: Need to check the Read privilege for objects in the Affected Price tab.

2.5.7 9330_125

Bug ID 19607674: JAVA PX ACTIONRESULT.EXCEPTION DOES NOT DISPLAY NEW LINES

Root Cause: Does not transfer '\r','\n' to <br>.

Resolution Transfer '\r','\n' to <br>.

2.5.8 9330_126

Bug ID 19777509: ENHANCE THE ADDROWS WEB SERVICE TO RETURN THE ID OF THE ADDED ROW

Root Cause: When adding a row through the addRows WebService, the response includes only the status message but no id for the added rows.

Resolution: Return the rowId if the client specifies the flag in the request.

Related Bugs:

19777495: NEED TO BE ABLE TO SPECIFY THE REVISION OF AN ITEM BY CO ID

19777429: NEED FLAG IN THE RESPONSE OF THE GETOBJECT WS FOR LATEST REVISION

19777531: NEED A WEB SERVICE IN A9 WHICH DELIVERS ROLLED UP RESOURCE INFORMATION

20212266: TABLE#LOADTABLE SERVICE RETURN ATTRIBUTE "ITEMREV" TYPE AS "XS:STR

2.5.9 9330_127

Bug ID 19690342: UNABLE TO SET COMMODITY CODE VALUE TO ITEM IF COMMODITY CODE HAS MORE PARTS

Root Cause: To display the latest description of the Item object, a PGC developer fixed one bug to get it from the Item service directly since the PART_DESC in map table has an incorrect value. It causes performance issues on the customer DB if the Part family relates to many Item objects. Then, this approach was changed to update the PART_DESC in the map table every time when loadTable() is invoked. Otherwise this causes another performance issue when customer has certain Part family to update all descriptions of related Items (10000+).

Resolution: According to a PGC functional request, here the latest description of Item is needed. Get the description of Item from PC ITEM table directly by joining it.

2.5.10 9330_130

Bug ID 19821011: COMPLIANCE IS NOT CALCULATED ON EXTERNAL SPECIFICATION COMPOSITION

Root Cause: Incorrect logic is used in the procedure for declaration external rollup.

Resolution: Update the logic to take 0 into consideration.

2.5.11 9330_131

Bug ID 19634477: UNABLE TO DISPLAY MULTIPLE ERROR MESSAGES IN NEW LINE WITH CHANGE

Root Cause: Does not transfer '\r','\n' to <br>.

Resolution: Transfer '\r','\n' to <br>.

2.5.12 9330_132

Bug ID 19633350: JAPANESE CHARACTERS GET GARBLED WHEN USER DOWNLOADS TEMPLATE FOR DECLARATION

Root Cause: When the user sets the encoding type as their local setting, when downloading the declaration template there are garbled characters in the Excel file.

Resolution: During export, ensure that the file is written using the customer setting

2.5.13 9330_134

Bug ID 19863760: UNABLE TO PERFORM SAVE AS ON DECLARATION OBJECT THROUGH AGILE API

Root Cause: The Supplier attribute is required when executing a Save As using SDK code.

Resolution: Made the Supplier attribute not required.

2.5.14 9330_135

Bug ID 19664431: AGILE 933 PROXY SERVER SETUP

Root Cause: 1. Only the URL entered in Java Client's Web Server URL can be used to do file uploads. This is used to check the origin of request that can be allowed to access the file server for uploading from the Web Client, but there are situations where the customer may need multiple accessing URLs to Agile such proxy server, https 2. Deploy Agile with HTTP URLs in Java Client and File Server's configuration file "server.conf", and want to access Agile in HTTP for internal users and HTTPS for external users.

Resolution: To achieve above, we provided configuration in the File Server's server.conf for those extra access URLs so that the File Server considers those URLs as valid "Access-Control-Allow-Origin"

2.5.15 9330_136

Bug ID 19781390: NUMERIC ATTRIBUTES CONFIGURED WITH A SCALE DO NOT DISPLAY CORRECTLY

Root Cause: Numeric attributes keep trailing zeros.

Resolution: Remove trailing zeros for Numeric attributes.

2.5.16 9330_139

Bug ID 19803007: WHERE USED REPORT SHOWS DUPLICATE ITEM NUMBERS

Root Cause: If one search involved both BOM and Manufacturing table and it is not a Where Used one level all released search, at this time, the SQL does not filter data completely, which causes issues with duplicates.

Resolution: Add more logic conditions to avoid duplicated results.

2.5.17 9330_141

Bug ID 19937803: PROGRAM TOP DISCUSSION REPORT DOES NOT CONTAIN MESSAGE FIELD

Root Cause: ER type request

Resolution: Add "MESSAGE" field on 3 reports - Project Top Discussions Report/My Discussions Report/Portfolio Priority Discussions Report.

2.5.18 9330_142

Bug ID 19764503: UNABLE TO IMPORT MULITPLE BOS ROWS WITH JAPANESE USER

Root Cause: The class type is hard-coded when creating compositions in import logic.

Resolution: Replace the hard-code with a localized string.

2.5.19 9330_143

Bug ID 19429852: AGILE 9.3.3 DRAG AND DROP ON SCO AFFECTED ITEM TAB DOES NOT WORK

Root Cause: When user clicks on type-in or search, request is sent for grid information, while grid information is NOT available.

Resolution: Find Grid information by grid ID sent in response.

2.5.20 9330_145

Bug ID 19986501: BOM EXPLOSION REPORT LIMITS CALCULATION SHOULD BASED ON TYPES

Root Cause: The estimated number of objects is not affected by the chosen Item types in the error message when the BOM numbers exceed the limit.

Resolution: Based calculation on chosen item types.

2.5.21 9330_146

Bug ID 19876100: AFFECTED ITEM IS REMOVED FROM COMPLETED QCR

Root Cause: The current design is not reasonable since the customer needs to be informed when the Affected Items are removed from Change objects, if the AI's related rev is used in the QCR.

Resolution: Display an error message when this situation occurs per PM's requirement.

2.5.22 9330_147

Bug ID 19594997: AGILE 9.3.3, AFTER PATCH 9.3.3.30 UPLOADED FILES FILE NAME WILL APPEAR GARBLED

Root Cause: UTF-8 encoding is required to parse the HTTP request during file upload.

Resolution: Use proper encoding UTF-8

2.5.23 9330_148

Bug ID 20101405: CHECKED THE AML THAT WHEN MFR NAME CONTAINS CHINESE, IT APPEAR GARBLED IN BOM COMPARISON REPORT

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

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

2.5.24 9330_150

Bug ID 20016668: UNRELEASED CHILD ITEM ERROR HYPERLINK BEHAVIOUR

Root Cause: Always show the Add Row Successfully message.

Resolution: Show error message when there is lack of privilege.

2.5.25 9330_151

Bug ID 20092469: PROGRAM TOP DISCUSSION REPORT TAKES TOO LONG TO LOAD ROOT PROJECT

Root Cause: GSK has more than 100,000 root projects. It takes a long time to display all of them in the list.

Resolution: Change the root project selector to search mode so that users can get the root project quickly through search criteria.

2.5.26 9330_152

Bug ID 20025999: BOM BULK CHANGE LIMITS ROWS TO 500 AFTER SORTING DATA

Root Cause: When the table is sorted the "max query result" setting in Java Client is used.

Resolution: In this case, the customer's requirement is to see all available results so the sort action should have a special handler for the wizard coming from Bulk Change.

2.5.27 9330_153

Bug ID 20077709: GLOBAL SEARCH PRIVILEGE DOES NOT SHOW INSUFFICIENT PRIVILEGE MESSAGE WHEN INSUFFICIENT PRIVILEGES

Root Cause: If the user presses the Save button, the system loads search results and refreshes the attention for insufficient privilege users.

Resolution: If the user presses the Save button, we do not load search results if the user does not have the privilege to save Global search.

2.5.28 9330_154

Bug ID 20160653: JOINED USER MISSING IN NOTIFICATION LIST OF REPLY POP UP IN DISCUSSION

Root Cause: An incorrect method is used to get the Notify Users list from the reply table.

Resolution: Correct the method to get the Notify Users list from the Discussion table.

2.5.29 9330_155

Bug ID 20180141: AGILE 9.3.3 CUSTOM REPORTS DATE FIELD ISSUES

Root Cause: Query treats date and time as date only to transform, make a empty string to output.

Resolution: Judge by attribute DateTimeFormat and follow related business logic.

2.5.30 9330_156

Bug ID 20042051: SMARTRULE - OBJECT EDIT CONFLICTS SET TO ALLOW IS NOT ALLOWING

Root Cause: We do not refresh object status before a save.

Resolution: When trying to save an object, refresh its status.

2.5.31 9330_157

Bug ID 20175591: UNABLE TO DELETE BLANK ROW IN A BOM TAB IF EVENT UPDATE IS ENABLED

Root Cause: For BOM blank row, an exception is thrown when an event is triggered.

Resolution: Need a special handler for BOM blank row when an event is triggered.

2.5.32 9330_161

Bug ID 20200089: REDLINE CHANGES DO NOT STRIKE OUT FOR THE NUMERIC ATTRIBUTES

Root Cause: We use the incorrect way to show the Numeric attribute in redline table.

Resolution: Use the correct way to show the Numeric attribute in redline table.

2.5.33 9330_162

Bug ID 20222911: EXPORT OBJECT FOR ADVANCED SEARCH RESULTS IS EXPORTING ONLY THE INTRODUCTORY PART

Root Cause: The wrong rev is assigned to the Item.

Resolution: Assign the correct id to the Item.

2.5.34 9330_166

Bug ID 19720866: LOAD TO CAD IS NOT LOADING THE SPECIFIED VERSION FROM SEARCH RESULTS

Root Cause: The function getobjectbyid() can not get the right version from design in search result.

Resolution: Get the version using rowID instead.

2.5.35 9330_167

Bug ID 20313134: REDLINE REMOVED BOM IS NOT SORTED BY ITEM NUMBER

Root Cause: Introduced by bug 8934597. When the redline action is deleted, the old value takes part in the sort. The new value is always null, so sorting does not work on deleted rows.

Resolution: Special handle the delete redline case when sorting.

2.5.36 9330_168

Bug ID 20239774: IMPORTING MPNS CREATES MPNS WITHOUT ACCEPTING THE WARNING

Root Cause: 933 feature bug

Resolution: Added some additional code for AutoNumber Object.

2.5.37 9330_170

Bug ID 20573338: LEGACY BOM COMPARISON REPORT SHOWS BOM ITEMS THAT ARE COMMON AFTER APPLYING 9.3.2.0.143.

Root Cause: HF 9320.143 changed the logic of the legacy BOM Comparison Report in which when two BOMS have the same Find Number, both still appear in the report.

Resolution: Update the logic.

2.5.38 9330_172

Bug ID 20312059: AXML EXPORTED BY AGILE CONTENT SERVICE HAVE NO REDLINES WHEN BOMNOTES BE DELETED

Root Cause: The empty tag was removed when fixing bug 14835608.

Resolution: Populate empty tag to reflect the redline delete action, if the new value is empty and the old value is not empty.

2.5.39 9330_173

Bug ID 19978648: AGILE 9.3.3 CUSTOM DASHBOARD TABLES NOT SORTING AND TAKING A LOT OF

Root Cause: This is caused by the customized Dashboard table. For the first column header 'Change icon', they do not want to show column name (same behavior with system Dashboard table), but for customized Dashboard table creation, the name is required.

Resolution: Add a special handler for the customized Dashboard table. If content type is image and if it is also the first column, set the name as blank.

2.5.40 9330_174

Bug ID 20371919: RESIZING AFFECTED ITEM WINDOW ON INTERNET EXPLORER DOES NOTT WORK CORRECTLY

Root Cause: The fix for 13440210 (9311.109) replaces the common UI resize function with a specific one for the Redline Title block sub page, which leads to the unexpected UI behavior while resizing.

Resolution: Put the special handler in the common file.

2.5.41 9330_175

Bug ID 20389760: ISSUE WITH OOTB ROLE SAVED TO CUSTOM ROLE

Root Cause: When the building activity discover object with Team.Name attribute, the new save-as role is not synchronized to the new user.

Resolution: When building activity discover object with Team.Name attribute, synchronize the new save-as role to the new user.

2.5.42 9330_178

Bug ID 20419717: AFTER PATCH 9.3.3.30 UPLOADED FILE NAME WILL APPEAR GARBLED

Root Cause: UTF-8 encoding is required to parse the HTTP request while uploading file.

Resolution: Use proper encoding UTF-8.

2.5.43 9330_179

Bug ID 20419572: ECO AFFECTED ITEM, REDLINE OF ITEMS LAST BOM COMPONENT NOT ABLE TO DOUBLE-CLICK

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

Resolution: Change the approach to calculate the bottom Y of the grid table.

2.5.44 9330_180

Bug ID 20109411: SEARCH RESULTS NOT SORTING PROPERLY IN CUSTOM SEARCH FOR DASHBOARD

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

Resolution: Added sorting process in memory for list and multilist type data

2.5.45 9330_182

Bug ID 20310381: DURATION SIGNOFF CALCULATION COUNTS WEEKEND

Root Cause: We do not take the weekend into consideration when calculating signoff duration

Resolution: Take weekend into consideration when calculating signoff duration.

2.5.46 9330_183

Bug ID 20456439: CHANGE PACKAGE REPORT GETS TRUNCATED WHEN EXPORTED TO EXCEL

Root Cause: There is an incorrect operation which puts the HTML serializer string as report value map key for Ref Des attribute in Change Package Report.

Resolution: Correct the incorrect operation.

2.5.47 9330_184

Bug ID 20350238: 9.3.3 RELEASE SUPPORT SAFARI7

Root Cause: This case for Keynote file is not a valid case as it is a real folder, not a single file.

Resolution: Suggest customer to go with the workaround (zip it manually and upload it).

2.5.48 9330_185

Bug ID 20442074: ADVANCED SEARCH ON TEAM TAB DOES NOT SHOW RESOURCE POOLS WHEN USING SELECT WITHIN USER GROUP

Root Cause: Agile attempts to filter user group list for the attribute, Activities.Team.Name, but this is invalid when there is no activity in the context.

Resolution: Skip the filter when there is no activity in the context, that is, objid == -1

2.5.49 9330_187

Bug ID 20350257: GLOBAL NAVIGATION BAR UI ISSUE

Root Cause: The minimum width of the top panel is 600px, and is not enough so the quick search moves to the next line.

Resolution: Change minimum width of the top panel to 650px.

2.5.50 9330_189

Bug ID 20517573: INVALID COLUMN INDEX ISSUE ON FILE FOLDER OBJECTS

Root Cause: This is a code issue. Values of variables are not cleared at the end of a loop. This leads to disproportionate parameters while compiling SQL.

Resolution: Added code to clear values of the variables at the end of loop

2.5.51 9330_190

Bug ID 20462854: TIME BUFFER VALUE ON DEPENDENCIES TAB SHOWS INCORRECTLY AFTER PROJECT IS CREATED USING XML FILE

Root Cause: This is caused by the String parse on Int that falls outside.

Resolution: Use long instead.

2.5.52 9330_191

Bug ID 20486888: IMPORTING RFQ RESPONSE DOES NOT UPDATE VALID FROM ATTRIBUTE VALUE

Root Cause: There is a code defect. We do not update the Valid From attribute if it has been changed.

Resolution: Changed code to implement this feature.

2.5.53 9330_192

Bug ID 20460694: UNABLE TO SET IMPORT PREFERENCE BLANK DATA ACTION USING AIS

Root Cause: Ais does not support to the ability to specify blank data action. This bug is an enhancement.

Resolution: Customer can specify the option ParsingAndValidationOptions|BlankDataAction=Retain using AIS.

2.5.54 9330_195

Bug ID 20525826: PCM - UNABLE TO CREATE RFQS

Root Cause: We update the attribute rs_event_state of the Response table with null value.

Resolution: Update attribute rs_event_state of the Response table without null value.

2.5.55 9330_196

Bug ID 20584699: ENABLE ASCENDING/DESCENDING ORDER ON HISTORICAL REPORT TAB

Root Cause: There is a NullPointerException blocked Report History Records sorting when retrieving table view information.

Resolution: Replaced the null value with a default one.

2.5.56 9330_197

Bug ID 20556123: CRITERIA FOR DOCUMENTS USING CASCADE LIST SAVES AS PARTS

Root Cause: when creating admin criteria using AI list attibute assigned by a cascading list and select one value like [Documents]AAA|BBB, it will always be saved as [Parts]AAA|BBB.

Resolution: when cascading list shows up, build proper class id to each leaf/parent node of the list.

2.5.57 9330_198

Bug ID 20486572: ACP IS NOT ABLE TO MIGRATE THE WORKFLOW CONFIGURATIONS PROPERLY.

Root Cause: Some recently added properties are missing in ACP.

Resolution: Added the new properties to ACP.

2.5.58 9330_201

Bug ID 20632276: ANALYSIS TAB FILTER PART WITH BEST PRICE DISPLAYS MANY RECORDS WITH NO BID

Root Cause: This is a code defect. We include the Response Lines without supplier, if the view is Parts with Best Price.

Resolution: Exclude the Response Lines without supplier, if the view is Parts with Best Price.

2.5.59 9330_202

Bug ID 20563019: MANUFACTURER PARTS CANNOT BE CREATED DUE TO HARDCODED ID 1488

Root Cause: A hard- coded id 1488 in the fix of 14506225 introduced this issue. If the customer removes the default subclass and uses a newly created Manufacturer Part subclass. The error occurs when we get the subclass node (1488).

Resolution: Get the attribute name via class id instead of subclass id.

2.5.60 9330_203

Bug ID 20605559: JAVA.LANG.NULLPOINTEREXCEPTION WHEN CHANGING STATUS OF CERTAIN CHANGE

Root Cause: We do not consider a null value for the variable.

Resolution: Added logic for null.

2.5.61 9330_212

Bug ID 20545040: AFTER APPLYING HF 9.3.3.0.170, DOWNLOAD ATTACHMENT FILENAME IS CORRUPT

Root Cause: The filename has been encoded to Hex and the browser token("MSIE") has been removed from IE11.

Resolution: We decode file name to UTF8 before setting it to the HTTP request. We also added an additional check for IE11 using token "Trident"

2.5.62 9330_213

Bug ID 20690991: SEARCH WITH PROMPT CHECKED CANNOT SEARCH JAPANESE CHARACTER CORRECTLY

Root Cause: Add an additional wildcard for search on MutiByte characters.

Resolution: Remove the wildcard for prompt search in the UI side since server code can separate handler MultiByte characters or singlerByte characters well.

2.5.63 9330_214

Bug ID 20677051: SOURCING PROJECT, ADD ITEMS WITH BOM FILTERS IS NOT WORKING,QTY:NO

Root Cause: BOM filter does not work correctly if the privilege, Enforce Field Level Read, is disabled.

Resolution: Added a condition to avoid this case as privilege, Enforce Field Level Read, is disabled and returns null for readable attribute.

2.5.64 9330_215

Bug ID 20598314: UNABLE TO OPEN FILE WHICH CONTAINS THE SPACE IN FILENAME USING IE

Root Cause: Do not decode file name in the server side.

Resolution: Decode the filename in the server side and open file.

2.5.65 9330_217

Bug ID 20769504: 'ADD BACK REFERENCE' ATTRIBUTE NOT PROPAGATED VIA ACP

Root Cause: The 'ADD BACK REFERENCE' was introduced in 933, but is missing for ACP.

Resolution: Added it to ACP.

2.5.66 9330_219

Bug ID 20739798: REQUIRE HF 117 IS INCOMPATIBLE WITH HF98 AND HF149

Root Cause: Hot fix 9330.117 is incompatible with 9330.149.

Resolution: Code base is 9330.149 and merged the code fix of 9330.117.

2.5.67 9330_220

Bug ID 20786122: UPDATE BOM TABLE EVENT NOT WORKING PROPERLY WHEN ITEMS ARE ADDED B

Root Cause: This is caused by a code defect. The wrong data row is passed from UI.

Resolution: Correct the code to get the correct row by row index.

2.5.68 9330_221

Bug ID 20837401: MCO DOES NOT INCLUDE THE LATEST RELEASED REVISION IN THE AXML PACK

Root Cause: The loop index is incorrect when iterating the sorted Revision list.

Resolution: Use the correct index.

2.5.69 9330_225

Bug ID 20759916: DISPLAY NO PRIVILEGE ON PPM REPORTS REPORTS

Root Cause: This issue is caused by the wrong report privilege check when the user adds the Enforce field level read privilege.

Resolution: Changed the privilege check.

2.5.70 9330_226

Bug ID 20868129: UNKNOWN NUMBER: OBJECT DOES NOT EXIST AND NO PRIVILEGE ERRORS

Root Cause: The object's subclass is not set.

Resolution: Set object's subclass.

2.5.71 9330_228

Bug ID 20880673: ACP FAILS FOR EVENT: NODE XXXXXX DOES NOT EXIST IN THE CACHE

Root Cause: When an event is propagated to the target system, it can not match the object type node id of the newly created subclass.

Resolution: Refresh ID node of object type by API name.

2.5.72 9330_229

Bug ID 20880646: ACP FAILS TO PROPAGATE EVENT ASSOCIATED WITH NEW SUBCLASS

Root Cause: When the user chooses the Approve for Workflow event type and <All> workflow, the <All> workflow is not handled correctly in ACP.

Resolution: Handle the <All> workflow correctly.

2.5.73 9330_231

Bug ID 20887518: USER GETS ERROR MESSAGE: INVALID API LICENSE ERROR

Root Cause: Multiple threads access the cached table descriptors. Before the first thread can complete initializing the cache table descriptors, the attempted access from a subsequent thread cause incorrect information to be returned.

Resolution: Ensured that the cached table data completes initialization before it is accessed by multiple threads.

2.5.74 9330_232

Bug ID 20849515: ONE-OFF - ISSUE WITH UPDATE TITLE BLOCK EVENT WHILE EDITING ACTIVITY.PLM_REFERENCE

Root Cause: There is a lack of number validation in createMultiListValue.

Resolution: Add number validation.

2.5.75 9330_233

Bug ID 19340584: AGILE ALLOWS USER TO UPLOAD FILES WITH SPECIAL CHARACTERS AFTER APPLYING HOT FIX

Root Cause: After applying HF122, it rolls back HF30's fix for specific characters.

Resolution: Merge HF30 back. Add invalid character support.

2.5.76 9330_234

Bug ID 20701110: ATTACHMENTS ARE MISSING WHEN ACCESSING ATTACHMENTS TAB VIA WHERE USED OBJECT

Root Cause: Do not get correct class id for Where Used object.

Resolution: Load current object class id for Where Used object.

2.5.77 9330_236

Bug ID 20925303: PGC DECIMALS WRONG

Root Cause: The BOM quantity is rounded in external rollup.

Resolution: Changed the type definition of the staging table used during external rollup so the actual quantity will be used.

2.5.78 9330_237

Bug ID 20508126: INVALID CALCULATIONS DUE TO MULTIPLICATION AND/OR ROUNDING RESULTS

Root Cause: The decimal precision in the database is 2 for Calculated PPM in external rollup logic when calculating the value. For example, if calculated PPM is 0.001, it will be rounded to 0 and regarded as invalid substance, then the whole substances view will be ignored if invalid substance exists.

Resolution: Remove decimal precision limitation on the database side for Calculated PPM.

2.5.79 9330_241

Bug ID 20859562: ACP IMPORT ERROR: UNABLE TO RESOLVE THE VALUE

Root Cause: When migrating the default value of a list attribute, we need to handle it specially

Resolution: Added special handler for default value of list attribute via ACP.

2.5.80 9330_242

Bug ID 20957469: REDLINE CHANGES DOES NOT WORK IF USING BULK CHANGE

Root Cause: The current bulk change logic only supports updating Item number, but no other attributes, which leads to this issue.

Resolution: Enhance the logic to handle event PX of updating attributes in BOM/Manufacturer Bulk Change.

2.5.81 9330_243

Bug ID 21022937: "NO PRIVILEGES" MESSAGE IN MY ASSIGNMENT WHEN TASK OWNER HAS ENOUGH PRIVILEGE

Root Cause: This bug is caused by lack off subClassId parameter when doing the privilege check.

Resolution: Add the sbuClassId parameter when doing the privilege check.

2.5.82 9330_244

Bug ID 20990470: SORT ON THE HAS ATTACHMENT ICON DOES NOT WORK IN QUICK SEARCH

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

Resolution: Define a comparison that observes the general contract.

2.5.83 9330_246

Bug ID 7312: ACP IMPORTED GLOBAL SEARCHES DOES NOT APPEAR IN WEB CLIENT/JAVA CLIENT

Root Cause: Since the id of the subclass of the source system is different from the target system, it cannot be found due to a non-existing id. This is why it has errors when importing.

Resolution: Find object by name/apiname instead of id in the target system.

2.5.84 9330_247

Bug ID 20984245: SOME CTOS ARE MISSING ACKNOWLEDGEMENTS ON HISTORY TAB

Root Cause: When a transfer order object is transmitted successfully, ACS updates the Where Sent status first, then resets the specific destination. Finally it logs the history to record the package information, but in some special scenarios, reset destination fails and the log history record is skipped.

Resolution: Log the history record before we reset the ACS destination.

2.5.85 9330_249

Bug ID 21072325: ACS/EXPORT BLOCKED

Root Cause: When sorting the redlined AML Parts of item by created date, and if all the AML parts are with same created date, the ExtractOutputStreamWriter#quickSort() method runs in to an infinite loop.

Resolution: Change the loop index to break out from the infinite loop.

2.5.86 9330_250

Bug ID 21036387: MERGE PATCHES 20239958 AND 19893948 TO REMOVE INCOMPATIBILITIES

Root Cause: Code conflicts.

Resolution: Merge the fix of HF51(18606832) to HF250.

2.5.87 9330_251

Bug ID 21037469: TRANSFERRED CHANGE COULD NOT FILTER BY PENDING DAYS IN WORKFLOW RO

Root Cause: For the TA case the query SQL does not take the date filer into consideration.

Resolution: Add the date filter check for the TA case when generating the query.

2.5.88 9330_252

Bug ID 21085253: RUNNING SAVED SEARCH MANUALLY ON INACTIVE LIST VALUE RETURNS INCORRECT DATA

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

Resolution: Changed the code to get the correct multilist value.

2.5.89 9330_254

Bug ID 21119198: MANUFACTURER PART NUMBER IN LOWER CASE GETS CONVERTED TO UPPER CASE

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

Resolution: Overwrite the method, createRealObjNumberCollection, to support upper/lower/mixed case for creating Item/Manufacturer/Manufacturer Part.

2.5.90 9330_257

Bug ID 21119435: PROJECTS MUTLIST01 ATTRIBUTE VALUE ON FILES TAB OF FILE FOLDER IS NOT ON ATTACHMENT TAB

Root Cause: This is a program cache issue. It does not refresh the cache after attachment file is changed.

Resolution: Remove cache from programbasecache, and use agile base cache.

2.5.91 9330_258

Bug ID 21175511: FAILS TO IMPORT A .XLSX FILE

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

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

2.5.92 9330_259

Bug ID 21107032: SCHEDULED ROLLUP TASK DOES NOT ROLLUP EXTERNAL REACH SPEC COMPLIANCE

Root Cause: We do not support external specification mapping in external rollup task in the current logic.

Resolution: Add this function.

2.5.93 9330_261

Bug ID 21097659: ADVANCED SEARCH USING CHANGEHISTORY FINALCOMPETE DATE IS INVALID

Root Cause: Get more incorrect data from SQL, as one table with two unnecessary alias names in from clause.

Resolution: Update the Alias Table Name in SQL, in order to remove one surplus table name.

2.5.94 9330_262

Bug ID 21200048: MANUFACTURER PARTS GET SOFT DELETED AT THE CREATION TIME

Root Cause: When the user has no modify privilege for change.AI.item number the add button is still enabled in the Redline tab. If the customer Adds by Create any MPN, the "insufficient priv" error shows up and newly created MPN is soft deleted in the system. Next time when the customer tries to create this MPN again the "object has existed" error shows up.

Resolution: If the customer does not have the modify privilege of change.AI.item number, the Add/Remove button of the Redline tab should be greyed out to disallow the customer to add by creating any new object.

2.5.95 9330_263

Bug ID 21150307: ALTER TIME OUT FUNCTIONALITY WHEN USERS ACCESS VIA SSO

Root Cause: In SSO, the web client disables the prompt for the timeout alert due to a previous bug. so the customer can get different error after performing some actions.

Resolution: Enabled the prompt, then reloaded the browser with location.reload api, and do not invalidate the agile session and logout in SSO. so that the end user does not have a change to modify and get errors after time out.

2.5.96 9330_265

Bug ID 21151206: AGILE933HF122 IS NOT COMPATIBLE WITH 9.3.3.24

Root Cause: Browser detection fails when running in IE11.

Resolution: Force IE to go to the IE7 document mode and resolve corresponding bugs.

2.5.97 9330_266

Bug ID 21131595: SCRIPT API IBASESCRIPTOBJ.GETDIRTYATTRIDS() RETURNS WRONG DATA

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

Resolution: Before we compare the numbers with scale setting, we format them first.

2.5.98 9330_269

Bug ID 21189843: ARRAYINDEXOUTOFBOUNDSEXCEPTION IS THROWN WHEN API AGILE SDK API

Root Cause: This is caused by an incorrect hard-coded tableID when the event is sent.

Resolution: Get the correct tableIDs based on the changed attributes id.

2.5.99 9330_270

Bug ID 21191845: ERROR IN IE 10

Root Cause: IE10/11 passes an entire location of uploading a file to the server and the server does not handle it properly.

Resolution: Fixed code to handle the entire location of file and retrieve real file name.

2.5.100 9330_271

Bug ID 21269154: IMPORTING DATE ATTRIBUTE DOES NOT CONSIDER USER TIME ZONE PREFERENCE

Root Cause: For Date Only attributes, Agile import uses user time zone preference setting to convert date string to date object.

Resolution: For Date Only attributes, use GMT time zone to convert date string to date object.

2.5.101 9330_272

Bug ID 21071127: SIMPLE LIST VALUES ARE GETTING DISAPPEAR ON GENERAL INFO WHEN CLICERROR IN IE 10

Root Cause: When creating the element for simple list fields in the Manufacturer's title block, both edit mode and modify privilege are checked. So if a user has no modify privilege for the attribute, the value is not generated in edit mode.

Resolution: Only check edit mode.

2.5.102 9330_273

Bug ID 21166119: PPM PROJECT IS CREATED FROM PROJECT TEMPLATE AND THE CONTENT RULE FROM TEMPLATE DOES NOT SHOW IN PROJECT TASK

Root Cause: The get the wrong subscription when creating from template with an "affected" relationship.

Resolution: Change the get subscription method when creating from template with "affected" relationship.

Related Bug: 21302952: DISPLAY NO PRIVILEGE ON PPM REPORTS REPORTS

2.5.103 9330_275

Bug ID 21200329: PARTS ARE NOT ADDED TO CTO SELECTED CONTENT VIA SDK

Root Cause: SDK adds an object into Transfer Order's Selected Content table with its Object Class Name, not Class API Name.

Resolution: Use object Class API Name instead.

2.5.104 9330_276

Bug ID 21322467: CAN NOT ADD OBJECTS TO RELATIONSHIP TAB IN AGILE WEB

Root Cause: The response buffer flush is not correct for adding object by search.

Resolution: Set the correct response string length and refresh buffer.

2.5.105 9330_278

Bug ID 21293828: INTERNET EXPLORER 11 DOES NOT ALLOW MULTIPLE FILE DOWNLOAD AFTER 9.3.3.0.122.

Root Cause: Between different frames, postMessage does not working with IE Document Mode 7 for opener.zipFileDone() after applying 9.3.3.0.122.

Resolution: Only using it in its own frame, not different frames.

2.5.106 9330_280

Bug ID 21294565: IMPORT INCLUDING RECORD WHICH VIOLATES CHARACTER SET SETTING REJECTS ALL RECORDS

Root Cause: Import does not validate the input number against custom character set.

Resolution: Add validation for custom character set.

2.5.107 9330_281

Bug ID 21381747: ALL CHANGES TO ANY WHEN SAVING FILTER IN JAPANESE INSTANCE

Root Cause: <personalisation><sort><sortcriteria><attribute> 2000007767</attribute><order>2</order></sortcrit er ia></sort><filter> <logicOperator>??</logicOperator>

Resolution: Pass logicOperator to server with non-english.

2.5.108 9330_282

Bug ID 21380153: UNABLE TO GET THE BASELINE SCHEDULE OF GRANDCHILD ACTIVITIES US

Root Cause: This bug occurs because the baseline version is lost when loading the Schedule table.

Resolution: Add the baseline version when loading the Schedule table.

2.5.109 9330_285

Bug ID 21380153: WE ARE NOT ABLE TO MASS DOWNLOAD ATTACHMENTS FROM AN OBJECT

Root Cause: Between different frames, postMessage does not work with IE Document Mode 7 for opener.zipFileDone().

Resolution: Only use it in its own frame, not different frames.

2.5.110 9330_288

Bug ID 21482532: SETVALUE TO DATEONLY ATTRIBUTE SETS THE WRONG DATE CONVERTED BY TIMEZONE

Root Cause: If the target attribute is a Date Only attribute and the user provided parameter is a Date object, SDK will clear HOUR,MINUTE, SECOND, and MILLISECOND field of the Date object directly before calling the server side API.

Resolution: Set the time zone to GMT before clearing HOUR, MINUTE, SECOND, and MILLISECOND field of Date object for Date Only attributes.

2.5.111 9330_289

Bug ID 21487492: MERGE PATCH 20598314 (9.3.3.0.215)WITH PATCH 21322467(9.3.3.0.276

Root Cause: N/A

Resolution: N/A

2.5.112 9330_292

Bug ID 21549264: REMOVE THE CONFLICTS BETWEEN HF 199 AND HF 278

Root Cause: Between different frames, postMessage does not work with IE Document Mode 7 for opener.zipFileDone().

Resolution: Only use it in its own frame, not different frames.

2.5.113 9330_293

Bug ID 21527159: TWO PXS AT NCR WORKFLOW CLOSE 'FIRING' TWICE

Root Cause: Nested change status action is performed when a user triggers an Event PX from Web Client. Then the Event PX does a change action by SDK API to trigger the custom workflow Process Extension.

Resolution: Added next status condition validation before triggering a custom workflow Process Extension.

2.5.114 9330_294

Bug ID 21527994: DISPLAY NO PRIVILEGE ON PPM-MY DOCUMENTS REPORT

Root Cause: This is caused by the wrong report attribute privilege check when user adds the Enforce field level rea privilege.

Resolution: Change the report attributes to use Activity Class attributes.

2.5.115 9330_295

Bug ID 21328738: JAVA CLIENT DOES NOT SHOW ANY LIST FIELD VALUES

Root Cause: Something is wrong in a circle statement. We only get the first value of list, and if the first value is inactive, there no value return.

Resolution: Update the circle statement and make it sensible.

2.5.116 9330_297

Bug ID 21564387: DRAG & DROP OF MULTIPLE ITEMS TO TASK CONTENT CAUSES INSUFFICIENT PRIVILEGE ERROR

Root Cause: RevforPart value of Usercontext is not set correctly if the user added a part as a relationship row by drag & drop.

Resolution: Evaluate the read privilege. Then set RevforPart into Usercontext correctly.

2.5.117 9330_298

Bug ID 21623282: ATOS FAILS WITH TRANSMISSION NOTES ERROR

Root Cause: Null point exception.

Resolution: Check whether the object is null before using it.

2.5.118 9330_299

Bug ID 21620050: EJBEXCEPTION SHOWN IN UI INSTEAD OF CUSTOM EXCEPTION IN PROCESS EXTENSION WHILE CLOSING THE RFQ

Root Cause: The lockRFQ and closeRFQ's transaction types are "Not supported".

Resolution: Check whether the object is null before using it.

2.5.119 9330_300

Bug ID 21630080: CANNOT SELECT USER GROUP IN NOTIFY WINDOW

Root Cause: When adding a user to a user group in the UG's Escatation tab, there is a parsing error since the selected user includes the user group's info.

Resolution: Parse selected user excluding user group's info.

2.5.120 9330_302

Bug ID 21759729: HIGLIGHT OF REQUIRED FILED IS MISSING WHILE CREATING NEW OBJECTS

Root Cause: A code defect that refreshes the required fields to default values when creating a project from template fails since not all required fields are filled in.

Resolution: Corrected the code to retain user inputs instead of refreshing to default values.

2.5.121 9330_304

Bug ID 21672414: NOT ABLE TO SET THE DEFAULT VALUE IN RFQ DESCRIPTION

Root Cause: Some attributes do not have default values set.

Resolution: Set default value on these attributes when creating RFQ.

2.5.122 9330_311

Bug ID 22022371: ROOT CAUSE OF AND SOLUTION FOR POOR PERFORMING SQL STATEMENTS

Root Cause: There are performance issues with 3 queries due to the lack of indices.

Resolution: Created 3 new indices which helps avoiding full table scans and improve performance a lot.

2.5.123 9330_316

Bug ID 19915061: USER.HASPRIVILEGE(USERCONSTANTS.PRIV_DISCOVER, OBJECT) PROVIDES WR

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

Resolution: Added a new API to get the correct user context of specific role for both PX role and login user role. Also added a method in SDK to check user privilege.

2.6 PLM Release 9.3.4

This section includes Hot Fixes included in Agile PLM 9.4.0.

2.6.1 9340_2

Bug ID 20427868: PATCH FOR PLMMOBILE 3.0 934 CERTIFICATION

Root Cause: This is caused by a code defect introduced by the fix of 934 bug 17802515. When the admin side checks the criteria with "create use in &user" the Item's Cover Page is loaded and some rev related attributes are specially handled. Thumbnail ID is one of them, but the get thumbnail ID method itself does the privilege check, which calls the admin criteria check again. This is an endless loop.

Resolution: Added a flag in user context to indicate whether the current call is from admin criteria check, if yes there is no need to check privilege for thumbnail.

2.6.2 9340_3

Bug ID 20425134: AGL93 CREATE HOT FIX FOR AGILE 9.3.4 TO FIX.CALENDAR ISSUES

Root Cause: As the requirement changed, we now need to remove the calendar change restriction on parent.

Resolution: Removed the calendar change restriction on parent.

2.6.3 9340_4

Bug ID 20723499: BOM REDLINE FROM EC MCAD REMOVE COMPONENT(S) FROM WRONG REV

Root Cause: Publish BOM function is not correct for redline BOM under a pending change.

Resolution: Correct the related functions.

2.6.4 9340_5

Bug ID 20681573: SMART RULE DUPLICATE ITEM NUMBERS DOES NOT WORK DURING SAVE-AS FUNCTION

Root Cause: Duplicate BOM check is not implemented for the Item Save As case.

Resolution: Per the PM's request, added the check for Smart Rule "duplicate Item Number" when saving as BOM table. In Disallow mode the message will pop up notifying the user that duplicates are removed. In Warning mode, the message will pop up letting the user choose to save as the BOM keeping/removing duplicates.

2.6.5 9340_6

Bug ID 20772122: CAN'T UPDATE AND SAVE EXISTING ASM WITH PARTS AFTER LOAD

Root Cause: 1. When the user maps a MultiList in EC client and sets its value as empty, the EJB layer does not handle (MultiList with empty string, directly transfer empty string to List ID, then got NumberFormatException).2. Get NullPointerException error when publishing BOM for that there is a non-CAD BOM existed in an assembly.

Resolution: Added the handler for the MultiLists with empty value.Added the handle for the non-CAD BOM publish.

2.6.6 9340_8

Bug ID 20818047: PORT 933.104 AND 933.121 TO 9.3.4

Root Cause: Port 933.104 and 933.121 to 934.

Resolution: Port 933.104 and 933.121 to 934.

2.6.7 9340_9

Bug ID 20582717: MOVING THE TASK BY DRAG AND DROP ON GANTT CHART CHANGES SCHEDULE DURATION TO 0

Root Cause: This is caused by the lack of working day check for drag and drop task.

Resolution: Added the working day check when the user drags and drops a task.

2.6.8 9340_12

Bug ID 21139896: TO DO PERSONALIZE IN DISCUSSION OBJECT LOST PAGETWO INFORMATION

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

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

2.6.9 9340_14

Bug ID 21067265: ACP IMPORT ERROR: UNABLE TO RESOLVE THE VALUE

Root Cause: When migrating the default value of the list attribute, we must handle it specially.

Resolution: Added special handler for default value of list attribute via ACP.

2.6.10 9340_18

Bug ID 21147812: HYPERLINK MISSING IN PX PUBLISH HTML

Root Cause: The 934 CCB 15 did a security enhancement which filters HTML hyperlink markups.

Resolution: Loosen the security restriction to allow HTML hyperlink like <a href='' target='_blank'/> on protocols: HTTP, HTTPS and mailto.

2.6.11 9340_20

Bug ID 21179498: ACP IMPORT ERROR - (MSGID = 20092)

Root Cause: In the server side, an exception is thrown when inserting records to langtable with a non-English user.

Resolution: Need to handle this special exception when importing attributes for non-English user.

2.6.12 9340_22

Bug ID 21343461: CAN NOT REDLINE BOM FROM SOLIDWORKS EC

Root Cause: When trying to redline a BOM and/or transfer find numbers from CAD to PLM, the wrong Item table (BOM vs. Redline BOM) was used in certain cases, especially if the Item is on a pending change.

Resolution: The correct Item table (BOM or Redline BOM) is used when redlining or transferring find numbers.

2.6.13 9340_23

Bug ID 21298454: MFR PARTS CANNOT BE CREATED DUE TO HARDCODED ID 1488

Root Cause: The hard-coded id 1488 in the fix of 14506225 introduced the issue. If the customer removes the default subclass and uses the newly created Manufacturer Part subclass, the error shows up when getting the subclass node (1488).

Resolution: Get the attribute name via class id instead of subclass id.

2.6.14 9340_24

Bug ID 21330270: REDLINE DATA SHOULD NOT BE LOST UPON RELEASING A CHANGE

Root Cause: The instruction in #16868125 is in conflict with the FDD DOC006747.

Resolution: Roll back the behavior change introduced by #16868125 and return to the original design.

2.6.15 9340_25

Bug ID 21419626: OOB [PRE-SALES]STREAMING FILES GET CORRUPTED AFTER VIEW COMAPRE

Root Cause: 934 WS implement changes from Axis to JRX-WS, and code changes lead xRef array from null value to empty array, but the Where Used xRef array still acts as if it is null value.

Resolution: Also judge xRef array as if it's empty.

2.6.16 9340_26

Bug ID 21433664: FORMAT OF VALUE FOR DATE ATTRIBUTES CAUSES TROUBLE ON THE CLIENT SIDE

Root Cause: The Date attribute value is not formatted correctly.

Resolution: Format the Date attribute value into string as yyyy-MM-dd'T'HH:mm:ss.SSS'Z' in GMT timezone.

2.6.17 9340_27

Bug ID 21443752: PGC DECIMALS WRONG

Root Cause: The BOM Quantity is rounded in external rollup.

Resolution: Change the type definition of the staging table used during external rollup so the actual Quantity will be used.

Related Bug: 21443796: INVALID CALCULATIONS DUE TO MULTIPLICATION AND/OR ROUNDING RESULTS

2.6.18 9340_29

Bug ID 21418555: UNABLE TO ADD MULTIPLE VALUES IN AFFECTED ITEMS TAB OF ECO ON WEB

Root Cause: The manually-entered value and Copy & paste value is not handled properly.

Resolution: Refix bug 17161067. Combine manually-entered value and pasted value.

2.6.19 9340_31

Bug ID 21459641 EC CORRUPTS BOM OF EARLIER RELEASED REV

Root Cause: The BOM batch redline logic serving the MCAD tool in A934 has a defect and leads to the current issues.

Resolution: Add the missing logic.

2.6.20 9340_33

Bug ID 21187466: LOAD DRAWINGS OPTION IN AGILE LOAD PREVIEW IS NOT WORKING

Root Cause: After 934 performance improvements for EC services, it does not load the drawing for all child part and sub assemblies.

Resolution: Add the load logic for all child part and sub assemblies.

2.6.21 9340_34

Bug ID 21486539: ATTRIBUTE 'FILE TYPE' IN ATTACHMENTS TAB IS EMPTY FOR FILENAMES WITH PARENTHESIS

Root Cause: The manually-entered value and copy & paste values are not handled properly.

Resolution: Refix bug 17161067. Combine the manually-entered value and pasted value.

2.6.22 9340_35

Bug ID 21563788: HTML HEX ENTITY CHARACTERS IN THE IMPORT LOG FILE

Root Cause: The encodeForHTML method causes the coding problem.

Resolution: Remove the code of encodeForHTML method.

2.6.23 9340_36

Bug ID 21538347: 9.3.4 IS LOOKING AT THE CHANGE AS A WHOLE AND NOT LIKE PLM 9.3.3

Root Cause: A code change in 934 mistake the criteria check for all AI instead of for the current AI for each one.

Resolution: Correct the logic.

2.6.24 9340_37

Bug ID 21602668: UNABLE TO GO BACK TO FILE LIST AFTER OPENING THE FILE IN ZIP FILE

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

Resolution: Do not create the CMF for the ZIP file.

2.6.25 9340_38

Bug ID 21659926: ITEM WITHOUT THE SPECIFIC SITE IS NOT ADDED TO SCO'S AFFECTED ITEM

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

Resolution: When auditing release, set the side id and pass it to the request when clicking the audit link.

2.6.26 9340_39

Bug ID 21696588: ACP IS NOT ABLE TO MIGRATE THE WORKFLOW CONFIGURATIONS PROPERLY

Root Cause: New attributes are missing in ACP.

Resolution: Added password required attribute in ACP.

2.6.27 9340_40

Bug ID 21697331: OBJECT NUMBER CONVERTS TO UPPER CASE WHEN USING IMPORT

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

Resolution: Overwrite the method createRealObjNumberCollection to support upper/lower/mixed case for creating Item/Manufacturer/Manufacturer Part.

2.6.28 9340_41

Bug ID 21762536: AGILE LDAP USER SYNC NOT WORKING FOR GENERIC LDAP CONFIGURATION

Root Cause: For a generic LDAP server, it needs to map objectGUID atribute to entryGUID in groovy script, but the map value is not saved into the Agile user.

Resolution: Added code to save the values.

2.6.29 9340_42

Bug ID 21636998: AUDIT STATUS SHOWS FALSE MESSAGE IN AGILE 934 FOR ITEMS WITH NO SITE

Root Cause: An API created a wrong answer. This made an invisible attribute go through the required fields check.

Resolution: Use another API to find the visible attributes, and if the target attribute is not in these attributes, the required fields check will not occur for this attribute.

2.6.30 9340_43

Bug ID 21799700: GETOBJECT WEBSERVICE NOT WORKING FOR PROJECT OBJECTS

Root Cause: The admin metadata is incorrect. The data type of attribute 2000000100 is integer.

Resolution: Run the SQL script to correct the data type to be double for attribute 2000000100.

2.6.31 9340_44

Bug ID 21758012: CURSOR FOCUS NOT IN FIRST EDITABLE FIELD

Root Cause: 934 ME-001 project (Two Columns project), fields have new CSS classes assigned.

Resolution: Code to set focus on fields honors the Two Column mode.

2.6.32 9340_45

Bug ID 21769583: NUMERIC ATTRIBUTES CONFIGURED WITH A SCALE DOES NOT SHOW CORRECTLY

Root Cause: Numeric attributes keep the trailing zeros.

Resolution: Remove the trailing zeros for numeric attributes.

2.6.33 9340_46

Bug ID 21699540: BOM SHOULD BE PUBLISHED TO SPECIFIC SITE DEFINED IN

Root Cause: EC web service implementation does not send the specified site to PC server and the PC side handles the site information even if it tries to get it.

Resolution: Make sure the specified site is sent to the PC side and the PC side can publish the structure to the site correctly.

2.6.34 9340_47

Bug ID 21841460: SCALE CANNOT BE CHANGED ON SOME PART COMPLIANCE ATTRIBUTES

Root Cause: Scale, Min Value and Max Value properties of the following 15 attributes are disabled and not to be editable: Parts.Compliance.Substances.Numeric01~Numeric10 Specifications.Substances.Numeric01~Numeric05

Resolution: Scale, Min Value and Max Value properties of the above 15 attributes are enabled and editable.

2.6.35 9340_51

Bug ID 21897832: AGILE IMPORT SCREEN REFRESHING FOR EVERY ATTRIBUTE MAPPING USING CHROME

Root Cause: We disable the cache of some HTTP requests for a security fix, but this leads to load images used by the import functionality every time.

Resolution: Enable the cache of the static resources, for example, images.

2.6.36 9340_53

Bug ID 21896804: IMPORTANT CONTENT WIDGET OF THE SUMMARY DISPLAYS: APPLICATION ERROR

Root Cause: This is a code defect. Values of some variables are not cleared up in a loop, which leads to disproportionate parameters while compiling SQL

Resolution: Added code to clear values of the variables at the end of the loop

2.6.37 9340_54

Bug ID 21802941: AUTOVUE FOR AGILE TAKES MUCH LONGER TO OPEN FILES COMPARED TO STAN

Root Cause: Two factors - 1. Pinging DFM costs a lot of time. 2. When replicating, checking file exists WS call also costs a lot of time.

Resolution: 1. The ping action was corrected to have a normal ping servlet approach.2. Removed file exists WS call, and used getfile size WS call instead.

2.6.38 9340_55

Bug ID 21873266: EXTERNAL ROLLUP RETURNING INCONSISTENT & INCORRECT CALCULATED CONC RESULTS ON SP

Root Cause: 1. External rollup by default use "g" as standard UOM, but the system UOM can be customized in Java Client.2. External rollup does not handle a threshold of 0 PPM correctly when calculating the rollup result.3. There are duplicated rows in SPECIFICATION_SUBSTANCES table, which is generated during external rollup. The duplicated rows look like bad data resulted from multiple threads of external rollup.

Resolution: 1. In the external rollup procedure, when putting data into the result table the UOM field should be determined by Java Client configuration.2. Updated the logic to take 0 in consideration in such a scenario.3. DISTINCT keyword can be used to resolve the problem.

Related Bug 21874436: PART OF PATCH 9.3.2.167 NEEDS APPLYING TO EXTERNAL ROLLUP BATCH JOB

2.6.39 9340_63

Bug ID 22092496: 9.3.4 WEB SERVICES ARE NOT RETURNING CORRECT RESPONSES ON LINUX SYSTEM

Root Cause: Oracle JAXP document builder instance which does not support reset feature, is loaded and created.

Resolution: Specify to use apache xerces JAXP document builder implementation.

2.6.40 9340_74

Bug ID 22092496: AXML EXPORTED BY AGILE CONTENT SERVICE HAVE NO REDLINES WHEN BOMNO

Root Cause: Empty tag was removed when fixing bug 14835608.

Resolution: Populate empty tag to reflect the redline delete action, if the new value is empty and old value is not empty.