'Generate Add New Button' behaviour

Gabbitas

Hi all,

My actual use case for this isn't quite so simple but....

Lets say I have an object called 'Car' and that object has an entry form which contains a reference attribute called 'wheel type'. Wheel type is displayed as a combo box and I configure it to show 'Generate Add New Button' using 'Default Implementation'

I start a process which displays the entry form and I can then enter a new car and whilst entering the car I can create a new 'wheel type' on the fly using the add new button. All good.

However:

If I configure the 'Generate Add New Button' using 'Custom Implementation' and start the same process again, when I try to create a new 'wheel type' on the fly it kills off the create car form and the whole thing falls over.

Why is this? Is this a bug? Is there a work around?

Any thoughts appreciated

UnionSystems

I vaguely recall having this problem and resolved it by displaying the 'Car' form in a tab rather than a modeless window.

Gabbitas

UnionSystems,

Thanks for the response and suggestion but in my case, putting the entry form for the 'car' in a new tab will feel wrong to the user. I try to keep entry of all new objects to modal or modeless windows and I think creating a new 'car' in a new tab will be bad UX.

I've explored using modal and modeless windows but there seems to be no difference between the two which seems strange to me. Perhaps it may be linked to kklosson's post here forum.awareim.com/https://forum.awareim.com/d/9653> I haven't tried it in a non test operation mode yet....

Thanks