Event request in page 6648 "Get Return Shipment Lines" trigger OnQueryClosePage()
Nobody has claimed this yet.
- Dominant language
- AL
- Stars
- 683
- Forks
- 459
- Avg merge
- 3d 26m
- Merged PRs (30d)
- 633
Description
Why do you need this change?
There is event OnBeforeOnQueryClosePage the page 5709 "Get Receipt Lines" trigger OnQueryClosePage().
The similar event is required in page 6648 "Get Return Shipment Lines" trigger OnQueryClosePage() what would allow extend the functionality accordingly.
We use this event to exit with 'true' standard trigger OnQueryClosePage() and instead using own trigger OnQueryClosePage() where we return and process not only user selected lines but also dependent lines which were not selected by user but are mandatory. Closing the page 6648 "Get Return Shipment Lines" should function in the same way as page 5709 "Get Receipt Lines" so the similar event is required.
Describe the request
Event:
[IntegrationEvent(true, false)]
local procedure OnBeforeOnQueryClosePage(CloseAction: Action; var Result: Boolean; var IsHandled: Boolean)
begin
end;
To be added to page 6648:
trigger OnQueryClosePage(CloseAction: Action) Result: Boolean
var
IsHandled: Boolean;
begin
IsHandled := false;
OnBeforeOnQueryClosePage(CloseAction, Result, IsHandled);
if IsHandled then
exit(Result);
....
....
end;
Provide an implementation (optional)
- I will provide the implementation for this extensibility request
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the OnQueryClosePage trigger on page 6648 "Get Return Shipment Lines" with page 5709 "Get Receipt Lines", especially its OnBeforeOnQueryClosePage event. Add the equivalent interception point to page 6648 and verify that handled results can control the close behavior while preserving the existing path.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100