Skip Headers
Oracle® Fusion Middleware User's Guide for Desktop Integration Suite
11g Release 1 (11.1.1)

Part Number E10624-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to current chapter
Up
Go to next page
Next
View PDF

4 Integration Into Microsoft Office Applications

This section covers these topics:

4.1 About Microsoft Office Integration

After installing the Desktop Integration Suite software on your computer, you can interact with content servers and the files on them directly from a number of Microsoft Office applications. You can perform a number of content management tasks, including opening files from a content server ("check out"), saving file to a server ("check in"), searching for files on a server, comparing document revisions on a server, and inserting files on a server or links to these files into the current document.

Note:

Not all these features may be available in all Office applications and for all content servers (depending on their server type and version).

The following Microsoft Office applications are supported:

4.2 Integration Into Microsoft Office 2002 (XP) and 2003

The Desktop Integration Suite client software adds a menu called Oracle UCM (Oracle Universal Content Management) to the main Office 2002 (XP) and 2003 application menu bar.

Figure 4-1 Oracle UCM Menu in Microsoft Word 2003

Description of Figure 4-1 follows
Description of "Figure 4-1 Oracle UCM Menu in Microsoft Word 2003"

The Oracle UCM menu contains the following menu items:

4.3 Integration Into Microsoft Office 2007

The Desktop Integration Suite client software adds a ribbon called Oracle UCM (Oracle Universal Content Management) to the Office 2007 application interface.

Figure 4-2 Oracle UCM Ribbon in Microsoft Word 2007

Description of Figure 4-2 follows
Description of "Figure 4-2 Oracle UCM Ribbon in Microsoft Word 2007"

The Oracle UCM ribbon includes the following panels:

4.4 Close Dialog

When you have a checked-out Office document open in your Office application and you close that document or the application, a special close dialog is displayed instead of the standard Office dialog (Figure 4-3).

Figure 4-3 Integration Close Dialog in Microsoft Office Application

Description of Figure 4-3 follows
Description of "Figure 4-3 Integration Close Dialog in Microsoft Office Application"

This special close dialog enables you to decide what to do with your checked-out document: you can save the changes (if there are any unsaved changes), check the document back in to the server as a new revision, edit the document metadata before checking it in, not check it in and save it locally as an offline file, or cancel the checked-out status of the document. See "Saving and Checking In Files in Microsoft Office Applications" and "Save Changes and Check In Document Dialog" for more information.

4.5 Microsoft Office Document Properties

A number of custom properties may be added to Microsoft Office files, depending on the content server type and configuration (specifically, the DesktopTag feature on Oracle Content Server instances). These new custom properties include:

To see the custom properties in Microsoft Office 2002 and 2003 applications, choose File, then Properties, and then open the Custom tab. In Microsoft Office 2007, click the Office button in the application, then choose Prepare, then Properties, then Document Properties, then Advanced Properties, and then open the Custom tab.

Note:

The custom properties are automatically handled by Desktop Integration Suite and should not be changed by end users.

Figure 4-4 Custom Document Properties (Microsoft Word 2003)

Description of Figure 4-4 follows
Description of "Figure 4-4 Custom Document Properties (Microsoft Word 2003)"

These custom document properties allow Desktop Integration Suite to keep track of where a managed file resides on a content server. This, in turn, enables users to check an Office document back in to a content server even outside a content management integration context. This may be useful in a number of situations, for example:

In either case, you can open that file in Microsoft Word on your computer, make changes, and then check it back in to the server using the Oracle UCM menu or ribbon in Word. Desktop Integration Suite looks at the custom properties embedded in the Word document to find out where to upload the file to.