BUG - BTP Workzone Shell Plugin issue with CommonDataModel.js (cannot find inbound with id Shell-plugin)

[jl-de]

Related Feature

Feature request: issue number

Description

A clear description of what the bug is.

We developed a Shell Plugin for the BTP Workzone standard version. And when starting the workzone, we are getting the error as below:

Cannot find inbound with id 'Shell-plugin' for plugin 'saas_approuter_com.sap.xxx.wzplugin' - plugin startup configuration cannot be determined correctly sap.ushell.services.CommonDataModel

In our manifest.json file, the "Shell-plugin" is defined there.

manifest.json

"crossNavigation": {
"inbounds": {
"Shell-plugin": {
"hideLauncher": true,
"semanticObject": "Shell",
"action": "plugin",
"signature": {
"parameters": {},
"additionalParameters": "allowed"
}
}
}
}
Via debugging, it seems the issue is that the manifest.json is manipulated by the workzone, that the inbound of "Shell-plugin" is auto concatenated with the contentProviderId and the site URL.

CommonDataModel.js

And the CommonDataModel.js is checking exactly the inbound id of "Shell-plugin", which raises then the error.

It seems to us, this is a bug in the standard CommonDataModel.js in case of workzone scenario.

Steps to Reproduce

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected results

Actual results

Screenshots

If applicable, add screenshots to help explain the problem.

Version/Components/Environment

Add any other context about the problem here
OS:

• Mac OS
• [X ] Windows
• Other

Root Cause Analysis

Problem

{describe the problem}

Fix

{describe the fix}

Why was it missed

{Some explanation why this issue might have been missed during normal development/testing cycle}

How can we avoid this

{if we don’t want to see this type of issues anymore what we should do to prevent}

[tobiasqueck]

@jl-de this has nothing to do with the tools being developed in this repository (and I don't think anyone of the maintainers has knowledge in that at area). I think the best way to get help is to open an incident with the workzone team.