Oracle Agile Product Lifecycle Management forProcessWorkflow Administration User GuideRelease 6.2E48719-01April 2015
Agile Product Lifecycle Management for Process Workflow Administration User Guide, Release 6.2E48719-01Copyright 2015, Oracle and/or its affiliates. All rights reserved.This software and related documentation are provided under a license agreement containing restrictions onuse and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense 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. Reverseengineering, disassembly, or decompilation of this software, unless required by law for interoperability, isprohibited.The information contained herein is subject to change without notice and is not warranted to be error-free. Ifyou 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 iton 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 usersare "commercial computer software" pursuant to the applicable Federal Acquisition Regulation andagency-specific supplemental regulations. As such, use, duplication, disclosure, modification, andadaptation of the programs, including any operating system, integrated software, any programs installed onthe hardware, and/or documentation, shall be subject to license terms and license restrictions applicable tothe 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 managementapplications. It is not developed or intended for use in any inherently dangerous applications, includingapplications that may create a risk of personal injury. If you use this software or hardware in dangerousapplications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and othermeasures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damagescaused 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 oftheir respective owners.Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarksare 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 AdvancedMicro 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 expresslydisclaim all warranties of any kind with respect to third-party content, products, and services. OracleCorporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to youraccess to or use of third-party content, products, or services.
ContentsPreface . ixAudience.Variability of Installations.Documentation Accessibility .Software Availability .Related Documents .Conventions .ixixixxxxi1 Introducing Workflow AdministrationIntroducing Workflows.Workflow Administration Overview .Associated Roles.Workflow Terms and Definitions .Recommendations for Creating Workflows.Searching for Workflows.Editing Workflow Process Templates .Using the Make Inactive Option .Copying Workflow Process Templates.Exporting and Importing Workflows.Exporting Workflows from Your Staging Environment .Importing Workflows into Your Production Environment .1-11-11-21-21-31-31-41-41-51-51-51-62 Using WFA to Create GSM WorkflowsCreating New GSM Workflow Templates.Summary Information Section .Name .Description.Template Type.Active.Resolution Criteria Section .Workflow Object Type .Attribute .Value.Match .Step Sections .2-12-22-22-32-32-32-32-32-32-42-42-5iii
Owners Table. 2-7Functional Areas . 2-7Conditions. 2-7Members. 2-8Roles. 2-9Selection Modes . 2-9Optional. 2-10Evaluation Methods . 2-10Signature Requests Table. 2-10Functional Areas . 2-11Conditions. 2-11Members. 2-12Selection Modes . 2-12Req # . 2-12Amber In and Red In Options. 2-13Optional. 2-13eSignature . 2-13Comments . 2-13Evaluation Methods . 2-13Notifications Table. 2-13Functional Areas . 2-14Conditions. 2-14Members. 2-15Selection Modes. 2-15Optional. 2-15Evaluation Methods . 2-15Transitions Table. 2-16Conditions. 2-17Transitions . 2-18eSignatures. 2-19Guard Conditions . 2-19Workflow Actions. 2-19Sig Doc Override. 2-20Comments . 2-20Adding Steps . 2-20Reordering and Removing Steps . 2-20Permissions Section. 2-21Actions. 2-22Principals. 2-22Tokens . 2-22Criteria. 2-23Workflow Permissions Section. 2-23Principal . 2-24Tokens . 2-24Conditions. 2-24Criteria. 2-26iv
3 Using WFA to Create SCRM WorkflowsIntroducing SCRM Workflow Templates . 3-1Creating SCRM Workflow Templates . 3-2Summary Information Section . 3-3Name . 3-3Description. 3-3Template Type. 3-3Active. 3-3Resolution Criteria Section . 3-3Workflow Object Type . 3-4Attributes . 3-4Value. 3-4Match . 3-4Steps Section . 3-5Owners Table. 3-7Functional Areas . 3-7Members. 3-7Roles. 3-8Selection Modes . 3-8Optional. 3-9Signature Requests Table. 3-9Functional Areas . 3-10Members. 3-10Selection Modes . 3-10Req # . 3-10Amber In and Red In Options. 3-10Optional. 3-11eSignature . 3-11Comments . 3-11Notifications Table. 3-11Functional Areas . 3-11Members. 3-11Selection Modes . 3-12Optional. 3-12Transitions Table. 3-12eSignatures. 3-13Guard Conditions . 3-13Workflow Actions. 3-13Sig Doc Override. 3-14Comments . 3-14Adding Steps . 3-14Reordering and Removing Steps . 3-15Permissions Section. 3-16Actions. 3-16Principals. 3-16Tokens . 3-16Criteria. 3-17v
Workflow Permissions Section.Principals.Tokens .Criteria.3-183-183-183-194 Using WFA to Create PQM WorkflowsCreating New PQM Workflow Templates. 4-1Summary Information Section . 4-2Name . 4-2Description. 4-3Template Type. 4-3Active. 4-3Resolution Criteria Section . 4-3Workflow Object Type . 4-3Attribute . 4-3Value. 4-3Match . 4-3Step Sections . 4-4Owners Table. 4-6Functional Areas . 4-6Members. 4-7Roles. 4-8Selection Modes . 4-8Optional. 4-9Evaluation Methods . 4-9Signature Requests Table. 4-9Functional Areas . 4-10Conditions. 4-10Members. 4-11Selection Modes . 4-11Req # . 4-11Amber In and Red In Options. 4-12Optional. 4-12eSignature . 4-12Evaluation Methods . 4-12Notifications Table. 4-12Functional Areas . 4-13Conditions. 4-13Members. 4-14Selection Modes. 4-14Optional. 4-14Evaluation Methods . 4-14Transitions Table. 4-15Conditions. 4-16Transitions . 4-17eSignatures. 4-18Guard Conditions . 4-18vi
Workflow Actions.Adding Steps .Reordering and Removing Steps .Permissions Section.Actions.Principals.Tokens .Criteria.Workflow Permissions Section.Principal .Tokens -234-234-244-244-254-265 Using WFA to Manage CSS WorkflowsIntroducing CSS Workflows.Predefined Workflows.Creating New CSS Workflow Templates .Summary Information Section .Name .Description.Template Type.Active.Step Sections .Transitions Table.Transitions .
Agile Product Lifecycle Management for Process Content Synchronization and Syndication User Guide Agile Product Lifecycle Management for Process Supplier Portal User Guide Agile Product Lifecycle Management for Process New Product Development User Guide Agile Product Lifecycle Management for Process Product Quality Management User Guide Agile .
1. The need for an agile way of working 6 2. The need for an agile way of working 9 3. Agile Core Values - Agile Project Management Vs. 10 Agile Event Management 4. Agile principles 12 _Agile Principles of Agile Project Management 13 _Agile Principles of VOK DAMS Agile Event Management 14 5. Agile Methods 16 _Scrum in Short 16 _Kanban in Short 18
Agile Estimating and Planning by Mike Cohn Agile Game Development with Scrum by Clinton Keith Agile Product Ownership by Roman Pichler Agile Project Management with Scrum by Ken Schwaber Agile Retrospectives by Esther Derby and Diana Larsen Agile Testing: A Practical Guide for Testers and Agile Teams by Lisa Crispin and .
Bruksanvisning för bilstereo . Bruksanvisning for bilstereo . Instrukcja obsługi samochodowego odtwarzacza stereo . Operating Instructions for Car Stereo . 610-104 . SV . Bruksanvisning i original
Agile Mindset and Vocabulary 11 Acceptance Testing Actual Time Estimation Agile Development Practices Agile Manifesto Agile Project Management Agile Release Train Agile Software Development Alignment Application Lifecycle Management (ALM) Architectural Epic Kanban Architectural Epics Architectural Feature Architectural Runway ART Metrics .
1.1 Purpose of the Agile Extension to the BABOK Guide1 1.2 What is Agile Business Analysis?2 1.3 Structure6 Chapter 2:The Agile Mindset 2.1 What is an Agile Mindset?7 2.2 The Agile Mindset, Methodologies, and Frameworks8 2.3 Applying the Agile Mindset9 2.4 Agile Extension and the Agile Ma
The Agile PLM suite of solutions covers five primary areas of product lifecycle management: Agile Product Collaboration (PC) - Management and collaboration of product record information throughout the product lifecycle, across internal organizations and the extended supply chain. Accessed through Web Client and Java Client.
1. Agile methods are undisciplined and not measurable. 2. Agile methods have no project management. 3. Agile methods apply only to software development. 4. Agile methods have no documentation. 5. Agile methods have no requirements. 6. Agile methods only work with small colocated teams.-7. Agile methods do not include planning. 8.
Artiﬁcial intelligence is an artefact, built intentionally. Deﬁnitions for communicating right now. Romanes, 1883 – Animal Intelligence, a seminal monograph in comparative psychology. Intelligence is doing the right thing at the right time. A form of computation (not math)–transforms sensing into action. Requires time, space, and energy. Agents are any vector of change, e.g .