A merge tool evaluates the ModuleAdminExecuteSequence table and then inserts the calculated actions into the AdminExecuteSequence table with a correct sequence number.
The ModuleAdminExecuteSequence table has the following columns.
If a standard action is used in the Action column of a merge module sequence table, the BaseAction and After columns of that record must be Null.
The sequence number of a standard action. If a custom action or dialog is entered into the Action column of this row, this field must be set to Null.
When using standard actions in merge module sequence tables, the value in the Sequence column should be the recommended action sequence number. If the sequence number in the merge module differs from that for the same action in the .msi file sequence table, the merge tool uses the sequence number from the .msi file. See the suggested sequences in Using a Sequence Table for the recommended sequence numbers of standard actions.
The BaseAction column can contain a standard action, a custom action specified in the merge module's custom action table, or a dialog specified in the module's dialog table. The BaseAction column is a key into the Action column of this table. It cannot be a foreign key into another merge table or table in the .msi file. This means that every standard action, custom action, or dialog listed in the BaseAction column must also be listed in the Action column of another record in this table.
Boolean for whether Action comes before or after BaseAction.
Value Meaning 0 Action to come before BaseAction 1 Action to come after BaseAction
A conditional statement that indicates if the action is be executed. Null evaluates to true.
If this table is present the AdminExecuteSequence table must also be present in the merge module.
Build date: 11/16/2013