[Event Request] Codeunit 1016 - OnBeforeSendJob

[frivadulla]

Why do you need this change?

Hi,

We would like to request the addition of an Integration Event at the beginning of the Code() procedure in Codeunit 1016 "Jobs-Send", following the standard IsHandled pattern.

Describe the request

Proposed change:

local procedure "Code"()
var
    TempDocumentSendingProfile: Record "Document Sending Profile" temporary;
    IsHandled: Boolean;
begin
    IsHandled := false;
    OnBeforeSendJob(Job, IsHandled);
    if IsHandled then
        exit;

    if not ConfirmSend(Job, TempDocumentSendingProfile) then
        exit;
    // ... existing code
end;

[IntegrationEvent(false, false)]
local procedure OnBeforeSendJob(var Job: Record Job; var IsHandled: Boolean)
begin
end;

Internal work item: AB#640650

[github-actions]

Hi @frivadulla,

Thank you for your extensibility request. To help us process it efficiently, please update the issue to include the required information.

📚 Extensibility Guidelines

Missing Information:

• Business or technical justification: Explain the business need or technical scenario that requires this change.
• Current limitation and scenario context: Describe the current behavior, the limitation you are facing, and why the change is needed.
• Existing extensibility review: List any existing events or patterns you evaluated and explain why they are not sufficient.
• IsHandled necessity: Justify why an IsHandled bypass is required instead of a standard event or redesign.
• Performance and execution impact: Describe any expected impact on execution flow or performance.
• Data sensitivity/security review: Provide a short review of any data exposure or security considerations.
• Multi-extension interaction risk: Note any possible conflicts or interaction risks when multiple extensions subscribe to this event.

Please update the issue with the missing details. We'll automatically re-analyze once updated.

Note

Automatically generated by the Triage Agent — advisory only. An engineer will review before any action is taken.

Tip

Not accurate? Reply with /not-accurate (optional: add a short explanation). Your feedback improves future responses.

[frivadulla]

Business or technical justification

We need to perform custom validations and checks on the Job record before it is sent to the customer (e.g., verify that mandatory fields specific to our business process are filled, ensure project status is valid for sending, and validate that related documents are in the correct state). If any validation fails, we need to prevent the send operation entirely.

Current limitation and scenario context

Currently, Codeunit 1016 "Jobs-Send" does not expose any event at the beginning of its Code() procedure. This means there is no way for an extension to:

1. Run pre-send validations on the Job.
2. Cancel the send operation based on business rules.
3. Replace the standard send logic with a custom implementation (e.g., using a different document sending profile or routing mechanism).

The only way to achieve this today would be to subscribe to events on the Document Sending Profile or Sales Header, which execute too late in the process and don't allow cancelling the send cleanly.

Existing extensibility review

• OnBeforeRunJobSalesQuoteReport (in custom codeunits): Only covers report generation, not the full send flow.
• Document Sending Profile events: These fire after the send decision has been made and the document is already being processed — too late to cancel.
• Page triggers (OnAction): Not reliable since the send can be triggered from multiple places and page-level overrides don't cover all entry points.

None of these provide a clean way to intercept and optionally cancel the full send operation at its entry point.

IsHandled necessity

The IsHandled pattern is required because in certain scenarios we need to skip the standard send logic entirely and replace it with a custom flow (e.g., sending via a different channel or format depending on project type). Without IsHandled, we could only add pre/post logic but not replace the core behavior.

Performance and execution impact

Minimal. The event fires once per send operation, which is a user-initiated action. Subscribers would perform lightweight record reads/validations. No loops or heavy processing expected.

Data sensitivity/security review

The event only exposes the Job record, which is already accessible to any extension with read permissions on the Job table. No additional data exposure or security risk.

Multi-extension interaction risk

Low. The IsHandled pattern is well-established in BC. If multiple extensions subscribe, the first one to set IsHandled := true will prevent subsequent logic. This is standard behavior and consistent with hundreds of other events in the base application.

[github-actions]

✅ Analysis complete - ready for further processing

---

Implementation:

Add a new integration event at the beginning of Code() in Codeunit 1016 Jobs-Send using the IsHandled pattern so extensions can intercept or replace the standard send flow.

Location in Code() procedure:

local procedure "Code"()
var
    TempDocumentSendingProfile: Record "Document Sending Profile" temporary;
    IsHandled: Boolean;
begin
    IsHandled := false;
    OnBeforeCode(Job, IsHandled);
    if not IsHandled then
        SendJob(TempDocumentSendingProfile);
end;

Event Publisher (add at the end of the codeunit with other events):

[IntegrationEvent(false, false)]
local procedure OnBeforeCode(var Job: Record Job; var IsHandled: Boolean)
begin
end;

---

File: JobsSend.Codeunit.al

Note

Automatically generated by the Triage Agent — advisory only. An engineer will review before any action is taken.

Tip

Not accurate? Reply with /not-accurate (optional: add a short explanation). Your feedback improves future responses.