Adobe Captivate



Slide 3 - Oracle Product Lifecycle Management Cloud

[pic]

Slide notes

Hello, my name is Kyle. Welcome to training for Innovation Management in Oracle Product Lifecycle Management Cloud.

In this session we talk about improved features and extended REST APIs in Innovation Management.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 4 - Agenda

[pic]

Slide notes

For the enhancements covered in this training, we’ll give an overview, followed by more detail to explain how you can use them, and what business value they bring.

Then we’ll walk you through a demonstration.

Next we’ll explain what you need to consider before enabling these features in your business, and what you need to know to set them up.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 5 - Enhancements Overview

[pic]

Slide notes

The enhancements that we’ll cover today include: improved audit trail in Requirements and improved user experience making edits to name and description in Proposals. Furthermore, all Innovation Management objects now have a “Send” feature that sends a notification about the object to other users. Also, you can now hide and re-order elements in the Actions menu of Requirement Specifications, and the add relationship dialog for displays only those objects for which you have privileges to use. In addition, you can now use Groovy script to create Requirements Specifications and Ideas. And finally, the REST APIs now enable you to manage an Idea team.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 6 - Record Export of Requirements PDF or Trace Report in History Table

[pic]

Slide notes

Audit Trail functionality has been enhanced in Requirements Specifications to include Export and Traceability Report.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 7 - Record Export of Requirements PDF or Trace Report in History Table

[pic]

Slide notes

With the ability to see who ran the Export and Traceability Reports and when, the Audit Trail is now more comprehensive, leading to better compliance with regulatory requirements and enhancing your ability to review your own work. For example, if a partner company states that they have not seen a current Requirements PDF in a few months, you can use Audit Trail to find the last time you exported that pdf from the system.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 8 - Update Name and Description within Proposal View

[pic]

Slide notes

This change allow you to update the Proposal name and description from within the Proposal instead of having to navigate to the related Concept in order to do so.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 9 - Update Name and Description within Proposal View

[pic]

Slide notes

The user experience has been improved since this used to require the user to go into concepts to make updates to these attributes. This was a training challenge for many customers. It’s far more intuitive to make these changes from within the Proposal view. For example, prior to this change, if you created a Proposal and later wanted to update the description, you would have to open the matching Concept and make the change there. Now, you can make that change in the Proposal itself.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 10 - Send Notification for Ideas, Requirements, Concepts, Proposals, and Portfolios

[pic]

Slide notes

Innovation Management objects can now be easily shared with other users using the ‘Send’ action. If you want to share your new object with other users, just select Actions > Send to send them a notification about it.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 11 - Send Notification for Ideas, Requirements, Concepts, Proposals, and Portfolios

[pic]

Slide notes

This leads to improved collaboration among users within Innovation Management because the method for notifying other users about and directed them to your object is greatly simplified. For example, you have just created a new Requirements Specification and you want to inform a manager in the procurement department about it so that she can begin matching parts with the specifications, you can easily do so with this Send feature.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 12 - Hide or Reorder Standard Actions in Requirements Specifications

[pic]

Slide notes

Using Application Composer, an implementer or administrator can configure the Actions menu to hide or reorder standard and admin-created actions. And since this functionality is performed through page layouts, you can set conditions on those layouts so that only specific users will have access to certain actions.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 13 - Hide or Reorder Standard Actions in Requirements Specifications

[pic]

Slide notes

This new ability improves user experience since only relevant actions can be enabled and shown in order of usage. Furthermore, it provides control over who can perform what actions. For example, if you want only product managers to be able to submit Requirements Specifications for approval, you can remove Submit for Approval from the default layout and create a layout for product managers that still displays Submit for Approval. Then, you can create a condition for the new layout using Groovy scripting that allows only product managers to view that layout and thus have access to the Submit for Approval action.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 14 - Add Relationships to Requirements Specifications/Requirements

[pic]

Slide notes

With this feature, users need to have the Review or Manage privilege on the object to be able to add that object as a Relationship to a Requirements Specification.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 15 - Add Relationships to Requirements Specifications/Requirements

[pic]

Slide notes

Now, the system no longer requires a special privilege to add relationships to Requirements Specifications. Since Review or Manage is required on the object to be added to the Relationship, the Administrator can control this in a granular manner. For example, if a new employee needs a user account, the administrator now only needs to make sure that user can access the objects that are part of their job description and no longer have to additionally worry about making sure they can also relate those objects to Requirements.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 16 - Create Requirements Specifications and Ideas using Groovy Scripts

