Skip Headers

Agile Product Lifecycle Management What's New in Agile PLM White Paper Release 9.3.3 E39276-01 |
| Contents

Previous |

# Agile Product Lifecycle Management

What's New in Agile PLM White Paper

Release 9.3.3

E39276-01

October 2013

Note: This document is a supplement to the release Readme and all other manuals, like the Capacity Planning Guide. It is intended to be an overview of the other documentation and does not replace the need to read and understand those documents. Errors contained in this document are not commitments to provide features.

## 1 New Features in Agile PLM 9.3.3

New features in Agile PLM 9.3.3 can be summarized into three key themes (see Figure 1 below).

Figure 1 Key Agile PLM 9.3.3 Themes

This document addresses new capabilities added in Agile PLM 9.3.3 as compared to prior Agile PLM releases. As with the last releases, there are detailed Transfer of Information (TOI) recordings accessed through My Oracle Support that cover all of these features.

## 2 Agile PLM Resources provided by Oracle

Oracle offers extensive training and documentation for customers to learn about Agile PLM 9.3.3. Below is a list of informative resources:

- Installation software is available as a download from Oracle Software Delivery Cloud: `````http://edelivery.oracle.com/`

  - New versions of Automated Upgrade Tool (AUT) and Averify are published to My Oracle Support

- Agile PLM Documentation Page at Oracle Technology Network (OTN): ```````http://www.oracle.com/technetwork/documentation/agile-085940.html`

- Samples for Agile PLM 9.3.3 are added to the new Sample Code website```` - `http://www.oracle.com/technetwork/indexes/samplecode/agileplm-sample-520945.html`

- Transfer of Information Recordings available through My Oracle Support: `````https://support.oracle.com/`

Note: Note: These are recording of Agile PLM Product Managers discussing the major new features of Agile PLM 9.3.1. They are available to any customer with licenses and support for Agile PLM.

- - 9.3.3 recordings are available through Support Note 1589164.1

  - 9.3.2 recordings are available through Support Note 1512952.1

  - 9.3.1 recordings are available through Support Note 1220374.1

  - 9.3.0 recordings are available through Support Note 854537.1

- Agile PLM official website: `www.oracle.com/plm`

- Agile PLM blog: `````http://blogs.oracle.com/PLM`

- Agile PLM Solution Space: `````http://www.oracle.com/goto/plmsolutionspace`

  - Go here for replays of recorded webinars.

- Twitter: `````http://twitter.com/agileplm`

- Agile PLM Community Page available through Support or at `````https://communities.oracle.com/`

  - In Support, select Community link in the top tab bar

  - On the top left side of the page, find or select "Agile PLM Product Lifecycle Management"

- External Yahoo! User Groups (note: content is not managed or controlled by Oracle)

  - `````http://tech.groups.yahoo.com/group/WRAU/`

  - `````http://tech.groups.yahoo.com/group/IAUG/`

  - `````http://tech.groups.yahoo.com/group/AgileAPI/`

## 3 Enterprise Process Management

Agile PLM 9.3.3 improves the ability of users to complete key businesses processes management in several ways. This section reviews the features impacting Enterprise Process Management.

### 3.1 PPM and Microsoft Project Co-Existence

The ability for Agile Product Portfolio Management (PPM) to interact with Microsoft Project remains very important to our customers. In 9.3.3, we have enabled PPM to import and export Microsoft Project 2010 and 2013 XML files. The menu options for Import are called "Load Microsoft Project XML" or "Create Project from XML File". The menu options for Export are called "Save As XML - Read Only" or "Save As XML - Edit". This capability to import and export XML opens up many use cases for customers to leverage PPM.

#### 3.1.1 PPM Feature Changes When Interacting with Microsoft Project

- The direct Microsoft Project plug-in has been eliminated. The server in 9.3.3 will block communications from old plugins.

- Tools and Settings Menu option has been renamed "Create Project from XML File". Using this method to import a MSP XML file will only allow creating a new project in PPM, even if Text 29 and 30 fields contain references to another PPM project. The user will be notified that this information is ignored.

