RPM Data Extraction Transform
Screenshots in this article are from RPM 7.0.
The Data Extraction transform does not actually change your print job data. Instead, it scans your data and extracts fields using the directions you give it. It assigns values from your actual print job to the job attributes used to control your outputs.
When the Data Extraction transform runs, your print job should be plain text. Lines and columns should be consistent from job to job.
Setup

The Data Extraction dialog holds a list of rules. Each rule says where to find a value in the job and which job attribute to put it in. The Rules list shows each rule’s Type, the Rule itself (such as “Line 6, Start 75, Count 5”) and its Output Field.
- Add Position… Add a rule that finds the value by line and column.
- Add Regex… Add a rule that finds the value with a regular expression.
- Edit… Change the selected rule.
- Remove Delete the selected rule.
Both Add buttons open the same rule dialog:

- Type
- Position The value is on Line, starting at character Start, and is Count characters long.
- Regex The value is what the regular expression matches. Select Result is count of matches to get the number of matches instead of the text.
- Destination: Variable The job attribute the value goes into, such as <jx> - Job or <T> - Title. To keep a value without overwriting an attribute, choose Capture 1 or Capture 2, then use it in file names (
<c1>,<c2>), program arguments (%1,%2) or banner text (%capture-1%,%capture-2%). - Extract From Print data file (the default) reads the job itself. LPD Control File reads the job’s LPD control file instead, for example
^J(.*)for the job name line. A job received another way, such as AppSocket, has no control file, so the rule finds nothing.
Transforms after Data Extraction, such as a Text Banner, see the values it found.
