Preface
Introduction to Data Transformation
- Data Transformation Overview
- Data Transformation Process Architecture
- Data Transformation Components
Data Processor Transformation
- Data Processor Transformation Overview
- Data Processor Transformation Views
- Data Processor Transformation Ports
- Startup Component
- References
- Data Processor Transformation Settings
- Events
  - Event Types
  - Data Processor Events View
- Logs
- Data Processor Transformation Development
- Data Processor Transformation Export and Import
- Data Processor Transformation Validation
  - Using a Speed-enhanced Data Transformation Engine for VRL Validations
- Data Processor Transformation in a Non-native Environment
Wizard Input and Output Formats
- Wizard Input and Output Formats Overview
- COBOL Processing Library
- JSON
- XML
  - Creating a Transformation that Transforms XML
Relational Input and Output
- Relational Input and Output Overview
- Relational Input
- Relational Output
Using the IntelliScript Editor
- IntelliScript Editor Overview
  - Creating a Script
- Opening an IntelliScript Editor
- Editing Procedures
- IntelliScript Editor Menus
XMap
- XMap Overview
- XMap Schemas
- Mapping Statements
- XPath Expressions
- XMap Variables
  - Creating a Variable in the XMap Editor
- XMap Example
Libraries
- Libraries Overview
- Library Structure
- Element Properties
- Library Management
- Edit Libraries with the Library Editor
- Edit Libraries with the IntelliScript Editor
Schema Object
- Schema Object Overview
- Schema Files
- Schema Object Overview View
- Schema Object Schema View
- Schema Object Advanced View
- Creating a Schema Object
- Schema Updates
  - Schema Synchronization
  - Schema File Edits
    - Setting a Default Schema File Editor
    - Editing a Schema File
Command Line Interface
- Command Line Interface Overview
- CM_console
Scripts
- Scripts Overview
- Script Components
- Script Component Properties
- Script Startup Components
  - Setting the Startup Component with the IntelliScript Editor
- Example Sources
- IntelliScript Editor
- Validate a Script
- Sample Scripts
  - Importing a Sample Script
Parsers
- Parsers Overview
- Platform-Independent Parsers
  - Newline Markers
  - File Paths
- Parser Component Reference
  - Parser
Script Ports
- Script Ports Overview
- Script Port Component Reference
Document Processors
- Document Processors Overview
- Defining a Document Processor
  - Display of Document Processor Output
- Document Processor Component Reference
- TextML XML Schema
- PdfToTxt_4 Table Configuration Editor
  - Editor Options
  - PDF Conversion Example
    - Configuring the First Table
    - Configuring the Second Table
Formats
- Formats Overview
- Standard Format Properties
- Format Component Reference
- Delimiters Component Reference
- Format Preprocessor Component Reference
  - HtmlProcessor
  - RtfProcessor
Data Holders
- Data Holders Overview
- XML Schemas
- Using a Schema to Map Anchors
- Generating Valid XML
  - Role of Schemas in Parsing
  - Role of Schemas in Serialization and Mapping
- Variables
- Variable Component Reference
  - Variable
- Multiple-Occurrence Data Holders
Anchors
- Anchors Overview
- Mapping Content Anchors to Data Holders
- Defining Anchors
- Standard Anchor Properties
- How a Parser Searches for Anchors
- Anchor Component Reference
- Searcher Component Reference
- Anchor Subcomponent Reference
Transformers
- Transformers Overview
- Defining Transformers
- Standard Transformer Properties
- Transformer Component Reference
Actions
- Actions Overview
- Standard Action Properties
- Action Component Reference
- Action Subcomponent Reference
Serializers
- Serializers Overview
- Serialization Anchors
  - Example of Serialization Anchors
  - Sequence of Serialization Anchors
- Standard Serializer Properties
- Serializer Component Reference
  - Serializer
- Serialization Anchor Component Reference
Mappers
- Creating a Mapper
- Components Nested within a Mapper
- Mapper Example
- Standard Mapper Properties
- Mapper Component Reference
  - Mapper
