Excel Import
In Blueprint new artifacts can also be created with an Excel import. It is important to note that you cannot undo an import from Excel. Unwanted artifacts would have to be deleted from within Blueprint.
To create new artifacts with an Excel import:
- Select the location for your new imported artifacts by selecting the parent folder or artifact. You cannot import new artifacts into a collection, baseline or review.
You also must have appropriate editing permissions for the location you have selected for your artifacts. - Click the More button in the main toolbar and select Import from Excel.
- Select the Excel file that you want to import into Blueprint.
Excel Spreadsheet Format
Each artifact you want to import must be in its own row in the spreadsheet. For Example:
The following columns can be included in the Excel spreadsheet:
Column Name | Required or Optional | Description | Valid Value |
Hierarchy | Optional | You can use the Hierarchy column to specify the relative outline level at which each artifact will be imported. When no Hierarchy is specified (no hierarchy column in the Excel spreadsheet), all artifacts are imported at the same level. | The plus sign (+) must appear in the appropriate column depending on the desired hierarchy. Only one row can have a plus sign (+) in the Hierarchy column. |
Name | Required | Defines the name of the artifact. | Specify the text that you want to import as the name of the artifact. |
Artifact Type | Required | Defines the artifact type. | This value must be an artifact type that exists in the project to which you are importing. |
Description | Optional | Defines the content for the description field | |
Artifact Properties | Optional | Values for artifact properties. | Values provided in the Excel file must match the acceptable value type for each property. |
Sample Excel Spreadsheets
The following examples will help guide you in the creation of your own Excel import file:
Simple Import Sample - Provides a basic template with only system properties.
Name | Artifact Type | Description |
User Story One | User Story | This is user story one |
User Story Two | User Story | This is user story two |
User Story Three | User Story | This is user story three |
Complex Import Sample - Provides an example with hierarchy columns, custom artifact types and custom properties. Keep in mind:
- The Hierarchy column and blank columns to the right of it are optional. The location of the plus (+) symbols indicate the hierarchy level.
- The values in the Artifact Type column are custom values. You will have to overwrite them with values that match your system configuration.
- The column names used to represent property names are also custom values. You will have to overwrite them with values that match your system configuration.
Hierarchy | Name | Artifact Type | Description | ||
+ | Credit Card Process Improvements | Process Improvement | |||
+ | Rejection Notice | Business Rule | We do a good job at notifying customers when their Credit Card is approved. We need to improve and ensure our Standard Operating Procedure (SOP) is met and customers are notified within 2 business days when their Credit Card application is rejected. | ||
+ | Process Timing Report | Process Improvement | As part of the Business Analysis, collect the average time to carry out each step in the Credit Card management process | ||
+ | Identify Tasks for Improvement | Process Improvement | |||
+ | Reduce Manual Tasks | Process Improvement | Identify any steps in the Credit Card management process that are purely manual (not supported by any bank technology). | ||
+ | Identify Non Enterprise Tasks | Process Improvement | Identify any steps in the Credit Card management process that still utilize the mainframe. |