- Within a project, the Action menu has been changed to "Load Microsoft Project XML", "Save As XML - Read Only", and "Save As XML - Edit". Using Load will only update the current project from an XML file using Text 29 and Text 30 references. Either Save As option can be used depending on the intent of saving the XML.

- Microsoft Project constraints will be retained until the schedule is altered in PPM. Users can update task descriptions and other information that does not affect the schedule without affecting a constraint. When the user performs Save As XML, the constraints will be part of the XML file.

- MSP XML can be loaded in a PPM system without being opened in Microsoft Project

- In the Create Project wizard, users can now choose to set the Schedule Editor to PPM immediately. As in earlier PPM releases, this wizard also assists with mapping Resources.

- Added a new Import Date Cover Page attribute. This indicates the date and time the XML was imported.

- Web Service and SDK APIs are added to import and export MSP XML.

- Additional validations are performed when importing MSP XML. PPM will check for duplicate tasks in Text30, for invalid dependencies, inactive users or user groups, inactive roles, and text field character sets.

#### 3.1.2 PPM and Microsoft Project Use Cases

1. Synchronize Microsoft Projects with PPM

   Figure 2 Synchronize Microsoft Projects with PPM

   Users can create a new project using Microsoft Project (MSP). Using Tools > Create, they can initiate a new project within PPM. If further editing is required within MSP, the user can use Actions > Save As to export the PPM project back into a MSP XML file, make changes in MSP, then use PPM Actions > Load to re-import the changes into PPM.

   This use case enables project managers who need MSP features to continue to edit projects with MSP, while overall project execution is tracked in PPM.

2. Import new Microsoft Project with Schedule Editor set to PPM

   Figure 3 Import new Microsoft Project with Schedule Editor set to PPM

   Similar to the first case, users can create a new project in MSP and then initiate a new project in PPM, but set the schedule editor to PPM.

   This case highlights the ability to use MSP as an authoring tool for projects, while then performing ongoing project changes and execution using PPM.

3. Create new PPM project from Template, save to Microsoft Project for editing, then reimport changes

   Figure 4 Create new PPM project from Template, save to Microsoft Project for editing, then reimport changes

   The PPM Template feature is a very powerful method to ensure projects are consistently created across the enterprise. This case shows how a template can be used for initial project creation, then saved out to MSP for editing. Once the editing is completed, import the modifications back into PPM. This case can help build user acceptance if project managers require MSP features to edit projects while ensuring corporate project templates are leveraged.

4. Cross PPM server import, using Microsoft Project to clean up file before editing

   Figure 5 Cross PPM server import, using Microsoft Project to clean up file before editing

   Customers often need to copy PPM projects from Development or QA systems to the Production system. This case shows how to accomplish this use case when needing to make some changes to the project before importing into production. MSP can be used to clean up descriptions and other project information that may not be correct from the first PPM system. Once imported, only Content information should need to be manually linked to the new project.

5. Cross PPM server import, without using Microsoft Project

   Figure 6 PPM server import, without using Microsoft Project

   This case is very similar to case 4. The major difference is whether a user needs to modify the MSP XML. If no changes are required, the MSP XML can be directly loaded into the second PPM system.

6. Sharing project information to enterprise

   Figure 7 Sharing project information to enterprise

   The new capability to save and load MSP XML is also available through the SDK and as Web Services. This enables automated sharing of PPM projects to other systems that can consume or produce MSP XML.

### 3.2 Managing Activity and Gate Owners

- When using the Owner Delegation process, only the Modify privilege on Delegated Owner attribute is required. Prior to 9.3.3, Web Client also required Grant privilege.

- The Owner attribute can be modified directly with Modify privilege. When the formal delegation process is not required, this allows privileged users to change Activity or Gate Ownership.

### 3.3 Time Sheet SDK

Time sheet information can now be set and retrieved using SDK. This provides significant potential to integrate PPM with other time reporting systems or with project financial systems.

### 3.4 Augmented Business Visualization

