Oracle Agile Product Lifecycle Management for Process 6.2 ...This software and related documentation...

Oracle Agile Product Lifecycle Management for Process Release Notes Release 6.2.2 E79127-04 January 2018

Copyright © 2018, Oracle. All rights reserved. ii

Copyrights and Trademarks Oracle Agile Product Lifecycle Management for Process Release 6.2.2 Release Notes

E79127-04

Copyright © 1995, 2018, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Copyright © 2018, Oracle. All rights reserved. 1

Contents CHAPTER 1: INTRODUCTION ................................................................................................ 3

Summary .............................................................................................................................................. 3 Product Support Note ............................................................................................................................. 3

CHAPTER 2: ENHANCEMENTS .............................................................................................. 4

What’s New in This Release? ................................................................................................................ 4 Hierarchy Denormalization ..................................................................................................................... 4

Enhancements ...................................................................................................................................... 5 Formulation Output Naming Strategy..................................................................................................... 5 Workflow Simplification .......................................................................................................................... 6 Change Owner ......................................................................................................................................... 7 Global Specification Search ..................................................................................................................... 8 Component Groups ................................................................................................................................. 8 Instance level Grouping Available within Breakdowns ......................................................................... 10 Items with 0% Composition Can now be Shown in LIO ........................................................................ 11 Refresh Hierarchy .................................................................................................................................. 12 Basis Refresh Warnings ......................................................................................................................... 13 BI Publisher 12.2.1.2 and 11.1.1.9 ........................................................................................................ 13 Workflow a Specification from Hierarchy Navigator ............................................................................ 13 Extensibility Enhancements .................................................................................................................. 13 Infrastructure Enhancements ............................................................................................................... 14

CHAPTER 3: RESOLVED ISSUES ......................................................................................... 15

6.2.2 Resolved Issues .......................................................................................................................... 15 General Resolved Issues ........................................................................................................................ 15 Content Synchronization and Syndication (CSS) Resolved Issues ......................................................... 17 Data Administration (ADMN) Resolved Issues ...................................................................................... 17 eQuestionnaire (eQ) Resolved Issues ................................................................................................... 19 Global Specification Management (GSM) Resolved Issues ................................................................... 20 New Product Development Resolved Issues ......................................................................................... 28 Product Quality Scorecard Resolved Issues .......................................................................................... 30 Ready Reports Resolved Issues ............................................................................................................. 31 Reporting Resolved Issues .................................................................................................................... 31 Supplier Portal Resolved Issues............................................................................................................. 32 Supply Chain Relationship Management (SCRM) Resolved Issues ....................................................... 33 User Group Management (UGM) Resolved Issues................................................................................ 34 Workflow Administration Management (WFA) Resolved Issues .......................................................... 35 Infrastructure Resolved Issues .............................................................................................................. 35

CHAPTER 4: HOT FIXES ........................................................................................................ 37

Hot Fixes ............................................................................................................................................. 37


Preface This document describes issues that you may encounter with this release. Internal Tracking numbers that appear in the tables are used to identify issues reported by customers. You can use these numbers to identify the issue should you need to contact Oracle Support. Locator numbers that appear in parentheses after some notes are for Oracle internal use only.

Chapter 1 Introduction


Chapter 1: Introduction

This chapter contains an overview of Release 6.2.2 of Oracle Agile Product Lifecycle Management for Process.

Summary Release 6.2.2 includes several enhancements and a number of bug fixes. If you are on a previous 6.2 release, to ensure the highest application stability possible, you are strongly encouraged to upgrade to 6.2.2. Please read through all Enhancements, Resolved Issues and Hot Fixes to fully understand what is included in this release. Documentation for Release 6.2.2 includes these Release Notes and several user and technical guides. For a complete set of user guides for PLM for Process, see the 6.2.2 release posted on the Oracle Technology Network (OTN): http://www.oracle.com/technetwork/documentation/agile-085940.html#plmprocess

Product Support Note Please note that product support for data that has been imported will only extend to data that could have been entered manually in the application user interface.

http://www.oracle.com/technetwork/documentation/agile-085940.html#plmprocess

Chapter 2 Enhancements


Chapter 2: Enhancements

This chapter contains new product features included in Release 6.2.2 of Oracle Agile Product Lifecycle Management for Process.

What’s New in This Release?

Hierarchy Denormalization (ID-59) Hierarchy Denormalization is a former solution pack that is now a core feature in PLM for Process. You no longer need to manage this feature as a solution pack. Upgrading to 6.2.2 will REMOVE all pre-existing denormalization data and new denomalization data will need to be generated. When upgrading or activating this feature make sure to plan for the amount of time needed to generate new denomalized hierarchy structures. Refer to the Agile Product Lifecycle Management for Process Hierarchy Denormalization Guide, “Performance Estimation for Initial Denormalization” chapter to help estimate time needed. Denormalization must be activated using the following steps:

a) Edit configuration file "<PLM for Process>\config\environmentvariables.config" and make the changes as below: PLM4P.HierarchyDenormDetectorService.Enabled = true PLM4P.HierarchyDenormProcessorService.Enabled = true PLM4P.HierarchyDenormInspectorService.Enabled = true

b) Edit configuration file "<PLM for Process>\config\Custom\CustomerSettings.config" and add the entry under node "<FeatureConfig></FeatureConfig>": <add key="HierarchyDenorm.Auditing.LifecycleEvents.Enabled" value="true"></add>

c) Restart RemotingContainer Service. d) Restart IIS.

To learn more about hierarchy denormalization refer to the Agile Product Lifecycle Management for Process Hierarchy Denormalization Guide.



Enhancements This release includes several enhancements, including formulation output naming and workflow simplification. These and other enhancements are described below.

Formulation Output Naming Strategy ID-53 Formulation output specification and short names can now be automatically assigned when the formulation specification saved. This is an extension that allows you to programmatically define your output naming strategy. The extension also includes the ability for the user to toggle auto naming on/off from within the user interface. Available with the release, the external output name can be inherited from the name of the formulation specification. This requires no development effort to configure. Learn how to configure your output names by referring to the Agile Product Lifecycle Management for Process Configuration Guide and refer to the Agile Product Lifecycle Management for Process Extensibility Guide for information on plugins. The screen below depicts customizing external output types.

Figure 1: Output name automatically updates to match the formulation specification



Workflow Simplification

