Windchill PDMLink Part Creation Utility

Slides:



Advertisements
Similar presentations
Creating Accessible PDF Documents Dick Hemenway CMAC Accessibility Committee.
Advertisements

SolidWorks Enterprise PDM Data Loading Strategies
SharePoint Forms All you ever wanted to know about forms but were afraid to ask.
Microsoft Excel 2003 Illustrated Complete Excel Files and Incorporating Web Information Sharing.
Chapter 12 Creating and Using Templates. If you have already created and designed a page you like, you can use the layout and design for other pages in.
MODULE 4 File and Folder Management. Creating file and folder A computer file is a resource for storing information, which is available to a computer.
Technical BI Project Lifecycle
1 Chapter Overview Understanding NTFS Permissions Assigning NTFS Permissions Assigning Special Permissions.
Creating Custom Forms. 2 Design and create a custom form You can create a custom form by modifying an existing form or creating a new form. Either way,
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment Chapter 9: Implementing and Using Group Policy.
1 Chapter 2 Reviewing Tables and Queries. 2 Chapter Objectives Identify the steps required to develop an Access application Specify the characteristics.
PLM windchill By- Bhanu Prakash Vemula Matrikel no
Tutorial 11: Connecting to External Data
1 Securing Network Resources Understanding NTFS Permissions Assigning NTFS Permissions Assigning Special Permissions Copying and Moving Files and Folders.
Microsoft Office Word 2013 Expert Microsoft Office Word 2013 Expert Courseware # 3251 Lesson 4: Working with Forms.
Working with Drivers and Printers Lesson 6. Skills Matrix Technology SkillObjective DomainObjective # Understanding Drivers and Devices Install and configure.
Microsoft Office 2007 Access 2007 Chapter 9 Administering a Database System.
Corso referenti S.I.R.A. – Modulo 2 07 – Group Policy 20/11 – 27/11 – 05/12 11/12 – 13/12 (gruppo 1) 12/12 – 15/12 (gruppo 2) Cristiano Gentili, Massimiliano.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment, Enhanced Chapter 9: Implementing and Using Group Policy.
Chapter 5 Java Script And Forms JavaScript, Third Edition.
ADM421 Scripting Group Policy Operations BJ Whalen Program Manager Windows Server Microsoft Corporation.
CHAPTER 9 Introducing Microsoft Office Learning Objectives Start Office programs and explore common elements Use the Ribbon Work with files Use.
CHAPTER 9 Introducing Microsoft Office Learning Objectives Start Office programs and explore common elements Use the Ribbon Work with files Use.
Automating Database Processing Chapter 6. Chapter Introduction Design and implement user-friendly menu – Called navigation form Macros – Automate repetitive.
Copyright © 2008 Pearson Prentice Hall. All rights reserved Copyright © 2008 Prentice-Hall. All rights reserved. Committed to Shaping the Next.
Chapter 8 iComponents and Parameters. After completing this chapter, you will be able to perform the following: –Create iMates –Change the display of.
Lesson 17 Getting Started with Access Essentials
Lesson 9-Setting and Using Permissions. Overview Describing file permissions. Using execute permissions with a file. Changing file permissions using mnemonics.
Click to edit Master subtitle style Mobile Test Suite Installation and configuration Paul Shepherd Senior Repair Technician Zebra Technologies Europe Limited.
Microsoft Office 2007 Access Chapter 3 Maintaining a Database.
1 ADVANCED MICROSOFT WORD Lesson 14 – Editing in Workgroups Microsoft Office 2003: Advanced.
Access Project 3 Notes. Introduction Maintaining the Database  Modifying the data to keep it up-to-date Restructure the Database  To change the database.
This eCPIC Quick Guide has been developed to assist System Administrators with creating Hierarchy Grids in eCPIC. The Hierarchy Grid functionality allows.
For additional assistance, please call the Help Desk Searching 1. If a Search window does not appear after logging into the system, click the Search icon.
[ Part III of The XML seminar ] Presenter: Xiaogeng Zhao A Introduction of XQL.
Linux+ Guide to Linux Certification, Third Edition
4 HTML Basics Section 4.1 Format HTML tags Identify HTML guidelines Section 4.2 Organize Web site files and folder Use a text editor Use HTML tags and.
XP New Perspectives on Microsoft Office FrontPage 2003 Tutorial 7 1 Microsoft Office FrontPage 2003 Tutorial 8 – Integrating a Database with a FrontPage.
8 Chapter Eight Server-side Scripts. 8 Chapter Objectives Create dynamic Web pages that retrieve and display database data using Active Server Pages Process.
Session 1 Module 1: Introduction to Data Integrity
1 Introduction to NTFS Permissions Assign NTFS permissions to specify Which users and groups can gain access to folders and files What they can do with.
Hyperion Artifact Life Cycle Management Agenda  Overview  Demo  Tips & Tricks  Takeaways  Queries.
Chapter 1 Introduction to Database. Database Concept Field: a basic data element or attribute of an object Record: a set of fields Table: a set of records.
Subscribers – DatA Extensions
Subscribers – List Model
© 2010 Delmar, Cengage Learning Chapter 11 Creating and Using Templates.
XP New Perspectives on Microsoft Office Access 2003, Second Edition- Tutorial 6 1 Microsoft Office Access 2003 Tutorial 6 – Creating Custom Forms.
1 PDMLink Application - User Features & Functions Module 6: Search Capabilities.
XP New Perspectives on Macromedia Dreamweaver MX 2004 Tutorial 5 1 Adding Shared Site Elements.
Today’s Agenda Object Management Library List PDM (Programming Development Manager) SEU (Source Entry Utility)
Access Test Questions Test Date: 05/05/16. Chapter 1 (Lynda.com) Question 1 An access database uses five main components (database objects). Which is.
Acess Test Questions. Chapter 1 (Lynda.com) Question 1 An access database uses five main components (database objects). Which is not one of them? Tables.
C Copyright © 2009, Oracle. All rights reserved. Using SQL Developer.
Making the Most of Search in SharePoint 2013 Christina Wheeler.
Data Integrity & Indexes / Session 1/ 1 of 37 Session 1 Module 1: Introduction to Data Integrity Module 2: Introduction to Indexes.
What’s the Coolest thing I did in Windchill 9. 1
Introduction to NTFS Permissions
Archiving and Document Transfer Utilities
Microsoft Office Access 2010 Lab 2
CARA 3.10 Major New Features
An In-Depth Look at the Autodesk® AutoCAD® App Autoloader Module
Bulk Loading Documents* into Windchill
PDMLink Design Object Numbering
Metadata Editor Introduction
Introducing Microsoft Office 2010
Microsoft Office Access 2003
Microsoft Office Access 2003
Geometric Network Toolset
Using Templates and Library Items
Access Test Questions Test Date: 05/05/16.
Presentation transcript:

