How to edit in Excel for future import

Exported Excel files are helpful for distributing information, quickly applying updates, and creating requirements or specifications in bulk. Once you have downloaded an Excel spreadsheet, you can:

Add a new row for each requirement or specification you would like the system to automatically create on import.
Modify non-key parts of existing rows to update requirements or specifications.
Modify key parts of existing rows to create copies of existing requirements or specifications.
Delete any row you are not using; this will not result in the deletion of the corresponding requirement or specification rule.

As a best practice, give a unique name to your edited spreadsheet. This reduces the possibility of accidentally overwriting it in subsequent exports.

Excel columns for exported requirements

Unless otherwise noted below, the standard values and restrictions for fields in the Excel file are the same as if you created a new requirement or modified data on an existing rule form:

Column name	Guidance
Application	Appears as a drop down menu; select a name from the list of available applications in your stack. Modify this key part on an existing row to create a copy of the requirement.
Requirement ID	Cells in this column have no data validation. Modify this key part on an existing row to create a copy of the requirement.
Short Description	Cells in this column have no data validation. If no text is provided, the value specified in the Requirement ID column is used.
Description	Cells in this column have no data validation.
Category	Appears as a drop down menu; select from the list of standard values or a custom value.
External Req. ID	Cells in this column have no data validation.
Importance	Appears as a drop down menu; select from the list of standard values or a custom value.
Status	Appears as a drop down menu; select from the list of standard values or a custom value.

Excel columns for exported specifications

Unless otherwise noted below, the standard values and restrictions for fields in the Excel file are the same as if you created a new specification or modified data on an existing rule form:

Column name	Guidance
Application	Appears as a drop down menu; select a name from the list of available applications in your stack. Modify this key part on an existing row to create a copy of the specification.
CaseType	Appears as a drop down menu; select a case type or supporting type. Modify this key part on an existing row to create a copy of the specification.
User Story Name	Appears when the Application methodology is set to `Scrum`. Cells in this column have no data validation. Modify this key part on an existing row to create a copy of the specification.
Use Case Name	Appears when the Application methodology is set to `PegaBPM` or `Other`. Cells in this column have no data validation. Modify this key part on an existing row to create a copy of the specification.
Short Description	Cells in this column have no data validation. If no text is provided, the value specified in the User Story Name or Use Case Name column is used.
Description	Cells in this column have no data validation.
Trigger	Appears as a drop down menu; select from the list of standard values or leave blank.
Actors	Cells in this column have no data validation. Use `Alt + Enter` keys to separate multiple actors.
Business Objective	Appears as a drop down menu; select from the list of standard values or leave blank.
Display As	Appears as a drop down menu; select from the list of standard values or leave blank.
Status	Appears as a drop down menu; select from the list of standard values or a custom value.
Subject Matter Experts	Cells in this column have no data validation. Use `Alt + Enter` keys to separate multiple SMEs.
Complexity	Appears as a drop down menu; select from the list of standard values or leave blank.
Acceptance Criteria	Appears when the Application methodology is set to `Scrum`. Cells in this column have no data validation. Use `Alt + Enter` keys to separate multiple acceptance criteria.
Pre-Conditions	Appears when the Application methodology is set to `PegaBPM` or `Other`. Cells in this column have no data validation. Use `Alt + Enter` keys to separate multiple pre conditions.
Post-Conditions	Appears when the Application methodology is set to `PegaBPM` or `Other`. Cells in this column have no data validation. Use `Alt + Enter` keys to separate multiple post conditions.

Note: The results (rows) and standard values available in exported Excel files are determined by the filter criteria set on the Requirements or Specifications landing page at the time the file was created.

application profile, requirements, specifications

Application Profile landing page

How to import and export requirements and specifications

Import Wizard Step

Requirement rule

Specification rule

Open topic with navigation

How to edit in Excel for future import

Excel columns for exported requirements

Column name

Guidance

Excel columns for exported specifications

Column name

Guidance