More products
User Project Access
Requirements Management
URI Generator
Requirements Management
Tailoring Addon
Requirements Management
Find the right fit

Tell us about your engineering tools and the problem you want to solve.

Talk to us
Softacus

Collection Creation

Collection Creation builds a collection from artifacts selected in a DOORS Next module or view. Users specify the collection name, destination folder and collection type directly in the widget.

Requirements Management

About this offering

Turn a module selection into a named collectionWorkflow at a glanceInputs and resultsTechnical fit and boundariesEvaluation questionsPlan your evaluation

Turn a module selection into a named collection

Collection Creation creates an IBM DOORS Next collection from selected module artifacts or a module view. Coordinators define the name, destination folder and available collection type without leaving the module. Use it when a review, exchange or handover needs a defined set of existing content. The widget performs creation and displays progress after membership and destination are chosen.

Workflow at a glance

Editorial overview based on vendor documentation.

  1. Select the contentOpen the module and choose artifacts or a view defining membership.
  2. Define the collectionEnter a recognisable name and select its folder and type.
  3. Create and inspectMonitor creation and verify the result against the intended selection.

Inputs and results

Inputs are the selection, name, destination and type. Output is a new collection at the selected location. The documented purpose is grouping artifacts; duplication, transformation or baselining is not established.

Technical fit and boundaries

An open module and selected artifacts or view are required. Available types and destination access depend on project configuration. Confirm release compatibility, deployment, creation permissions and behaviour for the chosen artifact types.

Evaluation questions

Can a folder be the source? The documented source is module content; the folder picker sets the destination. Is the collection immutable? Creation alone does not establish a baseline or frozen snapshot.

Plan your evaluation

Provide the release, module/view, expected membership, type, destination and baseline or formal-review requirements. Confirm conditional vendor eligibility and implementation/support scope in the offer.

  • Advanced Filtering — Prepare a focused module view before deciding collection membership; automatic integration is not claimed.
  • Export Files — Use file export when a handover needs supporting files rather than a collection alone.

These are editorial suggestions for related scenarios; they do not imply a shared licence or a product integration.

Source: Official documentation.

Discuss your requirements

More products
Report Generator View
Requirements Management
Project Explorer
Requirements Management
Module Link Statistics
Requirements Management
Find the right fit

Tell us about your engineering tools and the problem you want to solve.

Talk to us