Deactivating projects and requests in bulk

Deactivate projects and requests in bulk to quickly remove unnecessary objects from the user interface. This procedure reduces clutter and churn when users search for projects and requests. You can always reactivate projects if you change your mind.

About this task

Note: You can also deactivate up to 1000 projects at one time from the project list pages.


  1. Go to Settings>Administration Settings>Deactivation Administration>Deactivate Projects and Requests.
  2. Set up a query to find the subset of projects and requests you want to deactivate.
  3. After you set up the query, click Deactivate Projects and Requests to schedule the deactivation.
  4. Required: Enter a unique, descriptive name to reuse this query.

    The query name identifies the search so you can reuse it. The log file also draws part of its name from the query name.

    The window lists the number of projects that currently meet the search criteria. Unica Plan runs the query again when deactivation is scheduled and deactivates the projects that fit the criteria then.

  5. Schedule the deactivation.
    This feature uses the Unica Platform scheduler. For more information about the scheduler, see the Unica Platform documentation.
    1. Enter or verify the name of the schedule so you can use it again.
    2. Select when to start running the deactivation from the list.
      Note: A bulk deactivation process might require many minutes and use many system resources. Consider scheduling bulk operations for an off-peak time of day.
      • Now. If you choose this option, the deactivation goes into the queue immediately.
      • On a date and time. Specify when you want the deactivation to start.
      • On a trigger
      • On a trigger after a date
      • On completiton of other tasks
    3. Select when to stop running the deactivation from the following options.
      • Only run once
      • Stop after X occurences. Set the deactivation to run a specified number of times.
      • Stop by date and time. Set the deactivation to run until a specified date and time.
  6. Optional: You can also set up triggers to run on successful completion of the deactivation or on error.
  7. Click Run with this schedule.
    After you set up the deactivation, you view the schedule definitions so you can see your deactivation in the schedule.


When the deactivation completes, you receive an alert. If an error occurs, you also receive an alert. If you configured email notifications, you receive an email in addition to an alert. The alert contains the file path to the log for further details or troubleshooting.

The path to the log file is <Plan_home>\logs\bulkdeactivationreactivation. The log name is formatted bulkDeactivationReactivation-<search_name>.log, where "search name" is the name you entered in step 4. The log file lists projects and requests that were deactivated. For troubleshooting, the log also lists the names of any projects or requests that could not be deactivated categorized by the reason for the error.

After you deactivate projects and requests, you see them in the user interface only if you use predefined searches for Deactivated projects and requests. To see the deactivated projects, use the Deactivated Projects, Deactivated Requests, and Deactivated Projects and Requests searches. You can refine these predefined searches for more specific results.