Loading Action Scripts From a Transaction Log

You can load an Action Script from the transactions that are returned by a transaction log query. Action scripts created from the transaction log are often used to automate changes made manually in one version to another version.

To load an action script from a transaction log:

1. On the Home page, select Script.
2. From Source Type select Transaction Log.
3. On the Source tab, do the following:

   • Select the source version, hierarchies, and nodes.

   • Select whether to return system transactions, data transactions, or both.

     Note:

     If you select Data Transactions, you can select a version, hierarchies and nodes.

4. On the Filters tab, select from these options:

   • Levels — Click to specify action levels to filter:

     • Core –– Includes actions that indicate a change to version data (not metadata objects).

     • Logged –– Includes actions that indicate system activity occurred but did not result in additions, changes, or updates to data.

     • Loss –– Includes transaction history records that store data that has been lost due to a core action, such as deleting a node.

     • Result –– Includes actions that are associated with, and are a result of, a Core action.

     • Admin –– Includes actions that affect metadata objects (not version related data).

   • Actions — Click to specify transaction log action types to filter.

   • Properties — Click to specify a list of properties to filter.

   • Users — Click to specify users to filter.

   • Include Child Nodes — Select to include child nodes for nodes returned by the query.

   • Include Shared Nodes — Select to include shared nodes for nodes returned by the query.

   • From Date — Select and enter a start date.

   • To Date –– Select and enter an end date.

   • Filter to Current Session — Select to filter transactions to those performed during the current session.

   • From Transaction — Select and enter a start transaction ID.

   • To Transaction –– Select and enter an end transaction ID.

   • Max Records — Enter a value to limit the number of transactions displayed.

5. Click Load.
6. When the load completes, review the script actions and parameter values. You can:

   • Click to modify a row.

   • Select Script, then Substitute Versions to change a version. Select the version to be replaced and the version to replace it with and click OK.

   • Click a column header to sort rows alphabetically.

   • Click to filter one or more columns.

   • Click to switch between displaying properties by label or by name.

7. Select the check box in the Process column next to each row to run.

   Note:

   From the Script menu, use Select All to process all actions. You can select a subset of actions from a script and only process those actions.

8. Click to run the Action Script.

   The results of each script action are displayed in the Status and Result Value columns. The script and the results can be saved to a file using the Download option on the Script menu.