Creating and Editing Startup Rules

When creating or editing a startup rule, you must specify the following options:

• Version of the application that triggers the action. This is always the version of the application. Use the “short format” of the application version, not the full “product version.”

  For example, to create an operation that is triggered by InterAction 6.3, you would enter “6.30,” not “6.00.30.”

• Applications to which the operation applies:
  • Database Maintenance/Other Script Runner
  • Document Repository Server
  • Folder Dependency Analyzer
  • InterAction Active Directory Sync
  • InterAction Administrator
  • InterAction Application Collaboration
  • InterAction Data Value Tool Kit
  • InterAction Windows Client
  • Microsoft® Outlook® to InterAction Sync
  • Private Folder Converter (Used for legacy upgrade process only)
  • Project Folder Converter (Used for legacy upgrade process only)
  • Project Search Optimizer
  • Report Transfer Utility

  • User to Firm Contact Sync

    The same operation should apply to all components.

• Operation that should take place. If you select Display a Message or Exit the Program, you also must provide the message to display. If you select Execute a Program, you provide the command line.

You cannot create an Exit the Program operation for the current version of InterAction Administrator. If you could, you would effectively lock yourself out of Administrator!

If you select Execute a Program, you can launch any program or file that can be launched from a command line. You can use this to launch both actual applications (EXE files), HTTP files, or any other file that you can run from a command line.

If you select Single-User Mode, you are locking out all users from the selected applications. See “Locking Users Out of InterAction with Single-User Mode” on page 269.

Creating a New Version-specific Startup Operation

Create a Startup Rule

1. On the main window of InterAction Administrator, double-click Startup Rules.
2. Choose New.
3. Choose the version of the application that should trigger the action from the drop-down menu.
4. Select the applications that should trigger the action.
5. Select the Operation you want to take place.
6. Enter the Message to display or the Program Filename, Start In this folder, and Command Line Parameters fields for the program to run.
7. Choose OK.

8. Define the order for all the operations in the list.

   For details, see the procedure below.

9. If desired, test all of the defined operations.

   This is especially useful for checking the order of multiple items.

Change the Order of the Startup Rules

1. On the main window of InterAction Administrator, double-click Startup Rules.
2. Choose Order.
3. Select an operation and choose either Up or Down to change the order.
4. When you finish changing the order, choose OK.
5. When you finish editing the startup rules, choose OK.

Edit a Startup Rule

1. On the main window of InterAction Administrator, double-click Startup Rules.
2. Select the operation to edit and choose Edit.
3. Edit the fields as needed, then choose OK.

Test the Startup Rules

Testing the operations tests all of the items entered for the InterAction database and a selected application and version. This is useful for making sure that the defined order for multiple operations is correct.

1. On the main window of InterAction Administrator, double-click Startup Rules.

2. Choose Test.

   InterAction displays the Test Startup Rules dialog box.

   

3. Select the Application and Version to test.
4. Choose Test. InterAction Administrator displays a message for each operation defined for the selected version and application in the defined order.
   • For message operations, the actual message displays.
   • For program execution operations, a message displaying the name of the program to run displays.
   • For exit operations, the message you defined displays first, followed by another message stating that the application will exit.