| Agile Product Lifecycle Management Readme Release 9.3.4 E52160-02 |
|
 Previous |
 Next |
Hot fixes included in this product release are:
This section includes Hot Fixes included in Agile PLM 9.3.0.1.
Bug ID 17156140: PERM GEN OUT OF SPACE ISSUE WITH REFRESHINSTANCE
Root Cause: The SDK client always creates a new NetworkClassLoader instance even for the same cluster node when calling AgileSessionFactory.refreshSessionEx. The class loader instance that is held by the Weblogic thread, cannot be released. After many calls, too much class loader eats all of the PermSpace memory.That cause an OOM error.
Resolution: Only create one class loader instance for each cluster node and cache it. Next time, try to get the class loader for the same cluster node. Try to get it from cache first.
Bug ID 17252425: CANNOT REDLINE SPECIFIC ATTRIBUTE IN AFFECTED ITEMS.PAGE 2 FOR PART
Root Cause: If the list value includes a single quote mark, when calling the eval() function, the corresponding JS function cannot be executed correctly.
Resolution: Replace a single quote mark with '.
This section includes Hot Fixes included in Agile PLM 9.3.0.2.
Bug ID 16845732: WORKFLOW CHANGE STATUS TAKES A LONG TIME FOR PQM OBJECTS
Root Cause: When the user does a change status action on a PSR object, the system checks the quality analyst list for notify list, but the system loads user objects one by one when it checks if a user is enabled, so this costs much more time.
Resolution: Load the enabled user object information from the database at one time.
Bug ID 16692298: IQUERY.GETRESULTATTRIBUTES FOR PROJECT DOES NOT RETURN THE CONTENT
Root Cause: The getResultAttributes function does not resolve the related content attributes for this query.
Resolution: Created a new API, getRelatedContentAttributes, to return the related attributes.
Bug ID 17157211: ENTRY REQUIRED FIELDS FOR PENDING STATUS DO NOT WORK EVEN WHEN REQUIRED FIELDS ARE SET
Root Cause: When the user selects a workflow and does a save action on a pending status, even if the entry required field(s) which were set on pending status have been filled in, the system still treats the fields as if they are blank.
Resolution: If the field(s) are modified, these field(s) are flagged by the related dirty attribute(s), so do not check these dirty attribute(s) in the system background.
Bug ID 17201399: WORKFLOW CHANGE STATUS TAKES LONG TIME FOR PQM OBJECTS
Root Cause: 1. For the case where the status of the PSR object is moved to Cancel or Closed, the system checks each Affected Item in the current PSR object for whether it has related PSRs, but in this business process, the system loads all of the related PSR objects one by one of each Affected Item first. If there are a lot of related PSRs, it will cost a lot more time.2. For the case which removed one or more Affected Items from the PSR object, the system checks the removed Affected Items for whether they have related PSRs, but in this business process, the system also loads all of the related PSR objects one by one of the removed Affected Items first. If there are a lot of related PSRs, it will cost a lot more time.
Resolution: The system checks only needs related PSRs' ID and status fields for checking, so load these 2 fields' data of all the related PSRs of the Affected Items from the database one time.
Bug ID 17205810: UNABLE TO EXECUTE PERSONAL PQM REPORTS (ERROR: UNKNOWN NUMBER: OBJECT
Root Cause: Saved search can be removed, even if it has been used in a customer report or schedule. When a saved search is removed, the queryid is deleted, so a report that uses the saved search cannot find the queryID, which causes errors.
Resolution: Do not allow the end user to delete a saved query if the saved query is being used by other clients such as Dashboard/Report, and display the following error message: ”This query {0} cannot be deleted due to it's used in Dashboard /Report.”
Bug ID 17235113: NOT RECEIVING EMAIL NOTIFICATIONS
Root Cause: The Notification task picks up all pending notifications to send. Processing a huge pending notification causes a timeout. In the customer's case, it has more than 70,000 pending notifications. The time out setting is 30 minutes. It throws a time out exception and rolls back the transition. Therefore, the user cannot receive notifications.
Resolution: Add a notification process batch size to avoid an exception during a non-time out period. The batch size is configurable in agile.properties.
Bug ID 16941954: REMOVE AGILE RESTRICTION WHICH PREVENTS ITEM SYNCH FLOW FOR RELEASE
Root Cause: Agile PIP code has restriction to synch an Item when released.
Resolution: Item release status restrictions have been removed to synch.
Bug ID 17292147: BULK EDIT (INCLUDES CREATE/UPDATE/DELETE ROWS) SDK API SUPPORT
Root Cause: Agile SDK API does not exist to support this bulk functionality for the PSR's Affected Items tab.
Resolution: SDK added three new APIs for PSR's Affected Items tab to bulk Create/Update/Delete rows.
Bug ID 17386296: AGILE/PQM - CONSISTENTLY AND RANDOMLY ENCOUNTERED THE ISSUE WITH ?
Root Cause: When doing a status transition for a routable object, the code locks all Affected Items, regardless of whether they've been modified or not. If there are many Items related to thousands of PSRs, there is a high possibility for a lock error occurs.
Resolution: For a PSR object, 1. Only lock all Affected Items when changing from/to Cancel/Complete status 2. When executing this transition, do not lock the AI's related changes when invalidating their AI tab.
Bug ID 17438553: VERIFY TO CLOSE TAKES A LONG TIME FOR PQM OBJECTS
Root Cause: For the case without auto-promote, when changing status from Verify to Closed, the system refreshes all of the PSR's Affected Items' related redlined tables. In this process, all of the redlined BOM and MFR info of each PSR Affected Item is loaded to the cache first, which results in wasted time.
For the case with auto-promote, half of the cases were the same as the case without auto-promote, but when changing status automatically from Closed to Complete, the system updates the flags of all of the PSR's Affected Items' related change objects, in this process, all of the change objects of each PSR Affected Item would be loaded to the cache first, so more time is spent.
Resolution: Load all of the redlined BOM and MFR info of PSR Affected Items from the database one time. Load all of the Change objects of PSR Affected Items from the database one time and batch update the flags of each PSR Affected Item's Change objects.
Bug ID 19214325: AGILE NUMERIC OVERFLOW ERROR
Root Cause: The Sequence generator ID (AGILEOBJECTIDSEQUENCE) was exhausted due to design defect.
Resolution: 1. For the Core: Collect the reusable sequence blocks (with default threshold number 5000) and store the reusable gap info into "gap_table", create new stored procedure to fetch the id for the Agile system;2. For the History tables and "refdesig" table: Provide 3 new sequences for ”change_history”, ”item_history” and ”refdesig” table, use a negative int for new data of the above 3 tables;3. For Search: (1)Provide a new sequence for the search module, drop "ID" column from the "criteria" table, (2) Re-order query ids for existing rows in "query", "criteria", "select_list" tables, and update reference query id in the related tables.
Bug ID 18851831: REDLINE DATA NOT CLEAR WHEN SITE IS DELETED
Root Cause: The phantom cache is not cleared when invalidating the cache.
Resolution: Clear the phantom cache.
Bug ID 19630738: PUBLISH ITEM BALANCE UPDATES AGILE PIP PROGRAM ERRORS IN SOA
Root Cause: There is a static member variable called SimpleDateFormat in PXUtil.java. It will be shared for all the thread when a date is parsed/formatted, but SimpleDateFormat is not thread safe.
Resolution: Put the SimpleDateFormat into ThreadLocal to make sure that each thread has its own instance of SimpleDateFormat.
This section includes Hot Fixes included in Agile PLM 9.3.1.0.
Bug ID 16902850: SUB-ASSEMBLIES ARE COMING OVER AS A SINGLE COMPONENT (MISSING SUB-ASSEMBLIES)
Root Cause: The current procedure, addBomRowEx, may get an incorrect BOM flag for certain cases. When adding an Item to a Souring Project, the incorrect flag based on the procedure will lead to this issue.
Resolution: Added a constraint clause in procedure, addBomRowEx, to get the correct BOM flag. After the procedure has updated, 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.
Bug ID 17403502: ASSEMBLY AND CHILD PARTS ARE MISSING FROM SOME SKUS IN ACR FOR BEST SUPPLIER
Root Cause: When two assemblies have the same component and the added supplier is a partner, the child part of one assembly is filtered out.
Resolution: When the user selects best supplier and runs the ACR report, only load the best response lines to ensure that the child parts will not be filtered out.
Bug ID 17436637: COSTED BOM COMPARISON SHOWS 0 PRICE FOR SUPPLIER/PARTNER
Root Cause: This issue occurs on a specific structure when there is an Item with AML and the user adds a partner for quote. When the user saves it as a Sourcing Project and looks it up from a target, due to our code defect, if handles this particular Item structure for look up, it inserts the incorrect data to our database. When the Cost BOM Comparison report and ACR are run, they get the wrong result.
Resolution: Fixed the code to get the correct partner key and type for the specific structure which is Item with AML and add only partner for quoting.
Bug ID 17511662: EXPORT OF THE ANALYSIS TAB DISPLAYS NULL FOR IPN AND MPN MULTILIST
Root Cause: There is no current handler for dynamic lists.
Resolution: Add code to handle dynamic list.
Bug ID 17596257: PUBLISHED PRICE TO ITEM NOT SHOWING DUE TO LAST CHANGE BEING DEVIATED
Root Cause: The old logic of the Publish Price function is as follows:
Publish the price to the latest released change of the Rev that is added to the Sourcing Project. When the latest change is a deviation, the price is published to the deviation revision, but in the PC side, the Item Rev does not show deviation, so we are unable to see prices under Price tab of the Item.
Resolution: Change the logic of the Publish Price function to be as follows:
Publish the price to the latest released non-Deviation change of the revision that is added to the Sourcing Project. We provided a script to correct the existing prices that have the issue.
Bug ID 17575434: CANCELLED ECO WITH THE ITEM REVISIONS APPEAR IN THE SOURCING PROJECT
Root Cause: For Sourcing Project, Change Deviation can be searched for in the search dialog and cancelled Changes, such as ECOs, should not be searchable under option, Released Rev.
Resolution: Added a special handler for Sourcing Project for both search behaviors.
Bug ID 17890538: WHERE USED TAB IS NOT SHOWING ALL THE PARENTS
Root Cause: When unreleasing Change objects, we reset the Where Used flag of the Affected Item's BOM. If the BOM with the site was not changed by the latest change object, the Where Used flag of the BOM is set to 0.
Resolution: Make sure the Where Used flag is set to 1 if the BOM has been added in previous changes, but not redline deleted in the current change.
Bug ID 17940073: TRANSACTION TIMEDOUT WHEN ATTEMPTING TO REMOVE AFFECTED ITEM FROM PSR OBJECTS
Root Cause: When the user removes Affected Items from a PSR object, the system checks the removed Affected Items to see if they have related PSRs, but in this business process, the system loads all of the related PSR objects one by one for each removed Affected Items, so if there are a lot of related PSRs, it costs more time.
Resolution: The system only needs related PSRs' ID and status fields for the check, so load these 2 fields' data from the database from all of the related PSRs once time.
Bug ID 18017579: JRE 7 U51 UPTAKE
Root Cause: JRE 7u51 security changed.
Resolution: Add the Permissions and Codebase attributes in the MANIFEST.MF file for all signed JAR files.
Bug ID 18119899: UNABLE TO SAVE: AGILE ITEM P3 FIELD MODIFICATIONS
Root Cause: When updating an Item's attribute, the trigger PSR's refreshing AI event is triggered. The system also checks whether the update violates the workflow/status criteria for PSR objects. Performing such actions take a lot of time if the Item has a large number of associated PSRs.
Resolution: 1. Improve such actions with a better way, via DB access directly, rather than loading the table. 2. Only trigger the refresh AI event when it is used in the PSR's AI.
Bug ID 17588522: JAVAX.XML.TRANSFORM.TRANSFORMEREXCEPTION: JAVA.LANG.RUNTIME
Root Cause: The ACR report generated by SDK-API is an XML file and attribute "RM Cost (kg)" is transformed as an XML Tag name, but the parenthesis character is invalid as an XML tag name.
Resolution: Make the XML file valid by removing the parenthesis in the XML element.
Bug ID 18768142: AGILE CONFIGURED PX/EVENTS WIPED OFF
Root Cause: The created javax.naming.InitialContext loses the application environment property "java.naming.factory.initial", when it is cached as static member of InitialContextHolder.
Resolution: If the server Type is OAS, return a new InitialContext every time.
Bug ID 19168569: SLOW PERFORMANCE TO REORDER PAGE THREE ATTRIBUTES FOR SUBCLASS
Root Cause: When Agile displays a pop up reordering window of attributes, it gets properties of each attribute. For the criteria-based lists, it loads the results through search API, which takes time.
Resolution: When building each attribute, do not load the result of a criteria-based list.
This section includes Hot Fixes included in Agile PLM 9.3.1.1.
Bug ID 16926889: ATTRIBUTE UPDATES & WORKFLOW STATUS CHANGES ON TASKS ARE TAKING UNACCEPTABLY LONG TIME (2 MIN/TASK)
Root Cause: 1. Navigator is refreshed when the P2/P3 attribute value is changed.2. The whole template project, including its children, is loaded when we get the template project name.
Resolution: 1. Do not refresh the Navigator when changing a P2/P3 attribute value.2. Load the template project only when getting the template project name.
Bug ID 17161299: EXPORTED SEARCH RESULT OVER PAGE TWO COST FIELDS DOES NOT SHOW THE CURRENCY
Root Cause: Money is a special type, but we do not handle both value and currency for the search and export side.
Resolution: Added a special handler for the Money type, so we can catch value and currency and display it.
Bug ID 17179623: PERFORMANCE ISSUES WHILE USING SAFARI
Root Cause: This issue is caused by XMLHttpRequest timeout. For Safari, XMLHttpRequest has a default timeout of 10 seconds. It throws an exception when there is a timeout, but other browsers do not have this kind of issue.
Resolution: 1. Since there is a bug with Safari(5+) synchronous XHR, we now use asynchronous XHR instead of synchronous XHR when saving the BOM Redline table changes.2. To prevent the user from doing other operations when saving the BOM Redline table, freeze the UI.
Bug ID 17433575: CONTENT PAGE OF PROGRAM TAKES SEVERAL MINUTES TO LOAD
Root Cause: The view, All Document, that was created by the customer has a filter. Currently, we do not use cache for PPM's Relationships table. Therefore, for each record, it calls the database one time. That is why the tab opens so slowly.
Resolution: Use cache for PPM's Relationships table.
Bug ID 17601157: INCORPORATED PART IS SHOWING AS UNINCORPORATED WHEN ACCESS FROM WHERE USED TAB
Root Cause: In an Item's Where Used tab, the classid for parent-item's default change is incorrect.
Resolution: Set classid for parent-item's default change.
Bug ID 17157108: PHASE GATE ORDERING IS INCORRECT
Root Cause: When the user removes several activities under the Schedule tab of a Program, the remove order is random. This causes the display order of the remaining activities to be incorrect.
Resolution: Remove these activities in descending order according to their display order.
Bug ID 17271555: EXPIRATION DATE IS OFF BY ONE DAY WHEN THE DATA IS E
Root Cause: Date Only attributes showed Date and Time in UI/Report.
Resolution: Fix those attributes to show Date Only in UI/customer specific Reports.
Bug ID 17666049: AGILE CORE WEB SERVICES IS CREATING PARTS WITH INACTIVE PRODUCT LINE
Root Cause: The server uses the value that the Web Services client passes no matter if it is active or not.
Resolution: Use the active value for production line only. For other lists, we did not change the behavior.
Bug ID 17707018: CANNOT RELEASE SUBSTANCE DECLARATION WITH MORE THAN 1000 MPNS
Root Cause: This is caused by an Oracle database limitation. The key word 'in' in a PL/SQL statement can only add 1000 parameters.
Resolution: If the list is beyond 1000, correct the PL/SQL statement that there is no limitation like '(table.column,0) in ((1,0),(2,0)...)'.
Bug ID 17782397: ISSUE IN PROMOTION OF CHANGES WHEN FIRST LEVEL BOM COMPONENTS ARE GREATER
Root Cause: In a Safari browser, if the HTTP response time exceeds 10 seconds. by using an AJAX sync call, the browser throws a response timeout error and then hangs.
Resolution: Use an AJAX asynchronous call instead of synchronous.
Bug ID 17882549: OUTPUT OF REPORT IS CORRUPTED.WHEN RUNNING BOM COMPARISON REPORT
Root Cause: The BOM Comparison Report fails when a text attribute includes too many spaces in the BOM table. The report does not handle it well and consumes too much system memory.
Resolution: Optimize the method in the ReportTemplates.xsl file.
Bug ID 17952748: AGILE OOTB FUNCTIONALITY DOES NOT REMOVE SOME OF THE CONFLICTING REDLINES
Root Cause: When the released change had BOM redlines that conflict with the BOM redlines of other pending change(s), the system checks the same BOM of the Affected Items in pending change(s) and removes the related redlines. If the redlined BOM is newly added in pending change(s), the system does not remove it even it has the same BOM number of the Affected Item.
Resolution: Remove the redlined BOM which was newly added in pending change(s), if it has a redline conflict.
Bug ID 18017597: JRE 7 U51 UPTAKE
Root Cause: JRE 7u51 security has changed.
Resolution: Add the Permissions and Codebase attributes in the MANIFEST.MF file for all signed JAR files.
Bug ID 17562647: AGILE HISTORY SHOWS WRONG USER UPDATE
Root Cause: No user information is persisted when an attribute is redlined.
Resolution: Persist redline information to an additional column of the existing table and read user information from that table when the history log is built.
Bug ID 18129168: INCORRECT ADVANCED SEARCH RESULT WHEN PRICE QUERIED BY PRICELINE A
Root Cause: This issue is caused by 9302.1. All Price revs are included in the search scope, not just the latest rev.
Resolution: For Pricelines search:1. If the General Information.Version attribute appears in the format, the result covers all Prices, so maintain the current behavior.2. If the General Information.Version attribute does not appear in the format, the result only covers the latest Prices. There is similar behavior for the File Folders and Item objects.
Bug ID 18172423: AGILE BOM - MANUFACTURER BOM REPORT - ERROR: AN UNEXPECTED ERROR HAS OCCURRED
Root Cause: There is no handler for exceptions that are thrown from privilege checking in the Manufacturer BOM Report.
Resolution: Add the code to handle it.
Bug ID 18250767: WRONG REFERENCE DESIGNATORS WHEN RUNNING LEGACY BOM COMPARISON REPORT
Root Cause: When producing the report, attributes of child items are read mistakenly besides current item's.
Resolution: When retrieving BOM data only read current item's attributes.
Bug ID 18270053: 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 3 times recursive BOM check. 2. When releasing a large BOM with recursive data, there are additional complete scans in the BOM recursive check, which takes a lot of time.
Resolution: 1. Invoke doAuditStatus(along one time with 1 time recursive BOM check. 2. If it has 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 checking in "sync mode", but have to inform the administrator to identify (execute a script) and remove the recursion, and then release the change.
Bug ID 18402621: NOT ABLE TO CLOSE RFQ DUE TO EXCEPTION
Root Cause: There are more than 100 responses for RFQ 9140000019; that means that the server needs to load more than 100 ResponseEBean, but in sourcing-weblogic-ejb-jar.xml, it sets the "<max-beans-in-cache>100</max-beans-in-cache>".
Resolution: Enlarge the setting from 100 to 200.
Bug ID 18897151: AGILE THREAD POOL HAS STUCK THREADS
Root Cause: When trying to determine the next revision number for an Item, it is possible to end up with stuck threads on the server.
Resolution: The method to determine the next revision number was fixed to prevent stuck threads.
Related Bugs:
19140821: SUPPORT OF MANUALLY ASSIGNED NON CHANGE ORDERS TO ITEM
19266763: LIFECYCLE PHASE IS BLANK ON SAVE PREVIEW
Bug ID 19217489: USER USAGE REPORT IS INCOMPLETE WITHIN A GIVEN TIME PERIOD
Root Cause: The User Usage Report missed a user, whose login id included a quote symbol, and its nearby users.
Resolution: Use PrepareStatement set parameter instead of merging the SQL string.
This section includes Hot Fixes included in Agile PLM 9.3.1.2.
Bug ID 14301300: REMOVE AGILE RESTRICTION WHICH PREVENTS ITEM SYNCH FLOW FOR RELEASED ITEMS
Root Cause: Logic based on check whether item's@ RN-status is ReleasedChanges or PendingChanges
Resolution: removed the logic to REMOVE AGILE@ RN-RESTRICTION WHICH PREVENTS ITEM SYNCH FLOW FOR@ RN-RELEASED ITEMS
Bug ID 16920043: AGILEEC AUTONUMBER GENERATION VIA 123 BUTTON CAUSES ITEM TO BE OVERWRITTEN
Root Cause: AdminMetaData Web Service had an issue where it was not considering the AgileClass to fetch the sequence. It always returned a normal sequence irrespective of class/subclass name.
Resolution: Added the condition to pass the agileClass to getAutoNumber method.
Bug ID 17186661: ORACLE AXML XSD VALIDATION ERROR
Root Cause: The missing declaration causes a validation error.
Resolution: Add missing declaration in the XSD file.
Bug ID 16918240: LIFECYCLE LIST ON AFFECTED ITEMS (AI) TAB OF CHANGE WENT FROM SIMPLE AI SPECIFIC LIST TO LIST FOR ALL ITEMS-LIFECYCLE
Root Cause: When the attribute Lifecycle Phase appears as search box, it fills with all of the Lifecycle Phase options of the base class (that the AI class belonged to), class (all under the base) and subclass (all).
Resolution: As per the customer's request, change to Lifecycle Phase of the base class (that the AI class belonged to), class (the AI class belonged to) and subclass (the AI class). Also, removed the prefix before LCP.
Bug ID 17009963: CUSTOM BI TEMPLATE FOR MANUFACTURER BOM REPORT DOES NOT DISPLAY PAGE TWO ATTRIBUTE
Root Cause: The P2/P3 data cannot be loaded for customer BI of Manufacturer BOM Report.
Resolution: Fix these issues.
Bug ID 17010487: EXPORTING DATA AS CSV WORKS, BUT EXPORTED EXCEL IS UNABLE TO OPEN (CRASH /TIMEOUT)
Root Cause: The Report Export function treats HTML as EXCEL for output data.
Resolution: Fix issues.
Bug ID 16991148: UTILIZATION REPORT ON USER FAILS WITH FEATURE DID NOT PERFORM AS EXPECTED
Root Cause: Selected row does not exist in grid data model.
Resolution: Reload data model, if selected row does not exist.
Bug ID 17045578: UNABLE TO CANCEL TASKS WITH PROJECT STATE IN PROPOSED THROUGH SDK
Root Cause: UI for Actions Cancel has additional capabilities to cancel the entire tree. This should also allow the same capability to initiate a Cancel when in Proposed status in the SDK call.
Resolution: Add an SDK capability that tracks the UI Actions Cancel.
Bug ID 17015407: ERROR RETURNED INSTEAD OF RESULTS FOR A SAVED SEARCH
Root Cause: The relational operator is set to a wrong value.
Resolution: Change attribute operator value when generate a query bean.
Bug ID 16674988: UNABLE TO LOGIN TO NODE 2 OF AGILE APPLICATION SERVER
Root Cause: Missing system list.
Resolution: Make the list non-deletable.
Bug ID 16717715: MOVING ITEMS ONTO THE CHANGE ORDER THROWS UNKNOWN NUMBER: OBJECT DOESN'T EXIST
Root Cause: When the user adds Affected Items with attachments, sometimes, it takes about 15-20 minutes and throws an ”Object does not exist.” error. Based on a previous HF 9.3.1.1.234, it seems like this may be caused by file recursive copying or perhaps the file was deleted in the vault.
Resolution: By following the solution of HF 9.3.1.1.234, prevent the file from copying recursively and show an error message if the file can not be found in vault.
Related Bug:
16702399 - MOVING ITEMS ONTO THE CHANGE ORDER THROWS UNKNOWN NUMBER: OBJECT DOES NOT EXIST.
Bug ID 17188980: SEARCH ERRORS WHEN ADDING 'RELATIONSHIP' ELEMENTS TO REPORT OUTPUT
Root Cause: The SQL generated by the relationship search is not efficient. It joins one exceed table, which causes a huge amount of data to be returned, and causes database issues from like "unable to extend temp segment.”
Resolution: Get rid of the exceed table in the SQL statement.
Bug ID 17190888: COMMODITY DOES NOT APPEAR IN SOURCING PROJECT
Root Cause: This is a design issue. The old logic is such that the PCM Commodity attribute is mapped to item.partFamily.
Resolution: Change the logic. If the Smart Rule Force Commodity and Part Family to be Identical is set to Yes, then in most cases the Commodity attribute will not be enabled and the Commodity should be mapped to Part Family. If the Smart Rule Force Commodity and Part Family to be Identical is set to No, then the mapping should be to Commodity.
Bug ID 17190181: CONTACT USER IS UNABLE TO REMOVE REDLINES - INSUFFICIENT PRIVILEGE
Root Cause: When doing a redline action on Manufacture Parts, the user could remove Manufacture Parts without the modify privilege.
Resolution: Check the modify privilege before doing a remove action.
Bug ID 17187421: DATE APPEARS DIFFERENTLY BETWEEN ADVANCED SEARCH AND EXPORTED EXCEL
Root Cause: The DateFormat of export is written to date-time in default, and it is not controlled by Java Client.
Resolution: Add condition to control date format for export.
Bug ID 16989880: UNDO REDLINE FEATURE IS ENABLED IN RELEASED PCO
Root Cause: Do not disable add/remove/undo redline buttons if PCO was released.
Resolution: Disable add/remove/undo redline buttons if PCO was released.
Bug ID 17088533: EVENT TRIGGER ON ITEM CREATION WITH NULLPOINTER ERROR
Root Cause: Site information is not needed to add an Item into the selected object table of a CTO.
Resolution: Remove the line of code which is gets the site information from the Item object.
Bug ID 17297838: ERROR WHILE IMPORTING THE SMALL NUMERIC VALUES SUCH AS 0.0001, 0.0
Root Cause: 0.0005 0.00001 and so on will be formatted as 0.00050 or 0.000010 by BigDecimal tool class, so it adds an additional zero so that the scale length is not as expected.
Resolution: Use # of NumberFormat to remove the last zero of the decimal.
Bug ID 17369397: SUPPORT MULTI-THREADED CLIENTS
Root Cause: When switching an event Process Extension (PX) or the EC Solution pack to asynchronous mode, the same objects that are processed by EC Services (namely createUpdateObjects) might be changed by the PX at the same time. This can cause concurrency issues, meaning EC services will see that an object is modified or someone is working on the object errors. To accommodate these errors, retry logic had been added to retry the failed operations. This retry logic only retries for a given number of times while increasing the times between the retries. There are new general parameters for createUpdateObjects for the number of retries (retry-count) and the interval time (retry-interval).
Resolution: Added retry logic to accommodate asynchronous changes like modified objects and locked objects. It was also ensured that the new multi-threaded MCAD client works properly with EC Services.
Related Bugs:
Bug ID 17381683: SAVE OF TOP ASSEMBLY FILE ONLY SAVES TOO MUCH AND IS TOO SLOW
Bug ID 17375104: GETTING BAD INDEX: 1 OF 1 ERROR
Root Cause: The wrong index is used to get the object in the folder, which causes a IndexOutOfBoundsException.
Resolution: The code was corrected to use the right index to get the corresponding value.
Bug ID 17403256: VIEWING FILE ATTACHMENTS WITH AUTOVUE IS VERY SLOW
Root Cause: When opening the attachment of an Item, the system checks the Item rev in the related Change object, but in this process, the system loads all of the Affected Items of the Change first, so this causes a potential performance issue. The more Affected Items, the more time needed for loading the objects.
Resolution: Load the related Item rev directly. There is no need to load all of the Affected Items.
Bug ID 17418165: CASCADED LIST DOES NOT SHOW TOOLTIP IN EDIT MODE FOR EXISTING VALUES
Root Cause: Cascade List and Multi Select Cascade List pills miss tool tip.
Resolution: Show tool tip for CL and MSCL pills.
Bug ID 16517253: GET SHORTCUT' IS NOT WORK ON ATTACHMENTS TAB OF MFR PARTS HAVING '/' IN NUMBER
Root Cause: Special characters '/' and '#' in the object number are not encoded while forming the shortcut URL.
Resolution: The code was change to encode '/' and '#' in the object number on the client side and decode it on the server side.
Bug ID 17416706: SEARCH OUTPUT ID(NUM) INSTEAD OF ACTIVITYNAME FOR THE DEPENDENT UPON
Root Cause: The Attribute Root Parent from table Dependent Upon of Class Activity only fetches the ID, not the real name.
Resolution: According to ID of Root Parent, get the real name of it to display in the search result.
Bug ID 17466541: EXPORT SHOWS LARGER NUMBER OF USERS THAN ACTUAL FOR A USERGROUP.
Root Cause: Export all Users for a User Group regardless of the user's active or inactive status.
Resolution: Do not export an inactive user for User Group's User tab..
Bug ID 17451815: THE DYNAMIC LIST CRITERIA CHANGES AUTOMATICALLY TO ANOTHER ONE
Root Cause: For a non-English language user, when updating the display type and criteria of a single list, only the list which user modified should be affected.
Resolution: Add the where clause when updating.
Bug ID 17342419: IMPORT PARTS TO CHANGE AND MAKE RESTRICTED DOES NOT RESTRICT RIGHT
Root Cause: The server's cache is incorrect when importing a new Item into a new Change. It is critical to fix the server code, so now fix the import code.
Resolution: Invalidate the incorrectly cached table when completing the import of the Item.
Bug ID 17466691: PARTS CREATED WITH IMPORT WITHOUT REQUIRED ATTRIBUTES
Root Cause: It uses the superclass' attribute's default value, instead of the subclass' value.
Resolution: Use subclass' attribute instead of superclass'.
Bug ID 17510010: ITEM CREATION WITH COMMODITY CODE ALREADY ASSIGNED WITH MORE THAN 5,000 PARTS
Root Cause: The customer added more than 5,000 Parts to one Commodity, and It will take a long time when using this commodity code to create a new Part.
Resolution: Do not use cache to add or remove a commodity in the Part's Title Block.
Bug ID 17557235: BOMS ARE BEING PUBLISHED INCORRECTLY TO AGILE
Root Cause: Null exceptions are not handled when row keys are loaded.
Resolution: Add a null exception check for cases where row keys are loaded for a table.
Bug ID 17615562: EMAIL FROM AGILE IS NOT BEING DELIVERED
Root Cause: When the notification task calls the PCM marshtable function, PCM can not get the user id from the notification task and throws a null pointer exception. The error blocks all item-related notifications.
Resolution: Create a new PCM API and get the correct user id from the notification task.
Bug ID 15989453: USER USAGE REPORT DOES NOT WORK PROPERLY
Root Cause: LDAP users over-reported their usage.
Resolution: Fix the issue.
Bug ID 17585135: COULD NOT READ ITEM DESCRIPTION IN PROPAGATION WINDOW OF MODEL OBJECT
Root Cause: The index of Item Name and Item Description are hard-coded. If the customer changed the orders in the tab, Item Name is missing. If their revisions are the same, the option value of the propagation drop-down list will be the last one.
Resolution: Added a tool tip to show the full description.
Bug ID 17588811: PERFORMANCE ISSUES WHEN VIEWING FILE ATTACHMENT THE FIRST TIME WITH AUTOVUE
Root Cause: While viewing a file in AutoVue, if the file is not present on the local file server, remote calls are made to retrieve the file properties for the file on the remote file server. There are about 6-7 such calls, each call taking more time than expected.
Resolution: Correct the code to call the related method to get the correct column indexes.
Bug ID 17810969: CANNOT ADD A PURELY NUMERIC MANUFACTURER PART TO AN ITEM USING WEB SERVICES
Root Cause: A purely numeric name gets saved as an Integer. In SDK, the Manufacturer Name must be string type, but Web Services passes an Integer for the Manufacturer Name. The system throws an error and can not add a purely numeric Manufacturer Part to an Item's Manufacturer tab.
Resolution: Pass a String for Manufacturer Name to SDK.
Bug ID 17839876: SUPPLIER USER CAN REDLINE MANUFACTURE PART FOR WHICH HE HAS NO PRIVILEGE
Root Cause: The user can remove/undo redline actions on Manufacturer Parts without read Manufacturer Parts privilege.
Resolution: Add the related logic for checking for the read Manufacturer Parts privilege.
Bug ID 17911389: UNABLE TO RELEASE MD DUE TO EXHAUSTED RESULTSET ERROR
Root Cause: This issue is only reproducible on the customer's database and is caused by bad data. When a user does a Save As new declaration, the bad data is copied again. The error is thrown when handling the bad data during the release of a declaration.
Resolution: Avoid bad data when releasing a declaration. The error should not be thrown even if the database has some bad data.
Bug ID 18017600: JRE 7 U51 UPTAKE
Root Cause: JRE 7u51 security changed.
Resolution: Add the Permissions and Codebase attributes in the MANIFEST.MF file for all signed JAR files.
Bug ID 18017416: 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 the activity in Gantt.
Resolution: To be consistent with Web Client Module, convert ?? to null on PAGE_TWO of activity in Gantt.
Bug ID 18201702: RULES ARE STILL BEING APPLIED EVEN AFTER REMOVING FROM CONT
Root Cause: When a relationship object is removed, the rules are not removed. The rules still work after the relationship is deleted.
Resolution: Remove rules when removing a relationship object. Also, rebase on 9.3.1.2.7.
Bug ID 18136553: ACCEPTD DELEGATION DOES NOT MAKE THE ACCEPTED USER AS TASK OWNER
Root Cause: The SQL in method deleteInvalidNotifications is incorrect.
Resolution: Correct the SQL.
Bug ID 18176548: AFFECTED ITEM ON QUALITY CHANGE REQUEST (AUDITS) DOES NOT OPEN TO SELECTED REV
Root Cause: The system does not set the Item's revision info when generating and Item link in the QCR's Affected Items (AI) tab, so the link cannot take the user to the correct rev.
Resolution: Set the rev info for the Item link in the QCR's AI tab.
Bug ID 18178191: WEIGHT ON SUBSTANCES ROUND OFF TO 3 DECIMALS WHILE IMPORTING ON: RULES ARE STILL BEING APPLIED EVEN AFTER REMOVING FROM CONT
Root Cause: The code uses the JXL to format the Excel to aXML, but the decimal is lost by directly when JXL is used to parse number data.value = cell.getContents();
Resolution: Use the numberCell to parse the number value.
NumberCell nc=(NumberCell)cell;value=nc.getValue()+"";
Bug ID 18346649: DISABLED PAGE TWO APPEARS IN WEB CLIENT
Root Cause: To resolve a failover issue (bug 12925768), we set the required tablemodel to httpsession (fixed ObjectViewHandler.java), If the user disables P2/P3, we got an old tablemodel from httpsession. This is the problem.
Resolution: Clear the tablemodel from the httpsession.
Bug ID 18430516: REPLIES ARE NOT SORTED IN ORDER OF CREATION WHEN A DISCUSSION IS EXPORTED
Root Cause: SDK passes the wrong data to PC core code.The discussion parent id is not correct in the DB.
Resolution: Pass the correct parameter to PC core code.
Bug ID 17955531: AFTER THE MIGRATEUSERSTODB, SOME ATTRIBUTES DEFAULT VALUE WILL NOT BE AFFECTED
Root Cause: Home phone and Show Time sheet attributes are not handled properly.
Resolution: Change the logic that is used to retrieve default values.
Bug ID 18366659: OOTB EXPORT GIVES INCORRECT DATA
Root Cause: The conditions used when redline a price line against a PCO is not correct.
Resolution: Correct the conditions used when redlining a price line against a PCO.
Bug ID 18056686: CHANGE CANNOT BE RELEASED WITH ERROR JAVA.LANG.NULLPOINTEREXCEPTION
Root Cause: When a user edits redline info and saves while using multiple windows, sometimes bad data is caused because the current parent object (Affected Item) which is in grid context is not correct.
Resolution: Get the current parent object from the HTTP request and compare this object with the object in the grid context. If it is not the same, throw an error message and block the redline Save action.
Bug ID 18512729: COMPLIANCE CALCULATION IS INCORRECT
Root Cause: The user set the exemption list that has more than 32 values in a Specification. Since the exemption attribute in the Specification table is limited (only can save 32 values. Part of the list values), all data are saved to the map table MSATT. The rollup engine only gets the exemption value from the Specification table that is not all data and leads to the incorrect compliance result.
Resolution: Change code logic to load all exemption data if it has more than 32 values and keep the compliance result correct.
Bug ID 18512729: RELEASED DECLARATION SHOWS AS PENDING INSTEAD OF ACTIVE
Root Cause: There are thousands of Manufacturer Parts in the Declaration. It took a long time (more than 20 mins in dev env) to release the Declaration. It caused a timeout exception and cannot commit successfully. Most of the time is taken by registering so many internal events. Most of the events are duplicated. This performance issue is caused by a code defect.
Resolution: Reduce to add these duplicated internal events and optimize. This saves time and releases more quickly than before.
Bug ID 18512729: DESCRIPTION DIFFERENCES FROM WHERE-USED TAB VERSUS WHERE-USED REPORT
Root Cause: The Where Used report does not get the latest version for the selected Items.
Resolution: Add more cases to get the latest version of the Items.
Bug ID 18697599: UNABLE TO DISABLE PAGE TWO ATTRIBUTES AT SUBCLASS LEVEL
Root Cause: The Page Two attributes of subclass were not considered while propagating a subclass.
Resolution: Propagate P1, P2 attributes of a subclass.
Bug ID 18728840: TABLE_SUBSTANCES SDK METHOD DOES NOT RETURN ALL THE ROWS
Root Cause: When the SDK code provided by support gets the Substance table of an Item, the server side loads the Substance info and builds the BOS data. The defect is that the BOS in memory is built incorrectly, which leads to the wrong result. This issue is caused by server-side code.
Resolution: Correct the code that is used to build the BOS in memory.
Bug ID 18765142: ECO ASSIGNED TO PART IN SAVE PREVIEW BUT AFFECTED ITEM NOT ON ECO
Root Cause: If an Item has file folders, then the Smart Rule "copy files to rev -file folders" = reference with warning causes the issue.
Resolution: Ignore all warnings regarding the Smart Rule Copy to Rev for Save use case.
Bug ID 19183498: INCORRECT USER DETAILS IN USER GROUP - USERS TAB
Root Cause: When logging info is enabled and the user group contains LDAP users, the system will get a null pointer and skip to load other users of the user group.
Resolution: Avoid getting a null pointer error when logging info.
Bug ID 19263917: ITEM ATTRIBUTE HISTORY REPORT DOES NOT SHOW THE CHANGE FOR NUMERIC
Root Cause: There is a defect in the checking cell value in P2 when displaying the Item Attribute History Report.
Resolution: Fixed the problem.
Bug ID 19352880: DELAY TO DISPLAY THE VIEW ON
Root Cause: We do not cache the data for the Price table.
Resolution: Cache the data for the Price table.
Bug ID 19454159: ERROR WHILE ITERATING OVER THE ANALYSIS TAB OF A SOURCING PROJECT
Root Cause: When iterating over the Analysis tab, SDK side does not use NetworkClassLoader.
Resolution: Change the class loader to NetworkClassLoader.
Bug ID 19449287: FILE OPEN FETCHES THE WRONG FILE
Root Cause: Agile incorrectly chooses the filename of the first row in the File table of File folder for the OPEN file action.
Resolution: Choose the correct filename for the corresponding open file.
Bug ID 19460469: CHANGING PART TYPE DOES NOT BRING ENABLED PAGE TWO ATTRIBUTES ON NEW PART TYPE
Root Cause: The attributes on the Title Block and Page Two did not change by the Part type change when editing in the Item.
Resolution: When Part type is changed, save the new subclass and return to the view model with the attributes refreshed.
This section includes Hot Fixes included in Agile PLM 9.3.2.0.
Bug ID 17526886: CAN NOT RUN QUERY ON ENVIRONMENT WHERE 9.3.2 PATCH 10 HAS BEEN APPLIED
Root Cause: HF 10 was meant to include the changes done for 9.3.2 HF 01. For adding a new option called 'queryOnlyLatestVersions' there was an SDK change in IQuery necessary, but this change was not ported to HF 10.
Resolution: An existing method from IQuery was used, but this renders the new option as not supported for HF 10.
Bug ID 17176919: CREATE PPM PROJECTS AND TASKS USING PPM SCHEDULING ENGINE
Root Cause: The core web service has a bug in the Update Project data builder implementation for the Schedule Editor attribute. It always expects RN-Primavera.
Resolution: The Schedule Editor attribute has been enabled to allow valid values from the 'Schedule Editor List.
Bug ID 17203313: EFFECTIVE BOM EXPLOSION REPORT PRESENTS WRONG INFORMATION
Root Cause: The Effective BOM Explosion Report had missing or duplicated records.
Resolution: Fixed this issue.
Bug ID 17258447: AGILE PLM 932 SSO DOESNT WORK WITH OAM 11G R2
Root Cause: The SSO plug-in was not handling special character '.' for user id
Resolution: Fixed SSO plug-in to handle special character '.' for user id
Bug ID 17220485: AUTOVUE FOR AGILE 20.2.1 DOES NOT DISPLAY ALL XREF FILES THOUGH THEY ARE ALL PRESENT UNDER THE ATTATCHMENTS TAB OF AN ITEM
Root Cause: The mapping information for the streaming file is not cleaned properly in the Agile system (database) while executing the metafile remover tool.
Resolution: Removed the code to map the file info for the streaming file from the Agile system (database) while executing the metafile remover tool.
Related Bug:
17214463: AUTOVUE FOR AGILE 20.2.1 DOES NOT DISPLAY ALL THE XREF FILES EVEN THOUGH THEY AR
Bug ID 17293837: COMMODITY DOES NOT APPEAR IN SOURCING PROJECT
Root Cause: This is a design issue. Currently, the PCM Commodity attribute is mapped to item.partFamily.
Resolution: If the Smart Rule Force Commodity and Part Family to be Identical is set to Yes, then in most cases the Commodity attribute will not be enabled and the Commodity should be mapped to Part Family. If the Smart Rule Force Commodity and Part Family to be Identical is set to No, then the mapping should be to Commodity.
Bug ID 17160876: WORKING IN MULTIPLE WINDOWS MAY LEAD TO ATTACHMENT DATA CORRUPTION
Root Cause: The Agile application does not support multiple windows on the same browser, because there is only one user session per user application server.
Resolution: Fixed in code to avoid the deletion of attachments on another object or another revision or file folder version per HTTP request.
Related Bug:
17089376: WORKING IN MULTIPLE WINDOWS MAY LEAD TO ATTACHMENT DATA CORRUPTION
Bug ID 17435097: CANNOT ADD AFFECTED ITEM WITH ATTACHMENTS TO A CHANGE ORDER
Root Cause: If the visible value of the File Description attribute in the File Folders class is set to No, when the user adds Affected Items with attachments to routable objects, the index of the file description column returns a value of -1 when the system does a deep clone attachment action.
Resolution: Check the index before the set file description object.
Bug ID 17469371: VIEWING FILE ATTACHMENTS WITH AUTOVUE IS VERY SLOW
Root Cause: When opening an Item's attachment, the system checks the Item revision in the related Change object, but in this process, the system loads all of the Affected Items of the Change first. This caused a potential performance issue, since more Affected Items means that more time is needed during the loading process.
Resolution: Load the related Item rev directly. There is no need to load all of the Affected Items.
Bug ID 17294677: AUT EXECUTE-FTS-POST-TASKS-921 ROUTINE IS NOT WORKING ON 9.3.2
Root Cause: The problem is related to the AUT tool and the security improvements on the server with 9.3.2.
Resolution: [Changes to AUT] When execute-fts-post-tasks-921 is run against a 9.3.2+ database, an error message is thrown indicating that this task is only for use with Agile PLM version 9.3.1.x and prior databases.[Changes to Application Server] Add a new method in the application to update content URLs for indexable filetypes where their CONTENT_URL is NULL and return the number of rows updated.[Changes to Java Client] Expose a new button (next to the Index Attachments now button) in the menu bar of the Full Text Search page (Java Client > System Settings > Full Text Search) with hover text Update Content URLs now to invoke the new method in the application server. When this new button is clicked, first display a confirmation dialog with the text "Are you sure you want to update Content URLs now?" (same behavior as the Index Attachments now button).If the user clicks Yes, then call new method in the application server to update Content URLs and display informational message showing status and number of rows updated.
Bug ID 17294677: THE DYNAMIC LIST CRITERIA CHANGES AUTOMATICALLY TO ANOTHER ONE
Root Cause: For a non-English language user, when updating the display type and criteria of a single list, it should only affect the list on which the user modified.
Resolution: Add a where clause when updating. For a non-English language user, it affects the current modified list, not all the lists.
Bug ID 17615468: SAVE AS ACTION ON CHANGE STILL SHOWS AFFECTED ITEM'S LAST REV INCORPORATE DATE
Root Cause: The system copies the Affected Item's Incorporate Date when doing a Save As action for Change Order.
Resolution: Do not copy the Incorporate Date when doing a Save As for a Change Order's Affected Items row.
Bug ID 17604968: UNABLE TO IMPORT AXML FOR A DECLARATION WITH BOS WHEN NUMBER OF MPS GETS LARGE
Root Cause: When auto promoting from Released status to Implemented status, the flag notifyCCB is set to true, and the default approvers/acknowledgers/observers set in Released status receive the status promotion notification if they are not approvers/acknowledgers/observers in Implemented status.
Resolution: Do not notify the CCB at Released status when auto promoting from Released status to Implemented status.
Bug ID 17636021: ASSEMBLY COST (SUPPLIER RESPONSE) NOT WORKING AFTER UPGRADE
Root Cause: There is a performance issue if using the Exist statement in the table, which has a huge table and makes low efficiency.
Resolution: Change SQL statement to improve performance.
Bug ID 17647553: ERROR: FAIL TO CONVERT TO INTERNAL REPRESENTATION WHEN SEARCHING FOR PROJECTS
Root Cause: In the Search server side, when generating SQL, the attribute root parent is added into the select clause for privilege checking. This attribute should not be special handled. Only the attribute selected to be one output column requires adding three more columns (id, class, subclass). Therefore, this issue is caused by fetching the wrong column value as added three more columns in the selected clause.
Resolution: Handle the root parent from privilege checking the same as the one to be output column.
Bug ID 17715776: EXPORT DOES NOT GET THE SECOND RED LINE ADDED ITEM
Root Cause: This issue can be triggered in a special data structure, when there are two revs. If one is released before SCO, and the other is released after the SCO. when the SCO does some redline action in the BOM or AML tab the export may miss some redlined data. We export handle the wrong revision, which causes the missing redlined data.
Resolution: When there is redlined data in an SCO, we should handle this SCO revision but not the previously released SCO revision.
Bug ID 17731899: BOM COMPARISON REPORT GENERATES ERROR
Root Cause: Reports cannot handle the special character '""' and always throws an exception.
Resolution: Use a special handler for character '""'.
Bug ID 17786553: PUBLISH PRICES APPLET THROWS THIS FEATURE DID NOT PERFORM AS EXPECTED ERROR
Root Cause: Due to a code defect (hard-coded published price subclass), the applet throws an error if the Publish Price subclass does not exist when the user clicks the Publish Price button under the Analysis tab.
Resolution: Set the default Published Price if it exists, otherwise, show the first subclass of the Price object.
Bug ID 17767308: AGILE BOM - MANUFACTURER BOM REPORT - ERROR: AN UNEXPECTED ERROR HAS OCURRED
Root Cause: There is no code to handle exceptions thrown from privilege checking in the Manufacturer BOM Report.
Resolution: Added the handler.
Bug ID 17779046: AGILE PLM 9.3.2: LIST FIELD LINKED TO THE SITES LIST NON VISIBLE O
Root Cause: When we link a field to the Sites list as a single list in PPM, it checks the Discover privilege of the field, but the Sites object does not have a discover privilege and we also can not create a Discover privilege for Site.
Resolution: There is no specific privilege of Discover Site list. Users with the Admin privilege should be able to discover all Sites. When displaying the attribute of Sites, we do not need to check the discover privilege for it. We only need to check if the current user has the Admin privilege.
Bug ID 17804652: UNABLE TO UNRELEASE A PCO IN 9.3.2
Root Cause: The incorrect SQL is used to set Default Site change when unreleasing a Price Change.
Resolution: Use proper SQL code to set the Default Site change when unreleasing a Price Change.
Bug ID 17665968: CANNOT LOG IN TO AGILE FROM MCAD FOR USER WITH ALL NUMERIC LOGIN ID
Root Cause: If WS client passes an all numeric login id, Agile treats it as an internal database id instead of a user name.
Resolution: Treat the login id as the user name first, but if it can not find this name, then treat it as internal database id.
Bug ID 17896573: ITEMS CANNOT BE ADDED TO THE AFFECTED ITEMS TABLE WITHOUT READ ITEMS APPLIED TO ITEM
Root Cause: There are two potential defects that can trigger the privilege issue when adding Affected Items. One defect is when Agile does not set the Item's subclass when setting RowObjectID. The second defect is when Agile does not set the routable object's subclass when checking privilege for pending changes.
Resolution: Set the Items' subclass, and set the routable object's subclass.
Bug ID 17886725: FILE NAME IS GARBLED WHEN DOWNLOADING REPORT OUTPUT TO CSV FILE
Root Cause: The Agile Class Report is transferred to the wrong encoding when the Japanese language and SHIFT JIS is chosen as the encoding type.
Resolution: Correct the transfer method.
Bug ID 17911300: SCHEDULED ROLLUP ISSUE - NO PRIVILEGE ERROR FOR AGILEUSER IN THE HISTORY OF PARTS
Root Cause: The Compliance Rollup task is run by the Agile user. It is responsible for background task. The user did not have the read privilege for spec.name.
Resolution: When Agile retrieves the name of the Specification for log history, the Agile user must have read privilege for spec.name.
Bug ID 17939209:NOT ABLE TO PUBLISH PRICE TO ITEM'S PRICE TAB
Root Cause: The current logic is to publish the price to the latest released Change of the rev that was added to the Sourcing Project. When the latest change is a deviation, the price is published to the deviation rev, but in Product Collaboration, the Item rev does not show a deviation, so we are not able to see Prices under Price tab of the Item.
Resolution: Changed code to publish the Price to the latest released non-Deviation change of the rev that is added to the Sourcing Project. Provide a script to correct the existing Prices that have this issue.
Bug ID 17888426: CHANGE CYCLE TIME REPORT GENERATES ERROR WHEN INPUT STRING MORE THAN 1000
Root Cause: The transfer of a double value generates a NumberFormatException in the Change Cycle Time Report, because when the double value equals to, or is greater than, 1000 it includes a comma symbol.
Resolution: Filter and obtain a clean value from the double string.
Bug ID 17906453: MISSING UOM AND MATERIAL TYPE DATA FOR SOME PARTS IN AXML FILE WHEN EXPORTING ECO
Root Cause: When the user has no BOM.product line(s) privilege, export Change object to aXML with some Affected Items, some part Title product line(s) attributes do not get exported. A similar situation occurs with Part Category attributes.
Resolution: Add a privilege validation in export code.
Bug ID 17974332: EXPORTED ANALYSIS TAB DATA SHOW DIFFERENT RESULTS
Root Cause: Current procedure "addBomRowEx" may get incorrect BOM flag for certain cases. When adding an Item to a Souring Project, the incorrect flag based on the procedure leads to this issue.
Resolution: Add a constraint clause in procedure "addBomRowEx" to get the correct BOM flag. Now, the customer can use the Edit -> Update from Item Master Action to recall the procedure to update the BOM tree for existing Souring Project objects.
Bug ID 17829384: AFTER 9.3.2 UPGRADE, PROCESS EXTENSIONS PERIODICALLY FAILING WITH ERROR
Root Cause: in UserContextManager.getUserContext(IAgilePrincipal agPrincipal), uses the case sensitive user name to retrieve PX context, but this context is stored with a case insensitive user name. This returns the wrong context.
Resolution: Convert user name into lower case.
Bug ID 18017607: JRE 7 U51 UPTAKE
Root Cause: JRE 7u51 security has changed.
Resolution: Add the Permissions attribute in the MANIFEST.MF file for all signed JAR files.
Bug ID 17997938: TIMEZONE DISPLAY ERROR
Root Cause: The dateformat is set to another timezone when it parses some dates including another timezone.
Resolution: Set back the timezone.
Bug ID 18007289: RELATIONSHIP SEARCH LISTS UNMATCHING CLASS ATTRIBUTES FOR JAPANESE
Root Cause: Under JP env, when a user performs a relationship search, but a related Class select list displays Item Class, this is not correct. The related class select list is expected to display as Change class as corresponding attribute list of the criteria displays attributes of Change class.
Resolution: Specify the default Class Change in the related class select list.
Bug ID 18007297: REPORT PROPERTY ON DEFAULT LAYOUT CAN NOT BE CHANGED
Root Cause: The customer cannot edit/save report layout properties because of hard code.
Resolution: Skip the function. Add it into the system.
Bug ID 17939246: JAVA.IO.NOTSERIALIZABLEEXCEPTION: JAVA.UTIL.ARRAYLIST$SUBLIST ERROR
Root Cause: A List instance returned by ArrayList.subList() that is not serializable is put in the web session.
Resolution: Use ArrayList instance directly.
Bug ID 17955818: GETTING JAVA.LANG.ILLEGALARGUMENTEXCEPTION: YEAR - ERROR WHEN ACC
Root Cause: The static member variable SimpleDateFormat in PXUtil.java is shared for all the thread when parsing/formatting a date, but SimpleDateFormat is not thread safe.
Resolution: Put the SimpleDateFormat into ThreadLocal to make sure each thread has its own instance of SimpleDateFormat.
Bug ID 18069774: BUG IN REDLINES WINDOW
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 FF, but is "\r\n" in IE, which leads to this issue.
Resolution: 1. Code Level: Ignore the wrap character's difference between IE and FF when sending a cell value for a multi-text attribute during a redline. 2. DB level: Provide a script to remove existing bad data in table redline_attribute.
Bug ID 18062385: SEARCH ITEMS SPECIFICALLY ON ATTACHMENT
Root Cause: When searching based on table, attribute Attachments.Has Attachment is not supported. This is the root cause.
Resolution: Exclude this attribute from base on table/row.
Bug ID 18044949: BOM COMPARISON REPORT IS EMPTY
Root Cause: The BOM Comparison Report cannot work when an East Asian language (T/S Chinese, Japanese, Korean) is selected.
Resolution: Transfer Asian word to native ascii code.
Bug ID 18113084: WHEN CREATING DASHBOARD SEARCHES, IF THE USER ID CONTAINS NON-ENGLISH CHARACTERS, THE RESULT CONTAINS ERRORS
Root Cause: The server side uses a stream which does not support more than 8 bits encode type when preparing for a search parameter.
Resolution: Use the ByteArrayInputStream to encode.
Bug ID 18140218: SUBSTANCE NAME TO SUPPORT SEMICOLON & 2000 CHARACTERS: BUG IN REDLINES WINDOW
Root Cause: The semicolon is a delimiter in Agile. It can not be included in any object name in 932. Agile supports a maximum of 200 characters for Substance Name.
Resolution: Allow the use of semicolon for Substance and Substance Group name. Enlarge the substance name to 2000 characters.
Bug ID 18220404: DYNAMIC LISTS OF USERS (WITH CRITERIA) DISPLAY USERID AND NOT FULL NAME
Root Cause: Dynamic User List displays only the user id and does not include the full name in some tabs.
Resolution: Skip the reference user check when retrieving the column value for User List.
Bug ID 16710889: STATUS MISMATCH FOR DELEGATED OWNER ACCEPTANCE BETWEEN MY ASSIGNMENTS
Root Cause: SQL is not correct in method deleteInvalidNotifications.
Resolution: Correct the SQL.
Bug ID 18224651: PULLING UP RFQ TAB IN SOURCING PROJECT TAKES TOO LONG
Root Cause: A huge amount of data was stored in the customer's Response table, so when count distinct is used in a SQL statement, the process takes a lot of time.
Resolution: Used count instead of count distinct and then handles the rest of the business logic in the Java code.
Bug ID 17821624: CHANGING PART TYPE DOES NOT BRING ENABLED PAGE TWO ATTRIBUTES ON NEW PART TYPE
Root Cause: Attributes on title block, Page Two do not change by the Part Type change when the user edits in the Item.
Resolution: When Part Type is changed, save the new subclass and return back to the view model with refreshed attributes.
Bug ID 18097788: CANNOT USE GET FUNCTION USING VIEW VERSIONS
Root Cause: There are bugs in the code:1. The incorrect registered table id is used when using Get Attachment after view version pops up and is closed. 2. The incorrect object id is used in the log history when using GET file in the View version. 3. The object has been modified after getting the file from the View Version.
Resolution: Fixed code to provide proper table id, object id and not increment the Agile object version.
Bug ID 18327465: AGILE EXEMPTIONS REPORT FAILS WITH JAVA HEAP ERROR AFTER UPGRADE
Root Cause: A dead loop causes the heap warning when there is very large text in report headers.
Resolution: Split the content to jump out of the dead loop to make sure the report runs successfully.
Bug ID 18106467: ON ADVANCED SEARCH WHEN OPERATORS ARE ENGLISH AND JAPANESE FAILS
Root Cause: With some languages, the following two messages in PCResources.properties do not get translated:Dlg.AdvancedSearch.LogicOpAndDlg.AdvancedSearch.LogicOpOr
Resolution: Dlg.AdvancedSearch.LogicOpAnd=AND Dlg.AdvancedSearch.LogicOpOr=OR to Dlg.AdvancedSearch.LogicOpAnd=And Dlg.AdvancedSearch.LogicOpOr=OrI18N team should translate the messages.
Bug ID 18142281: BOM, AML, ATTACHMENT INFO MISSING WHEN EXPORTING ITEM FROM JAVA CLIENT
Root Cause: The HTTP request does not have the rev info.
Resolution: Add revision id from Java Client to the parameter named revchangeid in the HTTP request.
Bug ID 18263680: WORKFLOW STATUS CHANGE POP UP WINDOW AFFECTS ANY CHANGE ACTIVE IN THE MAIN WINDOW
Root Cause: The customer's use case in this bug is a similar multiple windows issue for workflow status change.
Resolution: Use the existing solution to resolve this issue, block this use case by throwing the related error message.
Bug ID 18349731: APPROVAL NOTIFICATION IS SENT TO ALL MEMBERS EVEN WITH AUTO PROMOTE ON
Root Cause: A behavior change was introduced by a 932 internal issue.
Resolution: Only record/send all approve when AutoPromote is set to no.
Bug ID 18422033: DYNAMIC LIST IN SEARCH MODE ALLOWS USERS TO SELECT FROM OTHER USERS
Root Cause: The dynamic list of Users with criteria does not call the proper API to retrieve data.
Resolution: Corrected the code so that it calls the API which is required to pass the list id.
Bug ID 18033239: COLON CAN NOT BE USED IN THE CASCADE LIST VALUE
Root Cause: From 9.3.2, the colon has not been supported when create cascade list elements.
Resolution: Roll back the colon restricton and fix the related functions to support colon in cascade list.
Bug ID 18455541: SORTING OF SEARCH BY ROOT PARENT DOES NOT WORK
Root Cause: Activity attribute root parent requires 3 more additional fields in the select clause, which disorders the sort index.
Resolution: Added a special handler for this attribute when generating a sort index.
Bug ID 18422197: AGILE THREAD POOL HAS STUCK THREADS
Root Cause: When trying to determine the next revision number for an Item, it is possible to end up with stuck threads on the server.
Resolution: The method to determine the next revision number was fixed to avoid stuck threads.
Bug ID 18475973: UNABLE TO ARCHIVE PROJECTS - GET ERROR MISSING IN OR OUT PARAM
Root Cause: The SQL string is wrong when attempting to archive a project with over 100 tasks on the Schedule tab.
Resolution: Correct the SQL string.
Bug ID 18316891: INCORRECT LIFECYCLE PHASE DATA IF CHANGE ITEM'S SUBCLASS
Root Cause: We do not check whether Lifecycle Phase is valid or not when changing the Item type.
Resolution: Update the Lifecycle Phase to null for all of revisions of an Item, including log history, when the type is modified and current phase is invalid in the new type.
Bug ID 18365003: INCORRECT JAPANESE TRANSLATION FOR MOVE SCHEDULE
Root Cause: Incorrect Japanese translation for move schedule.
Resolution: Correct the Japanese translation for move schedule.
Bug ID 18378502: ITEM REVISION SHOWS OLD REVISION AS DEFAULT WHEN IT IS SELECTED THROUGH EXPORT
Root Cause: Search incorrectly returns the latest ECO revision only for Export.
Resolution: Search returns the latest ECO or MCO revision for Export.
Bug ID 18476306: RELATIONSHIP SEARCH WITH PROMPT DOES NOT WORK
Root Cause: The user id of default user($User) in List/MultiList is stated as -2, and with prompt criteria, this user id(-2) does not convert to the actual user id.
Resolution: Convert $User id (-2) to actual user id.
Bug ID 18476140: RELEASED DECLARATION SHOWS AS PENDING INSTEAD OF ACTIVE
Root Cause: There are thousands of Manufacturer Parts in the Declaration. It took a long time (more than 20 mins in dev env) to release the Declaration. It caused a timeout exception and cannot commit successfully. Most of the time is taken by registering so many internal events. Most of the events are duplicated. This performance issue is caused by a code defect.
Resolution: Reduce to add these duplicated internal events and optimize. This will save time and allow for a quicker release.
Bug ID 18261156: PERFORMANCE ISSUES WHEN VIEWING FILE ATTACHMENT FOR THE FIRST TIME WITH AUTOVUE
Root Cause: While viewing a file in Autovue, if the file is not present on the local file server, remote calls are made to retrieve the file properties for the file on the remote file server. There are about 6-7 such calls, each call taking more time than expected.
Resolution: If the file is not present on the local file server, the file is first replicated from the remote to the local file server and then the file properties are retrieved. This saves several remote calls thus improving performance.
Bug ID 18692623: VALUE AFTER COLON FOR CASECADE LIST GETS TRUNCATED IN WEB CLIENT ENVIRONMENT
Root Cause: If the count of Items in the cascade list is more than 500, the Item value is truncated by a colon when it is displayed.
Resolution: In this case, do not truncate the value.
Bug ID 18634162: OUTOFMEMORYERROR IN REPORT IF MOVING TO NEXT PAGE BY STEP NUM, NOT NEXT BUTTON
Root Cause: When the user chooses Page Num to proceed to the report wizard step, the query information is missed in Item Mfrs Report (Step 2.id > Step 3.id).
Resolution: Modified code so that the missed date is now saved into the wizard context.
Bug ID 18729864: IMPORT - UNABLE TO VIEW MULTITEXT FIELD FROM AFFECTED ITEMS TAB OF PSR
Root Cause: The import does not support map PSR's multtext fields.
Resolution: Support mapping of PSR's multtext fields when doing import.
Bug ID 18694281: CASCADE LIST VALUES IARE NOT FULLY SHOWN WHEN EDITING THE FIELDS USING WEB CLIENT
Root Cause: Cascade list pills:<li onclick=""tooltip=""name=""saveid=""objid=""groupid=""isgroup=""tabindex=""class=""id=""></li>The title property is missing.
Resolution: Add the title property.
Bug ID 187444899: CHANGES ARE STUCK THOUGH AUTOPROMOTE IS SET TO YES
Root Cause: When a user does an AML redline and change status action, if the current change has AML redlines that conflict with the AML redlines of other pending change(s), the system throws "cause readline lost" warning and this warning goes into an infinite loop.
Resolution: Make sure this warning is thrown only once.
Bug ID 18848767: CASCADE LIST VALUES ARE NOT FULLY SHOWN WHEN EDITING THE FIELDS USING WEB CLIENT
Root Cause: There is no filter based on subclass for AI LCP.
Resolution: Add filter based on Item subclass for result returned for AFFECTED ITEM's LCP.
Bug ID 18843112: USER USAGE REPORT DOES NOT WORK PROPERLY
Root Cause: LDAP users over-reported their usage.
Resolution: Fix the issue.
Bug ID 18713099: PRINT DATE ATTRIBUTE FROM VIEWERS & FILES -> BANNERS CONFIGURATION
Root Cause: The date format for PrintDate is hard-coded. Also, date attributes are not formatted to the user date format.
Resolution: Fixed the issue by using a user date format for PrintDate and for all attributes of Date type.
Bug ID 18802542: EFFECTIVITY DATE IN THE TOP BANNER SHOULD MATCH DATE TIME FORMAT IN JAVA CLIENT
Root Cause: The date and time are not converted to the user defined timezone.
Resolution: Changed code to convert the watermark/banner time to the user date format/timezone
Bug ID 18866458: RECEIVING ERROR WHEN TRYING TO SAVE TEXT TO RFQ TERMS AND CONDITIONS
Root Cause: 1. WebLogic wraps complex data type parameters Arrays, Blobs, Clobs, NClobs, etc. with its own classes like weblogic.jdbc.wrapper.Clob and for it can not be converted to oracle.sql.CLOB. 2. It did not show full content of RFQ terms and condition and also displayed as one line without original format which defined in java client.
Resolution: 1. Add a special handler for type of weblogic.jdbc.wrapper.Clob 2. Show full content and display with format.
Bug ID 18994737: NO PRIVILEGE RESULT IN RELATIONSHIP SEARCHES
Root Cause: When we check the Read/Discovery privilege on dynamic list for relationship search, it gets the wrong Reference Type on the main object and related object.
Resolution: Get the Reference Type of main objects or relationship objects separately.
Bug ID 19074950: RUN BOM COMPARISON REPORT HAS ERROR (EMPTY FILE)
Root Cause: There is an encoding issue for Asia language when transferring XML to output files, which causes the failure to create the report. This is Windows specific.
Resolution: Fix the issue.
Bug ID 18773957: EXPORT BUTTON IN CUSTOM REPORT IS RANDOMLY DISABLED
Root Cause: A concurrent exception is caused when two reports are run at the same time.
Resolution: Use the 'synchronized' option to avoid the concurrence between two reports.
Bug ID 19147635: ADD/CANCEL BUTTON IS MISSING UNDER ADD FILES DIALOG
Root Cause: There is a bug in the code that does not handle the following use case: Agile is launched from a portal. That page's URL contains "/default". example:http://hostname/yyy/zzz/default.asp
Resolution: Fixed code to form the correct Agile host URL by comparing the A9 server context path + ”/default” with the referring URL.
Bug ID 18892441: CHARACTER CORRUPTION TO FILE NAME WHEN USING OPEN BUTTON
Root Cause: The file name has been encoded to Hex.
Resolution: Decode the file name to UTF8 before setting up the HTTP request.
Bug ID 19605095: WORKFLOW MATCHING CRITERIA IS IGNORED FOR DECLARATIONS
Root Cause: The workflow attribute of Declarations in the Title Block table lists all active workflows which is based on Declaration objects, not based on the setting for matching criteria in Java Client. The matching criteria setting does not work if the user set it.
Resolution: Follow another routable object like Change. Matching the criteria settings for Declaration workflow should work.
Bug ID 19601019: FAILED TO REPLICATE A NON-SERIALIZABLE OBJECT
Root Cause: ExportTask(.java) has non-serializable fields. TransferAuthorityDataModel.Sortor has non-serializable fields and both of these objects are put in ClientSession and ClientSession object is put in HttpSession, so in clustering we get non-serializable exceptions.
Resolution: Make the fields transient.
This section includes Hot Fixes included in Agile PLM 9.3.3.0.
Bug ID 17735036: AUT EXECUTE-FTS-POST-TASKS-921 ROUTINE NOT WORKING ON 9.3.3
Root Cause: The task "execute-fts-post-tasks-921" does not support 9.3.2 or above.
Resolution: [Changes to AUT] When execute-fts-post-tasks-921 is run against a 9.3.2+ database, an error message is thrown indicating that this task is only for use with Agile PLM version 9.3.1.x and prior databases.[Changes to Application Server] Add a new method in the application to update content URLs for indexable filetypes where their CONTENT_URL is NULL and return the number of rows updated.[Changes to Java Client] Expose a new button (next to the Index Attachments now button) in the menu bar of the Full Text Search page (JavaClient > System Settings > Full Text Search) with hover text Update Content URLs now to invoke the new method in the application server. When this new button is clicked, first display a confirmation dialog with the text "Are you sure you want to update Content URLs now?" (same behavior as the Index Attachments now button).If the user clicks Yes, then call new method in the application server to update Content URLs and display informational message showing status and number of rows updated.
Other Related Bugs:
17852753: UPDATE CONTENT URLS FAILS WITH LARGE ROWCOUNTS
Bug ID 17769151: OPEN DOES NOT WORK IN THE INTERNET EXPLORER BROWSER
Root Cause: Parameter prefFileMgrAttName is missing when the applet for IE is launched (17085264).
Resolution: Add the parameter for prefFileMgrAttName when launching the applet in IE.
Bug ID 17882316: DYNAMIC LIST CRITERIA CHANGES AUTOMATICALLY TO ANOTHER ONE
Root Cause: For the non-English language user, when updating the display type and criteria of a single list, it should only affect the list which the user modified.
Resolution: Add the where clause when updating. For non-English language users, it only affects the currently modified list, not all the lists.
Bug ID 18017614: JRE 7 U51 UPTAKE
Root Cause: JRE 7u51 security changed.
Resolution: Add the Permissions attribute in the MANIFEST.MF file for all signed JAR files.
Bug ID 17873454: CONTACT USER IS UNABLE TO REMOVE REDLINES - INSUFFICIENT PRIVILEGE
Root Cause: When the user does an Add/Remove redline action on Manufacturer Parts, the system replaces the selected Affected Item's revision in the user context with the current change revision, but undo-redline action does not do this, so it causes the system to get an incorrect lifecycle value for the Affected Item when matching the related criteria.
Resolution: Refer the Add/Remove redline business and replace the Affected Item's revision with the current change revision when the user does an undo-redline action on the Manufacture Part.
Bug ID 18029214: REDLINE FOR PART P3 ATTRIBUTES ON ECO SYSTEM DO NOT APPEAR CORRECTLY
Root Cause: In redline edit mode, the system does not hide the fields that the current user has no privilege to read.
Resolution: Hide the fields that do not have read privilege in redline edit mode.
Bug ID 18085954: CAN NOT SET/GET NEW ATTRIBUTES VALUE BY IEVENTDIRTYCELL
Root Cause: The incorrect revision is initialized for Price object when triggering update relationship event.
Resolution: Re-initialize the revision of the Price object when no revision is found.
Bug ID 18066585: ISSUE IN PROMOTION OF CHANGES WHEN FIRST LEVEL BOM COMPONENTS ARE MORE
Root Cause: In the Safari browser, if the HTTP response time exceeded 10 seconds by using an AJAX sync call, the browser throws a response timeout error and hangs.
Resolution: Use an AJAX asynchronous call instead of synchronous.
Bug ID 17976235: GLOBAL SEARCH SAVE AS FUNCTIONALITY
Root Cause: Create Shortcut is checked and grayed out in Web Client when a user executes the Save As function. The proper behavior is that Create Shortcut should be unchecked.
Resolution: The customer agrees with the fix in Web Client where Create Shortcut unchecked.
Bug ID 17438150: PROJ WEB SERVICE FOR LOADING PROJ THROWS EXCEPTION IN CODE FOR SOME PROJ
Root Cause: A criteria-based dynamic list cannot return a valid reference class id using ListMgr.getBaseClassId(listId).
Resolution: Change the way to get dynamic list reference class id with ADListDynamicCriteriaBased.getReferenceType().
Bug ID 18196186: ITEMS CANNOT BE ADDED TO AFFECTED ITEMS TABLE WITHOUT READ ITEMS APPLIED TO ITEM
Root Cause: There are two potential defects that can trigger a privilege issue in the adding Affected Item case: 1. Do not set Item's subclass when setting RowObjectID. 2. Do not set a routable object's subclass when checking the privilege for pending changes.
Resolution: Set the Items' subclass, and set the routable object's subclass.
Bug ID 18193918: LIST FIELD LINKED TO THE SITES LIST NON VISIBLE OBJECT
Root Cause: When we link a field to Sites list as a single list in PPM, it checks the Discover privilege of the field, but the Sites object does not have a Discover privilege. Additionally, the Site object can not have a Discover privilege.
Resolution: There is no specific privilege for Discover Site list. A user with Admin privilege should be able to discover all sites. When we display the attribute of Sites, we do not need to check the Discover privilege for it. We just need to check if the current user has Admin privilege.
Bug ID 18105474: REQUEST TO FORWARD PORT HF 9312.237 INTO 933
Root Cause: Special characters "/" and "#" that are used are not encoded while forming the shortcut URL. Many versions of the JavaScript method encodeToHex() exists in Agile. The wrong version which does not encode those characters is randomly used by the browser.The following are the situations in which the problematic characters are present:1. subclass name created by user2. object numbers3. revision number (while getting file in Item object)4. no Agile out-of-box subclasses of File Folder or Design classes (in case, they are deleted in Java Client by user)
Resolution: Changed code to make sure that all JavaScript methods have the same implementation and encode "/" and "#" characters in the object type, object number and object revision on the client side, and decode it on the server side.
Bug ID 18105530: SEARCH ERRORS WHEN ADDING RELATIONSHIP ELEMENTS TO REPORT OUTPUT
Root Cause: The SQL generated for relationship search is not efficient. It joins one exceed table, which causes the return of a huge amount of data, and brings issues from the database like "unable to extend temp segment.”
Resolution: Get rid of the exceed table on SQL statement.
Bug ID 18105504: REQUEST TO FORWARD PORT HF 9312.213 INTO 933
Root Cause: The UI for Actions > Cancel has additional capabilities to cancel the entire tree. This should also allow the same capability to initiate a Cancel when in Proposed status in the SDK call.
Resolution: Add an SDK capability that tracks the UI Actions > Cancel.
Bug ID 18125295: UNABLE TO SAVE TIMESHEET ON AGILE 933
Root Cause: Dashboard classid and objid are used when saving the timesheet table.
Resolution: Clean the dashboard classid and objid when switching to Timesheet/ My Assignment tab.
Bug ID 18139086: PERFORMANCE ISSUES WHEN USING SAFARI
Root Cause: This issue is caused by XMLHttpRequest timeout. For Safari, XMLHttpRequest has a default timeout of 10 seconds. It throws an exception when there is a timeout, but other browsers do not have this kind of issue.
Resolution: 1. Since there is a bug with Safari(5+) sycnronous XHR, we need to use asynchronous XHR instead of synchronous XHR when saving the BOM redline table changes.2. Freeze the UI to prevent the user from doing other operations when saving the BOM redline table.
Bug ID 18287073: AGILE CORE WEB SERVICES IS CREATING PARTS WITH INACTIVE PRODUCT LI
Root Cause: Previously, the server use the value ws client pass no matter it's active or not
Resolution: Currently, now we use the active value for production line only, for other list, we don't change the behavior.
Bug ID 18105496: REQUEST TO BACK PORT BUG 16889959 934 FIX INTO 933
Root Cause: Notification task will pick all pending notifications to send. Processing huge pending notification cause timeout. In dell?s case, it has more than 70,000 pending notifications. Time out setting is 30 minutes. It will throw time out exception and roll back transition . Finally user cannot receive notifications.
Resolution: add notification process batch size to avoid exception during non-time-out period. Batch size can be configurable in agile.properties
Bug ID 18286621: SEARCH ITEMS SPECIFICALLY ON ATTACHMENT
Root Cause: When searching based on table, attribute Attachments.Has Attachment is not supported.
Resolution: Exclude this attribute from base on table/row.
Bug ID 18273447: WORKFLOW MATCHING CRITERIA IS IGNORED FOR DECLARATIONS
Root Cause: The workflow attribute of Declarations in the Title Block table lists all active workflows, which is based on Declaration objects, not based on a setting for matching criteria in Java Client. The matching criteria setting does not work if the user set it.
Resolution: Follow the other routable objects like Change. The matching criteria setting for the Declaration workflow works.
Bug ID 18279073: ACCEPTD DELEGATION DOES NOT MAKE ACCEPTED USER AS TASK OWNER
Root Cause: The SQL code is not correct in method deleteInvalidNotifications.
Resolution: Correct the SQL.
Bug ID 18297981: $CURRENTREV EQUAL TO $INTRODUCTORY_RELEASEDCHANGE NOT WORKING AS EXPECTED
Root Cause: A criteria expression involving any of these three values: ($INTRODUCTORY_NOCHANGE, $INTRODUCTORY_PENDINGCHANGE, $INTRODUCTORY_RELEASEDCHANGE) always returns its own value when they are used as right evalute.
Resolution: Correct the incorrect business logic.
Bug ID 18388840: UNABLE TO EXECUTE PERSONAL PQM REPORTS
Root Cause: A saved search can be removed, even if it has been used in a customer report or schedule. When the removed saved search's queryid is deleted, the report which used the saved search cannot find the queryID, which causes errors.
Resolution: Do not allow an end user to delete a saved query if the saved query was used by other clients such as Dashboard /Report. Display an error message, "This query {0} cannot be deleted due to its use in Dashboard /Report."
Bug ID 18242608: PLMEVENTACTIONPX EXCEPTION RESULT FORMATTED WITH HTML IS NOT DISPLAYED
Root Cause: Per the 932 XSS project, default messages are shown in plain text (html encoded).
Resolution: Exceptional messages from the Event framework are shown in HTML format.
Bug ID 18366458: WORKFLOW CHANGE STATUS TAKING LONG TIME FOR PQM OBJECTS.
Root Cause: For Status Change:1. For the case which moved the status of the PSR object to Cancel or Closed, the system checks each Affected Item in the current PSR object if had related PSRs. In this business process, the system loads all of the related PSR objects one by one, of each Affected Item first, and if there were lots of related PSRs, it costs much more time.2. For the case which removed one or more Affected Items from the PSR object, the system checks the removed Affected Items if had related PSRs, but in this business process, the system also loads all of the related PSR objects one by one of the removed Affected Items first, if there were lots of related PSRs, it costs much more time.3. For the case without Auto Promote, when the status is changed from verify to closed, the system refreshes all of the PSR Affected Items' related redlined tables, in this process, all the redlined BOM and MFR info of each PSR Affected Item is loaded to the cache first, and so much time was spent.4. For the case with Auto Promote, half of the cases were the same as the case without Auto Promote, but when the status is changed automatically from Closed to Complete, the system updates the flags of all the PSR's Affected Items' related Change objects. In this process, all of the change objects of each PSR's Affected Items are loaded to the cache first, so more time was spent.
For SDK Business: The Agile SDK API does not exist to support this bulk functionality for PSR's Affected Items tab.
Resolution: For Status Change:The system checking logic only needs the related PSRs' ID and Status fields for the checks, so load these 2 fields' data from all of the related PSRs of the Affected Items from the database. Load all of the redlined BOM and MFR info of PSR's Affected Items from the database once. Load all of the Change objects of the PSR's Affected Items from database one time and batch update the flags of each PSR's Affected Item's Change objects.For SDK Business:Enhance Agile SDK by adding new APIs IServiceRequestAITable.bulkCreateRows(Object[] rows) throws APIException; IServiceRequestAITable.bulkUpdateRows(Map rows) throws APIException; IServiceRequestAITable.bulkRemoveAll(Collection c) throws APIException; to bulk create/Update/Delete PSR affected items tab rows.
Other Related Bugs:
18401706 -VERIFY TO CLOSE TAKING A LONG TIME FOR PQM OBJECTS
Bug ID 18378503: PPM ACTIVITY NOTIFICATIONS ARE NOT SENT TO ORIGINATOR OF PARENT ACTIVITIES
Root Cause: In 9.3.2, BaseServiceRoute.beforeStatusChange was rewritten.
Resolution: Use ChangeStatusRequest.setSignoffUser instead of ChangeStatusRequest.setAdditional.
Bug ID 18364699: AGILE BOM - MANUFACTURER BOM REPORT - ERROR: AN UNEXPECTED ERROR HAS OCURRED
Root Cause: There is no handler for exceptions that are thrown from privilege checking in the Manufacturer BOM Report.
Resolution: Add the handler.
Bug ID 18378191: AGILE/PQM - CONSISTENTLY AND RANDOMLY ENCOUNTERED THE ISSUE WITH ?
Root Cause: When doing a status transition for the routable object, the code locks all Affected Items (regardless of modified status). If many Items related to thousands of PSRs, there is a high possibility that a lock error can occur.
Resolution: For PSR object, only lock all of the Affected Items when changing from/to Cancel/Complete status.
Bug ID 18481121: AGILE THREAD POOL HAS STUCK THREADS
Root Cause: When trying to determine the next revision number for an Item, it is possible to end up with stuck threads on the server.
Resolution: The method to determine the next revision number was fixed to avoid stuck threads.
Bug ID 18511628: BOM COMPARISON REPORT OUTPUTS BLANK EXCEL FILE FOR CHINESE USERS
Root Cause: The BOM Comparison Report can not work when an east Asian language (T/S Chinese, Japanese, Korean) is selected.
Resolution: Transfer Asia word to native ASCII code.
Bug ID 18606832: NO WARNING IF THE ENTRY REQUIRED FIELDS ARE FILLED IN, WHEN EDIT THE COVER PAGE
Root Cause: For change, QCR and PSR objects, when the user selects one workflow and does a Save action in Pending status, even if the entry required field(s) on the cover page or page 2 or page 3 have been filled in, the system still treats these filled fields as blank in the Save action.
Resolution: If the field(s) are modified, these field(s) will be flagged as the related dirty attribute(s), then we skip the check for dirty attribute(s) in the system background.
Bug ID 18338825: ATTEMPTING TO SAVE AS ON MPN RESULTS IN UNKNOWN NUMBER. OBJECT DOES NOT EXIST.
Root Cause: When the user executes the Save As action, the value of the Manufacturer name is converted to uppercase from the request and sometimes, this value cannot be matched with the value in the database.
Resolution: Convert the value in the database to uppercase before the match.
Bug ID 18611345: AGILE LOGIN FAILURE REPORT DOES NOT WORK IN WLS ENVIRONMENT
Root Cause: Login failure is not be recorded into AUTH_FAILED in the WLS environment.
Resolution: Record the failures.
Bug ID 18611819: REQUEST TO BACK PORT BUG 18250132 934 FIX INTO 933
Root Cause: An object's subclass for AI is not set when checking privilege for required fields, which leads to the issue.
Resolution: Set object's subclass.
Bug ID 18634349: UNABLE TO ARCHIVE PROJECTS - GET ERROR MISSING IN OR OUT PARAM
Root Cause: The SQL string is incorrect when attempting to archive a project with over 100 tasks on the Schedule tab.
Resolution: Correct the SQL string.
Bug ID 18617309: URL ENCODING IS NOT WORKING CORRECTLY IN PROCESS EXTENSTIONS
Root Cause: javascript encodeURI() does not encode the character #, roll back the code change for bug 13086873 instead.
Resolution: Make Javascript encodeURI() encode the character #.
Bug ID 18640827: A933 UPGRADE - CRITICAL ISSUE - MCAD FAILS WITH SECURITY HF15 AND HF30 INSTANCE
Root Cause: A bug was introduced in 932 security enhancement project by removing "server.conf" from the A9 deployment (agileclassess.jar and fsclient.jar). This lead to issues in the standalone SDK program. (refer to bug Bug 17082996 and 18691474)
Resolution: Fixed the code by introducing a new API to get the File server web service in IFSLocator.getConnection() with extra parameters of fsHelper URL, current user credential to retrieve the File server web service connection.
Bug ID 18634349: EXEMPTION REPORT FAILING IN 933
Root Cause: When the user disables the calculated compliant on Manufacturer Part- > Compliance tab, the code returns -1 calling the api findColumn(attributeid). It does not check if this column exists. The error is thrown when getting the data from arraylist. It is a code issue.
Resolution: Check if the Calculated Compliant attribute on Manufacturer Part > Compliance tab is disabled and make sure it is okay to call the API findColumn(attributeid).
Bug ID 18614431: ERROR WHEN CREATING A CUSTOM REPORT ON PROJECTS WITH ACTUAL DURATION
Root Cause: For Create Custom Report on Projects with Actual Duration, the between operator is not handled correctly. It is stored as milliseconds instead of days.
Resolution: Add a special handler for this case to avoid errors
Bug ID 18561505: LOST FILE ATTACHMENTS AFTER INPLACE LOAD SUCCEEDS
Root Cause: There is a bug in the code. Reset the file path of files from INPLACE import to blank while getting/viewing/opening file if CHECKSUM is Enabled in system configuration.
Resolution: Do not overwrite the file path to blank while getting/viewing/opening file if CHECKSUM is Enabled.
Bug ID 18695567: IDATAOBJECT.REPLACETHUMBNAIL THROWS EXCEPTION WHEN CALLED FROM WEB
Root Cause: After replacing thumbnails on uploading of new files for Design objects, some sizes of thumbnails (small, medium, big) do not have values assigned as they do not get generated. Therefore, when returning the thumbnail information, an exception was thrown.
Resolution: If sizes of thumbnails have no values, the values are not read anymore and an empty value is returned.
Other Related Bugs:
18744970: ONLY ONE LIFECYCLEPHASE AVAILABLE IN MCAD PREFERENCES
18732283: NO RESPONSE RETURNED FOR SETTHUMBNAIL ONCE SET OVERWRITE TO TRUE
Bug ID 18713771: UNABLE TO EDIT NEW REV ON AFFECTED ITEMS TABLE OF CHANGE
Root Cause: The calculation of the bottom row (Bottom-Y) of the data grid is incorrect when the horizontal scroll bar disappears.
Resolution: Correct the logic for the calculation.
Bug ID 18613831: UNABLE TO ADD AFFECTED ITEMS BY CREATE FUNCTION INSUFFICIENT PRIVILEGE MESAGE
Root Cause: The value of Change Category is not added to the request context, which caused a check privilege fail when Criteria contains Change Category checking.
Resolution: Add the value of Change Category to user context.
Bug ID 18716143: EXEMPTION REPORT FAILS IN 933 WITH HEAPSPACE ERROR
Root Cause: The application goes into a dead loop to make a heap warning when there is a very large text in report headers.
Resolution: Split the content to jump out the dead loop to make sure the report runs successfully.
Bug ID 18803144: ITEM QUICK SEARCH RESULTS SHOWS INSUFFICIENT PRIVILEGE DOCUMENT CLASS OBJECTS
Root Cause: While doing a quick search, totalResult.getCachedDiscoveryObjects() get empty cached discovery objects, this leads to incorrect privilege checking. The readDiscObject is reused for each row, because it is the same for all keys in the map
Resolution: In quick search, reset cache to get cache discovery objects. Create a new readDiscObject for each row.
Bug ID 18451637: AUDIT STATUS HYPERLINK POINTS TO THE RELEASED REVISION INSTEAD OF THE PENDING REVISION
Root Cause: In the current business logic, we do not set rev info for the link.
Resolution: Set rev info for audit status hyperlink and link to the Item's correct rev.
Bug ID 18761104: INSUFFICIENT PRIVILEGES TO RESOLVE THIS AUDIT ISSUE
Root Cause: When the user audits a change status, if the current user has no read privilege for the required fields, the system shows a summary warning or error instead of the required fields's name.
Resolution: Show the required fields's name detail instead of the summary warning or error.
Bug ID 18712256: COLUMN HEADER SORT ON ATTACHMENTS TAB OF DISCUSSION OBJECT
Root Cause: Range setting is incorrect when loading Discussion's attachment table.
Resolution: Set the range to 0 to load all table rows from cache.
Bug ID 18823810: THUMBNAIL FOR NOT CONFIGURED FILE TYPE IS REPLACED WITH ONE GENERAL
Root Cause: N/A
Resolution: N/A
Related Bugs:
Bug ID 18267965: THUMBNAIL SWITCHES TO "NA" AFTER RELEASE AND ADD TO A NEW CHANGE
Bug ID 18940793: UNABLE TO REPLACE THUMBNAIL ON DESIGN OBJECT IN WCM IF FILE TYPE NOT CONFIGURED
Bug ID 18936427: UNABLE TO WRITE THE XML FOR THE PRIVILEGE CONFIGURATION TYPE
Root Cause: This bug was due to a wrong filename in the classpath file in ACP.
Resolution: Change the filename to the correct one.
Bug ID 18886266: EXTERNALLY REFERENCED CAD MODEL DOES NOT LOAD
Root Cause: When check editing a Design object duplication row in the Relationship table (ctr and eff object are both Design object), Agile always throws a duplication error message.
Resolution: Do not check a duplication row with itself (it is always a duplication).
Bug ID 18795976: BY DRAG & DROP, IEVENTDIRTYROWUPDATE.GETREFERENT CAUSES ARRAYINDEXOUTOFBOUNDS EXCEPTION
Root Cause: The fix for bug #14002912 has a defect for event, which leads to this issue.
Resolution: Updated the fix with a better solution that does not affect event.
Bug ID 18887798: FILE MANAGER IS NOT AVAILABLE WHEN UPLOADING FROM WEB CLIENT
Root Cause: The original URL from the Java Client configuration is case sensitive, so when it does not match with the Web Client launch URL, the file server stops.
Resolution: Remove the case sensitive check on the original URL from the Java Client configuration.
Bug ID 18925941: ORDER OF ADD/DELETE REDLINES IN AXML FILE IS INCORRECT
Root Cause: AML redlines in aXML files is not correctly ordered by created time.
Resolution: Fix code to sort the AML redlines in aXML & PDX formats by the redline's created time.
Bug ID 19012368: JAVA.IO.NOTSERIALIZABLEEXCEPTION: JAVA.UTIL.ARRAYLIST$SUBLIST ERROR
Root Cause: A List instance returned by ArrayList.subList(), which is not serializable is put in web session.
Resolution: Use ArrayList instance directly.
Bug ID 19049841: EFFECTIVITY DATE DISPLAYED IN THE TOP OF THE ITEM OBJECTS AFTER UPGRADE
Root Cause: Some logic code segments are missing and the getAttributeVisibility function is not implemented.
Resolution: Disable information when Item subclass - title block Effective Date is invisible.
Bug ID 19060775: RUN WORKFLOW JOB FUNCTIONS WITHOUT USERS REPORT, DISPLAY APPLICATION
Root Cause: When the customer does not have a license for some base classes, the system generates NullPointerException when a sort is done with Null value.
Resolution: Sort while filtering out Null value.
Bug ID 19220537: UNABLE TO GET FILES BY CLICKING ON HYPERLINK IN INTERNET EXPLORER IF FILENAME CONTAINS HASH (#)
Root Cause: A file named with special characters ('#') has been encoded to Hexadecimal ('\x23'), but did not get converted back when trying to access the file.
Resolution: Added code to decode the filename from Hexadecimal to normal
Bug ID 19018508: CALCULATED COMPLIANCE GETTING COPIED DURING SAVE AS MANFACTURER PART
Root Cause: Copy all the values from the source to the target if completing Save As.
Resolution: Filter some attributes when doing a Save As for Item/Manufacturer Part/Part family.
Bug ID 19055628: SKD: IPROGRAM, SAVEAS ON THE TEMPLATE UPDATES AND RETURNS THE TEMPLATE
Root Cause: When two different sessions create activities from a template, in the meanwhile SDK sometimes throws a lock issue which makes the new activity created failed, but it causes the template name to be changed.
Resolution: Do a check when the creation of a new activity from a template fails.
Bug ID 18966064: USERS NEED THE ABILITY VIEW CRITERIA AND DO SAVE AS ON GLOBAL SEARCH
Root Cause: There's additional global search privilege checkwhen doing saved search from AI table.
Resolution: Use ArrayList instance directly.
Bug ID 19146522: UNABLE TO RELEASE DEVIATION DUE INDEX:2,SIZE:2 EXCEPTION
Root Cause: There is an IndexOutArray code defect that causes problems when we check the required attributes during workflow routing.
Resolution: Correct the defect in related functions to allow for proper workflow routing.
Bug ID 19157460: CANNOT 'GET' USING VIEW VERSIONS
Root Cause: 3 bugs in the code:
1. There is an incorrect registered table id being used when executing Get Attachment after view version pops up and closes.2. The incorrect object id is used in log history when executing a GET file in view version.3. The object has been modified after Getting the file from view version.
Resolution: Use ArrayList instance directly.
Bug ID 19138428: PLMEVENTACTIONPX EXCEPTION RESULT FORMATTED WITH HTML IS NOT DISPLAYED
Root Cause: Per the 932 XSS project, by default, messages are shown as plain text (HTML encoded).
Resolution: Exceptional messages from Event framework are shown as HTML format.
Bug ID 19255084: RUN BOM COMPARISON REPORT HAS ERROR(EMPTY FILE)
Root Cause: There is an encoding issue in the BOM Comparison Report.
Resolution: Read the input stream as UTF-8 encoding.
Related Bugs:
Bug ID 19148439: BOM COMPARISON EXPORTED REPORTS ARE BLANK
Bug ID 19127743: UNABLE TO ADD MPN TO PART THAT CONTAINS PARENTHESIS IN MPN
Root Cause: The parenthesis is not parsed well for the MPN case.
Resolution: Identify Manufacturers with parenthesis first and then identify the Manufacturer Part. This is based on the fact that the customer uses parenthesis in pair for Manufacturer. Also the solution is limited to type in add case.
Related Bugs:
Bug ID 19144084: UNABLE TO ADD SUPPLIER TO PART NUMBER IF SUPPLIER NAME CONTAINS PARENTHESIS
Bug ID 19239728: SUBCLASSES NOT LISTED FOR IMPORT MAPPING POST ACP
Root Cause: Array index out of Bounds issue.
Resolution: Make sure the array index is not out of bounds.
Bug ID 19261388: UPDATE TABLE EVENT PROCESS EXTENSION DOES NOT WORK AS EXPECTED FOR BULK CHANGE
Root Cause: There is no selected Item information when triggering the update table event.
Resolution: Add the selected Item info when triggering update table information.
Bug ID 19279678: HF 9.3.3.0.13 TO CHECK BROWSER TYPE BEFORE CHANGING THE CALL METHOD
Root Cause: Gray screen in Internet Explorer when the user launches synchronous AJAX.
Resolution: Added CSS property specific for IE filter: alpha(opacity=20);
Bug ID 19340584: CANNOT LOG IN TO AGILE FROM MCAD FOR USER WITH ALL NUMERIC LOGIN ID
Root Cause: If the WS client passes an all numeric login id, we treat it as internal DB id instead of a user name.
Resolution: First treat it as a username, but if we cannot search this name, we treat it as an internal DB id.
Bug ID 19260466: ADD/REMOVE BUTTONS ARE GRAYED OUT ON RELATIONSHIP AND ATTACHMENTS
Root Cause: We do not take consideration of ”Add to Table” and ”Delete from table” when deciding whether to enable the Add and Remove buttons.
Resolution: Add the selected Item information when triggering the Update table information.
Bug ID 19266350: FETCHING RESULTS IN THE TIME SHEET REPORT SEARCH DOES NOTWORK WITH BLANK CRITERIA
Root Cause: Incorrect logic on timesheet search.
Resolution: Correct the timesheet search logic.
Bug ID 19432989: SCHEDULED ROLLUP ISSUE -NO PRIVILEGE ERROR FOR AGILEUSER IN THE HISTORY TAB
Root Cause: Compliance rollup task is running by Agile user which is responsible for background task. The user did not have the Read privilege for spec.name.
Resolution: When getting the name of a Specification for log history, the Agile user must have the read privilege for spec.name.
Bug ID 19433010: DYNAMIC LIST IN SEARCH MODE ALLOWS USERS TO SELECT FROM OTHER USERS
Root Cause: The dynamic list of users with criteria does not call a proper API to retrieve data.
Resolution: Correct the code to call the API which requires the application to pass the list id.
Bug ID 19451772: ITEM ID INVALID IDENTIFIER ERROR
Root Cause: SQL general errors, Change. Affected Item.Product Lines belongs to read through multiple list attributes, but this attribute is special when appending table MSATT.
Resolution: Added special code to handle the Affected Item. Product Lines for Change, PSR and QCR.
Bug ID 19297336: CHANGE CANNOT BE RELEASED WITH ERROR JAVA.LANG.NULLPOINTEREXCEPTION
Root Cause: When the user edits redline information and saves it while using multiple windows, sometimes bad data were is created because the current parent object (Affected Item) that is in the grid context is not correct.
Resolution: Get the current parent object from the HTTP request and compare this object with the object in the grid context. If not the same, throw an error message and block the redline Save action.
Bug ID 19432951: TO RESTRICT SENDING THE OUT OF THE BOX NOTIFICATION TO THE CHANGE
Root Cause: When using auto-promote from Released status to Implemented status, the flag, notifyCCB, is true, and the default approvers/acknowledgers/observers set in Released status receive the status promotion notification if they are not approvers/acknowledgers/observers in Implemented status.
Resolution: Do not notify the CCB at Released status when using auto-promote to move from Released status to Implemented status.
Bug ID 19514089: UNABLE TO CREATE A PPM PROJECT FROM XML FILE IN 9.3.3
Root Cause: The method to check the relationship between parent and child is incorrect. It results in the error message ”A dependency cannot be added between root and leaf rows within the same hierarchy.”
Resolution: Correct the method that checks the relationship between parent and child.
Bug ID 19545788: APPROVERS AND OBSERVERS ARE NOT BEING NOTIFIED UPON ENTRY OF RELEASE
Root Cause: The logic for parsing default reviewer setting in a workflow has a defect which leads to this issue.
Resolution: Update the logic.
Related Bugs:
Bug ID 19512890: NOTIFY UPON ENTRY DOES NOT WORK FOR APPROVERS AND OBSERVERS
Bug ID 19581998: FTS IS NOT WORKING WITH 9.3.3 HF 30 AND HF 61
Root Cause: Characters ”{” and ”}” are not excluded from parameters validation.
Resolution: Exclude”{” and ”}” from parameter validation in the configuration file ”validation.properties”.
Bug ID 19831964: INTERNET EXPLORER 11 SUPPORT/ CERTIFICATION FOR AGILE 9.3.3
Root Cause: Browser detection fails when running in IE11.
Resolution: Force IE to go to the IE7 document mode and resolve corresponding bugs.
Bug ID 19606772: HF 9.3.3.0.13 TO CHECK BROWSER TYPE BEFORE CHANGING THE CALL METHOD
Root Cause: The user gets a gray screen in Internet Explorer when launching synchronous AJAX.
Resolution: Added a CSS property specific to Internet Explorer filter: alpha(opacity=20);
Bug ID 19774606: UNDO REDLINES ITEM NUMBER, IT WILL POP UP AN INSUFFICIENT PRIVILAGE ERROR
Root Cause: The fix for 16441863 introduced a code defect that even when the user has the Modify privilege for Item number, the redline row is invalid.
Resolution: Added a fix on top of 16441863. Kept the previous logic that when user has Modify privilege of bom.item number the redline row should be valid.
Bug ID 19774697: EFFECTIVITY DATE IN TOP BANNER SHOULD MATCH DATE TIME FORMAT IN JAVA CLIENT
Root Cause: Date and time is not converted to the user defined timezone.
Resolution: Change the code to convert the watermark/banner time to the user date format/timezone.
Bug ID 19880393: USER USAGE REPORT IS NOT WORKING PROPERLY FOR LDAP USERS
Root Cause: LDAP users over-reported their usage.
Resolution: Fixed the issue.