A new sample is being provided that allows AutoVue Augmented Business Visualization to work with Agile PLM 9.3.3. This new capability allows users to right click on parts in AutoVue and initiate business processes in Agile PLM. The sample works with ECR and ECO processes, but this can be customized as needed. Note that the sample relies on Agile Engineering Collaboration (EC) MCAD integration to name the CAD files consistently. The correct identification of Items can be customized as needed. The next 2 figures show a user right clicking on a part in AutoVue to Create ECR and the results on the new ECR Affected Items table.

Figure 8 A user in AutoVue can right click to create an ECR or ECO

Figure 9 After creation from AutoVue, both the selected Part and Assembly Part are added to Affected Items

### 3.5 ECR Redlining

Redlining is now enabled on ECR Attachments tab. This is similar to Ad-Hoc redlines that have previously been available on File Folders. A new option to select files from Affected Items is available when adding attachments. This new capability allows users to specify potential changes to documentation as part of the standard ECR process.

### 3.6 Item Revision Specific Relationships

A new optional feature in Agile PLM 9.3.3 allows Item Relationships to be specific to revisions. This allows more detailed traceability between Item Revisions and related objects. Once enabled, Item Relationships can be specific to a specific revision, All revisions, or Latest revision. Selecting All revisions makes the relationship act similarly to previous releases. This feature also includes the ability to track impact, based on user selection. If a relationship is set to track impact, when an Item Revision is incremented a flag will appear on the Relationship to potentially uptake the new revision. This feature is well documented in the Agile PLM user manuals and with a dedicated Transfer of Information (TOI) recording. Administrators should carefully consider rollout of this feature to ensure users are well trained and that maintenance requirements are understood.

### 3.7 Split Add, Delete, and Update Privileges for Relationships Table

Use of Relationships table continues to be critical to enterprise process management and requirements traceability. Two new privilege types are introduced with 9.3.3, Add to Table and Delete from Table. When a user has Modify Privileges for Relationships.Name, they can Add or Delete rows. Otherwise the user needs Add to Table with Relationships in Applied to field to add rows. They need Delete from Table with Relationships in Applied to field to remove rows. Administrators now have additional methods to control when users can add or remove from Relationships tables.

### 3.8 Innovation Management Concept Design Attributes

Innovation Management Concept Design will read data from Parts in Agile PLM. New attributes are added to Item Page 2 in order to formalize the location of the attributes presented in Concepts. These new attributes can be enabled and used without using Innovation Management, but the attribute usage should not be changed to ensure consistency. Samples are provided for some of these attributes to count related objects.

- Material Cost - Item.P2.IMMoney11

- Non-Material Cost - Item.P2.IMMoney12

- Non-Recurring Cost - Item.P2.IMMoney13

- Last Cost Update - Item.P2.IMDate16

- Country of Origin (list = Country) - Item.P2.IMMultiList26

- Lead Time (days) - Item.P2.IMNumeric11

- Number of Where Used - Item.P2.IMNumeric12

- Number of Incidents - Item.P2.IMNumeric13

- Number of Manufacturer Parts- Item.P2.IMNumeric14

- Power Consumption - Item.P2.IMNumeric15

- Item Score - Item.P2.IMNumeric16

## 4 Intellectual Property Management

Managing and reporting on access to Intellectual Property, especially Attachments, is critical to our customers. With Agile PLM 9.3.3 we have dramatically improved the ability to add and protect attachments. This section reviews the features impacting Intellectual Property Management.

### 4.1 Improved File Transfers

First, Agile 9.3.3 improves control of Intellectual Property by better enabling file transfers into and out of Agile PLM. In addition to supporting up to 16GB file sizes, the following sections detail features specific to Upload and Download. Users can now complete uploads in the background while continuing their work in Agile PLM.

#### 4.1.1 File Uploads

Uploads in Agile PLM will leverage new HTML5 based Web Client components. The previous Advanced Transfer and Basic Upload windows have been eliminated. The new Upload components will open immediately without having to invoke Java.

When a user selects to Add files, the new File Upload Selector will open instantly. Users can use Browse for files to find and select multiple files from their drives. In addition, users can drag and drop multiple files directly from the operating system file browsers. If the user does not want to select Upload after choosing files, they can select the checkbox for Start Upload Immediately. The next figure shows the new File Upload Selector screen.

