ManageRecordCollection Activity

The ManageRecordCollection activity allows generation and manipulation of a record collection (“set” of records) for the records associated with an event.

This activity contains two modes:

  • If the setRecordListReadOnly function is passed as true:
It will take the input record list and set it to read-only. Setting a record list to read only will add all of the child records to the record list and will not allow any changes to the record list. This conversion is to be used to generate a snapshot of records and hierarchies so that any report on the record list can include the child records. It does not affect how record collections are manipulated in workflow.
  • If the setRecordListReadOnly is false:
The activity will read the record information from the document/event and create an output RecordList object.

When record collections (RecordList object) are manipulated in workflow, each record in the record collection is considered the root of the record hierarchies and allows processing of the hierarchies.

The ManageRecordCollection activity also allows you to separate records for one repository from all the records associated with the event/Indocument. If more than one repository is associated with the workflow, the repository name is required to identify the root repository. The root repository defines the scope of all relationships included in the record hierarchies and is used to validate the relationships supplied for bundling.

If bundlingOption = true, this activity allows you to identify records which should be the root of the hierarchies. Bundling is often required when records need to be grouped together along with relationships and processed as a unit. The activity reviews all records associated with the event/inDocument and identifies the ones which should be the root of the hierarchies. Such records are included in the record collection. The records which are not included in the record collection but are part of the record hierarchies are called “implicitly” included records. The activity does not allow one record to be included in more than one hierarchy. Such records are identified and output as another record collection in the OutRecordList2.