pageAL Developmentofficial - Microsoftderived - from the source, no model text

Page 676 "Schedule a Job"

Base Application · System.Threading

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Table 472 "Job Queue Entry" (relates to)Job Queue EntryCodeunit 453 "Job Queue - Enqueue" (calls)Job Queue - EnqueueRun Batch Jobs and XMLports (Learn pages)Run Batch Jobs and XMLports

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · System.Threading · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Schedule a Job
SourceTable Job Queue Entry
PageType StandardDialog

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
Content Description Description Specifies a description of the job queue entry. You can edit and update the description on the job queue entry card. The description is also displayed in the Job Queue Entries window, but it cannot be updated there.
Earliest Start Date/Time Earliest Start Date/Time Specifies the earliest date and time when the job should be started. If you leave the field blank, the job starts when you choose the OK button. The format for the date and time must be month/day/year hour:minute, and then AM or PM. For example, 3/10/2021 12:00 AM.

Procedures

  • ScheduleJob(JobQueueEntry: Record "Job Queue Entry"): Boolean
  • SetJob(JobQueueEntry: Record "Job Queue Entry")

Triggers

OnQueryClosePage

Relations

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Documented on Microsoft Learn

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "page", object_name: "Schedule a Job"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 2 sources