Windchill PDMLink Part Creation Utility PTC INTERNAL USE ONLY Windchill PDMLink Part Creation Utility

Introduction PDMLink’s Part Creation utility helps to selectively decide for which of the migrated CAD Documents should WTPart be created. The part creation process can be refined by configuring an XML file called ‘part_creation.xml’ which is used by the part creation utility at runtime, so as to filter and select the CAD documents for which WTPart need’s to be created. © 2006 PTC

Introduction Cont… The Object for which part’s are to be created can be selected based on the following 7 criteria. 1. CAD Document Authoring Application 2. Document Type 3. CAD Document Name 4. CAD Document Number 5. Attribute Value 6. Release Level 7. Folder Location © 2006 PTC

Part_creation.xml The part selection is determined by the criteria defined in part_creation.xml. This XML file is at ‘codebase\com\ptc\windchill\pdmlink\proimigration\server\xml’ The root tag of this file is <Specifier> tag. This tag contain one or more <PartAction> tags. <Specifier> <PartAction> </PartAction> </Specifier> The <PartAction> element can contain three child elements that can be used to filter and select CAD Documents. 1. <FolderSpec> [Folder specification], 2. <PISpec> [Product Item Specification] and 3. <PIVSpec> [Product Item Version Specification]. <FolderSpec> </FolderSpec> <PISpec> </PISpec> <PIVSpec> </PIVSpec> Conditions: PartAction Element must contain at least one of these elements or a combination of several. cannot use any single element more than once in the <PartAction> element © 2006 PTC

