Thanks a lot for your reply. I understood your point about making link a link button and hyperlink with target and give it parameter if I'd like. I'll put more information about what I want to do so that you and others can help I want to put some buttons in addition to the regular submit and each button should be responsible for doing 2 things: changing the status of the entity used in the form (changing a value generally) and doing the regular sumbit task of updating the value so if I used your solution that's what I expect I'll d and please anyone correct me
- make different versions of the update service each one will be the regular update plus putting extra code NOT to take the status from the parameters but seeting it to certain value -make the buttons as button links and set target of each one to the suitable update service version that suits it and assign the parameter name the Id of the entity record I wish to update and change the status like the delete or cancel links My point was to use a hidden field in the form say (actionSelected) and when a certain button is pressed then I'll use the javascript to set that field to certain value and do some customization in the update service to check for the value of actionSelected to decide to which status it will be updated and that will save me from creating different targets.That hidden input and javascript will help me decide which button was pressed and that's very important for me Thanks in advance for any help -- View this message in context: http://ofbiz.135035.n4.nabble.com/form-action-buttons-tp3170195p3170492.html Sent from the OFBiz - User mailing list archive at Nabble.com.
