Handling Relationships Across Multiple ReqIF Files in DX

Kemi
Kemi
  • Updated

Overview

This article explains how Data Exchange (DX) handles relationships in ReqIF imports, the limitations when working with multiple ReqIF files, and best practices for post-processing relationships.

1. Can DX Create Relationships Across Multiple ReqIF Files?

DX will only create relationships if both related items are in the same ReqIF file during import.
If items are split across different ReqIF files, DX cannot automatically relate them—this requires post-processing (script-based linking).

Conversation Mode Exception

  • If Conversation Mode is enabled, DX can create cross-file relationships IF:

    • The ReqIF IDs remain consistent across files.

    • The item types are defined in both files.

    • The items exist inside the import location in Jama Connect.

  • However, this is a very specific use case and not always feasible.

2. Why Does DX Need Item Types to Be Defined in Both Files?

✔ DX maps ReqIF Identifiers (not DOORS IDs) to Jama items.
✔ If one ReqIF file has Types 1 & 2 and another has Types 3 & 4, DX cannot create relationships across them because it lacks a unified mapping.
ReqIF ID (globally unique) is required for cross-file relationships, but some tools (like DOORS) may not follow the ReqIF spec consistently.

Solution for This Limitation:

  • Post-process the relationships by scripting a process to scan ReqIF files and map relationships based on ReqIF Identifiers.

3. Can a Script Be Used to Establish Relationships in Jama Post-Import?

No existing script today automates this process.
Possible Workarounds:

  • Scrape ReqIF files to extract relationships and generate mapping data.

  • Use a script to match ReqIF Identifiers and establish links in Jama.

  • Leverage Module Key + DOORS ID if needed, but this must be manually handled.

Checking the EES library (Enterprise Engineering Scripts) or a Confluence page may provide additional insights into available tools.

4. Best Practices for Handling Relationships Across ReqIF Files

If possible, consolidate related items in a single ReqIF file before exporting to DX.
Enable Conversation Mode if relationships must be retained across files.
Post-process relationships with scripts if using multiple ReqIF files.
Verify that ReqIF Identifiers are preserved across all related files.

5. Conclusion

  • DX can only create relationships within the same ReqIF file; cross-file relationships require manual post-processing.

  • Conversation Mode can help, but only if ReqIF IDs and item types are consistently mapped across files.

  • A script to automate post-import relationships in Jama does not currently exist, but a custom-built script could solve this issue.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.