Manage Cross-Project Resources - Nextedy Documentation

Use Global Templates for Shared Configuration

Global templates provide the primary mechanism for sharing Risksheet configuration across projects. When a document inherits from a template, it receives the template’s risksheet.json including all shared definitions.

Create a Risksheet template document containing the shared configuration
Configure the template path in Risksheet Project Properties so all projects reference the same template
Documents created from the template automatically inherit the shared configuration:

Shared Resource	Configuration Key	What It Provides
Enumerations	`enums`	Dropdown options with IDs, names, descriptions, and icons
Rating scales	`ratings`	Severity, occurrence, detection scales for risk assessment
Formulas	`formulas`	Named formula functions (e.g., RPN calculation)
Styles	`styles`	CSS class definitions for conditional formatting
Cell decorators	`cellDecorators`	Conditional formatting functions mapped to columns
Views	`views`	Saved column visibility presets

Documents can override specific parts of the inherited configuration by attaching their own risksheet.json.

When you update a global template’s risksheet.json, documents inheriting from it pick up the changes on the next page load. No manual update is needed per document.

Enum columns automatically filter values based on column type and project context. When a column loads items from multiple projects via the project parameter in typeProperties, enum values from all configured projects are merged:

{
  "columns": [
    {
      "header": "Risk Type",
      "binding": "riskType",
      "type": "enum:riskCategory",
      "typeProperties": {
        "project": "SafetyProject,CyberProject"
      }
    }
  ]
}

Task-type enums filter across configured task types in multiple projects. Risk-type enums filter by configured risk types. Project enum columns show only projects allowed in the configuration.

Configure Cross-Project Reviews

Work item-based reviews can store review items in a dedicated project while linking them back to risk items in the originating project:

{
  "reviews": {
    "reviewManager": "WorkItemBased",
    "typeProperties": {
      "linkTypes": "reviewItem",
      "linkRole": "reviews",
      "project": "ReviewsProject",
      "document": "Reviews/FMEAReviews"
    }
  }
}

When document is specified, review work items are created as document work items and positioned after the last existing review item in the target document.

Work item-based reviews require typeProperties.linkTypes and typeProperties.linkRole to be set. Missing either property results in a runtime error when creating reviews.

Cross-Project Workflow Status Transitions

When editing cross-project linked items, the workflow status dropdown correctly loads available transitions for the item’s home project. The status field presents only valid workflow actions based on the work item’s current state in its originating project.

Workflow status transitions are not available for newly created work items until they are saved. The status dropdown remains disabled for unsaved items.

Manage User Roles Across Projects

When downstream tasks reside in a different project, the assignee column’s userRole: 'project_assignable' fetches users from the Risksheet project context, not the task’s home project. Workaround: Use a global role where needed users are added across all relevant projects:

{
  "columns": [
    {
      "header": "Assignee",
      "binding": "assignee",
      "type": "ref:user",
      "userRole": "global_risk_team"
    }
  ]
}

Cross-Project Autocomplete and Suggestions

Autocomplete suggestions for link columns are automatically scoped to the configured projects. When typeProperties.project lists multiple projects, the suggestion API returns matching items from all listed projects:

Users type a fragment and see results from all configured project scopes
Invalid suggestions from projects that do not match the column’s type filters are automatically excluded
Configure suggester.limit in Risksheet Project Properties to control the maximum number of suggestions (default: 20)

Verify Your Configuration

After setting up cross-project resources:

Open a Risksheet document that inherits from the global template
Confirm enumerations, ratings, and formulas load correctly from the shared configuration
Verify that link columns show suggestions from all configured projects
Create a new linked item and confirm it appears in the correct target project
Test workflow status transitions on cross-project items

You should now see shared resources loading consistently across all projects using the same template and cross-project configuration.

​Use Global Templates for Shared Configuration

​Share Enumerations Across Projects

​Configure Cross-Project Reviews

​Cross-Project Workflow Status Transitions

​Manage User Roles Across Projects

​Cross-Project Autocomplete and Suggestions

​Verify Your Configuration

​See Also

Use Global Templates for Shared Configuration

Share Enumerations Across Projects

Configure Cross-Project Reviews

Cross-Project Workflow Status Transitions

Manage User Roles Across Projects

Cross-Project Autocomplete and Suggestions

Verify Your Configuration

See Also