Complete activities that are not being used

Home

Complete activities that are not being used

Overview

Edit configuration property settings to...

Disable the removal of inactive activities from the My Activities view
Change the amount of time an activity must be inactive before it is marked complete by the server
Disable the warning notification that is sent to activity owners before an activity is marked complete

When an activity is marked complete, it moves from the My Activities view to the Completed view. The default interval is 90 days. Before starting this procedure, determine the amount of time that you want to allow an idle activity to remain in the active views before it is marked complete and moved to the Completed view.
To edit configuration files, use the wsadmin client.
If e-mail notifications are enabled, Activities warns the owner of an activity that has not been modified in the specified time frame that the activity will be marked complete. This allows the owner to modify the activity and retain it on the dashboard. You can enable and disable this e-mail notification feature. If you do not want to automatically move activities into the Completed view, you can also disable this job.

Remove an activity that is not being used
Use the wsadmin client to access and check out the Activities configuration files.
Access the Activities configuration file:

Stand-alone deployment:
execfile("activitiesAdmin.py")

Network deployment:
execfile("profile_root/config/bin_lc_admin/activitiesAdmin.py")

If prompted to specify which server to connect to, type 1.
The information about which server to connect to is only used by the wsadmin client when you are running administrative commands to collect statistics.
Check out the Activities configuration files...
ActivitiesConfigService.checkOutConfig("<working_directory>", "cell_name")

where:
<working_directory> is the temporary working directory to which the configuration XML and XSD files are copied and are stored while you make changes to them. Use forward slashes to separate directories in the file path, even if you are using the Microsoft Windows operating system.
cell_name is the name of the WebSphere Application Server cell hosting the Lotus Connections feature. This argument is required even in stand-alone deployments. This argument is also case-sensitive, so type it with care. If you do not know the cell name, do one of the following to determine it:
Stand-alone deployment: From the file system...
WAS_HOME\profiles\profile_name\config\cells\
Network deployment: Type the following command while in the wsadmin command processor:
print AdminControl.getCell() 
For example:

AIX/Linux:
ActivitiesConfigService.checkOutConfig("/opt/act/temp","foo01Cell01")

Microsoft Windows:
ActivitiesConfigService.checkOutConfig("c:/act/temp","foo01Cell01")
Display the current configuration settings...
ActivitiesConfigService.showConfig()

From the returned list, look at the current values of the settings that begin with jobs.AutoComplete. and determine which property values you want to change:

jobs.AutoComplete.scheduler

Defines the Quartz scheduler that this job is associated with. The default value is cluster. Specify one of the following options:

cluster: Runs the job on any available server. This setting can be used even when Activities is installed on a single (non-clustered) server. Select this option in most cases because auto completion is a taxing job and this option enables Quartz to select a server that can handle it. This option runs the job on just one server, which is sufficient because all of the servers access the same database. This option is the default.
local: Runs the job on all servers. Choosing the local scheduler in a network deployment environment forces the job to run multiple times because the job runs on each server. Multiple runs are not necessary because all of the servers access the same database.
disabled: Prevents the job from running by preventing it from being loaded to the scheduler.
cell_name\<node_name>\server_name: Specifies a specific server that you want the scheduler to run on. For example: Cell01\Node01\server1. When you use an administrative command to run the scheduler for this job, specify "local" as the value of the schedulerName parameter.

jobs.AutoComplete.autoCompletionPeriod

Defines the number of days of inactivity that must pass before an activity is automatically marked complete. Specify the value in days. The default value is 90.

jobs.AutoComplete.prenotification

Defines whether or not to send an e-mail to the activity owners to warn them that the activity will be marked complete if no modifications are made to it. This Boolean value accepts either true or false. The default value is true. This setting requires that e-mail notifications are enabled.

To change the property values...
ActivitiesConfigService.updateConfig(<property>, <value>)

For example:
ActivitiesConfigService.updateConfig("jobs.AutoComplete.scheduler", "local") ActivitiesConfigService.updateConfig("jobs.AutoComplete.autoCompletionPeriod", "100") ActivitiesConfigService.updateConfig("jobs.AutoComplete.prenotification", "false")

Optional: If you decide to notify activity owners, you can change the number of days warning they are given by changing the interval at which the job runs. If the job is scheduled to run once a month, the owners get a month's notice that their activity will be marked complete. If it runs weekly, they get a week's notice.
To change the interval of the job, edit the value of the jobs.AutoComplete.trigger.cronExpression property. The default value is 0 0 23 ? * SAT, which specifies that the job should run weekly at 11 PM on Saturday. For information about how to format this value, go to the following external Web site: http://www.opensymphony.com/quartz/api/org/quartz/CronTrigger.html. Use the following command to edit this property:
ActivitiesConfigService.updateConfig("jobs.AutoComplete.trigger. cronExpression", <value>)

where <value> is a time interval written in the Quartz Enterprise Job Scheduler API CronExpression class format. For example: "0 30 4 ? * SAT"
After making changes, check the configuration files back in and do so during the same wsadmin session in which you checked them out for the changes to take effect. See Applying property changes for details.
Example
When making configuration changes to the ActivityAutoCompleteJob scheduled job, you are modifying settings in the oa-jobs.xml file. The XML sample below of oa-jobs.xml file content defines a job that runs weekly (Saturdays at 11 PM) and markscomplete any activities on the cluster server that have not been modified in 100 days. Because prenotification is set to true, an e-mail will be sent to all Activities owners who have Activities that have been inactive for 83 days, warning them that the next time this job runs, their activities will have been inactive for at least 90 days and will be marked complete, unless they make a modification to the activity.
<job>
  <job-detail>
    <name>ActivityAutoCompleteJob</name> 
    <group>OpenActivities</group> 
    <description>Automatically mark unmodified activities as 
     completed</description> 
    <job-class>com.ibm.openactivities.jobs.AutoCompleteJob</job-class> 
    <job-data-map allows-transient-data="true">
      <entry>
        <key>AssignToScheduler</key> 
        <value>cluster</value> 
      </entry>
      <entry>
         
        <key>autoCompletionPeriod</key> 
        <value>100</value> 
      </entry>
      <entry>
         
        <key>prenotification</key> 
        <value>true</value> 
      </entry>
    </job-data-map>
  </job-detail>
  <trigger>
    <cron>
      <name>Autocompletion Trigger</name> 
      <group>OpenActivities</group> 
      <job-name>AutoCompleteJob</job-name> 
      <job-group>OpenActivities</job-group> 
       
      <cron-expression>0 0 23 ? * SAT</cron-expression> 
    </cron>
  </trigger>
</job>
Related tasks
Manage trash
Choosing a scheduler for a job
Checking out the Activities configuration files
Apply property changes
Activity statistics

+
Search Tips | Advanced Search