UI Actions ID-7 You can now workflow a specification from multiple locations throughout the GSM application. You no longer have to be on the specification to initiate a workflow. Workflow is available from Hierarchy Navigator as well as specification search result listings. Calling the workflow dialog is also possible from other locations throughout GSM as an extension. This will allow you to place the workflow action in other locations throughout GSM using UI extensibility or navigation extensions. You can learn how to call the workflow dialog panel in the Agile Product Lifecycle Management for Process Extensibility Guide.

Figure 2: Right-click a specification within the hierarchy and select the Workflow action

Workflow Multiple Specifications at Once ID-66 You can now configure workflows to move multiple specifications at once using new out of the box workflow actions. You can learn more in the Agile Product Lifecycle Management for Process Extensibility Guide. Supported Relationships: • Trade > Lower Level Trades • Trade > Packaging Specifications • Trade > Material (+Owned Formulation Specification) • Trade > Referenced Output Material Spec • Referenced Output Material Spec > Produced By Formulations • Formulation > Material Inputs • Formulation > Material Input (+Owned Formulation Spec) • Pkg > Pkg SubComponents • GSM Activity > Related Items • Material Spec > Breakdown Material Component



Change Owner ID-69 Change Owner is available in GSM. Users with the [CHANGE_OWNER] can change current owner of a specification without re-workflowing the specification. For a single change, the user must have specification edit permission. For bulk change, the user must also have the ADMN site access role [DATA_ADMIN]. For more information, refer to the Agile Product Lifecycle Management for Process Global Specification Management User Guide.

Figure 3: Change owner in GSM Bulk Change Owner is available in ADMN. Users with [CHANGE_OWNER] role can use the new Change Owner Bulk Action and change multiple specification owners at once. For more information, refer to the Agile Product Lifecycle Management for Process Administrator User Guide.

Figure 4: Bulk change owner dialog in ADMN



Global Specification Search ID-69 You can now search for specifications using the Global Specification Search feature located in the GSM top menu bar. Global Specification Search allows you to search across all specification types by typing in at least 3 characters of the Specification Number, Name, Short Name or Equivalent. Refer to the Agile Product Lifecycle Management for Process Global Specification Management User Guide for more information. You will also find a new search criterion available for all GSM specification type searches called “Quick Search”. This will allow you to find specifications by typing in at least 3 characters of the Specification Number, Name, Short Name or Equivalent. This can be made to be the preferred criteria for all users by adjusting the search configuration files or can be set individually by selecting Customize and providing a saved search. Refer to the Agile Product Lifecycle Management for Process Search Extensibility Guide for more information around adjusting the default top search criteria. Material Specification Breakdown Components now included in LIO ID-56 We support material specifications as breakdowns to be expanded in the LIO tree. After generating the LIO tree, if your breakdown contains a material specification and this material specification has its breakdown, you can right-click on the material to show the breakdown of this material in the LIO tree. For more information, refer to the Agile Product Lifecycle Management for Process Label Ingredient Optimization Solution Pack.

Component Groups ID-72 A new grouping object called Component Groups is now available. Pre 6.2.2, you only had the option to associate component catalog terms to free text groups. You can now pre-define groups in component catalog using the Component Group object. These groups are available through a selection dialog when grouping your component catalog term. This simplifies grouping when in LIO, now all items using a specified component group will be automatically grouped together in your construction tree compared to individual nodes when using free text groups. Component Groups are more than just a name. They allow you to define attributes like external ID, status, default methods, restrictions and priorities.



Figure 5: Choices from left navigation panel

Figure 6: Choices from top menu bar



Figure 7: Component Group option and dialog Note: Free text groups are still supported but will be turned off by default. Use the following configuration to enable them. "GSM.ComponentCatalog.FreeTextGroups.Enabled"value="true" Turns on the ability to add existing free text groups in component catalog. By default, it’s false. See the Agile Product Lifecycle Management for Process Global Specification Management User Guide, Component Catalog chapter for more information and the Agile Product Lifecycle Management for Process Configuration Guide for more configurations.

Instance level Grouping Available within Breakdowns ID-72 You can now create instance level groups at the specification breakdown level. Pre 6.2.2, your only option was to rely on pre-defined groupings on the component catalog term or on the fly grouping from within LIO. Now you can designate groups at the specification level on the breakdown itself. This allows you to create complex structures from within a single breakdown. These instance level groups can be pulled into LIO using the Grouping action. Component groups are: • Included in formulation rollup calculations • Included in the specification print view • Available for selection by suppliers providing breakdown data in eQuestionnaire



Figure 8: Component Groups inside the breakdown control; hover action shows group composition

Items with 0% Composition Can now be Shown in LIO ID-58 For items that are defined as 0% in LIO tree, you can configure to list them in final statement when it suits your business. <setting key="LIO.DeclareZeroPercentElement.Enabled" value="true"/> When set to true, a component that is marked as 0% in LIO tree will be declared in final statement. By default this is true. Refer to the Agile Product Lifecycle Management for Process Label Ingredient Optimization Solution Pack for details.

Refresh Hierarchy ID-54 You can now refresh an entire formulation hierarchy with one action. The refresh hierarchy action refreshes all lower level input materials within the hierarchy, saving and recalculating the outputs. The Refresh Hierarchy action is available directly from the formulation specification as well as hierarchy navigator. Users with the role [FRM_ REFRESH_HIERARCHY] can refresh hierarchies from the formulation specification tools menu or Hierarchy Navigator. The user must have specification edit permission to all formulations that are in the hierarchy. You can also control whether refresh is allowed based on workflow status using the following configuration in CustomerSettings.config :  <add key="GSM.RefreshHierarchy.Impact" value="102"></add>. Users can also refresh hierarchies in bulk using the new Refresh Hierarchy Bulk Action feature in ADMN. For bulk change, the user must have the [FRM_ REFRESH_HIERARCHY] role as well as ADMN site access role [DATA_ADMIN]. Formulation edit permissions and workflow status validations are not evaluated when refreshing with the bulk refresh action. For more information refer to the Agile Product Lifecycle Management for Process Administrator User Guide.

Figure 9: Refresh Hierarchy Action on a Formulation Specification, Refresh Hierarchy Action within Hierarchy Navigator



