I'm having trouble creating a component that works as a Lightning Console Navigation Item. Console Navigation Items are often regular object pages, allowing List Views to be selected, and when a record is selected, the associated detail opens as a console tab according to the Navigation Rules defined for that Nav Item in the console app.

The Workspace API methods are there to open tabs and subtabs, which suggest we can create pseudo-console-functionality, bypassing Navigation Rules, but is there a way to define a component so that it behaves like a standard Navigation Item and respects those rules? And renders properly when switching between full & split views? 

I'm having trouble creating a component that works as a Lightning Console Navigation Item. Console Navigation Items are often regular object pages, allowing List Views to be selected, and when a record is selected, the associated detail opens as a console tab according to the Navigation Rules defined for that Nav Item in the console app.

The Workspace API methods are there to open tabs and subtabs, which suggest we can create pseudo-console-functionality, bypassing Navigation Rules, but is there a way to define a component so that it behaves like a standard Navigation Item and respects those rules? And renders properly when switching between full & split views?