[pic]

Slide notes

Groovy script can now create new Requirements Specifications and Ideas. Therefore, implementers and administrators can create actions invoked from either a button or the Actions menu that create a Requirements Specification or an Idea.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 17 - Create Requirements Specifications and Ideas using Groovy Scripts

[pic]

Slide notes

Adding the ability to create of Ideas and Requirements Specifications from other objects wherever appropriate promotes the use of these objects. And furthermore, implementers and administrators can write Groovy scripts for this purpose without resorting to web services. For example, if your quality process involves using Oracle Quality Management Cloud, you can now add a button to Quality Actions that creates a Requirements Specification with the name and description derived from the Quality Action. This Requirements Specification can then be used to define the requirements for resolving the Quality Action.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 18 - Manage Team on Ideas using REST APIs

[pic]

Slide notes

This new API feature provides the ability to manage Ideas Team using REST web services.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 19 - Manage Team on Ideas using REST APIs

[pic]

Slide notes

Using the REST APIs improves integrations that control access to Ideas by being able to manage the team programmatically. For example, if you have a customer relationship application that gathers product feedback, you can use REST APIs to migrate the product feedback from the CRM application into Idea Management and now you can also define who is on the team of each item based on criteria in the CRM system.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 64 - Summary of Enhancement Capabilities

[pic]

Slide notes

Here is the summary of the features I have talked about today. The improved audit trail in Requirements now displays exports and traceability reports. Also, you can now edit the name and description fields directly within Proposals, and you can notify other users about your Innovation Management objects through the new Send feature. Furthermore, you can reorder and hide actions within Requirements Specifications.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 65 - Summary of Enhancement Capabilities

[pic]

Slide notes

In addition, here is a summary of the remaining features I have talked about today. Improvements in the add relationship dialog for Requirements Specifications ensures that you will only see the objects for which you have the privilege to use in a relationship. Also, you can now create Requirements Specifications and Ideas using Groovy script, which enables users to create such objects while viewing other objects. And finally, REST APIs now allow you to automate the management of teams in Ideas.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 66 - Implementation Advice

[pic]

Slide notes

In this implementation advice section we will go through what you need to consider before enabling these features in your business, and what you need to know to set them up.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 67 - Feature Impact Guidelines

[pic]

Slide notes

This table depicts key update information for the features covered in this training. Note that all of the features are delivered ready to use and are included with the shipped job roles.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 68 - Feature Impact Guidelines

[pic]

Slide notes

This table depicts key update information for the remaining features covered in this training. Notice that all of these features are delivered ready to use and are included with the shipped job roles.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 69 - Features Delivered Ready to Use Impact Analysis

[pic]

Slide notes

This table details the impact to your current business flows of features in this training that are delivered ready to use by your end-users. The Requirements Audit Trail improvements has a minimal impact as it only logs additional actions. Also, the ability to edit proposal name and description is a small scale change that actually simplifies and improves the user experience. In addition, the Send object feature is a small scale enhancement because it provides a new action that users can execute from the Actions menu.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 70 - Features Delivered Ready to Use Impact Analysis

[pic]

Slide notes

Furthermore, this table details the impact to your current business flows of additional features in this training that are delivered ready to use by your end-users. The ability to reorder or hide actions is a small scale change that only impacts administrators. Improvements in the Add Relationship dialog in Requirements Specifications is a small scale change that simplifies the way administrators have to organize privileges for relationships. Also, the ability to create new objects through Groovy scripting is a minimal impact feature that will only be used by administrators to enable better ways to involve other objects in business processes.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 71 - Features Delivered Ready to Use Impact Analysis

[pic]

Slide notes

And finally, this table details the impact to your current business flows of the last feature in this training that is delivered ready to use by your end-users. The new capability of the REST APIs to manage teams on Ideas is a small scale change that will only enhance the administrator’s capacity to automate an important security feature in Idea Management.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 72 - Job Roles

[pic]

Slide notes

This table details the shipped job roles that will access the new capabilities covered in this training. The job roles are Product Manager and Design Manager.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 73 - Business Process Information

[pic]

Slide notes

The business processes associated with the new capabilities covered in this training are detailed here.

The high-level business process is Manage Innovation Management with activities Manage Product Requirements, Manage Product Concepts, and Manage Idea Management.

This concludes the presentation. Thank you for listening. You can easily pause and rewind if you require additional time to take in the details.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download