Basis Refresh Warnings ID-54 You will now be alerted when the basis could potentially need to be refreshed. Warning icons will appear in the formulation inputs grid, formulation tools action menu and hierarchy navigator. This warning can be disabled using the following configuration lines: <add key="GSM.FormulationInput.RefreshWarning.Enabled" value="false" configDescription= "Provides a warning icon on input basis icon and message when hovering over if the input material item requires refresh." /> <add key="GSM.Formulation.RefreshWarning.Enabled" value="false" configDescription= "Provides a warning icon next to the refresh button if one of the input material items requires refresh." /> <add key="GSM.Formulation.RefreshHierarchyWarning.Enabled" value="false" configDescription="Provides a warning icon next to the Refresh Hierarchy button if one of the input grandchild material items requires refresh." />

BI Publisher 12.2.1.2 and 11.1.1.9 622-397 (Bug ID 21493010) Agile PLM for Process 6.2.2 fully supports BI Publisher 12.2.1.2 and 11.1.1.9. To learn more refer to the Agile Product Lifecycle Management for Process Install_Upgrade Guide and the Agile Product Lifecycle Management for Process Configuration Guide.

Workflow a Specification from Hierarchy Navigator ID-7 Workflowing a specification from the Hierarchy Navigator panel is now available. You can right-click on the specification from the panel then select Workflow to workflow a specification just like you do when you open this specification and workflow. This feature can be implemented from other places as well. To learn more refer to the Agile Product Lifecycle Management for Process Workflow Administration User Guide and the Agile Product Lifecycle Management for Process Hierarchy Navigator Solution Pack.

Extensibility Enhancements

Table 2-1 Extensibility Enhancements

Bug/Enh ID Issue Resolution

N/A

The Rich Text editor used throughout Agile PLM for Process is now extensible. Refer to the Agile Product Lifecycle Management for Process Extensibility Guide for more information. (622-1407)



Infrastructure Enhancements

Table 2-2 Infrastructure Enhancements


20796961

To enhance security using key stretching, the hash function is now run for configured iterations to produce a derived password. (622-387)

21493010

Agile PLM for Process 6.2.2 fully supports BI Publisher 12.2.1.2 and 11.1.1.9. To learn more refer to the Agile Product Lifecycle Management for Process Install_Upgrade Guide and the Agile Product Lifecycle Management for Process Configuration Guide. Support has been removed for versions 11.1.1.7 and 11.1.1.5. (622-397)

Chapter 3 Resolved Issues


Chapter 3: Resolved Issues

This chapter contains resolved issues for Release 6.2.2 of Oracle Agile Product Lifecycle Management for Process.

6.2.2 Resolved Issues The following tables outline known issues that have been resolved for Release 6.2.2 of Oracle Agile Product Lifecycle Management for Process.

General Resolved Issues Table 3-1 General Resolved Issues


23059250

When attempting to open a supporting document with a comma in its file name, an error is displayed. This only occurs when using Chrome. Root cause: When the file name contains comma, "Content-Disposition" cannot be recognized correctly.

The file name is double quoted when adding it as head "Content-Disposition". (622-1486)

23185363

One of the values in a simple extended attribute in the system contains an apostrophe. The value is “Supplier's Technical Specification”. In the database and in the ADMN application the value appears correctly. However when the extended attribute is placed on a material specification, the value shows as “Supplier\'s Technical Specification”. Root cause: The value was escaped as javascript string.

The escape was removed, and the correct value is displayed. (622-703)




22828652

The most recently used list of formulation output material specification status was not updated. The status of the formulation output is shown incorrectly (relative to the formulation specification) on the history navigation. It doesn't reflect the change until the user edits and saves the formulation output material. The status is misleading. Root cause: The refresh of output material’s workflow status in MRU wasn’t considered.

If formulation output material is in the MRU list, when workflowing or resolving the workflow of the formulation, the output material’s workflow status in MRU should be refreshed. (622-538)

22925564

There is no spacing between an extended attribute value and any additional labels or UOM in custom sections on v6.2. This is a presentation problem for both web UI and the Specification Print function. Root cause: When an extended attribute is displayed with a UOM there is no space between the UOM and the value.

Added space between value and UOM. (621-1664)

24831850

Customer recently upgraded to 6.2.1 and noticed that the Italian Preferred culture doesn’t allow them to manage numeric data. Both on nutrient profile and trade specification they experienced that the system doesn’t allow numeric data to be inserted. Root cause: The thousand separator in Italian is '.'. The code didn't handle this.

Replace '.' with ',' so that the numbers will be uniform in different cultures. (622-1440)

24927633

Formatting is removed when printing the out of the box print templates on specifications including formulation, material, ingredient statements and nutrient profiles. Root cause: Text was encoded.

Correction to text, and now formatting is retained. (622-1444)

25174652

User provided text instead of numbers inside number of day required in action dashboard and received an error message. Root cause: Non-numeric characters cannot be converted to a number.

Check if the input can be converted to a number. Limit the input characters. (622-1604)




25525916

When creating calculated nutrient values using the Italian preferred culture, the results are that the same calculation works if run by a user with English preferred culture but does not work correctly if run by a user with Italian preferred culture. Root cause: When configuring formula in configuration, parser will try to convert number to double-type data relying on the Decimal Separator of current UI language.

Formula parser now always regards '.' as Decimal Separator when converting and sending number. (622-1842)

25537058

How do users turn back on the ability to cursor (spaces, also lines) while editing a Free Text? Root cause: Focus moves when Left/Right/Down/Up arrow key is pressed.

For the text area, stop focus from moving when Left/Right/Down/Up arrow key is pressed. (622-1818)

Content Synchronization and Syndication (CSS) Resolved Issues

Table 3-2 CSS Resolved Issues


23588570

Extended attributes cannot be created in TIPs. Root cause: The last changes were not posted to the server side.

Made the EA grid listen to all changes. (622-878)

25582580

CSS is not pulling Brand from the trade specification when publishing to other systems. Root cause: From v6.2.0, except Free Text type Brand, a new Type Ahead type Brand is also supported. But for the new type Brand, CSS doesn’t include it.

Added the new type Brand to CSS. (622-1810)

Data Administration (ADMN) Resolved Issues Table 3-3 ADMN Resolved Issues


22986118

Incorrect time showing in Cache Flush table. Root cause: Wrong logic in AM or PM calculation.

Changed the FlushAMPM in Web\portal\CacheAdmin\ ctlScheduleCacheGroupFlush.ascx.cs. (622-407)




23305228

A custom section was created that contained a custom qualitative lookup extended attribute; this attribute was based on a custom view with 19000 rows. Added the section on the template and as soon as a new issue was created from the template, the issue saves but then upon clicking the Ext Data tab in PQM, a length of string error is returned. Root cause: The length of the string exceeds the value set on the maxJsonLength property.

