Configuring Siebel Open UI > Configuring Siebel Open UI to Interact with Other Applications > Displaying Data from Siebel Open UI in External Applications >

Additional Considerations


The following list outlines additional considerations when displaying data from Siebel Open UI in external applications:

  • All parameters passed in a URL need to be URL-encoded. For example, "Account List View" would become "Account+List+View" or "Account%20List%20View". For more information on URL encoding, refer to:

    http://en.wikipedia.org/wiki/Percent-encoding

  • Anonymous sessions are supported in portlet expositions.
  • Tasks and workflow URLs are also supported in portlets.
  • SWE Commands are limited to the ones mentioned in Step 4 of Configuring Communications with Siebel Portlets When Hosted Inside iFrame. However, other parameters may be passed in portlet mode to the Siebel server. They will be honored by the server depending on the context.
  • If the content in the Siebel portlet is bootstrapped to load an applet using the GetApplet method, then the subsequent messaging to the portlet will be limited to whether the applet can be invoked. Operations such as invoking of popups or navigating to other views will not be supported. If these are required, the portlet must be bootstrapped via the GotoView call. For more information, see Configuring Standalone Applets to be Embedded in a Portal.
Configuring Siebel Open UI Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices.