How to maintain an inbasket display in LSO and Portal

The xml is the actual screen that displays the data like RQ10, AP20 etc... It is pretty straight forward using design studio. As an example I modified an RQ10 screen and than wrapped it in a portal page. Once that exists you reference the portal page within the User Node (Display exec). If you want the form to display the detail related to the work unit when it is opened don't forget to pass the variable on the portal Page.

Example for RQ10 - Also you must data map the variables (Portal Page - Custom)
function portalpage_OnInit()
{
page.addElement("RQH-REQUESTER",page.parameters.RQH_REQUESTER);
page.addElement("RQH-REQ-NUMBER",page.parameters.RQH_REQ_NUMBER);
return true;
}

We looked at the design studio xml inbasket and thought it wasn't as flexible as the html. It sounds we don't have an option here. To create inbaskets displays for LSO's built in processflow and processflow in Portal we'll need to use xml as our display method.

Have you tried creating a LSO xml inbasket with the same name as your Portal htm inbasket to see if they will both function? I know that LSO needs an xml file but the Mobile inbasket uses an htm file. To get both of these to work together they just need to be the same name. I don't believe that works the same between LSO and Portal but worth a try. All of our inbaskets are xml except for Mobile inbasket and I have been able to get all 3 to work together.