spk-logo-white-text-short2
0%
1-888-310-4540 (main) / 1-888-707-6150 (support) info@spkaa.com
Select Page

How to create Column Contexts for PTC Integrity documents

Written by SPK Blog Post
Published on May 29, 2014

One handy feature of PTC Integrity is the column context. Through the use of the column context a user can easily change what document columns are presented to them in the document view based on the role or task they are performing.

For example, by default a column context can appear as follows for a Requirement Specification document.

SPK-PTC-Integrity-1

By selecting a different pre-configured selection from the Column Context menu, you can change what columns appear within your document view.

For example, the Tracing context will display a set of alternate columns as follows:

SPK-PTC-Integrity-2

To create a new column context simply walk through the following steps:

  1. First you must define your new column context within integrity. You this as follows:
    1. Open the Integrity Administration client and Edit the MKS Solution type.
    2. Edit the following Properties of the MKS Solution type:
      • MKS.RQ.rm.document.open.viewSettings
      • MKS.RQ.rm.document.viewdocument.viewSettings
    3. Add the new custom context name as part of the comma delimited value string.  The new context value may not include whitespace.
    4. This will create the new custom context value that will appear in the Column Context menu.
  2. Once the Column Context menu has been updated to include the new Column Context value, the next step is to add the column selections that would be associated with that column context value. This is done through the viewSet.  For further information on how to create and publish viewSets please refer to the Integrity Server Administration Guide, or other blog articles on this topic.

Now that you know how to create and configure them, Column Contexts can be a handy feature to assist your local integrity user community.  Switching column contexts can allow users to quickly reconfigure their document view to present information that is most useful and relevant to their current task or role.

Next Steps:

Latest White Papers

A Checklist for Reducing Time to Market in Engineering

A Checklist for Reducing Time to Market in Engineering

Product teams all have the same goal: produce high-quality products and reduce time to market. Achieving these goals simultaneously can be difficult, but your team doesn’t have to sacrifice one for the other. Learn how in this eBook.What You Will Learn In this eBook,...

Related Resources

Why Traceability Is the Foundation of Modern Compliance

Why Traceability Is the Foundation of Modern Compliance

Key Takeaways End-to-end traceability is essential for regulatory compliance. Connecting requirements, risks, tests, changes, and approvals helps organizations maintain accurate compliance records throughout product development. Connected traceability improves audit...

Replacing IBM DOORS: Which Path Is Right?

Replacing IBM DOORS: Which Path Is Right?

Legacy IBM DOORS remains a mature requirements management platform, particularly for complex and regulated engineering programs. It provides structured specifications, baselines, electronic signatures, change management, and multi-level traceability.  However,...

Forward Deployed Engineers vs. Consultants: What’s the Difference?

Forward Deployed Engineers vs. Consultants: What’s the Difference?

Key Takeaways Consultants, professional services, and managed services serve different purposes. Consultants provide strategic guidance, professional services focus on implementation, and managed services support ongoing operations. Forward Deployed Engineers (FDEs)...