Nicolas Malin created OFBIZ-11812:
-------------------------------------
Summary: 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
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)