Internet Explorer (IE) cannot support selecting multiple files or drag and drop because it operates in compatibility mode. Users running IE will need to select one file at a time to add to the File Upload Selector screen.

Figure 10 File Upload Selector

The File Upload Manager screen appears once users select Upload. This screen shows file transfer progress and allows users to Pause, Resume, and Cancel transfers. Multiple parallel uploads are now supported. Users can choose to Auto Hide this window if they do not want to close this window. An upload progress indicator will still appear on the main toolbar with % progress until transfers complete. Users can navigate to other objects in Agile PLM while uploads are continuing and can also close the File Upload Manager window to complete uploads in the background. The File Upload Manager can be re-opened by selecting the button on the toolbar. When uploads complete, a green up arrow will be shown on the main toolbar.

Internet Explorer (IE) is running in compatibility mode, so incremental progress reporting is not supported, only complete file transfers. The next figure shows the new File Upload Manager screen.

Several new Admin settings related to Upload have been added and can be reviewed in the Administrator manual.

Figure 11 File Upload Manager

#### 4.1.2 File Downloads

Getting a file from Agile PLM will be transferred by Web Browser download capabilities. Agile PLM now supports pause and resume of downloads, with control over number of restarts. Several new Admin settings relating to Download have been added and can be reviewed in the Administrator manual.

Use of the open action has also been slightly changed. If the Admin setting for Productivity Components is enabled, a streamlined Productivity component will be used to open the file on the user client. If the Admin setting has been disabled, then the open action will act just like the get file action. In this case, no Java component will run on the user client.

### 4.2 Split Add, Delete, and UpdateModify Privileges for Attachments Table

For similar reasons to the Relationships table, many customers want to limit which users can add versus delete files from Attachment Tables. Two new privilege types are introduced with 9.3.3, Add to Table and Delete from Table. When a user has Modify Privileges for Relationships.Name, they can Add or Delete rows. Otherwise the user needs Add to Table with Attachments in Applied to field to add rows. They need Delete from Table with Attachments in Applied to field to remove rows. Administrators now have additional methods to control when users can add or remove from Attachments tables.

### 4.3 Protecting Thumbnail Access

Prior to Agile PLM 9.3.3, users had to be provided access to all or zero thumbnails. With this release, a user must have Get File or View File on the attachment related to a thumbnail in order to view the thumbnail. This ensures better control over protected information on the attachments table.

### 4.4 Protecting Attachments Through Additional File Attributes

Agile PLM offers significant ability to limit user access to information. One area customers have wanted more control is on the Attachments tab. With this release, 22 new attributes from File Folders Files tab can be read through to Attachments tab. Criteria to limit access can be written against these new attributes to better protect file access.

### 4.5 New User History Actions Reports

Three new Administrator reports are provided to help information managers better understand user actions in the system. All of these reports leverage information captured on Object History tables and return report results in Comma Separated Value (csv) format to be able to open in a spreadsheet.

- The Attachments Accessed by User Report shows all attachment history actions performed by a user within a time period. The user running the report selects a Date Range and one or more User Names, or All Users. Attachment actions include Get File, View File, Add File, Remove File, Checkout, and Checkin.

- The Attachment History Report shows all attachment history actions from a set of objects, either individually selected or based on a search. The user running the report selects a set of objects or a search.

- The User History Report shows all history actions performed by a user. The user running the report selects user names. Any rows from History tables by the users will appear in this report.

### 4.6 New Database Tables to Log Quick Searches and Object Read

In addition to being able to report on user actions already being tracked by Agile PLM, information managers may also want to understand what users are reading or searching for in the system. Agile PLM can now be configured to track object read access and quick search terms.

- Setting the Preference Record Recently Visited History to Yes will begin storing read access to the VISIT_HISTORY table

- Setting the Preference Record Simple Search to Enabled will begin storing search terms into the SIMPLE_QUERY_HISTORY table