Changed the default value to allow as many characters as possible. (622-1820)

24484829

Raw material specifications have an extended custom section which is a custom qualitative extended attribute dropdown. The values are populated from a separate file. When users add it to a specification, and edit it, it does not show the values for selection. Root cause: Application was always trying to load Spanish values if a user with Spanish preferred has logged in as cache initiator.

Dev package loads English values as well. (622-1615)

24760981

When users click the Preview button in a custom section, they get an unhandled error. Root cause: The custom section instance didn't have the root object when previewed.

Set the container as its root object. (622-1373)

25237605

While downloading the document which is in a legacy section, if users open that DRL a loading page remains displayed the entire time during download. It remains displayed even after successful download. Root cause: When attempting to open a legacy attachment whose file-type isn’t supported, the file will be downloaded and the popup loading page will be reserved.

If the file type of a legacy attachment is supported, open it in popup, otherwise, download it without showing any popup. This behavior corresponds with new Attachment section called SDMAttachment. (622-1677)



eQuestionnaire (eQ) Resolved Issues

Table 3-4 EQ Resolved Issues


21263827

Upon receiving an eQ and clicking eQ to GSM a user noticed that the formatting of the columns was uneven. The column which contains an operator value is much bigger than any of the other data columns and it compresses the way the actual data looks when there is plenty of space that can be taken from the operator column. Root cause: Missing set column item width. (<PLM4P_Home>\Code\Web\eQ\ ProductQuestionnaireViewer\Compliance.ascx)

Set the column item width on all Compliance tabs. (622-25)

25429863

After resending a retracted eQ, the guidance/comments do not get updated when received by the supplier. Root cause: The verification popup can’t synchronize the latest information with base page which is in edit mode.

Made data transport on front-end to synchronize information when in edit mode. (622-1849)



Global Specification Management (GSM) Resolved Issues

Table 3-5 GSM Resolved Issues


9221834

GSM translation errors occurred. Root cause: The pkid of 'Lowest Score’ we use for translation is different from the actual one. Added the translation. (622-43)

18298907

After migrating from 5.2.2 to 6.1.1.2, rich text for process step information under formulation specifications do not show borders for tables. Root cause: Failed to set property 'border' correctly when printing each TD tag when the entire table has a border value, such as 'border=1'.

Use property value of entire table for each TD tag when printing table. (622-98)

19150040

Font size and style gets changed when user changes the font color on Process tab of a formulation specification. Root cause: Changing the style of text to Bold created a <b></b> element. Then changing the font color of the text pulled the 'fontsize' from the element.

Changed el.style fontSize to Dom.getStyle(el, 'fontSize'). (622-96)

20373888

Rich text does not print background color correctly in PDFs. Root cause:

The Agile Product Lifecycle Management for Process Global Specification Management User Guide has been updated with this issue. (622-94)

21563402

The out of the box Product Spec Comparison Report has the following issues: 1. The max number of pages is based on

how many specifications chosen and not how many pages there actually are.

2. There are various bounds issues: Sourcing Type overlapping Receiving Facilities in Sourcing Relationships comparison.

3. The cross reference column data has added periods.

4. Custom sections not appearing correctly. Root cause: Last page block is missing. The last page block was added. (622-29)




22501262

The preview button for multi-component is not showing the % yield correctly. Root cause: TopLevelParent in LIOElementBase can only handle two tree levels.

The code has been fixed and the correct % yield is shown. (622-338)

22953481

When workflowing a material specification to a stage with required signature approvals, the comments provided in the notification emails were incorrect. They did not match the comment shown on the Approval/Audit Trail tab. It if the same specification was workflowed back to the previous stage and then workflowed forward again, the comment displayed in the notification email this second time did match the original comment shown in the UI. Each time the notification email comment appeared to lag behind by one iteration through the process. Root cause: When sending signature mail, table SpecWorkflowAuditHistory did not contain the latest comments and was not being updated.

Send signature mail after table SpecWorkflowAuditHistory is updated. (622-406)

23019772

Notification emails were not sent when functional area is blank (None) on the workflow step. Root cause: The null value for FunctionalArea field was overlooked when formatting the email body.

Added handler for null FunctionalArea field when formatting email body. (622-547)

23134249

"@specTypeName@" placeholder from Email Extensibility is not working for nutrient profiles. Root cause: The translation for GSMLib/BusinessObjects/lblType5750 was missing. The translation was added. (622-1013)

23255172

