Installing Powersheet into an Existing Project (Based on Nextedy provided JNJ MedDev Template)

Modified on Thu, 10 Jul at 4:50 PM

In this scenario, we are integrating Powersheet into a project that is based on the JNJ MedDev R&T template. Older version of this template was provided to Nextedy and configured to use Powersheets  a Requirements Traceability Matrix view on top of the User Need Specification documents. Although some updates were made to the upstream template since, the core document types, structure, and logic remain compatible. Therefore, we rely on Nextedy-provided preconfigured Powersheets, which were originally built against the earlier JNJ MedDev baseline.

This approach significantly simplifies the installation, as most elements are already prepared and only need to be reused or lightly adapted.


Summary of What’s Reused vs Configured

Component

Action

New Document type

Not needed — reuse existing LiveDoc types

templateDoc field

Uses query: title:Powersheet*

Powersheet config docs

Reuse existing documents (e.g. Reports/Powersheet RTM)

Model

Create new, then copy-paste YAML from template

Topic

Must be manually added; required for Powersheet visibility

Context property

Ensures documents with populated templateDoc field show up in Drive


Step-by-Step Setup

1. Enable the Powersheet Topic in Navigation

Without this step, Powersheet will not be accessible even via direct links.

  1. Go to Administration → Portal → Topics

  2. Add the following to each view where Powersheet should be available (typically admin, team, docspec):

<topic id="powersheet"/>

This topic controls visibility of the Powersheet Drive, which aggregates available configured documents.


2. Create templateDoc Custom Field for Documents

The templateDoc custom field determines which Powersheet template a document uses. In this setup:

  • ID: templateDoc

  • Name: Powersheet Template

  • Type: Object Enumeration (Document)

  • Query constraint (if configured):

title:Powersheet*

This makes any document whose title starts with “Powersheet” selectable as a template.

3. Ensure Powersheet Context Property is Configured

To show documents that refer to a Powersheet template in the Powersheet Drive (topic), the following project context property must be present:

com.powersheet.powersheetDocumentQuery=HAS_VALUE:templateDoc.KEY

This setting ensures that any document with a populated templateDoc field is considered a Powersheet and shown in the navigation topic.

4. Create or Import the Data Model

  1. Navigate to Administration → Powersheet → Models

  2. Click “New”

  3. Select “System Default” as the base (V-model style, Drive Pilot-based)

  4. Give your model a name (e.g., rtm)

  5. Save and open the model

  6. Overwrite the contents by copy-pasting the YAML definition from our reference rtm model (used in the preconfigured JNJ MedDev Template)

This model captures all relevant types, links, and constraints used in the JNJ context.


5. Reuse or Create Powersheet Configuration Document

Option A: Reuse from Template

If available, simply reuse the document from a project created from the Nextedy-provided “JnJMedDevRnT 2506 Template”:

  • Path: Reports/Powersheet RTM

  • This document:

    • Contains the full configuration

    • Has the powersheet.yaml already attached

    • Can be copied to the same location in your target project

Option B: Create a New One

If reuse is not possible:

  1. Create a new document (standard LiveDoc)

  2. Set title to something like “Powersheet RTM”

  3. Attach the powersheet.yaml configuration (from the reference Reports/Powersheet RTM)

  4. Add a “Open with Nextedy POWERSHEET” link into wiki block by adding this code to the Wiki content block:

$openPowersheetButton.renderOpenPowersheetButton($document)


6. Link User Needs Specifications to the Powersheet View

In the JnJMedDevRnT 2506 Template, each User Needs Specification (UNS) document — whether it’s a template or an instance — is intended to act as a Powersheet document. The Powersheet view renders:

  • All User Needs from the current document

  • Their downstream traceability (Design Inputs, Outputs, Tests, etc.)

  • A structured, editable table scoped to that specific spec

To enable this:

Do the following for both the UNS template and all existing/future UNS documents:

  1. Open the document

  2. Set the templateDoc custom field to point to your Powersheet RTM view template (e.g., Reports/Powersheet RTM)

  3. (Optional) Add the Powersheet button at the top by inserting this in the wiki:

$openPowersheetButton.renderOpenPowersheetButton($document)

Any document with templateDoc set will:

  • Show up in the Powersheet Drive

  • Open with the proper table view embedded and editable

This simple link activates Powersheet functionality on a per-document basis and enables focused V-model views aligned with JNJ’s document structure.

At This Point…

  • Users will see Powersheet in the sidebar (if the topic is enabled)

  • Powersheet documents will appear (if they reference a valid templateDoc)

  • Users can create new structured content via the editable table view, without needing to know the underlying Polarion model

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article