ExportRecords Action
The ExportRecords action is used to export data from a repository. Either all the records in the repository can be exported or records can be selected using a subset. The default workflow extracts all records related to selected records, including records in other repositories.
If only specific relationships are to be extracted, the workflow should be modified to specify the relationship name. The relationships to be extracted must be specified in the workflow as follows:
<Parameter direction="in" name="RelationshipName" type="string" eval="constant">Rel6</Parameter>
If no related records are to be extracted, specify a non-existing relationship as follows:
<Parameter direction="in" name="RelationshipName" type="string" eval="constant">NON_EXISTANT_RELATIONSHIP_X</Parameter>
Any number of relationships can be specified using multiple parameters (RelationshipName1, RelationshipName2, and so on).
You can also control whether the latest (last confirmed or unconfirmed) version is to be exported or only the last confirmed version is to be exported. This is done by specifying VersionOption as follows:
<Parameter direction="in" name="VersionOption" type="string" eval="constant">LATEST</Parameter>
The default is LATEST, that is, the last confirmed or unconfirmed version is exported.
To initiate the export, add a 0-byte file to the directory pointed to by incoming folder of URI in the FileWatcher data set definition.
The output is a zip file containing the following:
- One data export file per repository.
- One relationship file containing record relationship information.
- If related records are extracted, related relationships are also codified in the CONTAINS attribute which can be imported back into the application.
- One index file containing information of the relationship file and the data export files.
