Table of Contents


  1. Preface
  2. Introduction to Data Transformation
  3. Data Processor Transformation
  4. Wizard Input and Output Formats
  5. Relational Input and Output
  6. Using the IntelliScript Editor
  7. XMap
  8. Libraries
  9. Schema Object
  10. Command Line Interface
  11. Scripts
  12. Parsers
  13. Script Ports
  14. Document Processors
  15. Formats
  16. Data Holders
  17. Anchors
  18. Transformers
  19. Actions
  20. Serializers
  21. Mappers
  22. Locators, Keys, and Indexing
  23. Streamers
  24. Validators, Notifications, and Failure Handling
  25. Validation Rules
  26. Custom Script Components

Component Types

Component Types

The context of the Script determines the types of components you can add.
For example, anchors must appear nested within Parsers, Mappers, or Serializers. Also, additional input ports and additional output ports can appear only at the global level of the Script.
The following table describes the types of components that you can add to a Script:
Component Type
Takes data from a data holder and performs an operation on it. For example, the
action runs a Parser.
Identifies a section of the input document.
Document processor
Performs a complex transformation on an input document. For example, the
document processor converts a PDF document to plain text.
Defines the format of the documents for a Parser to process.
Isolates a single occurrence of a multiple-occurrence data holder.
Reads XML documents and writes XML documents. Can be set as the startup component.
Writes a message to the standard output or to a log. For example, the
notification indicates that the input document is not valid as against the schema that defines it.
Reads documents in any format and writes documents in any format. Can be set as the startup component.
Script Port
Defines an input or output document.
Reads XML documents and writes documents in any format. Can be set as the startup component.
Breaks large input files into chunks and passes the chunks to a Parser, Mapper, or Serializer. Can be set as the startup component.
Transforms an input string to an output string. Can be set as the startup component.
Determines whether input data conforms to a specific data definition.
Holds data that the Script receives through a service parameter, or holds data from component in the Script.

Updated March 03, 2021