The wire stories import workflow is an essential part of the wire stories import.

You can create it before or after creating the data source template. However, you won't be able to test the data source template prior to finishing the wire stories import workflow.

The workflow gets embedded in the Import WF box of the data source template.

Wire stories import workflow structure

A wire stories import workflow typically has two main parts, enclosed within wfres:workFlow node: SequentialWorkflow and opt:XmlImportOptions, as shown below:

<wfres:workFlow

xmlns:wfres="http://www.teradp.com/schemas/GN4/1/WFRes.xsd">

 

<SequentialWorkflow

   .....

 </SequentialWorkflow>

 

 <!-- workflow resources - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

<opt:XmlImportOptions

   ....

 />

</wfres:workFlow>

 

Therefore, the parts of the a wire stories import workflow are:

•SequentialWorkflow node: it differs for import of wire story files in the XML format, in the plain-text format or as feeds. Examples are in SequentialWorkflow for wire story files (XML format), SequentialWorkflow for wire story files (plain-text format) and SequentialWorkflow for wire story feeds.

•opt:XmlImportOptions node appears in two flavors: one with external XSLT (very short one), and another with embedded XSLT. Details are in opt:XmlImportOptions examples.