PartAction Element The PartAction tag determines whether or not the system should create part, and the Class for the WTParts to be created from the selected CAD Documents. The <PartAction> element has the following two attributes. Create :- Determines whether or not the part creation tool should create parts for the CAD Documents selected by <PartAction>. This attribute can have a value of either ‘True’ or ‘False’. The default value is True. Class :- This attribute determines the class for WTPart that would be created by the part creation tool for the selected CAD Document objects. This is a required attribute PartAction Element and Its Attributes Example: <PartAction Class="wt.part.WTPart"> ------------------------------------------------- <PartAction> Attributes Values Create True/False Class wt.part.WTPart wt.part.WTProduct wt.part.WTSerialNumberedPart wt.part.WTPart | com.orgname.OrgPart © 2006 PTC

Folder Specification Element This element allows for the selection of CAD Documents based on specific folder locations. The <FolderSpec> tag can contain one or more <FolderCriteria> Elements. The <FolderSpec> tag has the following attribute CriteriaJoin :- if the <FolderSpec> element contains multiple <FolderCriteria> statements, then this attribute determines if the system selects CAD Documents that meets all of this Criteria or any of the criteria. The ‘CriteriaJoin’ attribute can have a value of either And :- Selects CAD documents that meets all the of the criteria specified in <FolderCriteria> element. Or :- Selects CAD Document that meets any of the criteria specified in <FolderCriteria> Element. FolderSpec Element and Its Attributes <FolderSpec CriteriaJoin="Or"> <FolderCriteria></FolderCriteria> </FolderSpec> Attributes Values CriteriaJoin And/Or © 2006 PTC

FolderCriteria <FolderCriteria> element is a container for all of the <FolderCondition> element in <FolderSpec>. There can be multiple <FolderCriteria> element within a folder specification. The folder criteria element has the following attribute. ConditionJoin :- If the folder criteria element has multiple folder condition statements then this attribute specifies determines if the system should create parts for CAD Documents that meets all the criteria or any of the criteria’s. This attribute can have either of the following values. And :- The system selects CAD documents that meets all of the criteria specified in the <FolderCondition> elements. Or :- The system selects CAD documents that meet any of the criteria specified in the <FolderCondition> element. FolderCriteria Element and Its Attributes <FolderCriteria ConditionJoin="Or"> <FolderCondition></FolderCondition> </FolderCriteria> Attributes Values ConditionJoin And/Or © 2006 PTC

FolderCondition This element specifies and individual folder location from which to ‘select/not select’ the CAD documents. The <FolderCondition> has the following Attributes, Context :This attribute specifies the product context including organization for which parts have to be created. Operator :This attribute specifies an assignment operator that connects the lookup attribute to the value attribute. This attribute can have the following values: equal or notEqual Value : This attribute specifies the full path to the folder location. E.g. Value=”/Default/Templates” Attributes Values Context And/Or Operator equal/notEqual Value Eg: Root Folder/Some_location/ FolderCondition Element and Its Attributes <FolderCondition> Operator="notEqual" Value="/Default/Design“ Context="/wt.inf.container.OrgContainer=ITCINFOTECH/wt.pdmlink.PDMLinkProduct=GOLF_CART"/> </FolderCondition> © 2006 PTC

