UX Pattern for Combo not-in-list

I want to enable add WBS Phase if not in combo on Time Entry.

Wondering if anyone has worked out a generic ux pattern for this?

Thinking something like on-blur > confirm info message > rest-erp > row-update > (?)

Can anyone think of an OOB app that does something similar so I can inspect?

Open to any input on caveats or pitfalls that may come to mind.

No bites. Combo and Project Phase aside, Trying to think of any example of add-record-on-the-fly pattern in Kinetic. Is there such a thing?

What about Search is there an example of search > not found > addIt > return searchResult continue.

The requirement is stay on the record we’re editing rather than for example: abort, go elsewhere, add it, come back, hopefully you can save and not lose work, refresh, try again, abort, start over.

The only place I can think of that epicor has this is the stage field in stage ship confirm. Its really not a good design in most cases though - no separation of security, pretty much a recipe for a lot of similar variations and other data issues.

I have put a field to add new values in a ud code type before - just a text box below the combo with an Add button. Add button triggers a slideout to fill out the values. Closing the slideout saves the record and refreshes the combo.

1 Like

If it is at all helpful, there is a pop-up if you type in a Part Number that doesn’t exist, it’ll prompt if you want to add a new one. So, not based on a search, but similar to what you’re talking about.

It is based on a failed GetByID.

If you want to explore it, you can review the GetByID_OnError event in Part Entry. If you choose to add new, it calls an event-next to the GetNew event to create a new part.

1 Like

thanks @aosemwengie1 and @dcamlin have a nice weekend!

1 Like