Merge/Unsplit objects

CAST provides two manual mechanisms that can be used to group objects together. They are similar, but different:

Merging objects

The process of merging Data Functions and merging Transactional Functions is identical.

Note that the split is not permanent until you Save the changes to the server (see the Toolbar for more information about this).

How are Function Point, DET, FTR and RET values calculated when multiple transactions or data functions are merged?

When you merge multiple transactions or data functions you will be requested to choose a "root" item (as explained above). The values of the root item will be used to represent the block of transactions or data functions in the GUI immediately after you have completed the merge. However, to ensure that the "correct" values (i.e. the "sum value" of all merged items) are taken into account going forward, you will need to use the Compute action (note that the "sum value" is not exactly equal to the sum of all items in all cases since some columns/tables could be identical and will therefore count as 1).

Unsplit Transactional Functions

The Unsplit mechanism is only available for Transactional Functions, not Data Functions. It enables you to effectively reverse a split. All objects added during the split action are removed from the results and the split Transactional Function returns to its normal state - i.e. it encompasses all its sub-objects and called objects.

Transactional Function and Data Function recovery when their root object disappears

When merging Transactional Functions or Data Functions, one of the Transactional Functions / Data Functions is set as the root item of the group. The root represents the group of merged items. If the entry point / main table of the root is no longer available, the associated root Transactional Function / Data Function will also no longer be available and will be dropped.

In this case, when the root group includes more than one item (excluding the root), then the group of merged items will remain but the root item will be replaced by the first available item in the list of items.

If the root group includes only one item, then the merged item becomes a single Transactional Function / Data Function.

As a consequence of this, the previous root item will be marked as deleted and the new root item representing the merged items will be marked as added after a snapshot is generated.

If the entry point / main table of the root item that was previously missing is then recovered, then the Transactional Function / Data Function which was associated to this will be recovered as the same object as before. However, it won't automatically become the root item of the merged items - this is because the merging information is lost. If the merge operation was achieved through a custom procedure, this merge may return to its initial state, otherwise if the merge was done manually, it has to be redone manually to get back to its initial state.

CAST Website