Form Actions need a server side component Hot
When you build form actions that create conditional field requirements or set field values they are not honored on transitions that are called that do not use forms (eg, transition actions, editable grid, mass update)
we have a few situations where certain field values are set or required based on inputs from the user when performing a transition that uses a custom form with form actions. Form actions have been a great addition to a designer's toolbox and have dramatically sped out ability to deliver usable, robust interfaces. Recently however, as our user community has become more mature in using SBM the need to quickly update a lot of data has become increasingly important. This has led to more use of Mass Updates, Editable Grid and Transition Actions. Unfortunately, along with this increase we have noticed more and more items displaying data that appears out of sync with other data on the item. This is because when you do not use a form-based transition the form actions that you so carefully crafted to ensure proper data collection are not honored.
Please login to view any attachments.