Table of Contents

Search

  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

RunParser

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.


Updated February 12, 2020