You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Mekika Leila (Jira)" <ji...@apache.org> on 2023/09/29 08:20:00 UTC
[jira] [Updated] (OFBIZ-12664) Automatic callback element propagation inside a modal "tunnel" process
[ https://issues.apache.org/jira/browse/OFBIZ-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mekika Leila updated OFBIZ-12664:
---------------------------------
Description:
The callback element added by the Jira OFBIZ-11812 allows to refresh a screen area without reloading the whole page.
However, if you want to use this mechanism in a "tunnel" process, this parameter must be propagated manually between each form so that the final validation and closing of the modal triggers the execution of the callback.
The attached patch adds a propagate-callback parameter on submitButton that will automatically propagate the callback between the forms, simplifying the writing for the developer
For example:
A modal allowing to create an actor on the step 1 form and then allow to attach this actor to a task in the second step.
To test, apply the Example.patch on a trunk environment (with demo data) then go to the following page and click on the "Create" menu button to open the first modal:
[https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=10000|https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=10000]
The validation of the second step should refresh the WorkEffortPartyAssign list in the ListWorkEffortPartyAssigns screen
was:
The callback element added by the Jira OFBIZ-11812 allows to refresh a screen area without reloading the whole page.
However, if you want to use this mechanism in a "tunnel" process, this parameter must be propagated manually between each form so that the final validation and closing of the modal triggers the execution of the callback.
The attached patch adds a propagate-callback parameter on submitButton that will automatically propagate the callback between the forms, simplifying the writing for the developer
For example:
A modal allowing to create an actor on the step 1 form and then allow to attach this actor to a task in the second step.
To test, apply the Example.patch on a trunk environment (with demo data) then go to the following page and click on the "Create" menu button to open the first modal:
[https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=9000]
The validation of the second step should refresh the WorkEffortPartyAssign list in the ListWorkEffortPartyAssigns screen
> Automatic callback element propagation inside a modal "tunnel" process
> ----------------------------------------------------------------------
>
> Key: OFBIZ-12664
> URL: https://issues.apache.org/jira/browse/OFBIZ-12664
> Project: OFBiz
> Issue Type: Improvement
> Affects Versions: Upcoming Branch
> Reporter: Mekika Leila
> Priority: Trivial
> Attachments: OFBIZ-12664.patch, OFBIZ-12664_Example.patch
>
>
> The callback element added by the Jira OFBIZ-11812 allows to refresh a screen area without reloading the whole page.
> However, if you want to use this mechanism in a "tunnel" process, this parameter must be propagated manually between each form so that the final validation and closing of the modal triggers the execution of the callback.
>
> The attached patch adds a propagate-callback parameter on submitButton that will automatically propagate the callback between the forms, simplifying the writing for the developer
> For example:
> A modal allowing to create an actor on the step 1 form and then allow to attach this actor to a task in the second step.
> To test, apply the Example.patch on a trunk environment (with demo data) then go to the following page and click on the "Create" menu button to open the first modal:
> [https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=10000|https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=10000]
>
> The validation of the second step should refresh the WorkEffortPartyAssign list in the ListWorkEffortPartyAssigns screen
--
This message was sent by Atlassian Jira
(v8.20.10#820010)