Enhanced OQL filtering: the STARTED alias

OQL filtering capabilities are enhanced with the introduction of the new STARTED alias for jobs and job streams.

This feature significantly simplifies query writing and improves readability. It streamlines your filtering process by enabling a simple, case-insensitive keyword to replace more complex OQL filter logic.

The STARTED alias enables you to directly filter objects based on whether they have an actual start value, that is, whether they have started running.

For example, when monitoring jobs in the Orchestration Monitor, you can now use a query as simple as STARTED = true to find all jobs that have started. Additionally, you can create more refined queries by combining the alias with other OQL syntax keywords and fields for more in-depth filtering:
name LIKE '@job1' AND jobOptions.critical = true AND started = false
This provides a more intuitive way to check the run status of objects in the plan. For more information, see Using Orchestration Query Language