Deploying Siebel Open UI > Features of Siebel Open UI > Migration Tasks for Siebel Open UI >

Migration Options for Siebel File System Features in Siebel Open UI

W3C-based client applications typically run inside of a Web browser container and, for security reasons, are limited in their interactions with client-side applications and files on user computers. Conforming to a Web-standards approach dictates or suggests specific recommendations for designers of hosted deployments involving Siebel Open UI applications and documents or templates that use either structured or unstructured data.

Current Siebel Business Applications features for correspondence, for example, also force a change in the interaction between the user and the Siebel Open UI client, regarding legacy client-side proprietary document formats and applications.

For example, if a user tries to drag an email from Microsoft Outlook into the Siebel client, in order to save it as an attachment in the Siebel File System, then this operation cannot be completed. Such applications typically use different drag-and-drop methods and storage structures than those of the operating system itself. Before the user can save an item (such as an email message) into the Siebel application as an attachment in the Siebel File System, the user must save it as a file in a local or network directory.

Where Java Runtime Environment is present on the user computer, however, attachment files can be saved directly to the Siebel application.

Consider the following recommendations to make it easier to manage data and user interactions of these types:

• Where possible, integrate Siebel Open UI applications with true W3C-compliant client applications or hosted applications, such as Microsoft Outlook Web Access. Such applications can be integrated by using Web services on the back end or by using the JavaScript API on the client side, depending on the business requirements. Integrating with true Web-based client components can simplify many deployment challenges.
• Application designers might consider moving content that currently uses attachments based on proprietary document formats and applications into structured or unstructured data fields that use Web-centric formats such as XML or HTML. This approach:
  • Allows content to be formatted using Siebel Document Server or Oracle Business Intelligence Publisher.
  • Supports audit trails and approvals as content is changed and added by users.
  • Can make it unnecessary to manage content in documents. However, separate physical documents can be created as needed when content creation or revision is complete.
  • Can make it easier to search the modified content.
• Users must have locally available a directory, on the network or on the local computer (for example, a laptop), in which they can store modified files or content dragged from applications like Microsoft Outlook. Then they can save such files into the Siebel application as attachments in the Siebel File System.

This topic is part of Migration Tasks for Siebel Open UI.

Related Topics

Comparing Features Between Siebel Open UI and the Traditional Clients