<PISpec> Product Item Specification Element Product item specification allows to select CAD Document based on Product Item criteria. The <PISpec> element can contain one or more <PICriteria> elements and it has the following attribute: CriteriaJoin :If the <PISpec> element has multiple <PICriteria> statements then this attribute specifies if the system should select CAD Documents that satisfies all of the criteria or those that satisfies any of the criteria. This attribute can have the following values: And :- The system selects the CAD Documents that satisfies all of the criteria specified by <PICriteria> elements. Or :- The system selects CAD Documents that meets any of the conditions specified by <PICriteria> elements. Product Item Specification Element <PISpec> <PICriteria> <AttrCondition> ------------- </AttrCondition> </PICriteria> </PISpec> E.g: <PISpec CriteriaJoin= "Or"> …………………… Attributes Values CriteriaJoin And/Or © 2006 PTC

<PICriteria> Product Item Criteria <PICriteria> element is a container for all of the individual <AttrCondition> elements. There can be multiple <PICriteria> elements within a <PISpec> element. The <PICriteria> element has the following attribute. ConditionJoin: If the <PICriteria> element has multiple <AttrCondition> statements, then this attribute specifies if the system selects CAD Documents that meets all of the condition statements or any of the condition statements. This attribute can have the following values. And :- The system selects CAD Documents that meets all of the conditions specified by the <AttrCondition> statements. Or :- The system selects CAD Documents that meet any of the condition specified by the <AttrCondition> statements. E.g <PISpec> <PICriteria ConditionJoin= “Or”> …………………... </PICriteria> </PISpec> Attributes Values ConditionJoin And/Or © 2006 PTC

<AttrCondition> Attribute Condition This element allows identifying attribute values as criteria for selecting CAD Documents. This element has four attributes. Attributes Values AttrName Eg: name Operator equal/notEqual/greaterThan/greaterThanOrEqual/lessThan/lessThanOrEqual Value The value of the desired attribute. AttrTypeIsDate True/False <AttrCondition AttrName=”Some_date” Operator=”greaterThan” Value= ”01/01/1986” AttrTypeIsDate=”True”/> © 2006 PTC

<PIVSpec> Product Item Version Specification Element The product item version specification allows to select CAD Documents based on PIV Criteria. The <PIVSpec> is a container within which one or more <PIVCriteria> elements reside. The <PIVSpec> element has the following attribute CriteriaJoin :-If the PIVSpec element has multiple PIVCriteria elements, then this attribute specifies if the system selects CAD Documents that meets all of the Criteria or any of the criteria. This attribute can have the following value. And :- the system selects CAD Objects that meets all of the conditions specified in the <PIVCriteria> element Or :- The system selects CAD Documents that meets all of the condition specified by the <PIVCriteria> element. E.g: <PIVSpec CriteriaJoin= “Or”> ………………….. </PIVSpec> © 2006 PTC

<PIVCriteria> Element The <PIVCriteria> element is a container for all of the individual <PIVCondition> or <AttrCondition> element in <PIVSpec>. The <PIVCriteria> element has the following attributes. ConditionJoin : If the <PIVCriteria> element has multiple <PIVCondition> or <AttrCondition> element, then this attribute specifies if the system selects CAD Documents that meets all or any of the condition specified. This attribute can have the following value And :-The system selects CAD Documents that meets all the criteria’s specified by the <PIVCondition> element. Or :- The system selects CAD Documents that satisfies any of the criteria’s specified by the <PIVCondition> element E.g <PIVSpec> <PIVCriteria ConditionJoin= “Or”> .. </PIVCriteria> </PIVSpec> © 2006 PTC

<PIVCondition> Element This Tag contains the individual conditions under which a particular product item version should be selected. This tag can have the following attributes. Version :- This attribute specified whether the <PIVCondition> selects all version, latest version or a specific version of a CAD Document. This attribute can have the following value. a) latest :- Indicates that the <PIVCondition> element selects the latest version. b) all :- Indicates that the <PIVCondition> element selects all versions of a CAD Document. c) specific :-Indicates that the <PIVCondition> element selects CAD Document with a specific version value. Operator :- This attribute specifies an assignment operator. This attributes can have the following values. a) equal b) notEqual c) greaterThan d) greaterThanOrEqual e) lessThan f) lessThanOrEqual Value :- Indicates the version value to be searched for. E.g. A,B,A1 © 2006 PTC

