element <etl:transform>
Namespace:
Type:
Content:
complex, 5 attributes, 5 elements
Defined:
locally within complexType etl:TransformsType in etl.xsd, see XML source
XML Representation Summary
<etl:transform
    externalTaskId
 = 
string
    id
 = 
string
    parentPipelineTaskId
 = 
string
    saveState
 = 
boolean : "false"
    type
 = 
string : "SimpleQueryTransformStep"
    >
   
Content: 
etl:description? × etl:source? × etl:destination? × etl:procedure? × etl:taskref?
</etl:transform>
Content model elements (5):
Included in content model of elements (1):
Definition Locations
XML Source (see within schema source)
<element name="transform" type="etl:TransformType"/>
Attribute Detail
externalTaskId
Type:
string, predefined
Use:
optional
Defined:
locally, within etl:TransformType complexType
The command task (wrapped as a pipeline task) that handles the transform. E.g., 'org.labkey.api.pipeline.cmd.CommandTask:myEngineCommand'
XML Source (see within schema source)
<attribute name="externalTaskId" type="string">
<annotation>
<documentation>
The command task (wrapped as a pipeline task) that handles the transform.
E.g., 'org.labkey.api.pipeline.cmd.CommandTask:myEngineCommand'
</documentation>
</annotation>
</attribute>

id
Type:
string, predefined
Use:
required
Defined:
locally, within etl:TransformType complexType
XML Source (see within schema source)
<attribute name="id" type="string" use="required"/>

parentPipelineTaskId
Type:
string, predefined
Use:
optional
Defined:
locally, within etl:TransformType complexType
If an externalTaskId command task is defined, settings from this pipeline (to date, workflow process key) will be applied to the pipeline wrapping the externalTask E.g., 'org.labkey.api.pipeline.file.FileAnalysisTaskPipeline:myPipelineName'
XML Source (see within schema source)
<attribute name="parentPipelineTaskId" type="string">
<annotation>
<documentation>
If an externalTaskId command task is defined, settings from this pipeline
(to date, workflow process key) will be applied to the pipeline wrapping the externalTask
E.g., 'org.labkey.api.pipeline.file.FileAnalysisTaskPipeline:myPipelineName'
</documentation>
</annotation>
</attribute>

saveState
Type:
boolean, predefined
Use:
optional
Default:
"false"
Defined:
locally, within etl:TransformType complexType
Persist the job state to the database after this step (in addition to at the end of a successfully complete job). Use with extreme caution; if a later step causes an error in the job, this will still be the assumed state for the next run.
XML Source (see within schema source)
<attribute default="false" name="saveState" type="boolean">
<annotation>
<documentation>
Persist the job state to the database after this step (in addition to at the end of a successfully complete job).
Use with extreme caution; if a later step causes an error in the job, this will still be the assumed state for the next run.
</documentation>
</annotation>
</attribute>

type
Type:
string, predefined
Use:
optional
Default:
"SimpleQueryTransformStep"
Defined:
locally, within etl:TransformType complexType
Use 'StoredProcedure' when handling the transform task wtih a stored procedure. Use 'ExternalPipelineTask' (in conjunction with externalTaskId) when handling the transform task with an XML-defined pipeline task. Use 'TaskrefTransformStep' (in conjunction with a taskRef element) to queue another ETL to run.
XML Source (see within schema source)
<attribute default="SimpleQueryTransformStep" name="type" type="string">
<annotation>
<documentation>
Use 'StoredProcedure' when handling the transform task wtih a stored procedure.
Use 'ExternalPipelineTask' (in conjunction with externalTaskId) when handling the transform task with an XML-defined pipeline task.
Use 'TaskrefTransformStep' (in conjunction with a taskRef element) to queue another ETL to run.
</documentation>
</annotation>
</attribute>
Content Element Detail
etl:description
Type:
string, predefined, simple content
Defined:
locally, within etl:TransformType complexType
XML Source (see within schema source)
<element minOccurs="0" name="description" type="string"/>

etl:destination
Type:
etl:TargetObjectType, complex content
Defined:
locally, within etl:TransformType complexType
XML Source (see within schema source)
<element minOccurs="0" name="destination" type="etl:TargetObjectType"/>

etl:procedure
Type:
etl:SchemaProcedureType, complex content
Defined:
locally, within etl:TransformType complexType
XML Source (see within schema source)
<element minOccurs="0" name="procedure" type="etl:SchemaProcedureType"/>

etl:source
Type:
etl:SourceObjectType, complex content
Defined:
locally, within etl:TransformType complexType
XML Source (see within schema source)
<element minOccurs="0" name="source" type="etl:SourceObjectType"/>

etl:taskref
Type:
etl:TaskRefType, complex content
Defined:
locally, within etl:TransformType complexType
XML Source (see within schema source)
<element maxOccurs="1" minOccurs="0" name="taskref" type="etl:TaskRefType"/>

This XML schema documentation has been generated with DocFlex/XML RE 1.7.2 using DocFlex/XML XSDDoc 2.1.0 template set.
DocFlex/XML RE is a reduced edition of DocFlex/XML, which is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually using a high quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML.
DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-end XML Schema documentation generator with simultaneous support of framed multi-file HTML, single-file HTML and RTF output formats. (More formats are planned in the future).
A commercial license for "DocFlex/XML XSDDoc" will allow you:
  • To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support more than 300 template parameters (working the same as "options" of an ordinary doc-gen), which will give you an unprecedented control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To enable/disable documenting of the initial, imported, included and redefined XML schemas selectively.
  • To document local element components both globally and locally (similar to attributes).
  • To enable/disable reproducing of namespace prefixes.
  • To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
  • To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
  • To use PlainDoc.tpl main template to generate all the XML schema documentation in the form of a single HTML file.
  • To use the same template to generate the incredible quality RTF documentation.
  • To document only selected XML schema components specified by name.
  • To remove this very advertisement text
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML SDK and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required!
But this is not all. In addition to it, a commercial license for DocFlex/XML SDK will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only. And, of course, you could develop any template applications by your own!
Please note: By purchasing a license for this software, you not only acquire a useful tool, you will also make an important investment in its future development, the result of which you could enjoy later by yourself. Every single your purchase matters and makes a difference for us!
To buy a license, please follow this link: http://www.filigris.com/shop/