Gateway: How to generate a pure IIF file from document

[mrump]

Hi all,

we have used the Requirement Solution for some years now (stated with the 2007 solution) and recently updated to I10.2.

For a maintenace project I am now asked to Re-Import an updated Word-Document into a 3 year old Integrity Document that was originally imported with the 2007 Solution.

The Document does not include an attached "source-document.iif" file as this "process" was invented later.

Does anyone know a way to easily generate the a IIF file of the current doument content which I would attach manually afterward; so the re-import would have something to match against.

I assume that the file is generated temporarily during a gateway export process anyway.

Or do I have to create my own XML-report template

THX in advance

[ptc-4058474]

Hi Mattias,

I thought there was an example on our downloads page (http://www.ptc.com/appserver/auth/it/esd/product.jsp?prodFamily=MIG), but I don't see it anymore. Below is some sample XML you could use.

Regards,

Dave

==================================

<?xml version="1.0" encoding="UTF-8"?>
<mapping name="PTC Sample Microsoft Word Requirements Document Import and Reimport" template-version="3.0">
<description>A working sample for MS Word import and reimport</description>

<!-- Sample Mapping configuration for ALM 2009 Requirement Document.
The ALM_ prefix on the internal field names will need to be
changed to match the prefix used on the ALM 2009 solution installation.
-->

<!-- The document being imported overrides the document in Integrity. -->
<set-property name="owner" value="external"/>

<!-- Field mappings that apply to both the Document node and Content nodes.
They can be overridden in sub-maps. -->
<field external="Project"
internal="Project"
direction="in"
on-create-only="true">
<default>/ALM_Projects/Release1</default>
</field>

<!-- Specific mappings defined below.
Depending on mks:MKSItems/mks:Item/@prototype value in the IIF,
a set of field mapping is applied.
-->
<map-conditional property="prototype" />

<!-- Document / Segment root -->
<map name="DOCUMENT">
<!-- Support the reimport; this allows the Integrity document to be specified. -->
<link-field external="IssueId" field-type="id" />

<field internal="Type"
direction="in"
field-type="type"
on-create-only="true">
<default>ALM_Requirement Document</default>
</field>

<field internal="Shared Category"
direction="in"
on-create-only="true">
<default>Document</default>
</field>

<!-- The setting of field/@external indicates that an external value is expected. -->
<field external="Title"
internal="ALM_Document Short Title"
direction="both"
required="true"
comparable="true" />
</map>

<!-- Content -->
<map name="CONTENT">
<!-- This supports content item matching. -->
<link-field external="IssueId" field-type="id" />

<field internal="Type"
direction="in"
field-type="type"
on-create-only="true">
<default>ALM_Requirement</default>
</field>

<!-- The setting of field/@external indicates that an external value is expected. -->
<field external="Summary"
internal="ALM_Text"
field-type="richcontent"
data-type="xhtml"
direction="both"
attachment="ALM_Text Attachments"
comparable="true" />

<field external="Category"
internal="Category"
direction="both"
comparable="true">
<default>User Requirement</default>
</field>
</map>
</mapping>

[ptc-4058474]

I got interrupted, but meant to explain that this is a gateway re-import template that will allow you to update an existing document number with new content. So if you export to get the ID, then re-import, Integrity will note the changes in the current document. Hope this helps your cause, albeit another route.

[mrump · Accepted solution]

Hi David,

in the meantime I found a way to export the pure iif file.

All i needed was an addiotional entry in the gateway-tool-config.xml file:
[code]
<export-config>
<name>iif Raw</name>
<exporter id="IIF"/>
<extension>iif</extension>
<title-field>Summary</title-field>
<gateway-configuration-name>IIFDocumentExport</gateway-configuration-name>
</export-config>
[/code]