Database administrators can directly read these tables to determine user actions in the system, there is no report provided. In addition, database administrators should monitor table growth over time and use database capabilities to archive information no longer needed.

## 5 Continuous Product Improvement

With every Agile PLM release, we attempt to improve the functionality of the system based on customer feedback. This section reviews these additional customer requested features added to Agile PLM 9.3.3.

### 5.1 Expanded Item Page 2 Attributes

Many customer are tracking very large numbers of Item attributes in Agile PLM to fully define the product record. While we continue to support the creation of additional attributes, Agile PLM 9.3.3 is also expanding the number of available out of the box attributes. The table below shows the old and new number of Page 2 attributes available, including the new Innovation Management attributes previously covered in this document. All these new attributes can be used for criteria, searches, reporting, exporting, required fields, notifications, and read through to other tables.

Attribute Types | 9.3.2 | 9.3.3
--- | --- | ---
Date | 15 | 16
Heading | 10 | 25
List | 26 | 51
Money | 10 | 13
MultiList | 15 | 26
Multi Text | 19 | 26
Numeric | 10 | 16
Text | 25 | 50
Grand Total | 130 | 223

Table 1: Number of available Item Page 2 attributes

### 5.2 Expanded Item BOM Attributes

In addition to adding more Item Page 2 attributes, the Item BOM table is adding 15 Multilist attributes while also expanding Multitext to 15, List to 15, Date to 15, Numeric to 15, and Text to 15 attributes. The new multilist attributes can be used for use cases like tracking alternate parts.

### 5.3 Added Change Affected Item Attributes

The final attribute expansion is to add 10 Multi-text attributes to Change Affected Items tab. This allows customers to track more information about specific change instructions for each affected item.

### 5.4 Resolved issues with Overflow for Multilist Attributes

When more than around 300 list values were added to some Item Multilist attributes, reporting and exports would not output all the values. This has been corrected in Agile PLM 9.3.3.

### 5.5 Import Improvements

Importing data into Agile PLM remains a highly critical activity. This release makes significant improvements to import features requested by many customers.

#### 5.5.1 Blank Values overwrite Agile PLM Data

Blank values in import files can overwrite Agile PLM data. A new setting in Import controls whether this occurs.

#### 5.5.2 Assign Auto-Numbers to Newly Created Items

Import files can omit the number data to force Agile PLM to assign numbers. The subclass default number screens for import have been improved to make easier the selections of one auto-number to use for subclasses. At the end of an import process, the import wizard has a new option to export newly created data. This allows the user to understand which numbers were assigned to the data. The import log file is also improved to indicate assigned numbers so that automated imports can also retrieve information about the new objects.

#### 5.5.3 Validate No Longer Uses Auto-Numbers

Prior to Agile PLM 9.3.3, the Import Validate action would use real auto-numbers to verify import data. For some customers this could lead to exhausting auto-numbers. Agile PLM now does not use auto-numbers.

### 5.6 User Experience Improvements

With every release we improve how users interact with Agile PLM. The improvements for Agile PLM 9.3.3 are documented in this section.

#### 5.6.1 Improved Missing Rows Error Messages

Figure 12 Missing Row error message example

When Agile PLM 9.3.0 was introduced, table messages about missing rows were shown using new icons at the lower right side of a table. Users would need to hover their mouse over these icons to see the messages. Many customers want these messages to be more visible to users. With this release, the messages will be directly shown in red at the bottom of tables.

#### 5.6.2 Remove Newline Characters from Headers

In Agile PLM 9.3.3 newline characters will not appear in Headers. In earlier releases these newline characters would move the tabs down on the page which limited display space for attributes and tables. Removing the newline characters ensures more vertical space is available to display object information.

Figure 13 Removal of newline characters from headers

#### 5.6.3 List Searches can return up to 2500 Rows

With Agile PLM 9.3.0 the number of rows in List Searches was limited to 250 in order to ensure web client performance. With Agile PLM 9.3.3 we have added a configuration option for the search results to contain up to 2500 rows. If users have browser performance issues with this option set to a high number, then it should be reduced. Performance issues can include poor responsiveness or excessive use of memory.

