PTC Windchill
- Last updated
- Save as PDF
Overview
PTC Windchill is a PLM tool (Product Life Cycle Management) that focuses on the life cycle of physical products, such as parts, from the introduction phase, to growth, to maturity and finally decline. Within this world, businesses need software to guide them through each phase efficiently while ensuring high quality and centralized data. Windchill is able to this while executing rapidly on an interconnected system and ensuring that information flow from product concept to retirement is integrated between multiple teams across multiple departments.
Common Integration Patterns
Connector Setup Details
This section describes the basic steps needed to prepare your PTC Windchill instance for use with Hub. Note that additional fields for synchronization or configuration of queries may be required depending on the requirements of your integration.
Minimal User Permissions & Hub User
We recommend that you create a new user within your external tool, to be used only for your Hub integration. This is the user information you will enter when setting up your repository connection within Planview Hub. By creating a new user, you will ensure that the correct permissions are granted, and allow for traceability of the modifications that are made by the synchronization.
In general, your user account should have sufficient permissions to create, read, and update artifacts in your repository. However, depending on the use case, your user may need different permissions. For example, if you are only interested in flowing data out of your repository, your user may not need to have full CRUD access, as the 'create' and 'update' permissions may not be needed.
Your user should have a secure password or token. Please be aware that Hub will not allow you to save a repository connection utilizing a weak password/token, such as 'tasktop.'
See here to learn how to create a custom user in PTC Windchill.
Apply the following permissions to the relevant user or user group in the applicable domain in PTC Windchill:
-
Read
-
Download
-
Create
-
Create by Move
-
Modify
-
Modify Content
Connecting to the PTC Windchill Repository
Standard Authentication
Required Fields:
- Location/Connection URL
- Example Format: https://abc-ptcwin999.van.server.com/Windchill
- Username
- Password
Optional Fields:
- Throttling Settings: This field indicates the number of API calls that can be made per minute. See details here.
- Note: This field should only be set under the guidance of customer care as the ideal value is highly dependent on each customer's unique environment.
- Connection Security: If checked, insecure connections to this repository will be allowed. See details here.
Learn more about how to set up your repository in Planview Hub here.
Other Configuration Settings
Rich Text
Planview Hub: 19.4 and later
Supported Rich Text elements are:
-
Headings
-
Paragraph
-
List
-
Anchor
-
Emphasis (i.e., italic)
-
Strong (i.e., bold)
-
Strike (i.e., deleted)
-
Underlined
-
Subscript
-
Superscript
Full Scan
In general, a full scan is not required to synchronize updates from this repository. However, it is possible that some read-only fields may require a full scan. Please consult with customer care for additional details.
Learn more about how to configure change detection and full scan intervals in Planview Hub here.
Supported Features
Special Features Supported
You can learn more about special features in Planview Hub here.
Feature |
Applicable Hub Version |
Applicable Repository Versions |
---|---|---|
Time Worked (Worklogs) Impersonation |
||
Comments Impersonation Public/Private |
||
Attachments Impersonation |
||
State Transitions (Status can flow out of PTC as a single select, but not into PTC, as transitions are not supported) |
||
Person Reconciliation |
|
|
Supported Artifacts
Supported Work Items
Learn about the difference between containers and work items in Planview Hub here.
Supported Work Item Type |
Applicable Hub Versions |
Applicable Repository Versions |
Unique URL? |
---|---|---|---|
Part |
Planview Hub: 19.3 and later |
Any supported repository version: |
Yes |
Problem Report |
Planview Hub: 19.3 and later |
Any supported repository version: |
Yes |
Change Request |
Planview Hub: 19.3 and later |
Any supported repository version: |
Yes |
Requirement |
Planview Hub: 19.3 and later |
Any supported repository version: |
Yes |
Change Notice |
Planview Hub: 23.2 and later |
Any supported repository version: |
Yes |
Change Task |
Planview Hub: 23.2 and later |
Any supported repository version: |
Yes |
Supported Containers
Learn more about containment in Planview Hub here.
Containers that can synchronize between repositories |
Applicable Hub Versions |
Applicable Repository Versions |
Unique URL? |
---|---|---|---|
Folder Note: Beginning in Hub version 22.4, containers can be treated as work items. Learn more here. |
Planview Hub: 19.3 and later |
Any supported repository version: |
Yes |
Containers used to define the boundary of a collection (when clicking 'Manage Projects' on a collection) |
|
|
|
Products |
Planview Hub: 19.3 and later |
Any supported repository version: |
N/A |
Containers used for artifact routing |
|
|
|
Products, Folders |
Planview Hub: 19.3 and later |
Any supported repository version: |
N/A |
Supported Field Types
Note: If one field of a given type is supported, others that are also that type in theory should also work. However, sometimes there are instances in which this is not the case due to the repository. So, while we can claim support for fields at the type level, there is a chance that some specific fields of a given type will not synchronize properly.
Field Type |
Does Hub support custom fields of this type? |
How is field type referenced in the repository? |
Sample Repository Fields Supported |
Limitations |
---|---|---|---|---|
String |
|
String |
Name Number Created By (read-only) Modified By (read-only) Assignee (read-only) Reviewer (read-only) Change Notice Name (read-only) Change Notice Identity (read-only) |
|
Single-select |
|
String (Selection List) |
Priority Category |
|
Multi-select |
|
|
|
|
Boolean |
|
Boolean |
Investigation Required |
|
Date (Supported as Date Time in Hub) |
|
|
|
|
Date Time |
|
Date and Time, Date |
Need Date Resolution Date |
|
Duration |
|
|
|
|
Double |
|
|
|
|
Long |
|
Integer Number |
Maximum Allowed |
|
Person |
|
|
|
|
Persons |
|
|
|
|
Relationship(s) Learn how to configure relationships in Planview Hub here. |
|
|
Parent |
|
Rich Text Supported in: 19.4 and later; 4.20 and later |
N/A |
Rich Text |
Description Proposed Solution |
|
Location |
|
|
|
|
Artifact Link (Only supported for Change Tasks) |
Change Notice (read-only) |
|
||
Web Links |
|
|
|
|