The solution then is to recreate what Salesforce does internally to work with the tabs inside Console. On the opposite side of the first solution, in case your LWC is placed directly in the page via App Builder, then you have no Lightning Component wrapper. You can read what the official Salesforce documentation says on sending and handling custom events. This component is your wrapper and listener for the custom events. As you already know, the action button could not execute LWC directly, but can execute Lightning Component instead. This approach could be useful in case your LWC is invoked by Action Button for example. By sending custom events from LWC to the wrapper Lightning Component you can use Workspace API indirectly.
The solution is to create a wrapper Lightning Component for your LWC and implement all the tabs functionality inside that component as it is proposed by Salesforce itself.
0 kommentar(er)
