Velocity Server Rendering - Nextedy Documentation

Server Rendering Context

When a property is configured with serverRender, the server evaluates the expression using Velocity templates with automatically injected Polarion services. These services are available as context variables in all server-rendered expressions.

Injected Polarion Services

Service Variable	Purpose	Common Use Cases
`$trackerService`	Access work item data	Querying work items, running Lucene queries, accessing tracker metadata
`$txService`	Transaction management	Understanding execution context, managing Polarion transactions
`$repositoryService`	Repository-level operations	Accessing project metadata, users, roles, repository configuration
`$securityService`	Permission checking	Checking user permissions, role-based visibility, enforcing security constraints

All Services Are Auto-InjectedThese services are automatically available in every server-rendered expression. No additional configuration is required to access them.

Server-Rendered Property Configuration

Properties configured with serverRender in the data model are evaluated on the server before being sent to the client. This affects both how the property value is computed and its editability.

Property Definition

Name	Type	Default	Description
`name`	`string`	Required	Property name exposed in the Powersheet client
`serverName`	`string`	Same as `name`	Override for the actual Polarion field name when it differs from the client-facing name
`customFieldName`	`string`	`null`	Polarion custom field ID for properties stored in custom fields
`type`	`string`	See application	Data type of the property (`string`, `integer`, `date`, `enum`, etc.)
`storage`	`string`	See application	How the property value is persisted in Polarion
`readable`	`boolean`	`true`	Controls whether the property can be read by clients
`updatable`	`boolean`	`true`	Controls whether the property can be modified by clients
`scalar`	`boolean`	`true`	Whether property holds a single value (`true`) or collection (`false`)

Server-Rendered Fields Are Read-OnlyProperties with serverRender enabled are automatically marked as non-editable in the sheet, regardless of the updatable setting. The server computes the value on each query; client-side edits would be overwritten.

Velocity Template Context Variables

Server-rendered expressions have access to these context variables during template execution:

Variable	Description
`$item`	The current work item being rendered
`$tx`	The current transaction context
`$context`	The query context including project, document, and parameters
`$pObject`	The Polarion persistent object reference

Service Usage Patterns

Tracker Service

Use $trackerService to query work items, access tracker metadata, and run Lucene queries within server-rendered expressions. Run a Lucene search through the project the service hands back:

#set($project = $trackerService.getTrackerProject($context.projectId))
$project.queryWorkItems("type:requirement", "id")

Search through getTrackerProject, not directly on the service. The services exposed to a template are read-only proxies, and they admit only methods whose names begin with get, is, has, find, search, list, count or exists. queryWorkItems matches none of those, so calling $trackerService.queryWorkItems(…) is refused and the cell renders #SERVER_RENDER_ERROR.getTrackerProject is an allowed read, and the project it returns carries the same query method — which is why the two-line form above works while the one-line form does not.

Security Service

Use $securityService to implement role-based visibility and conditional content in server-rendered fields.

#if($securityService.canPerformActionOnWorkItem($item, "modify"))
  editable
#else
  read-only
#end

Repository Service

Use $repositoryService to access project metadata, user information, and repository configuration.

$repositoryService.getProjectByID("myProject").getName()

Security Considerations

Server-rendered properties interact with the Powersheet security model:

Aspect	Behavior
Editability	Server-rendered fields are always read-only in the client
Permission inheritance	Entity-level `readable`/`updatable` settings intersect with property-level settings
System read-only fields	`id`, `outlineNumber` are always read-only regardless of configuration

Verify in applicationThe exact list of available service methods depends on the Polarion server version. Consult the Polarion SDK documentation for the full API reference of each injected service.

Complete YAML Example

domainModelTypes:
  UserNeed:
    polarionType: userNeed
    properties:
      title:
      severity:
      computedStatus:
        serverRender: |
          #set($project = $trackerService.getTrackerProject($context.projectId))
          #set($linkedItems = $project.queryWorkItems("type:systemRequirement", "id"))
          #if($linkedItems.size() > 0)
            Linked
          #else
            Unlinked
          #end
        readable: true
        updatable: false
  SystemRequirement:
    polarionType: systemRequirement
    properties:
      title:
      priority:

Velocity Templates — Template syntax and expression language
Context Variables — All variables available in server rendering context
Polarion Services — Detailed reference for each injected service
Properties — Data model property configuration
Permissions — Security model for properties and entities

​Server Rendering Context

​Injected Polarion Services

​Server-Rendered Property Configuration

​Property Definition

​Velocity Template Context Variables

​Service Usage Patterns

​Tracker Service

​Security Service

​Repository Service

​Security Considerations

​Complete YAML Example

​Related Pages

Server Rendering Context

Injected Polarion Services

Server-Rendered Property Configuration

Property Definition

Velocity Template Context Variables

Service Usage Patterns

Tracker Service

Security Service

Repository Service

Security Considerations

Complete YAML Example

Related Pages