Configuring CLM Project Associations

Before users can start creating Collaboration Links from the CLM Application to Windchill [1], you need to define what Windchill products will be visible to the project you manage. This is done by defining associations between your project and the Windchill products. Once set, the association type will define on its own the available link types to create from the CLM project to the Windchill product. It is worth to mention that when creating an association, the available association types will depend in turn on the nature (domain) of the CLM Application.

This app supports the following associations and corresponding link types per application domain:

Application Domain Association Type Compatible Application Artifacts Collaboration Link Type
Requirements Management (RM) Provides - Requirements Requirement Derives From Architecture Element
Refined By Architecture Element
Satisfied By Architecture Element
Traced By Architecture Element
Change Management (CM) Provides - Related Change Requests Change Request Related Change Request
Affects Plan Item
Affected By Defect
Quality Management (QM) Uses - Architecture Elements Test Case Validates Architecture Element
Quality Management (QM) Uses - Defects Test Case Tests Development Item
Test Execution Record Blocking Defect
Test Result Affected By Change Request
Quality Management (QM) Uses - Quality Management Tasks Test Plan, Test Case, Test Execution Record, Test Script Related Change Request

To create an association with a Windchill product:

  1. Enter to the CLM project admin page.
  2. Locate the section for Associations to remote CLM projects.
  3. Click on the Add button (Add Association).
  4. Select Windchill in the Application combo.
  5. In the Association combo, and by looking at the above table, select the association type depending on the outgoing link types required.
  6. As soon as you select the association type, a pop-up window will appear [2]. If you hadn't previously started an OSLC Connect for Windchill session in the same browser, the new window will show you the OSLC Connect for Windchill login page and you must continue with this step, otherwise please go to the next one [3]. The login page is here to complete the user authentication process, so please provide valid user credentials, it is not necessary that such user has an admin role [3].
  7. What happens after the user authentication process (or if you had already started a session in other browser's tab) depends on whether the Windchill consumer was configured on the CLM Application as trusted or not. If it was configured as trusted, the only thing you need to do is to ignore a blank page that will be displayed for some milliseconds, and then you can go to the next step; otherwise, you will see the Authorize Application page which is a last confirmation to allow Windchill accessing the CLM Application information on behalf the user you used to login [4]. Click the Allow button and then close the pop-up window when indicated if it is not closed automatically.
  8. Back on the Add Association dialog, a new Project field will display the available projects for the logged-in user. Choose the project to which you want to create the association and click the OK button.

If everything went as planned, the Add Association dialog will be closed and the new association will be displayed on the Product Associations table. You can repeat these steps to add more association types over the same or other CLM Application projects; but just remember that this time, steps 6 and 7 won't be necessary as authentication and authorization is required only once per Windchill session.

To remove an association:

  1. In the Product Associations table, select the association row and click on the red remove icon.
  2. Confirm your decision by clicking on the OK button in the opened Confirm delete dialog.
  3. Finally click on the Save button of the project configuration page.

If everything went ok, the chosen association will be removed from the system and it will no longer appear on the table.