The import/export dialog box contains a set of import/export functions. Objective is to view mass information with different view and to be able to import the mass information without having the obligation to change it item by item.
Export functions:
All the exported file use the csv ";" separtor format.
Content of the export:
A table containing all the templates and examples defined in the site by work product.
A directory containing all the templates files
Export format:
Column number Field name Field semantic 1
Work product name Work product name 2
Discipline Discipline related to the work product 3
templates list printed The paths of the templates associated to the work product taken into account the alternative/non alternative option defined (if alternative option defined, the alternative path appears if not empty. If empty the non alternative path appears. If non alternative option defined, the non alternative path appears). 4
Examples list printed The paths of the examples associated to the work product taking into account the alternative/non alternative option defined. 5
template L1F1 First template path, first language 6
example L1F1 First example path, first template 7
template L2F1 First template path, second language 8 example L2F1 First example path, second template 9 template F1 semantic Semantic of first template if 2 templates defined 10 template L1F2 Second template path, first language 11 example L1F2 Second example path, first template 12 template L2F2 Second template path, second language 13 example L2F2 Second example path, second template 14 template F2 semantic Semantic of second template (if exist) 15 Comment Comment related to template, example access Exported file:
<root>/tmp/template.csv
<root>/tmp/templates/*
Example
(old format):
Content of the export:
A table containing all the procedures / guides included in the site.
A directory containing all the templates files
Export format:
Column number Field name Field semantic 1 UID Unique identifier of the procedure / guide item 2
Name Procedure / guide name 3 Type Type of the procedure: procedure, guideline, training, ... 4 Status Validation status of the procedure 5 Discipline Discipline to which the procedure belong to 6 File L1 The procedure file path taking into account the alternative/non alternative option defined - for the first language 7 Description L1 The procedure description in the first language 8 File L2 The procedure file path taking into account the alternative/non alternative option defined - for the first language 9 Description L2 The procedure description in the first language Exported file:
<root>/tmp/procedures.csv
A directory containing all the procedures / guidelines files
Example
(old format):Content of the export:
The list of all the html file (*.htm & *.html) under <root>/site directory
Export format:
Column number Field name Field semantic 1 html file path html file path
Exported file: <root>/tmp/htmlFileList.csv
Content of the export:
A table containing all the work products defined in the site.
Export format:
Column number Field name Field semantic 1 Work product name Work product name
2 Domain Domain to which the work product belong to
3 Discipline Discipline to which the work product belong to
4 Used indicated if work product is used or produced by any activity of the site (1: used and/or produced, 0: not used, not produced)
5 Parent Name of the parent work product - if any
6 Description Description of the work product
Exported file: <root>/tmp/workproducts.csv
Content of the export:
List of roles defined in the site.
Export format:
Column number Field name Field semantic 1 Role name Role name
Exported file: <root>/tmp/roles.csv
Content of the export:
List of glossary items
Export format:
Column number Field name Field semantic 1 uid Unique identifier of the glossary item 2 Name L1 Glossary item name in the first language 3 Name L2 Glossary item name in the second language 4 description Glossary item description in the first language 5 description L2 Glossary item description in the second language 6 source L1 Description source in the first language 7 source L2 Description source in the second language 8 equivalent L1 Glossary item equivalent name in the first language 9 equivalent L2 Glossary item equivalent name in the second language Exported file:
Exported file: <root>/tmp/glossary.csv
Content of the export:
XML export compatible with EPF Composer 1.2 (export excluding the process schemas description)
Resources required for the EPF import
Export format: XML - http://www.eclipse.org/epf/uma/1.0.3
Steps:
1. Select the plug-in to create
2. Get the XML file in <root>/tmp/EPFExport/exportForEPF.xml
3. Get the warning message file in <root>/tmp/EPFExport/exportForEPF_warning.txt
4. Get the ressources (by plug-in) in <root>/tmp/EPFExport
Content of the export:
A table containing all the activities defined in the site with the associated roles.
Export format:
Column number Field name Field semantic 1 Activity name Activity name
2 Phase Phase to which the activity belong to
3 Discipline Discipline to which the activity belong to
4 Project Kind obsolete data
5-n Role List of roles performing the activity classified by role responsibility (one column for each responsibility)
Exported file: <root>/tmp/activities.csv
Content of the export:
An activity-work product matrix.
An activity-work product table.
Export format:
Matrix:
Columns The work products Lines The activities Cells The cells contains either:
- in: the work product is used in the activity
- out: the work productis produced or updated in the activity
- in/out: the work productis used and produced or updated in the activity
- <empty>: the work productis neither used nor produced/updated in the activitytable
:
Column number Field name Field semantic 1 name Activity name
2 in List of in work product names separated by |
3 out List of out work product names separated by |
Exported file:
<root>/tmp/aam.csv
<root>/tmp/aat.csv
Content of the export:
3 reports are produced:
wbs.csv A Work Breakdown Structure containing all the activities wbs2.csv A Work Breakdown Structure containing all the activities and the steps schedule.csv An import file for MS project containing the activities, the hierarchy level and the comment with an hyperlink to the activity
Content of the export:
A table of activities attribute is generated. This export could be used for activities attribute mass update.
Export format:
Column number Field name Field semantic 1
UID Unique id of the activity 2
Name Name of the activity in the first language 3
State State of the activity modeling (if applicable) 4
Version Version of the activity modeling (if applicable) 5
Activity type Activity type: standard, peer review, formal review 6
Step List of step description in the first language separated with the '|' character. 7
Step L2 List of step description in the second language separated with the '|' character Exported file: <root>/tmp/activitiesAttr.csv
Example:
Content of the export:
A table of work product attribute is generated. This export could be used for work product attribute mass update.
Export format:
Column number Field name Field semantic 1
UID Unique id of the work product 2
Name Name of the work product in the first language 4
File name Naming rule 5
Location Location of file if standardized (on CM tool or file system) 6
CM policy Define the CM policy associated to the work product 7
Image name of the image representing the work product in the activity and work product schemas 8
Type Type of the work product: Document, Document section, Source code, Build, Database, Data file, Data, Binary file, Equipment, Tool, Event ... 9 Timing Text describing the timeframe for creating, updating the work product in the process 10 Domain Domain associated to the work product 11 Discipline Discipline associated to the work product
Exported file: <root>/tmp/WPAttr.csv
Content of the export:
A table containing all the items and their description in 2 languages.
Export format:
Column number Field name Field semantic 1
UID Unique id of the work product 2 Name Item name in the first language 3 Description Description of the item in the first language 4 Description L2 Description of the item in the second language
Exported file: <root>/tmp/itemDescription.csv
Import functions:
BEFORE EACH IMPORT, BACKUP THE PROJECT
Description:
Allow to import the whole role-activity links including the role responsibility from an excel matrix.
File format:
- The column A to E should contain the Work Breakdow Structure of the process indented starting at line 3.
- The role name should appears line 2 from F2 cell.
- The cell(i,j) from the matrix should either contain:
- X: meaning Role i participate to Activity j
- <empty>: meaning Role i do not participate to Activity j
- <role responsibility>: meaning Role i participate to Activity j with <role responsibility> (note: in the example, role responsibilities have been simplified to a given letter - to replace before import)- format is csv with ; separator
Note: currently the import use the name of the activity and not his UID. If several activities shared the same name, process builder try to find the appropriate activity in comparing the activity hierarchy.
Example of import file:
Imported file:
A table of activities attribute of the same format of the activities attributes export so that can be used to mass import activities attribute.
Imported information:
The following attributes are imported:
Column number | Field name | Field semantic | Imported ? |
1 |
UID | Unique id of the activity | NO (key) |
2 |
Name | Name of the activity in the first language | NO |
3 |
State | State of the activity modelling (if applicable) | YES |
4 |
Version | Version of the activity modelling (if applicable) | YES |
5 |
Activity type | Activity type: standard, peer review, formal review | YES |
6 |
Step | List of step description in the first language separated with the '|' character. | YES |
7 |
Step L2 | List of step description in the second language separated with the '|' character | YES |
Imported file:
A table of work product attribute of the same format of the work product attributes export so that can be used to mass import work product attribute.
Imported information:
The following attributes are imported:
Column number Field name Field semantic Imported ? 1
UID Unique id of the work product NO (key) 2
Name Name of the work product in the first language NO 4
File name Naming rule YES 5
Location Location of file if standardized (on CM tool or file system) YES 6
CM policy Define the CM policy associated to the work product YES 7
Image name of the image representing the work product in the activity and work product schemas YES 8
Type Type of the work product: Document, Document section, Source code, Build, Database, Data file, Data, Binary file, Equipment, Tool, Event ... YES 9 Timing Text describing the timeframe for creating, updating the work product in the process YES 10 Domain Domain associated to the work product NO 11 Discipline Discipline associated to the work product NO
Description:
Allow to import the item descriptions using the same format as item description export.
File format:
Column number Field name Field semantic Imported ? 1
UID Unique id of the work product NO (key) 2 Name Item name in the first language NO 3 Description Description of the item in the first language YES 4 Description L2 Description of the item in the second language YES Note:
- If the description should contain several lines, the end of line in a given excel cell is managed with a alt-enter (it generate in the csv file a 0A instead of 0D 0A and enclose the text with ". This point is managed by the import tool).
Eunomia Process Builder, the Business Process Modeling Tool (BPM tool) | Web site: http://www.eunomia-process.com/ | main page |