Your Command Control database can be protected through the use of the Transactions feature, which automatically locks the database when you start making changes and prevents other Framework users from making any changes. You must then commit the transaction to save the changes and release the lock, and you are prompted by customized questions to provide information that can be viewed in the Compliance Auditor. You can cancel the transaction at any time.
To use this feature, you must first enable it and create a customized Commit Transactions page, then you can use the feature and commit the changes you have made.
You can configure the Command Control Manager to require the Transactions feature to be used when configuring Command Control rules.
You can also configure your own Commit Transaction page to be used for committing a transaction. The data entered on the Commit Transaction page can be viewed in the Compliance Auditor.
To configure this feature:
Click on the home page of the console.
Click in the task pane.
Select the check box to enable the use of Command Control transactions.
Click .
Specify a name for the field you want to display when a user commits a transaction. For example, you might want to request the user’s name, so you could specify . A blank field called appears on the screen when a user commits a transaction.
Select if you want the user to enter one line of text, or select if you want the user to be able to enter several lines of text.
Select if you want to force the user to enter text in this field. The button on the page does not become available until the user has entered text in this field.
Repeat Step 4 through Step 7 for any other fields you want to display when the user commits the transaction.
Select .
Click on the home page of the console.
Make the configuration changes you want.
A message appear next to in the navigation pane to indicate that the Command Control database is locked, by whom, and when it was locked.
Click in the navigation pane, then click . Complete the fields as set up on the Transaction Settings page, then click .
Alternatively, if you do not want to keep the changes you have made, select in the task pane and select to confirm. Any changes you have made since the database was locked are removed.
When you have finished changing your Command Control database, you must commit your transaction to save the changes and release the lock on the database. The Commit Transaction page can be customized to request whatever information you require when a transaction is committed (see Enabling Transactions and Configuring Settings for details).
To commit a transaction:
Click on the home page of the console.
Click in the task pane.
To create a backup of the Command Control database before the pending changes are written to the database, enable the Create backup option, then specify a reason for the backup in the text box.
Complete the customized fields according to company policies.
Click .