#### 5.6.4 Improved Table Header Display of Field Names

Figure 14 Table Header example

With Agile PLM 9.3.3, table headers will be shown with field names first and the page name in parentheses second. The header can also wrap text up to two rows. This new capability should ensure users can better understand search results and other table displays.

#### 5.6.5 Up to 100 Columns in Searches and Reports

Many customers send search results to excel for a variety of data analysis reasons. Some customers using many Item attributes need to run 2 or 3 searches in order to output all the information needed for data analysis. With Agile PLM 9.3.3, searches and reports can have up to 100 columns in order to improve these use cases. This setting is configurable by the administrator to ensure App Server performance issues can be mitigated.

#### 5.6.6 Improve Search Save-As Behaviors

Prior to this release, performing Save-As on saved searches could result in the original search being changed. This behavior has been corrected.

### 5.7 Improve Display of Revision Effectivity Periods

Agile PLM tracks effectivity periods of revisions when defining a Change Order. These dates appear on an Item on the Title Block and in the Changes tables. Prior to this release these dates also appeared on the BOM tab. These dates have been moved to the Item header next to the Revision field. The next figure shows the display of effectivity dates on June 24, 2013. For current or future effectivity, the dates show in normal black text. For passed effectivity, the dates show in red italics.

Figure 15 New display of effective dates in Item header, based on June 24, 2013 as the current date

### 5.8 Additional Objects Locking Behavior Options

This feature ensures that when more than one user is editing an object, the admin can control whether conflicting attribute changes can occur. A new Smart Rule "Object Edit Conflicts" has been introduced with values Allow, Disallow, and Warning. Allow is the existing system behavior. This means the second save will overwrite information automatically. Warning will tell the second user they will be overwriting changed information, but will then allow the save to complete. Disallow will prevent the second user from saving until they start the edit process again.

### 5.9 Enable Price Periods with Open Dates

In previous releases, only one type of period was allowed on a Sourcing Project - Quarterly, Monthly or Semi-Annual. PCM now supports price periods with open start/end dates. We now store the Price Period ID on the Sourcing Project. This allows us to get the correct Current Price Period in the event that there are multiple price periods with the same start date.

### 5.10 Editable Quantity per Assembly on Item table of the Sourcing Project

The Sourcing Project Item Tab now allows editing ofQuantityperAssembly (QPA)for components through Web Client and SDK.This capabilityallowsthe sourcing project owner to change this value just within the Sourcing Project. One scenario could be alternate parts listed on the BOM as zero quantity, but the sourcing project owner wants to request the alternate part in a quote rather than the primary part.

Or, if the user wants to allow for a split of both parts e.g. .25 of one and .75 of the other. The QPA can be adjusted so the supplier is aware of the need for both parts. Another scenario is if is a NPI BOM and the current revision reflects and items with a QPA = 1, but the design engineer has advised that he's in the process of modifying it to 2. The QPA can be updated so the supplier is aware of the real quantity.

### 5.11 Additional improvements to PGC Weight Rollup Performance

In Agile Product Governance & Compliance (PGC), the substance weight rollups introduced in Agile PLM 9.3.2 already performed very well for large datasets. Additional performance improvements have been made in Agile PLM 9.3.3 to rollup even faster.

### 5.12 Enable New Search and SDK Methods to Identify Parts Without Parents (Orphans)

During a product development cycle, the product team can be creating many new part numbers for their designs. At the end of the cycle analysts often want to learn which parts were never used. This feature allows analysts to perform an advanced search for Where Used Item Number, for latest or all revisions, is Null. Analysts can then obsolete or recycle the part numbers that were never used in a design.

Figure 16 Where Used search options for orphans

### 5.13 Updated Agile eXpress Installer for All Client Operating Systems

Agile eXpress is still used by many customers to give their supplier users the ability to open PDX files in a graphical user interface. The previous Agile eXpress installer only supported Microsoft Windows and had issues with Windows 7 and higher. We are re-packaging Agile eXpress with installers for all supported client operating systems to ensure non-Agile users can open PDX packages using Agile eXpress.