Hierarchy Navigator for trade specifications is not exporting to Excel when the specification name contains a special character (forward slash '/)', in the name of the specification which is in turn used as the name of the sheet in the Excel workbook. Root cause: Characters such as \ / ? * [ ] : are not allowed in the name of worksheet.

Replace special characters with _. (622-756)




23340897

There are values in the theoretical breakdowns that do not match the regulatory breakdown on the Composition tab of the Formula Output popup. Even with the Automatically Refresh option checked, the regulatory breakdown still doesn’t exactly match the theoretical breakdown. Root cause: The precision for PLM4P has been updated. The precision is configurable from the UI.

For calculation, corresponding configuration was added in the configuration files, and regulatory breakdowns now exactly match the theoretical breakdown. (622-881)

23506035

Manually entered breakdown components do not roll up properly on formulas. Root cause: After applying the hot fix 6.1.1.6.2, the regulatory breakdown did not work properly. Also precision for Percent Formulation value as 6 digits was hard coded when judging whether Percent Formulation changed. The issued data reported by the customer exceeded precision of 6 digits.

Fixed the regulatory breakdown issue and used precision of 12 digits. (622-885)

23549067

Hierarchy Navigator disappears. Root causes: 1. Opening Hierarchy Navigator from BI

Publisher caused a script error due to cross site security.

2. Popups were opened in iframes(YDialog) since 6.2, while Hierarchy Navigator would not be displayed by the original design.

Adapt the code to the float popup window introduced in 6.2. (622-877)

23736192

In the Formulation Output basis, when users convert unit of measure from 100g to 100ml, they see differences in the way conversion takes place between theoretical, override and specification values. Root cause: This was a pre-existing bug that was not addressed before new functionality was added.

1. When users convert unit of measure

to convert 100g to 100ml, the specification per 100ml value matches the overrides value or theoretical value.

2. If the nutrition has no overrides value but comments, the specification value matches the theoretical value instead of no data.

3. The nutrition source pushes to output material instead of all displaying ‘Theoretical’. (622-954)




24404825

After upgrading to 6.2.1 users cannot see the menu items Issue and Copy unless, in the related specification workflow status, they don’t have write permission. This behavior is different from previous versions. Root cause: This was introduced with an enhancement in 6.2.2 which gave the ability to copy a template to create another template using a template creator role.

User must have corresponding specification create role, for example, for Menu Item, user must have [SPEC_CREATOR_6500] or [SPEC_CREATOR], or he cannot see Issue and Copy even though he can read the specification. For template copy and issue, user must have [TEMPLATE_CREATOR] role. (622-1098)

24559307

On a packaging material specification, if a user's Global Spec UOM setting is set to a specific value, the specification displays an error when navigating between tabs. Root cause: If a specification’s packaging material General Preferences UOM was not defined, the user’s Global Spec UOM was used. User’s Global Spec UOM used MassVolumeUOMList. But out of box MassUOMList are used for specification’s packaging material General Preferences UOM.

Use MassVolumeUOMList instead of MassUOMList. (622-1335)

24515866

If a master specification has an image attached as a supporting document, printing of a related trade specification in GSM does not allow for selection of this image as part of the output. Root cause: The handling of SDMSupportingDocuments (type='1208') when acquiring print items in explicit master specifications, trade specifications and menu item specifications was missing.

The functionality has been added. (622-1301)

24563889

The user received an error when printing a supporting document on a menu item specification. Root cause: The handling of SDMSupportingDocuments (type='1208') when acquiring print items in menu item specifications was missing.

The handling of SDMSupportingDocuments was added. (622-1330)




24690366

Apostrophes in spec names prevent "Approve/Reject" window from opening in Supplier Portal. Root cause: Specification name was not encoded when passed by the url query field. Single quote will cause javascript errors. Encode specification name. (622-1417)

24702123

Report layouts for internal and external trade specifications are the same. Root cause: Print option "ddStyleLayoutSpecification" is missing. The name of form input was changed in 6.2.

Added "ddStyleLayoutSpecification" to print options. (622-1374)

24758736

When refreshing the identified formulas for the first time in a session, the user receives a timeout error. Root cause: The Formulation refresher performed a bulk-load when reading EA section items, but that was just done instance by instance. Once the number of EA sections is big, the similar queries on the polymorphic EA objects introduced a heavy cost.

Extend the bulk-load session up to EA section container and allow adjust of the optimization with the extension configurations. (622-1654)

24912060

Enter key causes page to reload. Root cause: Javascript function 'forNoLineBreaksTextareas' is used to prevent postback when clicking Enter if the text field has the 'IsMultiLine' attribute, or the page will post back by default.

Added attribute "IsMultiLine" to the Short Name text field. (622-1438)

25120997

In the Add Inputs prompt in a formulation specification, if you click the Done button more than once, inputs are duplicated in the formulation. Consider the Done button locking the modal popup window so no further input can be provided. Root cause: When the code is adding the selected input to current formulation specification, user is still able to click the Done button, which adds the input again.

Display 'Please wait' and disable all mouse clicks on this popup. (622-1640)




25210137

When user attempts to customize a trade specification, user receives error: . Invalid object name 'gsmApprovedUsageConceptJoin'. Root cause: Table gsmApprovedUsageConceptJoin has been deprecated since 6.2, but config\Extensions\EQTModelCustomExtensions.xml was not modified accordingly.

Replaced gsmApprovedUsageConceptJoin with the new table, gsmSpecConceptJoin. (622-1624)

25311798

When attempting to change the font in a formulation step instructions, user receives an unhandled error. Root cause: In Chrome browser, font-family: "Arial Black", which contains encoded string ", an error occurs in recognizing the font style.

Removed " from style, making the font style recognizable. (622-1672)

25368718

Signature request emails showing “N/A”, Root cause: When sending signature mail, we tried to get the latest comments from table SpecWorkflowAuditHistory. If using EmailMessageCommand, this generates the email body before committing the transaction, But at this point, the table was not updated.

Changed EmailMessageCommand to EmailCommand, EmailCommand will be run after committing the transaction. (622-1702)

25389461

Incorrect formulation output compliance rollup if material inputs have 0 quantity. Root cause: If a material has a Complies With item, and quantity is 0 on related formulation specification as input, then it will show as Compliant in Complies in the Formulation Output’s compliance rollup but show as Not Compliant in the detailed Nutrient/Property Breakdown window. That is not consistent.

When %Composition is equal to 0%, we will not show it in the Nutrient/Property Breakdown window. (622-1819)




25394702

When copying or issuing a nutrient profile, the ingredient statement at the bottom does not show while still in edit mode. Root cause: After clicking Copy and before saving the data of the ingredient statement, it has not been recorded in the database. So the rich text editor fails to read the information in time.

When creating a new specification (from blank/template/copy/issue), the rich text editor will get data from original "INGREDIENT STATEMENT" value in context (if exists) only on current UI language. This behavior is consistent with other text areas. (622-1797)

25536961

Historical Signature Document information is incorrect whenever the workflow step has been cycled through multiple times. Root cause: The time span between workflow time and sigDoc’s creation time is used to get all SigDocs for any workflow stage. We use this timeSpan.Seconds<2 to indicate valid SigDocs. That’s not correct and we should use timeSpan.TotalSeconds<2.

Use the total seconds of the time span instead. (622-1795)

25546104

When attempting to add a sourcing approval to a GSM material specification, user receives an unhandled error. The user who faced this issue has only SCRM Sourcing Approval Reader access. User should receive a more user friendly error message. Root cause: [SAC_CREATOR] was not used to determinate the visibility of the Create New button.

Check role [SAC_CREATOR]. (622-1796)

25711900

Calculation Numeric script uses 100g nutrient value to calculate result. When this custom section is used in formulation specification where 100g to 100m conversion takes place, the Calculation script does not appear to be calculating based on 100g values and instead calculates based on 100ml values. Root cause: When users convert unit of measure from 100g to 100ml, the custom section recalculates based on 100ml.

Calculate custom section based on 100g even when users convert unit of measure from 100g to 100ml. (622-1864)




25748459

When copying a formulation, the equivalent numbers are not copied to the new formulation but they are copied to the new formulation output specification. Root cause: When copying a formulation, the cross reference field is not copied to the new formulation. However it is copied to the new formulation output specification even though the specification isn’t a template.

The behavior of formulation outputs (not reference) now correspond with row material/formulation in copy/issue mode. (622-1874)

25757863

When attempting to navigate to the Theoreticals section under the Compliance tab, the user receives an error. Root cause: In the Complies With section of a formulation output, when clicking a row whose Theoretical Name is null, the popup page crashes due to incomplete information.

As designed, if a row whose Theoretical Name is null, then it cannot be clicked in read-only mode. (622-1875)



New Product Development Resolved Issues

Table 3-6 NPD Resolved Issues


23116493

TMFR members disappear from the project after Workflowing to the next step. Root cause: After completing a workflow transition of an activity, the project and stages are refreshed and it is no longer possible to save the activity.

Project and stages are no longer refreshed after completing a workflow transition of an activity. (622-578)

23310011

Routing Requirements on NPD activities do pull relevant members of a functional area from the Project Team of the related project when the Set Based on Project mode is set to Yes and project stage Evaluate All Criteria is selected. However, when a step has only Owner and no Signature Request nor Additional Notifies, no email is sent to the owner. When a step has both Owner and Additional Notifies set up, both sets of emails are sent.

For ALL Members mode in Owners, use “SELECT_MANY” not “SELECT_ALL” as the workflow control key as is done with signators and notification recipients. (622-697)

23732710

Workflowing an NPD activity to a step with a group as Owner causes an unhandled error. Root cause: Selection mode from 6.2.0 cannot be null, but old data contained a null value for it. (622-1096)

24335568

Clicking on a stage icon for an NPD activity opens a window containing an error. Root cause: Cannot cast object of type 'Xeno.Prodika.PLM.Framework.BusinessObjects. PLMMultiPartAttachment' to 'System.WeakReference'.

For type 'Xeno.Prodika.PLM.Framework. BusinessObjects. PLMMultiPartAttachment', rather than cast it to 'System.WeakReference', this issue was fixed within “Document Collaboration with in-place editing” and “Document Collaboration” type activities. (622-1039)

24363473

Workflowing NPD activities causes unhandled errors. Root cause: In our code, Actual Additional Notifies equals all users and group users defined in Additional Notifies section plus all TSAs of such users. But if duplicated users existed in the two user collections, this issue occurs.

If one user has been added as an Additional Notifies, it will not be added again. This resolved the issue and activities can be workflowed normally. (622-1093)




24364008

As part of upgrading from 6.1 to 6.2, project and activity templates were updated based on requirements for Owner membership (for example Evaluate First vs. Evaluate All radio buttons). Refreshing the projects from their templates has removed all pending action items associated to them. Root cause: After upgrading from 6.1 to 6.2, a new table 'npdActivityTempStepOwnersJoin' was added to record the relationship between activity step and its owners. The data in the table is used when refreshing the template. However data migration for the table did not occur and this caused the action items loss after refreshing the template.

Data migration occurs for the table 'npdActivityTempStepOwnersJoin', and existing action items are no longer removed. (622-1124)

24440394

When attempting to create instances of activity of type “Document Collaboration with in-place editing”, downloading a copy of the attached document, updating values, renaming and adding a file and then try to save the instance caused an unhandled error. Root cause: The data was designed to delete twice. An error occurred at the second delete, because it had already been removed. Only remove data one time. (622-1191)

24837463

The NPD POP function is giving time out errors when an activity of type "Project Schedule" is selected for output with the PDF output format. Root cause: The print template was set with keep-together on. So the time-out error occurred when there were too many project schedules to print to more than one page.

Modified the print template to enable the project schedule to print to more than one page. (622-1589)

25106361

User search generates different SQL than other users when searching for specific projects. Root cause: In table plmStageGateWorkflowStatuses, a special stageNumber was used for such two statuses. But in table commLookups (Category='NPDDevelopmentStage' ), available stage name was not recorded for the statuses.

When project was in Terminate or Complete status, no stage was related to it. A blank stage name for stageNumber was added. (622-1588)




25652956

NPD team leaders have the edit button but are unable to update the TMFR. Root cause: NPD project leader cannot update Condition, Gate Keeper, Additional notes, or Guidance due to the changes of design.

Corresponding to 6.1.1.6, NPD project leader should not be able to update below grid in TMFR (from template): Functional Area, Required (checkbox), but is able to update other grids regardless of admin role. (622-1831, 33623)

Product Quality Scorecard Resolved Issues Table 3-7 PQS Resolved Issues


20807590

PQS scorecard titles do not align with the scoreboxes. Root cause: The columns did not have the appropriate attribute to align anchor titles to the scoreboxes.

Adjust the column’s attribute to align the anchor titles to the scoreboxes. (622-133)

25065771

On PQS Session, when user wants to change the scorecard type, user has to hit Ctrl F5 before the pull-down with the options are available for user to choose. Root cause: Drop down scorecard type and status were not refreshed since 6.2.

Refresh the page after entering edit mode as done in 6.1.*. (622-1546)

24752597

In Chrome, when viewing a sample in a PQS session, there is no Close button. Root cause: The path of the image in the css is /gsm/images/close.png, while the PQS was deployed under a different environment. So the image was not accessible. Use a relative path instead. (622-1606)



Ready Reports Resolved Issues

Table 3-8 Ready Reports Resolved Issues


24349987

When attempting to create a new report in 6.2 selecting Nutrient Profile as the Target Object and Category Equals as the criteria leads to a 404 error when the green plus sign is clicked. Root cause: Incorrect path was defined for MultiTreeviewPopUp.aspx.

The path for MultiTreeviewPopUp.aspx should be @APP_PATH@/WebCommon/Popups/. Titles now align correctly. (622-1097)

Reporting Resolved Issues Table 3-9 RPT Resolved Issues


24610031

One of the reports the customer had configured in PLM4P v6.1.1.5 failed to work properly in PLM4P v6.2.1.0. . In the report generation screen, a pop-up window failed to load properly. When selected the, the pop-up window displayed the ‘Loading’ message until it eventually timed out and the user was presented with an error message. Root cause: The database was accessed too many times, causing performance problems.

Data is retrieved only once and then processed in memory. (622-1333)



Supplier Portal Resolved Issues

Table 3-10 SP Resolved Issues


21803794

When attempting to submit changes on one of the specifications in Supplier Portal, the user receives an unhandled error. Root cause: The eQ created will be also archived if the template is archived. But archived eQs cannot be sent by design.

Now, templates cannot be archived. Before archiving an eQ, validate if it is a template. (622-10)

23608134

Trade eQ custom section was not showing fields as required. Root cause: The required star icon was invisible even though it did exist.

In order to show the red star icon always, style “display:block;” was added for css class “cssxIcoRequired”. (622-880)

24403296

When a sourcing approval goes to review and a supplier rejects it, an email to a single-selected individual works correctly. However the email does not work when sending to a selected group. Root cause: This function returned Group_PKID.

It now returns allUser_PKIDs in a given group instead. Email is now sent to the group if a group is selected when the supplier rejects a sourcing approval. (622-1094)

24461222

After logging in to Supplier Portal, user accesses the EQ section and then clicks on an open EQ. It opens the EQ in a popup window and there is no way to close the window. No Close button is provided. Root cause: This issue happened when Supplier Portal and GSM were deployed to different servers.

Background images were updated in Web\css\CommonStyles.css. (622-1230)



Supply Chain Relationship Management (SCRM) Resolved Issues

Table 3-11 SCRM Resolved Issues


22958084

Supplier Contact report must have business unit (BU) specified to run properly. Root cause: BU is a mandatory. But when only status is selected and BU is not selected, the report is generated.

Error message is now shown and the report cannot be created. (622-542)

23109611

Send notification to sourcing supplier tag is not working. Root cause: In Code\Libs\SCRMLib\ SupplierServiceImpl.cs, the old table was used to acquire supplier user (spSupplierRepSCRMCompaniesJoin, spSpRepSCRMFacilitiesJoin).

The new tables ContactCompanyRelationship and ContactFacilityRelationship replace the old ones (622-572)

23128551

Incorrect date shows in SCRM. This was expected to be fixed by a PQM patch. Root cause: Code retrieved culture from default.

Now culture is retrieved from current user’s culture. (622-533)

23272247

For several facility titles in SCRM containing CR/LF, the user cannot see the Business Unit or complete custom section because of missing scroll bars. Root cause: CR/LF were not escaped in javascript. The javascript function was broken.

Escaping special characters when the string was rendered in javascript has solved this issue. (622-787)

25191091

When attempting to customize the search criteria for Supplier Document - Company/Facility Search, user receives an error. Root cause: Current model name "Supporting Docs - Company/Facility" is detected as a potentially dangerous request queryString by XssSecurityUtil.

Removed validation for model name. (622-1666)




25484486

When attempting to add a facility to a company with cross reference System Name matching the user’s Profile & Preference Settings System Code (SCRM), the user receives an unhandled error. Root cause: If User System Code is equal to certain cross reference, there is an invalid access to an uncompleted data the first time saving a facility.

Make checks when saving to guarantee data consistency. (622-1808)

User Group Management (UGM) Resolved Issues Table 3-12 UGM Resolved Issues


24400940

UGM change request notifications display incorrect source. Root cause: An email address was used to recognize a user. Different users with the same email address were added as well.

Now email address and user’s name is used to recognize a user. (622-1095)

25294117

Customer has users whose email addresses have single apostrophe. When users enter the email address with single apostrophe, an error is returned. Root cause: When approving the user creation request, the email address which contains apostrophes made the sql syntax not correct. Escape such characters. (622-1657)



Workflow Administration Management (WFA) Resolved Issues

Table 3-13 WFA Resolved Issues


21968957

Performance testing revealed that opening large workflow templates takes a long time. Root cause: A single-page-based browser-rendering issue was investigated.

The following pages were changed. 1. Web\wfa\TemplateControls\ctlInterme

diateActivityTemplate.ascx 2. Web\wfa\TemplateControls\ctlInitialA

ctivityTemplate.ascx 3. Web\wfa\TemplateControls\ctlLastAct

ivityTemplate.ascx (622-1034)

23255060

When attempting to change Amber In/Red In days in a workflow template, the user gets an error. Any number less than 366 works for the two fields. The user is not able to update Amber or Red days greater that 365 on workflow SLA. Root cause: The number 365 was hard-coded as the maximum number for Amber SLA and Red SLA.

The max limitation was adjusted to 1000 for both fields. (622-702)

24456487

Unable to customize in WFA after adding country in UGM customization. Root cause: WFA doesn’t support EQT Model Custom Extensions.

Update web.config to make WFA support EQT Model Custom Extensions. (622-1587)

Infrastructure Resolved Issues Table 3-14 Infrastructure Resolved Issues


9221834

Translation errors occurred in several applications. Root cause: The pkid of 'Lowest Score' in our certified database is different from the other database.

1. At the beginning of processing translation, run script in certified database to add data to make it match those in other databases.

2. Insert record into table commonlookups. 3. Insert it into commonLookups 4. Select the pkid from dual where it does not

exist. (622-43)

20796961

To enhance password derivation, the hash function is now run for configured iterations to produce a derived password. (622-387)




24415173

The following parameter in the EnvironmentVariables.config file can be a little confusing for customers. PLM4P.DB.URL = data source=SERVER\DATABASE;user id=USER;password=PASSWORD Root cause: As this is not a code defect, a connection string sample is required.

Added comments for SQL Server connection string. (622-1704)

Chapter 4 Hot Fixes


Chapter 4: Hot Fixes

This chapter contains hot fixes included in Release 6.2.2 of Oracle Agile Product Lifecycle Management for Process.

Hot Fixes The following table lists hot fixes that are included in the Oracle Agile Product Lifecycle Management for Process 6.2.2 release.

Table 4-1 Hot Fixes

Hot Fix Issue Resolution

6.1.1.4.44 See bug 23116493 in New Product Development Resolved Issues. 23116493 (622-578)

6.1.1.4.46

When a user adds a particular extended attribute to a custom section, its values disappear. Root cause: Application was always trying to load Spanish values if a user with Spanish preferred has logged in as cache initiator.

English values are loaded as well. 24484829 (622-1615)

6.1.1.5.34

See bug 23736192 in Global Specification Management (GSM) Resolved Issues.

1. When users convert unit of measure to convert 100g to 100ml, the specification per 100ml value will match the overrides value or theoretical value.

2. If the nutrition has no overrides value but comments, the specification value will match the theoretical value instead of no data.

3. The nutrition source will push to output material instead of all displaying ‘Theoretical’.

23736192 (622-954)

Chapter 4 Hot Fixes



6.1.1.5.35

Sourcing approval was missing workflow owner after Supplier Review. Root cause: When supplier user workflows SAC via Supplier Portal, the entire group should be treated as owner when the next step has owner assigned. But out of box, the group was ignored, and also notification mail was not sent to the entire group.

The entire group should be treated as owner when the next step has owner assigned under the following three selection modes: One Member, Multiple Members and ALL Members. Also the entire group should receive notification mail. 24843158 (622-1487)

6.1.1.5.36

See bug 25711900 in Global Specification Management (GSM) Resolved Issues. 25711900 (622-1864)

6.1.1.6.7


23506035 (622-885)

6.1.1.6.8

See bug 23272247 in Supply Chain Relationship Management (SCRM) Resolved Issues.

23272247 (622-787)

6.1.1.6.10

Refresh formulation gets request timeout. Root cause: The formulation refresher performed a bulk-load when reading EA section items, but that was just done instance by instance. Once the number of EA section items is large, the similar queries on the polymorphic EA objects introduced a heavy cost.

Extend the bulk-load session up to the EA section container and allow the optimization to adjust with the extension configurations. 24758736 (622-1654)

6.1.1.6.11

Trade specification gross weight calculation is not correct when density is included. Root cause: When density existed, we calculated Gross Weight based on density, and then converted the final calculation result based on UOM 'kg' again.

When density exists, only convert Gross Weight based on kg one time. 25106777 (622-1598)

6.1.1.6.12

See bug 21968957 in Workflow Administration Management (WFA) Resolved Issues. 21968957 (622-1034)

6.1.1.6.13


23019772 (622-547)

6.2.0.0.13

See bug 23109611 in Supply Chain Relationship Management (SCRM) Resolved Issues. 23109611 (622-572)

Chapter 4 Hot Fixes





6.2.0.0.16

See bug 24363473 in New Product Development Resolved Issues and bug 24400940 in User Group Management (UGM) Resolved Issues.

24363473 (622-1093), 24400940 (622-1095)


6.2.0.0.19


6.2.0.0.20 See bug 24349987 in Ready Reports Resolved Issues. 24349987 (622-1097)

6.2.0.0.21


23506035 (622-885)

6.2.0.0.22

When attempting to create a report selecting trade specification as the Target Object and Business Unit Equals as the criteria, user receives a 404 error when the green plus sign is clicked. Root cause: Correct path was not defined for MultiTreeviewPopUp.aspx, ListPopup.aspx and frmSimpleListPopUp.aspx. When selecting by ItemType for trade specifications, search criteria with datafiled="ItemTypeID" was used by mistake.

Correct paths for them should be: DataSourceURL:@APP_PATH@/WebCommon/ Popups/MultiTreeviewPopUp.aspx, DataSourceURL:@APP_PATH@/WebCommon/ Popups/ListPopup.aspx and DataSourceURL:@APP_PATH@/WebCommon/ Popups/frmSimpleListPopUp.aspx. When selecting by ItemType for Trade Specifications, search criteria with datafiled="ItemTypePKID" should be used. 24743054 (622-1406)

6.2.0.0.24 6.2.1.0.11

Application crashes randomly with error. Root cause: Page can record the length of scroll bar. Once the value of length is a Double type, system views this as a problem and throws an exception error.

Let system allow scroll length to be a Double type. 25031753 (622-1500)

6.2.0.0.25

When using the advanced search function in the Specification & Documents tab in Supplier Portal if a search would return results (if there are any specifications available to the user) the query times out instantly. Root cause: One SQL couldn’t run successfully in Oracle 11g.

The SQL needs to be modified in file SupplierActionsDataColumnTransformer. 25189896 (622-1628)

Chapter 4 Hot Fixes



6.2.0.0.26

Formatting is removed when printing the out of the box print templates on specifications including formulation, material, ingredient statements and nutrient profiles. Root cause: Text was encoded.

By not printed as encoded string, formatting remains during print. 24927633 (622-1444)

6.2.0.0.27

The issue is that for deactivated nutrients, their PKIDS are showing instead of their name when modifying a material output’s nutrients from a formulation specification in “Designable” status. Root cause: When a certain nutrient isn’t active, it will display as PKID in popup selected list of formulation output.

Modify caption templates to record the entire nutrient name. So that the true name of a nutrient will be displayed even when it isn’t active. 25218652 (622-1686)

6.2.0.0.28

When attempting to log on in other languages such as Chinese Traditional, French, German, and Spanish, other than English and utilizing the advanced search functionality in the Specification & Documents section of Supplier Portal (SP), search returns a generated SQL error where there are results returning from the search. If there are no matching results, user just receives a message that there is no record. Running the generated SQL in SQL developer returns the expected results in a few seconds. Root cause: If one specification name is defined in multi-language, doing advance search on it via non-English language will generate duplicated SQL.

Resolution: When generating SQL in advance search, make extra judgment to avoid from duplicated query on one specification. 25302115 (622-1687)

6.2.0.0.31

See bug 25484486 in Supply Chain Relationship Management (SCRM) Resolved Issues. (622-1808)

6.2.0.0.32 See hot fix 6.2.1.0.13 listed below. (622-9)

6.2.1.0.1

Single Sign On using in house solution SAML 2.0 with Oracle PLM for Process after upgrade is not working. Root cause: The raw authentication configuration didn’t take effect when using SSO authentication.

Make the raw authentication configuration take effect when using SSO authentication. 24498657 (622-1404)

Chapter 4 Hot Fixes



6.2.1.0.2


6.2.1.0.3 See bug 24610031 in Reporting Resolved Issues. 24610031 (622-1333)

6.2.1.0.5


6.2.1.0.6


23506035 (622-885)


6.2.1.0.8

When attempting to access PQS > Sessions, user receives an error message about half of the time. Root cause: Redirect failed when navigating to PQS Session page.

Modify redirect logic used when navigating to PQS session. 25170569 (622-1629)

6.2.1.0.9

Formulation step consumed warning. Root cause: We have a method named “IsOutputNotConsumedAt100Percent” to check the output, but it return the opposite result.

The correct data is returned. 24300166 (622-1430)

6.2.1.0.12

In GSM, the shelf life value is disappearing. Root cause: When switching tabs, ShelfLife is reset to be null value.

ShelfLife should not be reset to a null value, but instead keeps a value consistently. 24571016 (622-1348)

6.2.1.0.13

Comments are not saved on NPD activity steps unless associated documents are attached. Root cause: Comments will not be saved on the NPD activity if no document was uploaded in Document Collaboration type.

Comments should be saved even if no document is uploaded. 25570075 (622-9)

6.2.1.0.15 See bug 25525916 in General Resolved Issues. (622-1842)

Chapter 4 Hot Fixes


Oracle Agile Product Lifecycle Management for Process 6.2 ...This software and related documentation...

Documents

Transcript of Oracle Agile Product Lifecycle Management for Process 6.2 ...This software and related documentation...