|
|
Parse Structured formThe Steps tab of the Parse Structured form looks and works much like the Steps tab of the Activity form, with three differences described here.
You can use all the methods and instructions accepted by the Activity form. You can use preconditions, transitions, and iterations. See Activity form — Completing the Steps tab.
Parse methods
On the Steps tab of the Parse Structured form, you can use all methods available to activities, plus four parsing methods:
These four methods consume portions of the input string, advancing a cursor.
The input may contain record delimiter or line terminator characters marking the end of each line or record. To position the cursor appropriately for the next record or line, include a step that skips over these characters. SR-3237 B-20098 rejected. Examine the input carefully, as files created on Windows and UNIX platforms may follow different line terminator conventions.
For example, if a Windows TXT file contains useful data in 100 bytes plus the carriage return and line feed characters (\n\r) at the end of each line, the second data segment starts at offset 102, not byte 100. Use Parse-Char-Pos method with an Offset parameter of 2 to discard the two unneeded characters.
Iteration
If creating an iteration in a Parse Structured form, you can select For Each Page, For Each Embedded Page, For Each Element in Value List, and For Each Element in Value Group. These operate identically in a Parse Structured step and an activity step. For details on these three iteration choices, see Activity form — Completing the Steps Page — Iteration.
API
Field |
Description |
| API Version |
Choose |
Activity Type
On the Security tab of the Parse Structured form, set the Activity Type to Activity.
About Parse Structured rules