When using a Parse Structured rule to extract property values from more than one record, use care to ensure that the cursor position is reset at the end of each input record. If a delimiter appears as the last character or characters in one record, it must be processed (or skipped over) so the cursor is in the starting position for the next record.

Type the keyword $ANY as the Record Type to match records that don't correspond to any other record type value.

For example, assume the input files contain a mix of records with three different layouts — header, detail, and summary — indicated by a single character H, D, or S in byte 1 of each record. If your application needs to process all three types, create three rows in this array with H, D, and S in the Record Type . Records of each type must have a common length. On the Methods tab, enter 0 (zero) for the Record Type Offset position and 1 for the Record Type Length .

On the Methods tab, indicate the length and byte offset position of the record type within the record.

This option is useful for files that contain one header record followed by one or more detail records, such as in a Microsoft Excel CSV file. Select Once? in the first row to process the header rule. Leave this check box cleared in a second row, to process remaining records.

• Clipboard
• XML ParseRule
• Delimited ParseRule
• Structured ParseRule
• Skip — Do not process this segment

Or enter the name of a function in the Pega-IntSvcs:MapTo library.

Clipboard

Enter a property name from the primary page (after a leading period). Use the form Param.name parameter name to set a parameter value on the parameter page of the activity in the Activity field.

XML Parse Rule

Enter the Namespace name (second key) and the Element Name name (third key) of the appropriate Parse XML rule. Separate the Namespace from the Element name with a space. That is, use the syntax "NamespaceName ElementName" and not "NamespaceName.ElementName." The system uses the page class of this service rule as the first key part of the parse rule.

Note: To maintain backward compatibility for service rules created in releases before PRPC Version 5.2, you can specify a data mapping with only a Namespace value. In that case, the system determines the Element Name key at runtime from the root element of the incoming XML document. However, this mapping works only if the Parser Type of the Parse XML rule is set to DOM and validation is not enabled. As a best practice, specify both the Namespace Name and the Element Name of the rule.

Delimited ParseRule

Enter the second and third key parts of a Parse-Delimited rule, separated by a period ( Namespace and Record Type ). The system uses the Page Class you entered on the Service tab as the first key part.

Structured ParseRule

Enter the second key part of a Parse Structured rule ( Record Type ). The system uses the Page Class you entered on the Service tab as the first key part.

Rule-Utility-Function from a MapTo library

Either select a property to hold the results of the function or leave this field blank, as appropriate for the function.

The system uses values of two parameters pyServiceUser and pyServicePassword on the parameter page as authentication credentials for a requestor.

These two parameters can be set in service file processing by earlier rows in this tab can set these values.

Clear to cause the primary page to be reinitialized to empty after processing of this row completes.

If this field is blank, no automatic commit operations are performed.

This field supports the Global Resource Settings syntax (=.PageName.PropertyName). The default property name for this field is pyCommitFrequency. For more information, see Using the Global Resource Settings feature.

The system records in instances of the Log-Service-File class the current processing status of each file, and can retry from that point. Checkpointing can work in conjunction with the Attempt Recovery fields on the File Listener form, to allow recovery from a temporary input/output failure.