Jobs List

The Jobs List is a centralized repository displaying all master jobs related to the application's platform activities, including crawling, profiling, data quality checks, and more. It provides an overview of jobs, including key details such as Job Master ID, Job Name, Execution Count, Execution Scope, Class Name, Method Name, and Target Reference ID, and more. Designed as a read-only interface, the Jobs List allows authors to monitor all existing jobs in the application platform.

Navigate to Administration > Jobs List to view the screen below.

The Jobs List displays a grid view with the following columns:

  • Job Master ID: It displays a unique ID for each job.

  • Job Name: It displays the descriptive name of the job, either assigned by the system (for default jobs) or defined by the author during job configuration.

  • Priority: The Priority column indicates the execution priority level assigned to each job.

  • Executions: This displays the number of times the specific job has been executed since its creation. When an author clicks on the execution count from the Jobs List, a detailed Execution pop-up appears, providing key insights into the job’s recent execution history. This pop-up displays the status of past runs—such as Success, Partial Success, Hold, Error, or Killed—along with the execution count, which indicates how many times the job has been executed. It also displays the average duration of the job’s execution, providing authors with a quick overview of its performance and reliability.

  • Schedules: The Schedules column shows the number of schedules associated with each job. Clicking on a number navigates to the scheduling page, allowing users to view or manage the job’s scheduled executions.

  • Job Workflows: The Job Workflow column shows a numeric identifier for each job’s workflow. Clicking a number (other than 0) navigates to the Job Workflow page, where users can view detailed steps, dependencies, and the execution path of that specific job.

  • Execution Scope: It indicates whether the job is executed internally (within the OvalEdge platform) or externally (triggered via external systems or APIs).

  • Class Name: It refers to the backend Java class that contains the logic for executing the job.

  • Method Name: It specifies the particular method inside the class that gets triggered when the job runs.

  • Target Reference Type: This describes the type of system entity or data object that the job is targeting, such as a database, schema, glossary term, or file system.

  • Module Group: It categorizes each job based on the functional module to which it belongs. It enables users to quickly identify and filter jobs by their associated business or system module.

  • First Time/Last Time Executed On: The First Time Executed On and Last Time Executed On columns show when a job was run for the first time and when it was most recently executed. These timestamps help track job history and monitor execution frequency.

Last updated

Was this helpful?