Behavior

Field	Description
Disabled dependency	Specifies the action (Error /Skip) to be taken for a disabled Dependency.
Disabled process/task	Specifies the action (Error /Skip)to be taken for a disabled Process/Task.
On set process abnormal	Indicates whether to enable a process to finish all items before reaching an abnormal status. These are the valid options: Option Description ABORT This is the default option. When this option is selected, any item marking the parent process as abnormal will cause the parent process to abort. Any active items in the process will complete but no scheduled items will run. CONTINUE With this option, any item marking the parent process as abnormal will cause the parent process to go abnormal but the process will continue to run as normal. Active items in the process will continue to run and scheduled items will continue to run. This option is only relevant when Fail parent process on error, or Mark parent process abnormal on error has been selected in a process item.
Maintenance offset	The offset from the start of the production day at which the Scheduler will begin to perform maintenance (that is clean up expired logs and run history).
Disable maintenance	Determines whether to disable maintenance. If this option is selected, then maintenance (that is clean up expired logs and run history) must be done manually.
Reset tokens on rerun	Determines whether to reset the tokens on rerun. If this option is selected, all attribute values are restored to their original value. This means that if there are any variable tokens in the attributes, they will be resolved once again.
Display audit info on login	Determines whether to display the last login and operation details in the Web Client on login.
Disable client auto connect	Applicable only for Windows Client. Determines whether to disable client auto connect. If disabled, the Windows client will not automatically try to reconnect if it loses connection to the Scheduler. If connection is lost (and the Scheduler is the currently viewed Scheduler), you will be prompted with a dialog box asking if you want the client to try and reconnect to the Scheduler.
Legacy process folder support for web client	In the web client, process folder filtering happens at the database server whereas filtering in the windows client is performed within the application. If regular expressions are used in the name and alias fields of the folder filter, they will not work in the web client. If the Legacy process folder support option is checked, the web client will use the process folders created from the windows client although they may not work correctly. Otherwise, existing folders will not show up in the web client and will need to be re-defined. With legacy support turned on, we will remove any asterisks from the name or alias filter strings to provide some backwards compatibility.
Max Active Days for Process	In test environments, processes are sometimes not actively managed and if they don’t complete, will roll forward to the next day, eventually cluttering the schedule. The Max Active Days for Process determines how many days to allow a process to be active before automatically cancelling it. If the value is one, processes from yesterday are ok but processes from the day before yesterday will be canceled with a log message indicating why. Keeping the value at 0 has no effect.
Max Open Days for Alert	In test environments, alerts often don’t get managed on a regular basis and thousands of alerts left open can cause performance problems. The Max Open Days for Alert determines how long, in days, an alert can remain in an open status before being automatically closed. When closed, a comment is added indicating the alert has expired. Setting the value to 1 would not affect yesterday's alerts, but would close alerts from the previous day. Keeping the value at 0 has no affect.
Item-level Security	This option enforces operational security based on the task folder.   By default, operational security for process item tasks is based on the root process folder. With this option selected, a user with access to the process folder, but not to the folder of a contained task, will not be able to perform any operations on that task.