Dear developement team,
there is one point I think it would be very nice to a lot of user of SC. Using the capture function in a form is a really good help in producing lean forms, which can easy be handled by the user.
But after selecting one record in the capture-grid, there is one point missing. The capture-button is bound to one field of the former form and the value of that field is being changed by making the selection. The whole process stops here, just one or two meters before it really ends. The focus is still set to the capture button. Would it not be logic to set the focus to the field, to which it is bound? This would trigger the onfocus-ajax-event, which would give us the possibility to work with the given value of the capture-function.
I want to give an example:
Order form with product-ID, showing the product-name (just to confirm the correct product), qty, price, showing of qty in stock.
It is very useful here to use the capture-function to find the correct product-ID in a grid, where you can search by product category, character in name … or whatever.
Today, after making the selection by the capture function, the user has to re-enter the product-ID field an leave it, in order to trigger the onblur-event of that field, where normally such behaviour like refreshing other fields is stored. OK, for us form developer it is no problem to do that, explaining that to normal app user is senseless
With the suggested behaviour, I think it is simple to implement, the focus would be in a field, where the normal user would expect it to be, the data would be possible to set up to date by the onfocus-ajaxevent and everyone would be happy