FormFragment currently "collects" actions but ultimately embeds them in the form itself. It also uses a hidden form field to control whether the actions for the fragment are executed on the server side.
An alternative approach would be for the fragment's actions to be stored in its own hidden field. On a form submit, the fragment could remove the element and, thus, no update to the server for those fields and no need to maintain the "enabled/disabled" form field.
This also has additional applications for use with FormInjector and Ajax forms wherein rows can be easily added and removed from the client-side.
|Workflow||Default workflow, editable Closed status [ 12567043 ]||jira [ 12589787 ]|
|Workflow||jira [ 12429953 ]||Default workflow, editable Closed status [ 12567043 ]|
|Field||Original Value||New Value|
|Fix Version/s||5.0.13 [ 12313205 ]|
|Resolution||Fixed [ 1 ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Assignee||Howard M. Lewis Ship [ hlship ]|