Mapping Life Cycle and States The EMP Documents Lifecycle and States need to be mapped to WTPart lifecycle and States. To do this, edit ‘lifecyclemap.properties.xconf’ in ‘/codebase/ com/ ptc/ windchill/ pdmlink/proimigration/’, and add properties in the following format. <Property default="PartLifeCycle" name="EPMLifeCycle"/> <Property default="PartLifeCycle.State1" name="EPMLifeCycle.State1"/> <Property default="PartLifeCycle.State2" name="EPMLifeCycle.State2"/> <Property default="PartLifeCycle.State3" name="EPMLifeCycle.State3"/> <Property default="PartLifeCycle.State4" name="EPMLifeCycle.State4"/> Propagate the changes made to the xconf file, which will add the following entries to ‘lifecyclemap.properties’. EPMLifeCycle=PartLifeCycle EPMLifeCycle.State1=PartLifeCycle.State1 EPMLifeCycle.State2=PartLifeCycle.State2 EPMLifeCycle.State3=PartLifeCycle.State3 EPMLifeCycle.State4=PartLifeCycle.State4 © 2006 PTC

Executing WTPart Creator To execute the WTPart Creator tool run the following command from windchill shell : WT_Home/codebase>windchill com.ptc.windchill.pdmlink.proimigration.server.WTPartCreator Which will give the following menu .. ProIntralink to PDMLink Part Create Migration Tool -------------------------------------------------- 1. Search for CAD Documents to process. 2. Validate your objects, and see existing warnings. 3. Create new parts. 4. Create links WTPart ->EPMDocument . 5. Build Part Structures. 6. Add Parts to Baselines. 7. Delete the temporary status table. 8. Exit >>> Choose an option: © 2006 PTC

Examples 1. CAD Document authoring application <PISpec CriteriaJoin="And"> <PICriteria ConditionJoin="And"> <AttrCondition AttrName="authoringApplication" Operator="equal" Value="PROE" AttrTypeIsDate = "false"/> </PICriteria> </PISpec> 2. Document type <AttrCondition AttrName="docType" Operator="equal" Value=“CADCOMPONENT" AttrTypeIsDate = "false"/> © 2006 PTC

Examples 3. CAD document name <PISpec CriteriaJoin="And"> <PICriteria ConditionJoin="And"> <AttrCondition AttrName="CADName" Operator="equal" Value="72155.prt" AttrTypeIsDate = "false"/> </PICriteria> </PISpec> 4. Attribute value <PISpec CriteriaJoin="Or"> <PICriteria ConditionJoin="Or"> <AttrCondition AttrName="name" Operator="notEqual" Value="SomeThing*" AttrTypeIsDate = "false"/> <AttrCondition AttrName="number" Operator="equal" Value="34436675" AttrTypeIsDate = "false"/> © 2006 PTC

Examples 5. Release Level <PISpec CriteriaJoin="And"> <PICriteria ConditionJoin="And"> <AttrCondition AttrName="state. state" Operator="equal" Value="INWORK" AttrTypeIsDate = "false"/> </PICriteria> </PISpec> 6. Folder Location <FolderSpec CriteriaJoin="Or"> <FolderCriteria ConditionJoin="And"> <FolderCondition Operator="equal" Value="/Default/SomeFolder" Context= "/wt.inf.container.OrgContainer=ORG/wt.pdmlink.PDMLinkProduct=PRD"/> </FolderCriteria> </FolderSpec> © 2006 PTC

WTPartCreator startup © 2006 PTC

After Choosing Option 1 © 2006 PTC

After Choosing Option 2 © 2006 PTC

After Choosing Option 3 © 2006 PTC

After Choosing Option 4 © 2006 PTC

After Choosing Option 5 © 2006 PTC

After Choosing Option 7 It will remove the rows exists with status initial or validated It will not remove rows with status created or linked or built © 2006 PTC

Questions © 2006 PTC