Create a Work Item - Nextedy Documentation

Prerequisites

A Powersheet document open in Siemens Polarion ALM with a valid sheet configuration and domain model
The entity type you want to create must be defined in the domain model with a valid polarionType mapping
Your user account must have create permissions (isCreatable enabled) for the target work item type

Step 1: Add a New Row

Click the Add button (➕) in the sheet toolbar. A new empty row appears in the sheet with default values from the entity factory configuration.

The new row is created at the current hierarchy level. If you have a multi-level sheet (for example, UserNeed > SystemRequirement > DesignRequirement), the row is added at the level corresponding to the selected cell’s entity type.

Step 2: Enter Required Fields

Click into the new row and type directly into cells to populate field values. The cell that receives initial focus is determined by the hasFocus property in your sheet configuration:

columns:
  title:
    title: Title
    width: 200
    hasFocus: true
  severity:
    title: Severity
    width: 100

Press Enter to commit the cell edit. Fields configured as isReadOnly: true or with updatable: false in the domain model cannot be edited.

Powersheet supports saving several custom field types including integer fields (c_intField), floating-point fields (c_floatField), and currency fields (c_currencyField). Each field type tracks both the current value and the original value for change detection.

Step 3: Understand Document Routing

When your domain model defines constraints on the entity type, new work items are automatically routed to the correct Polarion document. The constraint system scopes new entities to the current document context automatically. For example, a domain model that routes SystemRequirement items to a specific document:

domainModelTypes:
  SystemRequirement:
    polarionType: sys_req
    constraints:
      create:
        document:
          moduleFolder: /System Requirements
          moduleName: SRS
          type: sys_req_spec

When a user creates a SystemRequirement, it is automatically placed in the document matching the specified folder, name, and type.

The constraint system can route new items based on the source entity’s document context. This is useful when the same entity type should go to different documents depending on where it was created from within the expansion path.

Constrained Picker Values

In a multi-level sheet, constraints can also filter the available values in picker columns. For example, when creating a UserNeed and selecting a linked SystemRequirement, the picker shows only system requirements from the matching document type.

Constraint Type	Behavior
Document routing	New items are placed in the specified Polarion document
Picker filtering	Dropdown values are filtered based on document type and component
Multi-property	Combines document type and component constraints

Step 4: Review Before Saving

Before saving, use review mode to inspect your pending changes:

The Review toggle appears automatically in the toolbar when any changes exist
Click it to filter the sheet to show only rows with pending changes
New rows are indicated with the Added state marker on the row header
Use the review mode dropdown menu to filter by change type

Review Filter	What It Shows
Added	Newly created rows not yet persisted to Polarion
Modified	Existing rows with changed cell values
Problems	Rows with validation errors that block saving

The row count display shows the format N/M rows where N is the number of visible filtered rows and M is the total row count.

Adding a row without entering any data does not enable the Save button. Only actual data changes (typing values into cells) mark the row as dirty. If you add a row and then undo, the sheet returns to its original clean state.

Step 5: Save Changes

Click the Save button (💾) in the toolbar. During the save operation:

The sheet checks for any active error state — if errors exist, you see an alert message and the save is blocked
The sheet temporarily enters read-only mode to prevent concurrent edits
All pending entity changes (with Added state) are validated and sent to the server
Server-generated identifiers (such as objectId) are assigned to new items via key mapping
The undo stack is cleared on successful save
Original read-only state and permissions (isCreatable, isDeletable, isUpdatable) are restored

If the sheet is in an error state, the save operation is blocked with the message: “There is an error in the app and save should not happen. Please, reload the browser.” Resolve any errors or reload the page before attempting to save again.

Step 6: Undo and Redo

If you make a mistake before saving, use the Undo () and Redo () buttons in the toolbar:

Undo reverses the last operation (add, remove, or edit) and restores the previous sheet state including row position and content
Redo re-applies a previously undone operation
Both operations preserve selection state, including multi-row selections
Undoing all operations disables both the Undo and Save buttons

Select multiple rows using Shift+Click (click the first row, hold Shift, click the last row). You can then remove all selected rows at once with the Remove button. This operation is fully undoable.

Step 7: Verify

You should now see the new work item in the sheet with a server-assigned ID. The row header no longer shows the Added state indicator, and the Save button is disabled (indicating no pending changes remain).

Open the corresponding Polarion LiveDoc to confirm the work item appears in the expected document location with the correct work item type. If document routing constraints are configured, verify the item was placed in the correct module folder.

Troubleshooting

Symptom	Cause	Resolution
Save button stays disabled	No actual data entered in the new row	Type values into at least one cell
Save blocked with error alert	Sheet is in an error state	Reload the browser and retry
Row appears but picker is empty	Constraint filtering too restrictive	Check `constraints` configuration in domain model
Wrong document placement	Missing or incorrect `create` constraint	Verify `moduleFolder`, `moduleName`, and `type` values

​Prerequisites

​Step 1: Add a New Row

​Step 2: Enter Required Fields

​Step 3: Understand Document Routing

​Constrained Picker Values

​Step 4: Review Before Saving

​Step 5: Save Changes

​Step 6: Undo and Redo

​Step 7: Verify

​Troubleshooting

​See Also

Prerequisites

Step 1: Add a New Row

Step 2: Enter Required Fields

Step 3: Understand Document Routing

Constrained Picker Values

Step 4: Review Before Saving

Step 5: Save Changes

Step 6: Undo and Redo

Step 7: Verify

Troubleshooting

See Also