[jira] [Commented] (OFBIZ-11812) New child element callback on link to go out information on dynamic navigation from form

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OFBIZ-11812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17368883#comment-17368883 ] 

ASF subversion and git services commented on OFBIZ-11812:
---------------------------------------------------------

Commit b4e46ff0703b640c93f2e69a5e78b473a8be34c3 in ofbiz-framework's branch refs/heads/trunk from Gil Portenseigne
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=b4e46ff ]

Implemented : New child element set-callback on link to control dynamism (OFBIZ-11812)

Refreshment information are controlled by the calling object,
instead of the called form.

This avoid dependency between called form and parent screens.

The set-callback tag generate a jwt encoded UpdateArea widget, that
is transmitted through submits and links until a submit with no
update-area information is met.  This specific submit ends the
process launched by the link, and trigger the refresh action
contained into the JWT token.


> New child element callback on link to go out information on dynamic navigation from form
> ----------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-11812
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-11812
>             Project: OFBiz
>          Issue Type: Sub-task
>          Components: framework/widget
>    Affects Versions: Trunk
>            Reporter: Nicolas Malin
>            Priority: Major
>              Labels: screen, widget
>         Attachments: OFBIZ-11812.patch
>
>
> When a user realize an updating, creation, or run a complex tunneling process, if after that you need to refresh a screen area without reload all, the action form need to know what it want to update.
> {code:xml}
>  <form name="AddProductStoreAssoc" type="single" target="AddProductStoreToGroup">
>      <field name="productStoreGroupId"><hidden/></field>
>      ...
>      <on-event-update-area area-target="EditProductStoreGroupAndAssoc" event-type="submit" area-id="centerdiv">
>          <parameter param-name="productStoreGroupId" from-field="productStoreGroup.productStoreGroupId"/>
>      </on-event-update-area>
>  </form>
>  {code}
> This create a dependency between the screen where is displaying information and the updating form. Instead create more complicate case to pilot the dynamic interaction between the displaying result and the updating action, we change the reasoning. A user want a good displaying after his operation is finished, so after he terminated his process.
> We introduce a new element, callback on the link. A user start a process in general after follow a link, and when is done, we follow the callback to call the area to refreah.
> {code:xml}
>  <link target="EditProductCategoryRollup" link-type="layered-modal">
>      <auto-parameters-entity entity-name="ProductCategoryRollup"/>
>      <callback area-target="ListProductCategoryChildRollup">
>          <parameter param-name="productCategoryId" from-field="parentProductCategoryId"/>
>      </callback>
>  </link>
>  {code}
> With this the developer is concentrate on the start and the end of a process. The form or the tunneling process isn't linked to the final screen.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)