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

Defining a Global Component

Defining a Global Component

You can insert components in either a global or local scope.
Global scope
The component is defined at the top level of the IntelliScript. It can be accessed or used at any location in the project.
Local scope
The component is defined at a nested level of the IntelliScript. It can be accessed or used only at the particular nested location.
Data Transformation
components can be either global or local.
For example, anchors are usually defined locally. You might define an anchor as a global component, however, if you want to use the same anchor configuration in several parsers or several times in the same parser. In each desired location, you can reference the globally-defined anchor by its identifier.
A parser can then use
, instead of repeating the configuration of the marker anchor every time it is needed. You can select
from the component list at the appropriate location within the parser, or you can drag
to the location.

Updated March 18, 2021