How to define Side Panels for linked to Child Window Applications

[former_member233867]

We are trying to use the NWBC Side Panel with PPM 6.0 in NWBC 3.5.  We have a Role that has a menu defined that gives the users a link to the INM_WORKCENTER_APP which displays the current user's Tasks in a table.

When we click on a task in the table it opens the task details using the CPROJECTS_FPM application in a new window.  This new window that opens up doesn't have any of the Side Panels that we have defined on the role with the main menu links.

We have tried to add the side panel using different application alias and at different levels in the Role, but can't get a Side Panel to show up on the child window.  We even tried to switch the window to open INPLACE in the main window and it still switches to no side panels.  The only side panels we are able to see is side panels that the user has manually added under connections and the Data Context Viewer side panels.

Is NWBC capable of having side panels to be defined to be available for these linked to child applications that are called from a main application screen?  If so, what is the possible configurations we need to make on the role for this to work properly?

Thanks in advance for any help!

[Former Member · Accepted solution]

Which version of NWBC are you using? Side panels aren't supported in the HTML version.

[former_member233867 · Accepted solution]

We are using NWBC 3.5 Desktop Version

[Former Member · Accepted solution]

Then I suggest you change the POWL action handler to use methods URL_CONSTRUCT and URL_LAUNCH of ABAP class CL_NWBC to navigate to the WDA. Another option is to use Launchpad or OBN. I suspect the problem is that the WDA is launched as a stand-alone application, not within NWBC.

[former_member233867 · Accepted solution]

Thanks for the suggested areas to research.  We'll do some more digging and let you know.

[former_member233867 · Accepted solution]

Wanted to close this thread with the solution that worked for us.

We had to change the Launchpad configuration for Role CPROJECTS Instance OIF.  We changed the Application from a Web Dynpro ABAP type to Object Based Navigation.  Set the Application Parameters Business Object to PROJECT and Operation to DISPLAY.

Then for our role defined in PFGC for our NWBC, we added a new menu item to the Web Dynpro application CPROJECTS_FPM with Configuration CPROJECTS_FPM.  Then under Object Based Navigation we set the Object Type to PROJECT and Method to DISPLAY to match what we set above in the Launchpad.  Then set the menu item to be invisible since we didn't want it to show to users.

Now when we launch the child window it uses OBN and sees the definition in our role and utilizes the same Side Panel definitions defined for the role.