[Event Change Request] Codeunit 1521 "Workflow Response Handling" - OnShowMessageOnBeforeShowMessage

Open
#29,223 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
25/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Domain
backend

Research direction

Start in Codeunit 1521, "Workflow Response Handling", at ShowMessage and the OnShowMessageOnBeforeShowMessage event. Check the existing event declaration and its call, then verify that Workflow Step Instance is available to subscribers and the request is reflected consistently. The repository states that new pull requests are no longer accepted.

Written by the indexing model from the issue text.

Description

event-request Integration
Why do you need this change?

Request for enhanced Publisher Signature.
We need the "Workflow Step Instance" to determine and handle the SupressMessage parameter.

Describe the request

Hello,
can you please add the variable WorkflowStepInstance to event OnShowMessageOnBeforeShowMessage?

    local procedure ShowMessage(WorkflowStepInstance: Record "Workflow Step Instance")
    var
        WorkflowStepArgument: Record "Workflow Step Argument";
        SuppressMessage: Boolean;
    begin
        WorkflowStepArgument.Get(WorkflowStepInstance.Argument);

        SuppressMessage := false;
        OnShowMessageOnBeforeShowMessage(WorkflowStepArgument, SuppressMessage, WorkflowStepInstance);
        if not SuppressMessage then
            Message(StrSubstNo(ShowMessagePlaceholderMsg, WorkflowStepArgument.Message));
    end;
[IntegrationEvent(false, false)]
local procedure OnShowMessageOnBeforeShowMessage(WorkflowStepArgument: Record "Workflow Step Argument"; var SuppressMessage: Boolean; WorkflowStepInstance: Record "Workflow Step Instance");
begin
end;

Internal work item: AB#608818

Dominant language
AL
Stars
988
Forks
692
Avg merge
49m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/ALAppExtensions

All issues in microsoft/ALAppExtensions

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.