- Mapper Anchor Component Reference
Locators, Keys, and Indexing
- Overview of Locators, Keys, and Indexing
- Example of Locators
- Example of Indexing by Key
- Source and Target Properties
  - Source Property
  - Target Property
- Standard Locator and Key Properties
- Locator and Key Component Reference
Streamers
- Streamers Overview
- Text Streamers
- XML Streamers
- Standard Streamer Properties
- Streamer Component Reference
- Streamer Subcomponent Reference
Validators, Notifications, and Failure Handling
- Overview of Validators, Notifiers, and Failure Handling
- Failure Handling
  - Using the Optional Property to Handle Failures
  - Writing a Failure Message to the User Log
    - Configuring User Log Output
    - Viewing the User Log
- Validators
- Standard Validator Properties
- Validator Component Reference
- Notifications
- Notification Component Reference
Validation Rules
- Validation Rules Overview
- Validation Rules Element Reference
- Edit the Validation Rules in an External Editor
- Create a Validation Rules Object
- Import a Data Transformation Service with Validation Rules
Custom Script Components
- Custom Script Components Overview
- Custom Component Example
- Custom Component Properties
- Developing a Custom Component
  - Java Interface Example
  - Sample Custom Java Components
- Configuring a Custom Component
  - Sample Scripts Containing Custom Components

User Guide

10.5
- 10.5.6
- 10.5.2
- 10.4.0

Back Next

RunParser

The

RunParser

action runs a secondary Parser. The output of

RunParser

is appended to the output of the main component that activated it, such as a Parser or serializer.

Use the

RunParser

action to follow the links in an HTML file and run a secondary Parser on the link destinations. In a serializer, you can use it to parse bits of unstructured data in the input.

Note the following difference between the

RunParser

action and the

EmbeddedParser

anchor:

RunParser

parses a new source.

EmbeddedParser

parses a section of an existing source.

The following table describes the properties of the

RunParser

action:

Property	Description
disabled	Determines whether the Script ignores the component and all of the child components. Use this property to test, debug, and modify a Script. You can choose one of the following options: Selected. The Script ignores the component. Cleared. The Script applies the component. The default is cleared.
exclude_strings	Defines the strings that must be absent from the input_source . If a specified string is present, the RunParser action does not access the source or activate the secondary Parser.
include_strings	Defines the strings that must be present in the input_source value. If a specified string is missing, the RunParser action does not access the source or activate the secondary Parser.
input_source	Defines a data holder that contains one of the following objects: If input_source_as_text is selected, input_source contains a string. If input_source_as_text is cleared, input_source contains the path and file name of the input document. Default is the `VarLinkURL` system variable.
input_source_as_text	Determines the type of data in the input_source data holder. Selected. input_source contains a text string. Cleared. input_source contains a file path. Default is cleared.
name	A descriptive label for the component. This label appears in the log file and the Events view. Use the name property to identify the component that caused the event.
next_Parser	Defines the name of the Parser to run. A recursive call to the same Parser is permitted.
on_fail	The action to take if the component fails. You can choose one of the following options: Cleared. Take no action. CustomLog. Write to the user log. LogError. Write an error message to the engine log. LogInfo. Write an information message to the engine log. LogWarning. Write a warning message to the engine log. NotifyFailure. Send a notification. Default is cleared. For more information about handling component failures, see Failure Handling.
optional	Determines whether a component failure causes the parent component to fail. You can choose one of the following options: Selected. Component failure does not cause the parent component to fail. Cleared. Component failure causes the parent component to fail. Default is cleared. For more information about component failure, see Failure Handling.
phase	Determines when the Script processes the component. You can choose one of the following options: initial. The Script processes the component during the initial phase. main. The Script processes the component during the main phase. final. The Script processes the component during the final phase. For more information, see How a Parser Searches for Anchors. Default is main.
pre_processor	Defines a document processor to apply to the source after the document processor defined in the associated AdditionalInputPort pre_processor .
remark	A user-defined comment that describes the purpose or action of the component.
retries	Defines the number of times to retry if the request fails. Default is 0.
seconds_to_wait	Defines the interval in seconds between retries. Default is 60.

Rename Saved Search

Table of Contents

User Guide

User Guide

RunParser

RunParser