TransactionDelete

The TransactionDelete event notifies the client after a transaction was deleted from the transaction stack (the list of all transactions that can be undone or redone). Only _Post is available.
Transactions are deleted when the stack exceeds its maximum size (the oldest transactions are removed and can no longer be undone), when a new transaction is committed after other transactions were undone (the undone transactions can no longer be redone), and when a document is closed (the whole stack is cleared).

EventNames:

• TransactionDelete_Post

Remarks:

The transaction stack contains a list of all transactions that can be undone or redone. Transactions are deleted as the result of three things. First, the transaction stack has a fixed number of transactions it can hold, (which is defined in the registry). When the number of transactions goes over this limit, the transactions at the bottom of the stack are deleted. This means they can no longer be undone. The second reason a transaction is deleted is when a transaction is undone and then another transaction is committed. All transactions in the undone state are deleted and can’t be redone. The third reason is as a result of a document being closed. Whenever a document is closed the entire transaction stack is cleared. All transactions in the stack will be deleted.

Examples:

TransactionDelete_Post:

Register-InventorEvent -EventName TransactionDelete_Post -Action 'PostTransactionDelete'

function PostTransactionDelete() {
	#Write event code here
}