Object Filter Conditions

The following conditions can be used to create customized filters.

Where the process has no parent
Where the process is for maintenance
Where the description contains specific keywords
Where the process is on a Process Server
Where the process is in Queue
Where the Remote System name contains specific keywords
Where the Remote Status contains text
Where the process was scheduled to Start less than some time ago
Where the Run Date was less than some time ago
Where the End Date was less than some time ago
Where the process time field is before relative date/time in time zone
Where the process time field is after relative date/time in time zone
Where the process ran/runs in the current 24-hour period starting/ending at time in time zone
Where the process has Status
Where the process is from Process Definition
Where the process is from a Process Definition whose name starts with prefix
Where the process is from a Process Definition whose name contains specific keywords
Where the process is of Definition Type
Where the process belongs to Application
Where the process belongs to Application containing specific keywords
Where the Priority is value
Where the process is scheduled to Start within the last time period or within the next time period
Where the process is scheduled to start after date
Where the process is Owned by user or role
Where the process complies with IntelliSearch search string
Extend filter with user-defined SQL

Note: When parent and descendant processes match a filter, the descendants will be listed multiple times: once for matching the filter, and once more for being a descendant of a process that matches the filter. You use the Where the process has no parent condition to display them only once, as descendants of a process matching the filter.

Relative Dates and Times

The following filter conditions use time expressions.

Where the process time field is before relative date/time in time zone
Where the process time field is after relative date/time in time zone

The time field mentioned in these conditions can be set to any of the following values.

KeepExpiration
LastModificationTime
LastStatusChangeTime
NextSubmitBaseTime
RemoteCreationTime
RemoteRunEnd
RemoteRunStart
RunEnd
RunStart
RuntimeExpiration
ScheduledStartTime

The relative date/time criterion can be either of the following.

A specific time, with an optional positive or negative offset of days. For example, Time: 10:51:32 AM, offset: -, days: 7 queries for occurrences prior to seven days ago at 10:51:32 AM.
A time expression as accepted by Time.expressionNow().

The time zone criterion defaults to the user's time zone and accepts any valid time zone in the list.