### 5.14 Allow Transfer Authority to Work for Inactive Users

When users leave a company and are disabled, they often remain participants of running processes. Many customers want to transfer the user's authority rather than replace the user throughout running processes. This change allows a Transfer of Authority to be created for Inactive users.

### 5.15 ACS Adds Optional Backlink from Routable Object (ECO) to ATO

Customers use Agile Content Service (ACS) to automatically create Automated Transfer Orders (ATOs) for Change processes to integrate to ERP and other enterprise systems. When reviewing an ATO, the Change is listed as included content, which make navigation from the ATO to the Change very easy. When there is an integration issue, analysts often need to navigate from the Change to the ATO. This feature adds an ACS option to include the ATO on the Change to make this navigation easy. For some use cases, like using ACS for periodic synchronization of objects, this option can remain off.

### 5.16 Limit User Access to Java Client

Many customers only want their users to operate in Web Client. With Agile PLM 9.3.3, a user must have an administrator privilege or a new Client Access privilege to login to Java Client.

### 5.17 Reports for Agile Administration Includes New 9.3, 9.3.1, and 9.3.2 Attributes

Administration reports have been improved to include all new attributes from previous releases.

### 5.18 Reset Passwords Not Allowed for LDAP users

Agile PLM has an option on the Login screen to allow users to reset passwords. Prior to this release LDAP users were able to attempt to use this option, even though their LDAP password cannot be reset by Agile PLM. With this release, LDAP users cannot use this option.

### 5.19 Drop ChangeCAST From the ProductAgile PLM

ChangeCAST is a legacy tool replaced by Agile Content Service (ACS) in Agile PLM 9.0. ChangeCAST will not ship with Agile PLM 9.3.3. There are many potential options for customers still running ChangeCAST; three of these options are shown in the next figure. Additional documentation about these options can be found in the Agile PLM documentation.

Figure 17 ChangeCAST Migration Options

## 6 Platform Certification Summary

- Application Server:

  - WebLogic 12c (12.1.1) on 64-bit JDK 7

  - Added support for WebLogic 12c (12.1.2) ONLY for HP-UX platform

- Database:

  - Continued support for 11gR1 (11.1.0.7+) and 11gR2 (11.2.0.3+) (RAC and standalone)

  - Added support for Database 12cR1 (12.1.0.1+)

- Web Browser:

  - Firefox (now 21 and 10) on Windows and Solaris

  - Safari 6 and 5 on Mac OS

  - Internet Explorer 9 and 10

    Note: The RMW modules are only supported on IE

  - Chrome 27 and 18

- Server Operating Systems:

  - Oracle Solaris 11 and 10 (SPARC64, x86-64)

  - Oracle Linux 6 and 5 (64-bit)

  - Red Hat Enterprise Linux 6 and 5 (64-bit)

  - Microsoft Windows Server 2008 R2

  - IBM AIX 7.1 and 6.1 (POWER 64-bit)

  - SUSE Linux 11 and 10 (64-bit)

  - Add HP-UX Itanium 64) (using Weblogic 12.1.2)

- AutoVue for Agile:

  - Oracle AutoVue for Agile PLM 20.2.2

- Server Virtualization:

  - Oracle VM 3 with OL, Solaris and Windows Server

  - Oracle Solaris Containers/Zones

  - IBM AIX LPARs

  - Microsoft HyperV (see Support Note 1563794.1)

Note: Review the Oracle Agile PLM 9.3.3 Capacity Planning Guide for the official, detailed platform certification matrix. Any errors in the list above do not override the official intended software support.

This document is provided for information purposes only, and the contents hereof are subjected to change without notice. This document is not warranted to be error-free, nor is it subjected to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document; and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose without prior written permission from Oracle.

I think it's important to show versioning dots (ie. 9.3.3 not 933)

## 7 Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at ```http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc`

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit ```http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info` or visit ```http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs` if you are hearing impaired.

Agile Product Lifecycle Management What’s New in Agile PLM White Paper, Release 9.3.3

E39276-01

Copyright © 2013, 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.