EMC ApplicationXtender for Microsoft Office

Transcription

1 EMC ApplicationXtender for Microsoft Office Release Update Concepts Guide P/N A02 EMC Corporation Corporate Headquarters: Hopkinton, MA

2 Copyright EMC Corporation. All rights reserved. Published December, 2010 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up to date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners.

3 Table of Contents Preface... 9 Chapter 1 Introduction to AXO What is AXO? Who can use AXO? Office Business Application developers IT workers Knowledge workers AXO terminology and concepts Chapter 2 Architectural Overview AXO components AXO setup program AXO Visual Studio Add In AXO architecture Configuration and deployment process: basic method Configuration and deployment process: AXO Visual Studio Add In utility AXO configuration files Configuration files for Microsoft Word Configuration files for Microsoft Excel Configuration files for Microsoft PowerPoint Configuration files for Microsoft Outlook Chapter 3 AXO add in functionality Overview Common functionality Launching an AXO add in Logging in to an ApplicationXtender store Opening a default business use case Querying documents in the ApplicationXtender repository Viewing an ApplicationXtender result set for a predefined query Viewing document properties and indexes Scan a paper document and publish it to ApplicationXtender Viewing ApplicationXtender documents/document containers within Microsoft Office Opening ApplicationXtender documents/document containers within Microsoft Office Viewing ApplicationXtender content in a Web Access browser Viewing ApplicationXtender content in the Windows Presentation Foundation Viewer Working with document and element versions Protecting ApplicationXtender content by using EMC Documentum IRM Services for ApplicationXtender Exporting protected ApplicationXtender content EMC ApplicationXtender for Microsoft Office, Concepts Guide 3

4 Table of Contents E mailing protected ApplicationXtender content User interface elements that support IRM functionality For more information Publishing Office documents to ApplicationXtender Browsing content for a website Submitting ApplicationXtender content to a business process Deleting ApplicationXtender documents/document containers Microsoft Outlook Explorer functionality Ribbon based log viewing and configuration Ribbon options in Word, Excel, and PowerPoint, for AXO logging Ribbon options in Outlook for AXO logging Chapter 4 Licensing and Security Licensing considerations Planning and implementing security Configuring authentication and selecting a security provider Granting access privileges to end users Enabling automatic login Chapter 5 Designing the add in Components of an add in Design considerations Basic XML for an AXO add in User interface produced by the example add in XML file Chapter 6 Configuring a Business Use Case Components of a business use case Views component Ribbon component Dynamic ribbon elements example code ApplicationXtender content management features Login feature Query feature Defining queries Using template or form data as input to a query Result Set feature Document properties feature Document container view feature Web Access feature Publish feature Browser feature Outlook specific features Outlook Explorer Browse ApplicationXtender documents feature Insert from scan feature Export Microsoft Outlook items to ApplicationXtender feature Outlook ad hoc export feature Outlook inspector Choosing the features for a business use case Defining interaction between business use case features Loading a business use case Enabling customizations for a business use case Understanding the importance of configuration versioning EMC ApplicationXtender for Microsoft Office, Concepts Guide

5 Table of Contents Specifying unique identifiers for shared features Example XML for an AXO business use case User interface produced by the example business use case XML file Chapter 7 Getting Started with AXO Creating and deploying an AXO add in Configuring a business use case EMC ApplicationXtender for Microsoft Office, Concepts Guide 5

6 Table of Contents List of Figures Figure 1. Visual Studio Add In Figure 2. AXO configuration process: basic method Figure 3. AXO deployment process: basic method Figure 4. AXO configuration/deployment process: using the AXO Visual Studio Add In Figure 5. The Scan menu Figure 6. WPF Viewer user interface Figure 7. AppXtender tab Figure 8. Modify tab Figure 9. Microsoft Word add in with IRM protection Figure 10. Protect option dialog box Figure 11. Attachment Property dialog box Figure 12. Start Business Process context menu Figure 13. AppXtender ribbon Figure 14. Modify tab Figure 15. Microsoft Office 2010 File menu Figure 16. Microsoft Office 2010 file menu after login Figure 17. Microsoft Office 2010: open from EMC ApplicationXtender dialog box Figure 18. Microsoft Office 2010: Publish to EMC ApplicationXtender dialog box Figure 19. View containing a tabbed workspace Figure 20. Example Office ribbon for Outlook Inspector Figure 21. Example Office ribbon with query entry fields Figure 22. Dynamic ribbon elements Figure 23. Login dialog box Figure 24. Query dialog box Figure 25. Result Set view: grid layout Figure 26. Result Set view: vertical layout Figure 27. Document properties Figure 28. Document elements Figure 29. Document container view Figure 30. Publish to ApplicationXtender: Save options Figure 31. Publish to ApplicationXtender: Document properties Figure 32. Browser feature Figure 33. Microsoft Outlook Explorer: ApplicationXtender browsing feature Figure 34. Outlook Explorer: ApplicationXtender browsing settings Figure 35. Outlook browsing: query results Figure 36. Outlook browsing: query criteria EMC ApplicationXtender for Microsoft Office, Concepts Guide

7 Table of Contents Figure 37. Scan button on the Outlook ribbon Figure 38. Figure 39. Microsoft Outlook Explorer: ApplicationXtender export feature (automatic move) Microsoft Outlook Explorer: ApplicationXtender export feature (manual copy) Figure 40. Outlook 2007 Explorer: Upload to EMC ApplicationXtender settings Figure 41. Outlook 2010 Explorer: upload to ApplicationXtender settings Figure 42. Upload Document Setting: ad hoc configuration Figure 43. Publish to EMC ApplicationXtender Figure 44. Outlook inspector: Attaching an ApplicationXtender document to an e mail Figure 45. Basic business use case for Microsoft Word EMC ApplicationXtender for Microsoft Office, Concepts Guide 7

8 Table of Contents List of Tables Table 1. Terminology: comparison of ApplicationXtender to Microsoft Office Table 2. Microsoft Word basic configuration files Table 3. Microsoft Word out of the box configuration files Table 4. Microsoft Excel basic configuration files Table 5. Microsoft Excel out of the box configuration files Table 6. Microsoft PowerPoint basic configuration files Table 7. Microsoft PowerPoint out of the box configuration files Table 8. Microsoft Outlook basic configuration files Table 9. Microsoft Outlook out of the box configuration files EMC ApplicationXtender for Microsoft Office, Concepts Guide

9 Preface This guide describes EMC ApplicationXtender for Microsoft Office concepts and provides information on how to plan for an implementation. In this guide, the product name ApplicationXtender for Microsoft Office is referred to as AXO. The screen captures in the AXO documentation are examples and may vary from the actual product screens. Intended audience This guide is intended for business application architects, designers, or developers who are responsible for using the AXO software to create custom business solutions for their users by integrating ApplicationXtender content management functionality with Microsoft Office 2007 and 2010 client applications. The guide is also intended to assist IT administrators who are responsible for planning for an AXO implementation. In some companies, the same user may perform both tasks. This guide assumes familiarity with XML, EMC ApplicationXtender, and the 2007 and 2010 Microsoft Office systems. In addition to this guide, the documentation set for EMC ApplicationXtender for Microsoft Office includes: EMC ApplicationXtender for Microsoft Office, 2010 Update, Installation Guide EMC ApplicationXtender for Microsoft Office, 2010 Update, Deployment Guide EMC ApplicationXtender for Microsoft Office, 2010 Update, Release Notes Detailed configuration information for AXO software components is available as an online help system from the Windows Start menu. Revision history The following changes have been made to this document. EMC ApplicationXtender for Microsoft Office, Concepts Guide 9

10 Preface Revision date Description May 2010 Initial publication December 2010 Updated to include support for Microsoft Office EMC ApplicationXtender for Microsoft Office, Concepts Guide

11 Chapter 1 Introduction to AXO This chapter introduces the EMC ApplicationXtender for Microsoft Office (AXO) software. It describes the purpose of AXO, identifies the intended users, and introduces terminology and concepts. The chapter includes the following sections: What is AXO?, page 11 Who can use AXO?, page 12 AXO terminology and concepts, page 13 What is AXO? AXO is a software module that allows business application architects, designers, and developers to integrate ApplicationXtender content management functionality into Office Business Applications (OBAs) based on a Microsoft 2007 or 2010 Office system. OBAs connect line of business (LOB) systems such as Enterprise Resource Planning (ERP), Customer Relationship Management (CRM), and Supply Chain Management (SCM) with the people that use them through the familiar user interface of Microsoft Office. AXO supports and extends the concept of OBAs by providing a set of components and tools to develop add in software solutions for ApplicationXtender integration with Microsoft Office. AXO provides: Access to core ApplicationXtender functionality from within supported Microsoft Office client applications Custom business solutions based on ApplicationXtender that minimize end user operations for performing business activities Centralized customization, configuration, and deployment Parity with existing ApplicationXtender Microsoft Office integration functionality Each AXO add in solution provides basic ApplicationXtender content management functionality (login, open from ApplicationXtender, and publish to ApplicationXtender) from within supported Microsoft Office applications. In addition, you can configure an add in to provide highly customized functionality by using one or more business scenarios, or business use cases. A business use case supports a specific business process or activity performed by end users. The goal is to customize each solution to support only tasks required to complete a specific business activity, thereby reducing the number of end user actions required to perform routine operations. EMC ApplicationXtender for Microsoft Office, Concepts Guide 11

12 Introduction to AXO AXO provides a basic add in solution for each supported Microsoft Office application: Outlook, Word, Excel, and PowerPoint, and also an Out of the Box configuration which is not content type specific. You can use these add in solutions with minimal configuration or create new solutions using AXO configuration components. AXO also provides example business use case configuration files that you can modify for your use. AXO configuration files, page 24 provides a list of example files provided with AXO. Who can use AXO? AXO users fall into three different categories: Office Business Application developers, page 12 IT workers, page 12 Knowledge workers, page 13 The following sections describe how these users interact with AXO add in solutions to perform their jobs. Office Business Application developers OBA developers are responsible for customizing the AXO components to create add in solutions for specific user groups and Microsoft Office applications. The primary customization task involves designing and configuring business use cases based on business process or user needs. AXO provides example business use case configuration files that you can modify for your use. The content of the configuration files determines the appearance and behavior of ApplicationXtender functions inside Office applications. For example, as an OBA developer, you could design a business application solution for Microsoft Word that allows users to complete weekly status reports using a Word template. After users complete the status reports, they would publish them to the ApplicationXtender repository for historical purposes. During the configuration process for this solution, you would include only user interface elements that support the creation and submission of status reports. By customizing the solution to support a specific task, you reduce the number of steps it takes end users to perform their work. Chapter 5, Designing the add in and Chapter 6, Configuring a Business Use Case provide more information. IT workers IT workers and OBA developers use the AXO functionality to create AXO add in solutions for Office for deployment to various work groups within the company. Add in solutions are generated using both AXO components and customer specific ApplicationXtender data including data source names, application names, and the Web Access URL. The solutions can then be published for distribution using either the company s website or network file share. This implementation strategy allows OBA developers to perform a centralized customization that can be distributed from a single location as 12 EMC ApplicationXtender for Microsoft Office, Concepts Guide

13 Introduction to AXO well as to create various add in solutions that target different groups of business users. In addition, AXO s distribution strategy uses the Microsoft ClickOnce functionality to install add in updates automatically, thereby resolving potential update and upgrade issues. In some companies, the tasks of the OBA developer and IT worker may be performed by the same person. The EMC ApplicationXtender for Microsoft Office Deployment Guide provides details on deploying AXO add in solutions. Knowledge workers Microsoft Office application end users, who are generally knowledge workers or business officers, use the customized functionality delivered by AXO add in solutions to perform routine and ad hoc tasks required by their business operations. They use ApplicationXtender functions that are integrated into Office applications and customized for a specific business activity. These users may perform the same set of tasks daily and work with only one ApplicationXtender application, for example, Accounts Payable or HR. AXO add in solutions allow end users to perform the following ApplicationXtender content management tasks while working with Microsoft Office documents: Querying and viewing ApplicationXtender documents Opening/inserting ApplicationXtender documents into Office applications Creating, updating, and uploading documents from Office applications Other functionality, including Microsoft Office application specific functionality, is also available. Chapter 3, AXO add in functionality provides a more detailed description of available functionality. AXO terminology and concepts The AXO software and documentation introduces common content management terminology. In AXO, an ApplicationXtender data source is referred to as a store, an ApplicationXtender application is referred to as a content type, and an ApplicationXtender document is referred to as a document container. The term ApplicationXtender repository is synonymous with store. AXO uses Microsoft Office terminology for document related items rather than ApplicationXtender specific terminology because end users may not be familiar with ApplicationXtender. Table 1, page 14 provides a comparison, or mapping, of both sets of terminology. Note: The definitions in the table pertain to Microsoft Office files only. They do not apply to PDFs or other file formats. EMC ApplicationXtender for Microsoft Office, Concepts Guide 13

14 Introduction to AXO Table 1. Terminology: comparison of ApplicationXtender to Microsoft Office ApplicationXtender term/concept Comparable Microsoft Office term/concept Description in ApplicationXtender Document None A file or group of files stored in an ApplicationXtender application and identified by index information. Each page of an ApplicationXtender document is a single object, such as a scanned image file or a word processing document. Each ApplicationXtender document is a combination of objects, each stored as a page within the document. For instance, a document for a hospital patient might include scanned admission forms, a doctor s report in Microsoft Word format, and an x ray image file. A single ApplicationXtender document can contain one page or thousands of pages. Page Microsoft Office document or a single page of another document format (for example, PDF) In AXO, a document container holds elements, which can be either Microsoft Office documents or pages of other document formats. A single object or entity, such as a scanned image file or a word processing document. ApplicationXtender supports multiple object types in a document. A page can come from one of many different sources. For example, a very long word processing file is considered a page by ApplicationXtender. A page could also be a single scanned image, a 30 minute video clip, or an audio recording. When you create a document in ApplicationXtender, the object added as the new document is the first page of that document. Up to 250,000 pages can be attached to a document. The same index record is attached to all of the pages (objects) in a single ApplicationXtender document. In AXO, an ApplicationXtender page is referred to as an element. Each Office document is a single page/element. 14 EMC ApplicationXtender for Microsoft Office, Concepts Guide

15 Introduction to AXO ApplicationXtender term/concept Comparable Microsoft Office term/concept Description in ApplicationXtender Subpage Page Page of a Microsoft Office document. AXO does not use the concept of a subpage. Index Properties A group of fields where descriptive information pertaining to documents can be stored. This group of field definitions is used by ApplicationXtender when storing index information within an application. In AXO, ApplicationXtender index properties are referred to as document properties. Microsoft document properties, formerly called ODMA properties, are referred to as common properties in AXO. Because AXO relies on Microsoft technology, you should also be familiar with the following Microsoft terminology: Office Business Applications (OBAs) An Office Business Application (OBA) is a composite application that uses applications within the Microsoft Office System (such as Outlook, Word, or Excel) as the front end for a Line of Business (LOB) application. Note: All new ApplicationXtender documents created from Microsoft Office 2007 and 2010 applications use the new office format, which is based on an Open XML standard. ClickOnce AXO uses Microsoft ClickOnce technology in its deployment strategy. ClickOnce is a deployment technology that allows you to create self updating Windows based applications that can be installed and run with minimal user interaction. A ClickOnce application can be installed on an end user s computer and run locally even when the computer is offline, or it can be run in an online only mode without permanently installing anything on the end user s computer. The EMC ApplicationXtender for Microsoft Office Deployment Guide provides more information on how the AXO deployment process uses ClickOnce. Visual Studio Tools for Office (VSTO) AXO uses the Microsoft VSTO technology in its deployment strategy. Office Open XML EMC ApplicationXtender for Microsoft Office, Concepts Guide 15

16 Introduction to AXO Office Open XML (commonly referred to as OOXML or OpenXML) is an XML based file format specification for electronic documents, such as spreadsheets, charts, presentations, and word processing documents. 16 EMC ApplicationXtender for Microsoft Office, Concepts Guide

17 Chapter 2 Architectural Overview This chapter provides an architectural overview of AXO. It includes the following sections: AXO components, page 17 AXO architecture, page 20 AXO configuration files, page 24 AXO components AXO components are provided in two setup programs: AXO and the optional AXO Visual Studio Add In. The EMC ApplicationXtender for Microsoft Office Release Notes provides a list of software that must be installed before running the AXO and AXO Visual Studio Add In setups. The EMC ApplicationXtender for Microsoft Office Installation Guide provides installation procedures. AXO also provides tools that allow OBA developers to localize the text in the user interface provided by AXO solutions. After signing the files containing the localized text, OBA developers submit the files to EMC to be signed. Upon receipt of the EMC signed files, OBA developers then deploy the localized solution. Contact your EMC representative for details about how to use the language pack feature. In addition, AXO Update includes language packs for Spanish. AXO setup program The AXO setup program installs the following components: ApplicationXtender feature work items Software components that provide ApplicationXtender content management functionality and custom user interface elements. ApplicationXtender feature work items are customizable and configurable user interface parts that can be used for various business use cases. You can customize the presentation and behavior of each ApplicationXtender work item to make it suitable for a particular business use case. The goal is to minimize end user actions required to perform specific business functionality. An ApplicationXtender feature work item addresses only EMC ApplicationXtender for Microsoft Office, Concepts Guide 17

18 Architectural Overview user interface views while the business logic and data objects in AXO are provided through a connection to ApplicationXtender Web Services. Configuration files Supplied basic add ins A set of preconfigured add ins and associated business use cases that you can use for demonstration purposes. The example add ins, which are designed to work with the ApplicationXtender demo database, contain core ApplicationXtender content management functionality. You can modify these add ins for your own use with minimum configuration. Example business use cases Example business use case XML files that demonstrate how you can assemble AXO work items to support a particular business process or task. Sample XML for ApplicationXtender features A library of sample XML files for various AXO work items that you can reuse in developing your own custom solutions. These samples showcase the ApplicationXtender features that are provided with AXO. Out of the box versions of all of the above, which allow going directly to a simple production system after providing just the AX server name in the configuration. AXO deployment utility (.bat file) Tools that manage the generation and maintenance of installation and update solutions of AXO add ins at your site. Log tool (AXOLogsTool.exe) Windows tool that collects log information for AXO add ins. Copy this file to the machine on which the AXO add in is installed, and then run it. provides more information. AXO Visual Studio Add In AXO provides a graphical user interface (GUI) for creating and publishing ClickOnce packages for AXO add in solutions for supported Microsoft Office applications. This GUI tool, which is an add in package to Microsoft Visual Studio 2008 and 2010, standard editions, lets OBA developers configure AXO business use cases and add in solutions using a visual designer. It provides an alternative to configuring and deploying AXO add in solutions manually using XML files and batch files. The AXO Visual Studio Add In provides: Visual Studio project templates for AXO add in projects and business use case projects Visual Ribbon Designer that leverages the Windows Presentation Foundation (WPF) ribbon Integration of the business use case creation process with the standard Visual Studio MSBuild process Comments, samples, and user prompts in the XML schema The AXO Visual Studio Add In also validates the configuration and provides syntax help. 18 EMC ApplicationXtender for Microsoft Office, Concepts Guide

19 Architectural Overview After configuring an AXO add in solution for a specific user group and Microsoft Office application, the OBA developer uses the AXO Visual Studio Add In to perform the following tasks: Generate a ClickOnce package for the AXO add in Publish the ClickOnce package to a shared folder or as a Web application Update and create a new version of an existing ClickOnce package In addition, the AXO Visual Studio Add In helps OBA developers manage add in packages by maintaining a record of locations and versions of published packages. The following figure shows the AXO Visual Studio Add In. Figure 1. Visual Studio Add In The online help that is installed with the utility provides procedures on using the AXO Visual Studio Add In. You can access the help from the Windows Start menu as well as from the Help menu in the add in. Note: As an alternative to installing and using the AXO Visual Studio Add In to configure and publish AXO solution packages, you can create XML files manually by using an XML editor and deploy the XML files by using the procedures in the EMC ApplicationXtender for Microsoft Office Deployment Guide. You can also import XML files into the AXO Visual Studio Add In by using the procedures in the online help for the add in. However, AXO release 5.40 and 6.0 XML files are not supported in AXO 6.5 due to changes in the XML configuration objects. EMC ApplicationXtender for Microsoft Office, Concepts Guide 19

20 Architectural Overview AXO architecture AXO uses a multi tier architecture in which the AXO add in communicates with the application server by using ApplicationXtender Web Services at the back end. Therefore, ApplicationXtender Web Services must be installed before configuring AXO components. It is recommended that you install ApplicationXtender Web Access.NET, which installs ApplicationXtender Web Services in integrated mode, rather than installing ApplicationXtender Web Services in stand alone mode. Otherwise, the following AXO features will be unavailable: Microsoft Outlook Explorer browsing feature Web Access feature Web Access render mode in the Document Container View feature Note: End users are not required to have a Web Services license when running AXO add ins. The EMC ApplicationXtender for Microsoft Office Release Notes provides a list of prerequisite software and hardware required for using AXO. The AXO architecture provides components that support the tasks of configuring and deploying AXO add in solutions. Two options are available for performing these tasks: using an XML editor (basic method) and using the AXO Visual Studio Add In utility (visual designer) provided by AXO. The following sections describe the process flow for these high level that use the available options. Configuration and deployment process: basic method The basic configuration and deployment processes for AXO include manual configuration and deployment of AXO XML files. Configuring the AXO files includes specifying available functionality as well as the default layout for the user interface. It also includes specifying customer ApplicationXtender data, which includes the address for the ApplicationXtender Web Access Server and the names of the ApplicationXtender stores and content types that users can access from the add in. AXO configuration files, page 24 provides a list of configuration files provided with AXO, and the EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides procedures on configuring AXO components. Figure 2, page 21 illustrates the AXO configuration components and demonstrates how they interact with one another. As shown in the diagram, the OBA developer configures an AXO add in solution by modifying example AXO configuration files. 20 EMC ApplicationXtender for Microsoft Office, Concepts Guide

21 Architectural Overview Figure 2. AXO configuration process: basic method The output of the AXO configuration process is a configured add in solution, which serves as input to the AXO deployment process along with the configured deployment definition file. The deployment definition file defines the version, update settings, and business use cases (if applicable) for the deployment package. AXO provides a deployment definition file for each supported Office application. Figure 3, page 22 illustrates the AXO deployment components for a basic (manual) deployment scenario and demonstrates how they interact with one another. As shown in the diagram, the IT worker generates and deploys the add in solution to a location that users can access, either a website or network file share. Knowledge workers then navigate to this location and install the initial version of the add in on their workstations. Updated add in packages at the deployment location are installed on end user workstations automatically when users launch the associated Microsoft Office application. The EMC ApplicationXtender for Microsoft Office Deployment Guide provides more information. EMC ApplicationXtender for Microsoft Office, Concepts Guide 21

22 Architectural Overview Figure 3. AXO deployment process: basic method Configuration and deployment process: AXO Visual Studio Add In utility As an alternative to the basic configuration and deployment process flow, OBA developers can create and publish add in deployment packages by using the AXO Visual Studio Add In utility. This utility provides Visual Studio projects that can be used to develop AXO business use cases and 22 EMC ApplicationXtender for Microsoft Office, Concepts Guide

23 Architectural Overview AXO add in solutions. Figure 4, page 23 illustrates the configuration and deployment process that uses the AXO Visual Studio Add In utility. As the diagram indicates, the deployment process flow is slightly different from the manual AXO configuration/deployment process. For example, when using the add in to deploy AXO packages, it is not necessary for OBA developers to understand the deployment definition file. As with the manual process, add in deployment packages are made available to users on either a website or network file share. Figure 4. AXO configuration/deployment process: using the AXO Visual Studio Add In The online help for the AXO Visual Studio Add In utility provides more information. EMC ApplicationXtender for Microsoft Office, Concepts Guide 23

24 Architectural Overview AXO configuration files As mentioned in AXO components, page 17, the AXO setup program installs example XML configuration files. You can use these files with minimal configuration or create custom add in solutions for your end users. The tables in the following sections identify the basic and out of the box configuration files for each supported Microsoft Office application as well as the directory path in which they are installed. The basic and out of the box configuration files are prototypes that can be adapted to your own specific needs. Additional sample XML files are installed in C:\Program Files\ApplicationXtender\AXO\Configurations\Samples. Chapter 5, Designing the add in and Chapter 6, Configuring a Business Use Case provide the contents of the basic add in and business use case XML files, respectively. Note: The basic business use case BasicContentManagement.xml is identical for Microsoft Word, Excel, and PowerPoint. The out of the box business use case ContentTypeFree.xml is also identical for Word, Excel, and PowerPoint. The differences between the basic and out of the box configurations are: The basic configuration (BasicContentManagement.xml) is pre coded to use a Store element value of AppXtenderDEMO for the repository, and ContentType (from the repository) of HR. This configuration is for demonstration and experimentation. It can be adapted to your needs if you find it applicable. The Out of the Box configuration (ContentTypeFree.xml) does not predefine the values for Store and ContentType, and allows users to select from dropdowns based on available repositories and their associated content types. After providing the AX server name in the XML file, this configuration can be deployed with no further changes in a production environment. The AXO Deployment Guide has detailed information on creating and distributing deployment packages. Configuration files for Microsoft Word Configuration files for the basic add in for Microsoft Word are located in C:\Program Files\ApplicationXtender\AXO\Configurations\Basic\Word. Table 2. Microsoft Word basic configuration files To configure this component Example AXO add in for Microsoft Word Basic business use case Example business use case that demonstrates various AXO features including a ribbon based query Use this XML file AXTOWordAddIn.xml BasicContentManagement.xml AXTOFeatures.xml Configuration files for the out of the box add in for Microsoft Word are located in C:\Program Files\ApplicationXtender\AXO\Configurations\Out_Of_The_Box\Word. 24 EMC ApplicationXtender for Microsoft Office, Concepts Guide

25 Architectural Overview Table 3. Microsoft Word out of the box configuration files To configure this component Example AXO add in for Microsoft Word Out of the box business use case Use this XML file AXTOWordAddIn.xml ContentTypeFree.xml Configuration files for Microsoft Excel Configuration files for the basic add in for Microsoft Excel are located in C:\Program Files\ApplicationXtender\AXO\Configurations\Basic\Excel. Table 4. Microsoft Excel basic configuration files To configure this component Example AXO add in for Microsoft Excel Basic business use case Example business use case that demonstrates various AXO features including a ribbon based query Use this XML file AXTOExcelAddIn.xml BasicContentManagement.xml AXTOFeatures.xml Configuration files for the out of the box add in for Microsoft Excel are located in C:\Program Files\ApplicationXtender\AXO\Configurations\Out_Of_The_Box\Excel. Table 5. Microsoft Excel out of the box configuration files To configure this component Example AXO add in for Microsoft Excel Out of the box business use case Use this XML file AXTOExcelAddIn.xml ContentTypeFree.xml Configuration files for Microsoft PowerPoint Configuration files for the basic add in for Microsoft PowerPoint are located in C:\Program Files\ApplicationXtender\AXO\Configurations\Basic\PowerPoint. Table 6. Microsoft PowerPoint basic configuration files To configure this component Example AXO add in for Microsoft PowerPoint Basic business use case Example business use case that demonstrates various AXO features including a ribbon based query Use this XML file AXTOPowerPointAddIn.xml BasicContentManagement.xml AXTOFeatures.xml EMC ApplicationXtender for Microsoft Office, Concepts Guide 25

26 Architectural Overview Configuration files for the out of the box add in for Microsoft PowerPoint are located in C:\Program Files\ApplicationXtender\AXO\Configurations\Out_Of_The_Box\PowerPoint. Table 7. Microsoft PowerPoint out of the box configuration files To configure this component Example AXO add in for Microsoft PowerPoint Out of the box business use case Use this XML file AXTOPowerPointAddIn.xml ContentTypeFree.xml Configuration files for Microsoft Outlook The configuration files for the basic add in for Microsoft Outlook are named differently than for the other Office applications. They also contain different information, to accommodate the differences between Outlook and the other Office applications. The Outlook configuration files are located in C:\Program Files\ApplicationXtender\AXO\Configurations\Basic\Outlook. Table 8. Microsoft Outlook basic configuration files To configure this component Example AXO add in for Microsoft Outlook Basic business use case for Outlook Inspector Configuration file for Outlook Explorer Use this XML file AXTOOutlookAddIn.xml InspectorBusinessUseCase.xml ExplorerFeatures.xml Configuration files for the out of the box add in for Microsoft Outlook are located in C:\Program Files\ApplicationXtender\AXO\Configurations\Out_Of_The_Box\Outlook. Table 9. Microsoft Outlook out of the box configuration files To configure this component Example AXO add in for Microsoft Outlook Configuration file for Outlook Explorer Use this XML file AXTOOutlookAddIn.xml ExplorerFeatures.xml 26 EMC ApplicationXtender for Microsoft Office, Concepts Guide

27 Chapter 3 AXO add in functionality This chapter provides a high level overview of the AXO add in functionality available for supported Microsoft Office client applications. The chapter includes the following sections: Overview, page 27 Common functionality, page 27 Microsoft Outlook Explorer functionality, page 41 The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system that is installed with AXO provides details on configuring an add in. Overview AXO lets you create custom add in solutions that incorporate ApplicationXtender content management functionality into Microsoft Office based add ins. You determine both the functionality and the appearance of the user interface for the add in by using AXO s configuration work items. These work items are the building blocks you use to configure a business use case for an add in. After configuring one or more business use cases, you deploy the functionality to users by using an AXO add in. AXO gives you the flexibility to tailor each add in solution to a specific business department or group of users. The remainder of this chapter provides a high level overview of the functionality available for AXO add in solutions. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides specific configuration options for AXO components. Note: As an alternative to creating a custom business use case for an add in, you can provide core ApplicationXtender content management functionality directly from the Microsoft Office Button (for Office 2007), or from the Office 2010 File > ApplicationXtender backstage, by using the add in XML file. This option lets you deploy ApplicationXtender functionality with minimal configuration. Chapter 5, Designing the add in provides more information. Common functionality AXO provides a common set of add in functionality for Microsoft Outlook Inspector, Word, Excel, and PowerPoint. Microsoft Outlook Explorer functionality, page 41 provides a description of Outlook Explorer specific functionality. EMC ApplicationXtender for Microsoft Office, Concepts Guide 27

28 AXO add in functionality Common add in functionality provides the ability to: Launch an AXO add in Log in to an ApplicationXtender store Open a (default) business use case Query documents in the ApplicationXtender repository View an ApplicationXtender result set for a predefined query View document indexes, properties, and thumbnails Scan a paper document and publish it to ApplicationXtender Insert a scanned document into an existing document container. View ApplicationXtender documents/document containers within Microsoft Office Work with document and element versions Protect ApplicationXtender content Publish Microsoft Office documents to ApplicationXtender as a new: Document Revision to an existing document Element for an existing document (append, prepend, or insert as a specific element number) Element version Browse content for a website Submit ApplicationXtender content to a business process Delete ApplicationXtender documents/document containers The following sections describe common add in functionality in more detail. Launching an AXO add in With the exception of Microsoft Outlook add ins, which are launched automatically when users open Outlook, AXO add ins are not started when the associated Microsoft Office application (Word, Excel, or PowerPoint) is started. Instead, users must explicitly open the add in by clicking an AXO related button from the ribbon, for example, Login or Business Applications. This design reduces the initialization time for the Microsoft Office application. It is possible to configure an AXO add in to start automatically, by using the <DefaultBusinessUseCase> parameter in the AXTOxxxxAddin.xml file, where xxxx is Word, Excel, or PowerPoint. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides detailed configuration information on this topic. Logging in to an ApplicationXtender store Every business use case must provide the ability for users to log in to the ApplicationXtender content management system from within a Microsoft Office application. You can define multiple Login 28 EMC ApplicationXtender for Microsoft Office, Concepts Guide

29 AXO add in functionality features for a business use case, each of which is associated with a different ApplicationXtender store. Login feature, page 61 provides a sample user interface. AXO lets you specify whether to share a single ApplicationXtender server session for concurrent connections to the ApplicationXtender store with the same login credentials. This means that, when users launch more than one Microsoft Office application at the same time, they can use the AXO login to the CM repository inside the first application for all other Office applications. For example, AXO can share a server session when a user connects to the store within Word and then uses the same credentials to connect to the store within Excel. Sharing a server session does not consume an additional ApplicationXtender license. The session sharing feature is disabled by default. To enable this feature, configure the Web Access server setting InterAppAxSessionSharing in the Office application configuration files provided by AXO. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides detailed configuration information for session sharing. Opening a default business use case If you choose to create a business use case for an add in, you can define a default business use case that opens automatically when users launch the Microsoft Office application/add in. You can also configure an AXO add in to open a business use case based on association with a Microsoft Office document or template. Loading a business use case, page 85 provides more information. If you configure more than one business use case for an add in, you can allow users to access the additional business use cases by using the Microsoft Office Button (for Office 2007), or by using the Office 2010 File > ApplicationXtender backstage.. The add in configuration section of the EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides more information. Querying documents in the ApplicationXtender repository Most end user tasks require the ability to search for documents in the ApplicationXtender repository. You can customize the document query feature to control the extent to which users can modify search criteria for the query. For example, you can configure a Query dialog box that allows users to change properties (index values) before they run the query. You can even specify which properties users are able to change. Alternatively, you can allow users to run a predefined query from the Office ribbon without displaying the search criteria. Query feature, page 62 provides a sample user interface. The AXO Query feature also supports the use of custom fields and regular expressions. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides more information. EMC ApplicationXtender for Microsoft Office, Concepts Guide 29

30 AXO add in functionality Viewing an ApplicationXtender result set for a predefined query Following the execution of a document query, end users need to review, analyze, and research the list of ApplicationXtender documents that met the specified search criteria. The AXO Result Set View function provides this capability. As with other AXO work items, you can customize the Result Set View options in advance for each business use case. For example, you can customize the Result Set View to change the orientation of the search results. Result Set feature, page 64 provides a sample user interface. Viewing document properties and indexes The Document Properties feature allows end users to view document container properties (indexes, including multiple indexes) and/or common properties, depending on the configuration you specify. If the AXO add in is configured to save tracking (reference) information for an ApplicationXtender document container when users save a local copy of a Microsoft Office document/page that is part of that document container, the reference information is also saved as document properties in the local document. The reference information includes the ApplicationXtender store name, content type, and document container ID, among other things. Saving the reference information creates an association between the ApplicationXtender document container and the local copy of the document page. When a user opens the document from a Microsoft Office application on a machine on which AXO is installed, the add in uses the reference information to connect to the ApplicationXtender store. The association between the local copy of a document and the ApplicationXtender document is maintained provided new pages are not added to the ApplicationXtender document. If the association is broken, users can cancel the upload process or upload the local copy as a new page of the ApplicationXtender document. The Reference feature is configured at the AXO add in solution level by using the XML tag TrackLocalDocument. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides detailed configuration information. Figure 27, page 67 illustrates a sample user interface for viewing document properties. Scan a paper document and publish it to ApplicationXtender The Scan option is available in the AXO menu and in the Windows Presentation Foundation Viewer. Note: You must be logged into ApplicationXtender to see and use the Scan option. To use the Scan option from an Office application menu: For MS Office 2007 applications, click the Microsoft Office button and then select Scan > Scan. For MS Office 2010 applications, in the File menu, click AppXtender, and then select Scan. 30 EMC ApplicationXtender for Microsoft Office, Concepts Guide

31 AXO add in functionality Figure 5. The Scan menu The Scan option is also available from within the WPF Viewer in the Scan Tab. Refer to the AXO online help for details on setting up scan functionality. Viewing ApplicationXtender documents/document containers within Microsoft Office After end users perform a query using an AXO add in, they can select a document element from the result set for viewing. AXO provides the ability to view ApplicationXtender document pages of EMC ApplicationXtender for Microsoft Office, Concepts Guide 31

32 AXO add in functionality different formats without exiting the Microsoft Office application. Documents can be rendered in one of the following formats: Native Microsoft Office (for ApplicationXtender documents that are entirely in Office format). Opening ApplicationXtender documents/document containers within Microsoft Office, page 32 provides details. Web browser by using either the ApplicationXtender Web Access thin client or IRC (Interactive Rich Client). Viewing ApplicationXtender content in a Web Access browser, page 32 provides details. Windows Presentation Foundation (WPF). Viewing ApplicationXtender content in the Windows Presentation Foundation Viewer, page 33 provides details. Microsoft XPS Adobe Acrobat Reader PDF Figure 29, page 69 provides a sample user interface. You can configure a default viewer for ApplicationXtender documents and specify whether the document should appear in the current workspace or in a new window. You can also allow users to check out the document for editing rather than restricting them to viewing a read only version of the document. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides more information. Opening ApplicationXtender documents/document containers within Microsoft Office AXO provides the ability to open ApplicationXtender documents that are in Office format using the Microsoft Office application. When end users open an Office document from the ApplicationXtender Result Set View, they can choose to open it in read only mode or check out the document for editing. Users must enter check out comments to proceed with a document checkout. After editing a checked out document in Office, a user can publish the document to ApplicationXtender. Publishing Office documents to ApplicationXtender, page 39 provides more information. Viewing ApplicationXtender content in a Web Access browser The Web Access feature allows end users to view ApplicationXtender content in a Web Access browser window within Microsoft Office. Users can retrieve, view, and manage content from ApplicationXtender content types using this feature. Web Access feature, page 69 provides more information. Note: It is recommended that you avoid using the Web Access feature when configuring AXO add ins for Microsoft Excel. Web Access feature, page 69 provides more information. 32 EMC ApplicationXtender for Microsoft Office, Concepts Guide

33 AXO add in functionality Viewing ApplicationXtender content in the Windows Presentation Foundation Viewer The Windows Presentation Foundation (WPF) image viewer provides the same functionality as ApplicationXtender Desktop and Web Access for viewing document containers and elements in an AXO add in. The WPF Viewer provides tabs for managing the content displayed in the viewer. Users can perform tasks in the viewer s tabbed interface: Home tab: Navigate content in a document container Display element components such as thumbnails, annotations, text or images for OCR processed content and overlays Modify tab: Change the text font for OCR processed content. Manage document container elements, including creating, deleting, and replacing elements; and creating and deleting element versions. Apply annotations and redactions. Scan tab: Scan Uses a selected scanner to scan documents, and append scanned documents to the opened document container. Select Allows selecting a scanner from a list of installed scanners. Configure Allows configuring a selected scanner. Publish Document Enabled only when scan is launched from the Office menu. Although documents scanned into the viewer are not yet published to the AX repository, the are available to be published to the AX repository. View tab: Controls how the viewer displays content, including zoom and rotation features. The basic business use case (BasicContentManagement) supports the WPF Viewer. Note: Excel add ins do not support the use of the WPF Viewer in modeless dialog boxes. The following figure shows a sample user interface for the WPF Viewer. EMC ApplicationXtender for Microsoft Office, Concepts Guide 33

34 AXO add in functionality Figure 6. WPF Viewer user interface The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides detailed configuration information for the WPF Viewer. Working with document and element versions Users can view version control history for ApplicationXtender documents and elements by using document container (ApplicationXtender document) functionality. Users can also open a page in another document version. The AppXtender tab of the ribbon provides options for working with document and element versions, as shown in the following figure. Figure 7. AppXtender tab 34 EMC ApplicationXtender for Microsoft Office, Concepts Guide

35 AXO add in functionality The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides detailed configuration information for document containers and for the ribbon. Users can also work with document container element versions (ApplicationXtender document pages) in the WPF Viewer. The Modify tab of the WPF Viewer work item provides options for creating and deleting document container elements and element versions, as shown in the following figure. The annotation tools, including redaction, are also on the Modify tab. Figure 8. Modify tab Viewing ApplicationXtender content in the Windows Presentation Foundation Viewer, page 33 provides additional description of the new WPF Viewer component. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides detailed configuration information for the WPF Viewer. Protecting ApplicationXtender content by using EMC Documentum IRM Services for ApplicationXtender AXO provides support for EMC Documentum IRM Services for ApplicationXtender. If IRM protection is enabled for an ApplicationXtender application (content type) in ApplicationXtender Application Generator, AXO displays user interface elements that allow users to apply IRM protection to ApplicationXtender content for the application. Users can perform the following tasks when working with content for IRM enabled content types: In Microsoft Outlook, when users attach ApplicationXtender content to an e mail, the option Restrict access to sensitive information is displayed. By selecting this option, users can e mail a protected version of the content as an attachment rather than the original content. In Microsoft Word/Excel/PowerPoint, when users open an ApplicationXtender document element from the repository, the ribbon button Protect Element is displayed. Users can protect and save a local copy of the document by clicking the button. Note: The IRM server does not support protecting documents in Office 2007 and 2010 format, for example,.docx,.xlsx, and so on. As a result, AXO does not provide protection for these documents. The following sections describe these capabilities in more detail. Exporting protected ApplicationXtender content Once an Office document is opened from the ApplicationXtender repository, a new tab, AppXtender, is added to the Office ribbon. This tab allows users to perform ApplicationXtender functions on the document. If IRM is enabled for the ApplicationXtender application (content type), the ribbon button EMC ApplicationXtender for Microsoft Office, Concepts Guide 35

36 AXO add in functionality Protect Element on the AppXtender tab is enabled; otherwise this button is greyed out. When enabled, this button allows users to apply IRM protection to an Office document that has been retrieved from the ApplicationXtender repository by AXO. Users can then save the protected copy on their local machine. The original ApplicationXtender document in the repository is not changed. Figure 9. Microsoft Word add in with IRM protection Once a user has chosen to protect the current document by using IRM, AXO determines whether the document has been changed. If so, AXO prompts the user to specify whether to protect the modified (local) version of the document or the server version of the document. If the user chooses to protect the modified document, the modified document is saved to the ApplicationXtender repository first. When the Protect Option dialog box appears, users apply an IRM policy to the document by choosing from a list of policies created by an administrator on the IRM Server. Each policy specifies who can access the content, the actions they can perform on it, and how long they can access it. Users can also modify the default access control for the selected policy and specify the output directory folder for the exported document by using this dialog box. A sample Protect Option dialog box is shown in Figure 10, page EMC ApplicationXtender for Microsoft Office, Concepts Guide

37 AXO add in functionality Figure 10. Protect option dialog box E mailing protected ApplicationXtender content Users can also e mail protected ApplicationXtender content from an AXO add in for Microsoft Outlook. Figure 11, page 38 shows the user interface changes required in order to provide IRM functionality to e mail an ApplicationXtender document as an attachment in Microsoft Outlook. EMC ApplicationXtender for Microsoft Office, Concepts Guide 37

38 AXO add in functionality Figure 11. Attachment Property dialog box User interface elements that support IRM functionality The following table identifies the status of the user interface elements to support IRM functionality. IRM Protection Option (AppGen) Restrict the access to exported document (checkbox status) Office button (Print, Save as, Send) Disabled Hidden Enabled Disabled Optional Enabled Enabled Enabled Required Checked and disabled (mandatory protection) Disabled Ribbon button (Protect Element) Enabled For more information The following table lists the documentation that provides more information on IRM support. For information on Understanding ApplicationXtender specific restrictions for IRM and high level tasks for enabling IRM protection for ApplicationXtender content Refer to ApplicationXtender Release Notes and ApplicationXtender Concepts and Planning Guide 38 EMC ApplicationXtender for Microsoft Office, Concepts Guide

39 AXO add in functionality For information on Installing and configuring the IRM Server Creating and managing IRM users and groups, including the account ApplicationXtender uses to connect to the IRM Server Defining IRM policies for ApplicationXtender Enabling IRM Services for ApplicationXtender Refer to IRM Server Installation Guide for Windows IRM Server Administrator s Guide IRM Server Administrator s Guide ApplicationXtender Core Components Administrator s Guide Publishing Office documents to ApplicationXtender AXO provides configuration work items that allow end users to publish Microsoft Office documents to the ApplicationXtender repository without exiting the Microsoft Office application. You can configure documents to be saved as new ApplicationXtender documents, document revisions, elements, or element versions. Publish feature, page 70 provides a sample user interface. Browsing content for a website AXO provides the ability to open any web page in a browser window within a supported Microsoft Office application. For example, you can configure the browser feature to display the home page of the company website. Browser feature, page 71 provides a sample user interface. Submitting ApplicationXtender content to a business process AXO provides an integration with ApplicationXtender Workflow Manager that lets users submit ApplicationXtender documents to a business process from within an AXO OBA. When you use a Result Set work item in a business use case XML file for a workflow enabled content type, AXO adds a context menu item named Start Business Process to the context menu that appears when users right click the selected document in the Result Set View. In addition, each predefined business process displays as a sub menu under Start Business Process. By clicking one of the business processes on the menu, users can start the selected document on that business process. The new option displays only if workflow is enabled for the ApplicationXtender application (content type) in ApplicationXtender Application Generator. No additional XML configuration is necessary to provide workflow functionality for a content type. Figure 12, page 40, illustrates the Start Business Process option on the context menu for the Result Set. In the sample dialog box, three business processes are defined for the content type associated with the selected document: process 1, process 2, and process 3. EMC ApplicationXtender for Microsoft Office, Concepts Guide 39

40 AXO add in functionality Figure 12. Start Business Process context menu Deleting ApplicationXtender documents/document containers The AppXtender tab of the ribbon provides options for managing document containers. Users can delete the following content by using these options: A document container (ApplicationXtender document) A document container version (ApplicationXtender document revision) A document container element (ApplicationXtender page) An element version from a document container The following figure shows a sample ApplicationXtender ribbon with these options. 40 EMC ApplicationXtender for Microsoft Office, Concepts Guide

41 AXO add in functionality Figure 13. AppXtender ribbon The Modify tab of the WPF Viewer work item provides options for managing document container elements, as shown in the following figure. Figure 14. Modify tab Viewing ApplicationXtender content in the Windows Presentation Foundation Viewer, page 33 provides more information on the WPF Viewer component, and the EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides detailed configuration information for the WPF Viewer. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides detailed configuration information for document containers and documents. Microsoft Outlook Explorer functionality Microsoft Outlook 2010 Explorer includes a ribbon. The AXO add in functionality for Microsoft Outlook 2007 Explorer varies from that provided for the other supported Microsoft Office 2007 and 2010 applications because the Explorer window uses a different user interface model. For example, the Office ribbon is not available in the Explorer 2007 window. AXO functionality for Outlook Explorer 2007 includes the ability to: Query ApplicationXtender documents by using the ApplicationXtender Outlook folder View an ApplicationXtender result set by using the ApplicationXtender Outlook folder Export Microsoft Outlook item types (e mail and/or e mail attachments, appointments, meeting requests, or contacts) to ApplicationXtender Outlook specific features, page 72 provides more information for both Outlook 2010 and Outlook Ribbon based log viewing and configuration AXO has ribbon options that allow viewing and configuration of AXO logs from within Microsoft Office applications (Word, Excel, PowerPoint, and Outlook). EMC ApplicationXtender for Microsoft Office, Concepts Guide 41

42 AXO add in functionality Ribbon options in Word, Excel, and PowerPoint, for AXO logging The Add Ins tab in the Office Ribbon now includes selections for setting up AXO logging, as shown in the following screen image. The options are: View Log: Click this button to open the AXO log file. Open Log Folder: Click this button to open the folder that contains the AXO log file. Severity dropdown list: Click this button to change the current Severity Filter of the AXO logging system. AXO Logging Settings: Click this button to display the AXO Logging Settings dialog, which controls logging defaults. The AXO Logging Settings dialog presents options for setting logging defaults. 42 EMC ApplicationXtender for Microsoft Office, Concepts Guide

43 AXO add in functionality The options are: Enable File Listener: This checkbox causes log information to be written to the log file specified in the Log File Name option. If this option is left unchecked, then log information will not be collected. Enable Event Log Listener: When this checkbox is checked, the AXO log information will be written as a Windows event log, and the user can view the event logs via the Windows Event Viewer. Log File Name: Enter the filename that you want to use for the log file. The default is Message.log, and the default path is determined by the application (Word, Excel, PowerPoint, or Outlook) in use when you opened the logging settings dialog. The path for the AXO Excel log is shown. To edit the path for Word or PowerPoint or Outlook, you must access this screen from the ribbon within the corresponding application. Severity Filter: You can set the default level of events to be logged using this dropdown list. The options are: All: Allows all events to be logged. Off: Does not allow any events to be logged. Critical: Allows only critical events to be logged. Error: Allows critical and error events to be logged. Warning: Allows critical, error, and warning events to be logged. Information: Allows critical, error, warning, and information events to be logged. Verbose: Allows critical, error, warning, information, and verbose events to be logged. Activity Tracing: Allows critical, error, warning, information, verbose, and activity tracing events to be logged. When selected, the trace events selected in the Trace outputs list are logged. Trace outputs: Items selected for this option are logged when Activity Tracing is selected in the Severity Filter option. Ribbon options in Outlook for AXO logging The AXO logging options within Microsoft Outlook are accessed from the ribbon (for Outlook 2010, and from the menu (for Outlook 2007), as shown in the following screens. The options are the same as described previously for the Microsoft Office Applications. AXO ribbon options for logging in Outlook 2010: EMC ApplicationXtender for Microsoft Office, Concepts Guide 43

44 AXO add in functionality AXO ribbon options for logging in Outlook 2007: 44 EMC ApplicationXtender for Microsoft Office, Concepts Guide

45 Chapter 4 Licensing and Security This chapter includes the following sections: Licensing considerations, page 45 Planning and implementing security, page 45 Enabling automatic login, page 47 The ApplicationXtender for Microsoft Office software module requires an AXO license. Consult your EMC price guide for the appropriate model number to purchase the license. Licensing considerations When a user is running multiple Microsoft Office applications simultaneously, AXO allows the applications to share the same ApplicationXtender Web Services session and, consequently, the same license. Each time users log in to an AXO add in, they consume an ApplicationXtender seat license by creating an ApplicationXtender Web Services session. Because users often leave Microsoft Office applications open for extended periods of time (for example, Outlook), ApplicationXtender licenses could be tied up and unavailable for use by other users. To avoid this problem, you can configure the add in to automatically log a user out of an ApplicationXtender Web Services session. After logout, consumed Web Services licenses are released back into the pool of licenses. You can also configure a warning to users that they will be logged out automatically if they remain inactive for a configurable amount of time. The add in configuration section of the EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides more information. Planning and implementing security AXO add in modules use the security that is already in place for existing ApplicationXtender data sources (stores). Planning for and implementing ApplicationXtender security includes the following tasks: Configuring authentication and selecting a security provider Granting access privileges to end users EMC ApplicationXtender for Microsoft Office, Concepts Guide 45

46 Licensing and Security This guide provides a brief overview of security. The EMC ApplicationXtender Concepts and Planning Guide provides additional planning information for security and to the EMC ApplicationXtender Core Components Administrator s Guide provides procedures for implementing security. Configuring authentication and selecting a security provider Authentication requires all users to log in to a system bt using a valid username and password, which ensures that each user is who he or she claims to be. You configure authentication credentials and select a security provider for each data source by using ApplicationXtender Admin. ApplicationXtender Admin offers two pre packaged security providers: Windows integrated security This security provider enables users to log in to an AXO add in using the credentials from their current Windows session. You can allow users to log in to the add in automatically or by reentering their Windows credentials in the login dialog box. CM security This security provider requires that users log in to an AXO add in using an ApplicationXtender user name and password. You can also use other security models supported by ApplicationXtender, for example, a directory service security provider that uses LDAP. The Security Providers section of the EMC ApplicationXtender Concepts Guide provides more information, as does the Implementing Security section of the EMC ApplicationXtender Core Components Administrator s Guide. Granting access privileges to end users Another aspect of security is authorization, which is the granting of specific access privileges according to the user name. Security profiles contain information pertaining to a user s specific privileges within the ApplicationXtender content management system. Security profiles are configured from within the ApplicationXtender Application Generator (ApplicationXtender AppGen) module, following standard user and group security rules. ApplicationXtender AppGen offers three levels of security (application, functional, and document) to prevent unauthorized users from gaining access to sensitive information stored in the ApplicationXtender content management system. 46 EMC ApplicationXtender for Microsoft Office, Concepts Guide

47 Licensing and Security Enabling automatic login AXO provides the capability for end users to access different ApplicationXtender stores without having to log in to ApplicationXtender multiple times. You configure automatic login for an ApplicationXtender store in one of two ways depending on the security model used by the store: In an ApplicationXtender environment that uses a Windows integrated security model, you can configure the AXO add in to allow the end user to log in to ApplicationXtender by using the current user credentials. In an ApplicationXtender environment that uses a non Windows security model, you can configure the AXO add in to allow the end user to save ApplicationXtender login credentials. The credentials are encrypted and saved in the user s Windows setting folder. The saved login credentials can be used in any AXO add in and Microsoft Office application that runs on behalf of the user. You can also configure an add in to allow the user to log in again as a different ApplicationXtender user and either save or not save the newly provided credentials. Automatic login is configured by using the AXO Login work item. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides configuration details for the Login work item. EMC ApplicationXtender for Microsoft Office, Concepts Guide 47

48 Licensing and Security 48 EMC ApplicationXtender for Microsoft Office, Concepts Guide

49 Chapter 5 Designing the add in This chapter describes how to plan for and design an AXO add in. It includes the following sections: Components of an add in, page 49 Design considerations, page 49 Basic XML for an AXO add in, page 50 User interface produced by the example add in XML file, page 51 Components of an add in The add in is an XML file that integrates ApplicationXtender content management functionality with a supported Microsoft Office 2007 or 2010 application. You can configure an AXO add in to provide basic ApplicationXtender content management functionality (login, open from ApplicationXtender, scanning and inserting from a scan, and publish to ApplicationXtender, ) directly from the Office menu. Optionally, you can configure one or more business use cases for an add in, each of which is designed to address a particular business solution. Chapter 6, Configuring a Business Use Case provides more information. Design considerations Before configuring an AXO add in for Microsoft Office, decide whether users require basic access to ApplicationXtender content management functionality or a custom business solution. Consider the following: The business group or set of users that requires the functionality provided by the add in Identify the department or user group that requires the ability to a Microsoft Office application in conjunction with ApplicationXtender content management functionality. The specific business process or task to be solved Identify the goal that users are trying to achieve and which supported Microsoft Office application requires the add in. The functionality required to support the business process or task EMC ApplicationXtender for Microsoft Office, Concepts Guide 49

50 Designing the add in Identify which ApplicationXtender content management and Microsoft Office features are required by users. Chapter 3, AXO add in functionality provides more information. The ApplicationXtender store and content type required to support the add in functionality Identify which store and content type the add in requires and create them by using ApplicationXtender, if necessary. Basic XML for an AXO add in AXO provides basic example add in solutions for each supported Microsoft Office application. The following example XML represents the AXTOWordAddIn.xml file in the C:\Program Files\ApplicationXtender\AXO\Configurations\Basic\Word install directory, which defines the basic add in for Microsoft Word. You could also use this XML file without modification for Microsoft Excel and PowerPoint add ins as well; duplicate XML files are supplied in their respective install directories. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides a description of the basic example XML for Microsoft Outlook. The example add in configuration file shown below adds menu commands for basic ApplicationXtender content management functionality (open, publish, scan if a scanner driver is installed, and login) to the Microsoft Office 2007 Button menu, and the Microsoft Office 2010 File menu. Note the XML elements in bold text below in the file text below. The add in also provides access to two business use cases from the Office File menu: AXO Features and Basic Content Management. Chapter 6, Configuring a Business Use Case shows the basic example XML for an AXO business use case. Note: Indentation and line breaks shown in the example XML files in this document are not necessary in the XML file, but have been added to show the logical structure. <?xml version="1.0"?> <AXTOWordAddIn Version="2.0" xmlns=" <BusinessUseCases ShowMenu="true"> <BusinessUseCase id="axtofeatures" Version="2.0"> <DisplayName>AXO Features</DisplayName> <Description>Demonstrates some of AXO's features</description> <Image>AXTO_AxLogoRed</Image> </BusinessUseCase> <BusinessUseCase id="basiccontentmanagement" Version="2.0"> <DisplayName>Basic Content Management</DisplayName> <Description>A prototype out of the box Business Application</Description> <Image>AXTO_AxLogoBlueBorder</Image> </BusinessUseCase> </BusinessUseCases> <ApplicationXtenderServerUrl> <SessionTimeout>60</SessionTimeout> <OpenOptions Allow="true" /> <PublishOptions Allow="true" /> <EnableScan>true</EnableScan> <LoginOptions ShowMenu="true"> <Store Name="AppXtenderDEMO" IntegratedSecurity="false" /> </LoginOptions> </AXTOWordAddIn> 50 EMC ApplicationXtender for Microsoft Office, Concepts Guide

51 Designing the add in User interface produced by the example add in XML file The basic example XML for the add in for Word adds commands to the Microsoft Office 2010 File menu (or to the Office 2007 Button menu) to enable users to access basic ApplicationXtender content management functionality: Open, Publish. Login, and Business applications. The example XML file for this add in connects to the AppXtenderDemo store on the ApplicationXtender server. Figure 15, page 51. Figure 15. Microsoft Office 2010 File menu After the user logs in to the ApplicationXtender store, the example add in enables the Open and Publish commands, as shown in and Figure 18, page 54, respectively. EMC ApplicationXtender for Microsoft Office, Concepts Guide 51

52 Designing the add in Figure 16. Microsoft Office 2010 file menu after login When users select the Open from EMC ApplicationXtender command, AXO displays a dialog box by the same name, as shown in Figure 17, page 53. This dialog box allows users to search the ApplicationXtender repository, locate a document, and open the document from within Office. Users can specify desired search criteria for an ApplicationXtender query or execute a saved query without viewing the search criteria. 52 EMC ApplicationXtender for Microsoft Office, Concepts Guide

53 Designing the add in Figure 17. Microsoft Office 2010: open from EMC ApplicationXtender dialog box EMC ApplicationXtender for Microsoft Office, Concepts Guide 53

54 Designing the add in The Publish to EMC ApplicationXtender command allows users to index and save Microsoft Office documents to ApplicationXtender. Users can choose to save an Office document to the repository as a new document, a replacement element, a new element, or a new element version. Figure 18. Microsoft Office 2010: Publish to EMC ApplicationXtender dialog box When users successfully open or publish a document by using the Open or Publish commands, respectively, the add in adds an AppXtender tab to the user interface. This tab provides options for saving and checking out ApplicationXtender documents. 54 EMC ApplicationXtender for Microsoft Office, Concepts Guide

55 Configuring a Business Use Case Chapter 6 This chapter provides an overview of the process for configuring an AXO business use case for Microsoft Office client applications. The chapter includes the following sections: Components of a business use case, page 55 Choosing the features for a business use case, page 83 Defining interaction between business use case features, page 84 Loading a business use case, page 85 Example XML for an AXO business use case, page 87 User interface produced by the example business use case XML file, page 91 Components of a business use case An AXO business use case is an optional configuration (XML) file that addresses a particular business solution based on an integration of ApplicationXtender content management functionality and a supported Office 2007 or 2010 application. The business use case configuration file defines how an Office application interacts with the ApplicationXtender content management system. Each business use case is comprised of the following top level components: views, ribbon, and ApplicationXtender content management features. The configuration options for these components define the appearance of the add in within the Office application. Unless otherwise noted, the screen captures presented in this chapter represent the user interface that is created by using the basic configuration files provided with AXO. You can customize these files to reflect your specific business process and ApplicationXtender environment. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides detailed information on configuration options. Views component The views component defines the properties of custom business use case view panes (referred to as task panes in Microsoft Word documentation) on the Microsoft Office application interface. You can configure a view pane to allow users to change the location or width of the view. EMC ApplicationXtender for Microsoft Office, Concepts Guide 55

56 Configuring a Business Use Case Each view contains one or more workspaces. A workspace is the area within which users perform tasks such as in to the ApplicationXtender store or running a query when using an AXO add in. A view can have unlimited workspaces; however, too many workspaces in an add in can cause the user interface to appear cluttered and unusable. You can configure one of two types of workspaces, either a standard or a tabbed workspace. As the name implies, a tabbed workspace is represented in the user interface with a named tab that identifies the purpose of the workspace. Figure 19, page 56 shows an example of a view containing a tabbed workspace with three tabs. Figure 19. View containing a tabbed workspace Workspaces, in turn, contain AXO feature work items. Feature work items provide the ApplicationXtender content management functionality in an AXO add in. ApplicationXtender content management features, page 61 provides more information. Ribbon component The ribbon is a standard Microsoft Office component that controls the actions users can perform from the Microsoft Office Fluent Ribbon. AXO provides configuration options for the ribbon to support ApplicationXtender specific functionality. These options allow you to customize the ribbon for a specific business use case. Following customization, the ribbon represents all available actions, both standard Office and ApplicationXtender specific, that a user can perform within the add in when the business use case is active. You can associate AXO feature work items with standard Microsoft Office Ribbon elements by using the business use case XML file. For example, you can configure a ribbon tab for ApplicationXtender that contains buttons for launching a query, displaying the search results, and opening ApplicationXtender documents, as shown in Figure 20, page 57. The configuration file for the basic business use case for Outlook Inspector, InspectorBusinessUseCase.xml, provides example XML. 56 EMC ApplicationXtender for Microsoft Office, Concepts Guide

57 Configuring a Business Use Case Figure 20. Example Office ribbon for Outlook Inspector You can also configure the ribbon to display entry fields for specifying search criteria, as shown in Figure 21, page 57. The example AXO file AXTOFeatures.xml described in AXO configuration files, page 24 provides example XML. Figure 21. Example Office ribbon with query entry fields Note: The basic business use case provided for Microsoft Word, Excel, and PowerPoint has a built in ribbon. When end users open an ApplicationXtender document within this business use case, an AppXtender tab providing save and version control options is added to the ribbon automatically. Therefore, the example XML that defines this business use case, BasicContentManagement.xml, does not contain the ribbon component. The following table identifies and describes the function of each Ribbon button. All of these buttons are available on ribbon defined in the basic content management XML. EMC ApplicationXtender for Microsoft Office, Concepts Guide 57

58 Configuring a Business Use Case Ribbon element Save Save As Replace Element New Revision New Element Version New Document Edit/Read only Check Out/Check In Undo Check Out View Document Versions View Element Versions Delete Document Delete Document Version Delete Element Delete Element Version Document Information Protect Document Description Save the document to ApplicationXtender Choose a document format to save locally Replace an element in an existing ApplicationXtender document Update revision numbers Save to ApplicationXtender as a new version of the current element Save to ApplicationXtender as a new document Lock/Unlock the currently opened ApplicationXtender document Check out/check in the currently opened document Undo the current check out View the currently opened ApplicationXtender document versions View the currently opened ApplicationXtender document element versions Delete the document from ApplicationXtender, including all versions Delete the latest document version from ApplicationXtender Delete the document element from ApplicationXtender Delete the latest version of the document element from ApplicationXtender ApplicationXtender version information for the currently opened document Protect the document by using EMC Documentum IRM Services for ApplicationXtender The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides ApplicationXtender specific configuration information. See also the Microsoft documentation for standard Office Ribbon configuration information. If you installed the AXO Visual Studio Add In, you can design AXO ribbons using the Visual Ribbon Designer. This designer leverages the Windows Presentation Foundation (WPF) ribbon. The WPF ribbon follows the Microsoft Office Fluent user interface and provides components to build an Office style ribbon. Launch the AXO ribbon designer from the context menu for a ribbon.xml file in a BusinessUseCase project. The online help for the designer provides more information. 58 EMC ApplicationXtender for Microsoft Office, Concepts Guide

59 Configuring a Business Use Case Dynamic ribbon elements example code AXO supplies example XML code for including ribbon elements for content types, query types, and so on. The supported COBI objects are ContentType and Query, in either a gallery, combo, or drop down. The AXTOFeatures.xml files in each of the subdirectories of C:\Program Files\ApplicationXtender\AXO\Configurations\Basic contain the example code. Now OBA developers do not need to hand code all the ContentTypes/queries/ and so on into the ribbon XML, and changes in the Content Management system can automatically be reflected in the client add ins. The example code is shown here: <group id="dynamicitems" label="dynamic Items"> <dropdown id="axto_ctdropdown" label="select ContentType To Query" extension="documentcontainer AppXtenderDemo"> <Events> <Event Name="OnClick"> <PerformAction Action="ShowNewQueryByContentType" Target="AXTOFeatures.QueryWorkItem"> </PerformAction> </Event> </Events> </dropdown> <gallery id="axto_querygallery" label="select Saved Query" extension="query AppXtenderDemo HR"> <Events> <Event Name="OnClick"> <PerformAction Action="ExecuteQueryByName" Target="AXTOFeatures.QueryWorkItem"> </PerformAction> </Event> </Events> </gallery> </group> If the attribute extension has been set, AXO will handle this ribbon code as a built in ribbon element, and users clicking an item of this element will trigger the defined event. The value of extension attribute will match the following format: [ContentTypeClass] [StoreName] [ContentTypeName] Some valid configurations are: DocumentContainer AppXtenderDemo All valid content types in AppXtenderDemo store Query AppXtenderDemo HR All valid queries in HR content type in AppXtenderDemo store DocumentContainer All valid content types in all logged in stores Query AppXtenderDemo All valid queries in AppXtenderDemo store The AXTOFeatures.xml business use case configuration file includes the configuration of these built in AXO ribbon elements. EMC ApplicationXtender for Microsoft Office, Concepts Guide 59

60 Configuring a Business Use Case Figure 22. Dynamic ribbon elements 60 EMC ApplicationXtender for Microsoft Office, Concepts Guide

61 Configuring a Business Use Case ApplicationXtender content management features End users interact with ApplicationXtender by using AXO work items. The business use case contains work items that support the following ApplicationXtender content management features: Login feature, page 61 Query feature, page 62 Result Set feature, page 64 Document properties feature, page 67 Document container view feature, page 68 Web Access feature, page 69 AXO also provides common features a Publish feature and a Browser feature that can be used with Word, Excel, and PowerPoint. Publish feature, page 70 and Browser feature, page 71 provide more information. In addition to ApplicationXtender content management features and common features, AXO provides features specific to Microsoft Outlook, as described in Outlook specific features, page 72. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides more information. Login feature The Login feature allows end users to log in to the ApplicationXtender content management system from within a Microsoft Office application. You can define multiple Login work items for a business use case, each of which is associated with a different ApplicationXtender store. You can configure login properties for each store such as layout style for the Login dialog box, security settings, and the user interface that displays following successful login. You can also specify whether users are logged out of the store automatically as soon as they close the associated business use case. To Login: In Office 2007, click the Microsoft Office Button and then select Login > the ApplicationXtender Store name. In Office 2010, click File > AppXtender and select Login. Figure 23, page 62 illustrates a sample user interface for logging in to the ApplicationXtender content management system. EMC ApplicationXtender for Microsoft Office, Concepts Guide 61

62 Configuring a Business Use Case Figure 23. Login dialog box The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides more information. Query feature The Query feature allows end users to search the ApplicationXtender repository. This feature supports the same query functionality that is available in ApplicationXtender Desktop. For example, users can search for documents by using both ApplicationXtender document properties (index values) and common properties such as Title, Subject, or Author. Users can also use full text search and logical operators. The ApplicationXtender Document Manager User s Guide provides detailed information on performing queries. Figure 24, page 63 illustrates sample user interface for querying content in an ApplicationXtender repository. Note that ApplicationXtender properties appear in all uppercase characters on the Query tab while common document properties appear in mixed case. As shown in the illustration, AXO provides client side field validation for search criteria fields, including tooltips that identify the required data type for each field. 62 EMC ApplicationXtender for Microsoft Office, Concepts Guide

63 Configuring a Business Use Case Figure 24. Query dialog box You can configure the add in to use values from Microsoft Office documents as search criteria for a query. Using template or form data as input to a query, page 64 provides more information. You can also allow users to perform a query from the Office Ribbon rather than using the query dialog box. EMC ApplicationXtender for Microsoft Office, Concepts Guide 63

64 Configuring a Business Use Case Defining queries AXO add ins support multiple ways of defining queries. The method you use depends on several factors including how much control you want to give users to modify the query. For example, you can configure a Query dialog box in the business use case that allows users to change properties (index values) before they run the query. You can even specify which properties users are able to change. Alternatively, you can allow users to run a predefined query from the Office Ribbon without displaying the search criteria. You can configure the business use case XML to display the following types of ApplicationXtender queries: A new (blank) query A predefined query A saved query that users can modify You can also allow users to save modified queries to ApplicationXtender for either public or private use. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides information on configuring ApplicationXtender queries using AXO. Using template or form data as input to a query AXO leverages the use of standard templates or forms as input into an ApplicationXtender Document Query. You can provide search criteria for a query from Microsoft Office documents by using: Outlook item properties, such as the subject line of a mail item An Outlook form A Word template or form Cell data in an Excel spreadsheet AXO s use of standard Microsoft Office templates and forms to supply data for queries means that users do not have to learn how to use ApplicationXtender. Instead, they are able to use their existing knowledge of the standard form to execute a search. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides information on configuring queries to use template or form data. Result Set feature The Result Set feature allows end users to view ApplicationXtender query results from within a Microsoft Office application. You can configure properties for the result set, such as layout style, orientation, default visible columns, and default column headers and sort order. Figure 25, page 65 illustrates a sample Result Set View configured to display entries in a grid layout. 64 EMC ApplicationXtender for Microsoft Office, Concepts Guide

65 Configuring a Business Use Case Figure 25. Result Set view: grid layout Figure 26, page 66 illustrates a sample Result Set View configured to display entries in vertical columns (tree view). If users add index fields to the Result Set View by using the (Customize) button, the tree view is not wide enough to display the additional fields. In this case, the symbol appears next to each entry in the result set, indicating that additional properties are available. For example, in the following illustration, expanding the symbol displays the additional fields MIDDLE INIT and JOB CODE below each entry. Tooltips identify the data that is displayed in the additional fields. EMC ApplicationXtender for Microsoft Office, Concepts Guide 65

66 Configuring a Business Use Case Figure 26. Result Set view: vertical layout The user interface allows end users to customize the result set as follows: Add, move, hide, remove, and rename columns Dynamically filter the list of documents based on selected index field Filter results based on custom filter criteria Perform client side sorting on one or multiple columns. (Note: This action takes place on the user machine; it does not re query the database.) Show the full metadata for the document selected in the view as a separate view Toggle the Result Set View between visual and hidden states Display a thumbnail for each document entry in the list If you enable end user customizations for a business use case, users can save their changes to their local machine for future sessions. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides information on configuring Result Set Views. 66 EMC ApplicationXtender for Microsoft Office, Concepts Guide

67 Configuring a Business Use Case Document properties feature The Document Properties feature, displayed by right clicking a document in the result set and selecting View Properties, allows end users to view document container properties (index values, including multiple indexes) and common properties, depending on the configuration you specify. ApplicationXtender index properties appear in all uppercase characters on the Properties tab; common document properties appear in mixed case. Figure 27, page 67 illustrates a sample user interface for viewing document properties. Figure 27. Document properties You can also configure the Document Properties feature to display elements for an ApplicationXtender document container. Figure 28, page 68 illustrates a sample user interface for viewing document elements. Click Views to determine how the document elements are displayed. The current view shows Thumbnails. EMC ApplicationXtender for Microsoft Office, Concepts Guide 67

68 Configuring a Business Use Case Figure 28. Document elements Document container view feature The Document Container View feature allows end users to view ApplicationXtender document containers that are in a non Office format from within a Microsoft Office application. After running an ApplicationXtender query from the add in, users select a document container to view from the Result Set View. The add in renders the document by using the <RenderMode> defined in the business use case XML file: PDF, XPS, or Web Access browser. Figure 29, page 69 illustrates a sample user interface for viewing document containers in PDF mode. 68 EMC ApplicationXtender for Microsoft Office, Concepts Guide

69 Configuring a Business Use Case Figure 29. Document container view The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides more information. Web Access feature The Web Access feature allows end users to view ApplicationXtender content in a Web Access browser window within Microsoft Office. You can configure the Web Access browser window to display ApplicationXtender search criteria, query results, and document content. If the end user has already logged in to the store using the AXO add in, the Web Access browser shares the session rather than requiring the user to log in again. The EMC ApplicationXtender Web Access User s Guide provides information on performing end user tasks in the Web Access browser window. Note: When users work with workbooks in an AXO add in for Microsoft Excel, Excel attempts to keep the cursor focus on the workbook in the user interface rather than on the fields in the Web Access browser window. As a result, it is recommended that you avoid using the Web Access feature when configuring AXO add ins for Microsoft Excel. Alternatively, users can close or minimize the active Excel workbook before attempting to input values in the Web Access browser window fields. EMC ApplicationXtender for Microsoft Office, Concepts Guide 69

70 Configuring a Business Use Case Publish feature The Publish feature allows end users to publish Microsoft Office documents to the ApplicationXtender repository. You can allow users to save Office documents as new ApplicationXtender documents, replacement elements, new elements, or new element versions. For new elements, users can choose how to attach the element to the existing ApplicationXtender document: append as the last element, prepend as the first element, or insert as a specific element number. To publish an Office document: In Office 2007, click the Microsoft Office Button, and then select Publish > ApplicationXtender. In Office 2010, click File > AppXtender > Publish. Figure 30, page 70 illustrates a sample user interface for publishing Office documents to ApplicationXtender. Figure 30. Publish to ApplicationXtender: Save options After specifying how the document should be saved, the user chooses the content type and specifies values for document properties, which are used to index the document in ApplicationXtender. Required fields are shown in bold text. AXO provides client side field validation for property fields, including tooltips that identify the required data type for each property, as shown in Figure 31, page EMC ApplicationXtender for Microsoft Office, Concepts Guide

71 Configuring a Business Use Case Figure 31. Publish to ApplicationXtender: Document properties AXO presents scan results in the WPF viewer. The scan tab in the document viewer contains a Publish Document button that you can use to publish the results of the scan to ApplicationXtender. Browser feature The Browser feature allows end users to view a web page in a browser window within Microsoft Office. For example, you can configure the browser feature to display the home page of the company website. Figure 32, page 72 illustrates a sample user interface for viewing website content in a browser window within Microsoft Office. EMC ApplicationXtender for Microsoft Office, Concepts Guide 71

72 Configuring a Business Use Case Figure 32. Browser feature The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides more information. Outlook specific features AXO provides the following Outlook specific features: Outlook Explorer, page 72 Outlook inspector, page 82 These features are described in the following sections. Outlook Explorer AXO provides the following features for Outlook Explorer: Browse ApplicationXtender documents feature, page 72 Export Microsoft Outlook items to ApplicationXtender feature, page 76 Browse ApplicationXtender documents feature AXO provides a browsing feature that lets users search the ApplicationXtender repository and view search results within Microsoft Outlook Explorer. When users install the AXO add in for Outlook, AXO adds a predefined folder named ApplicationXtender to the Mail Folder section of the Outlook Explorer navigation pane. This folder serves as a container for ApplicationXtender queries, both predefined and/or new. You can configure the queries that display in this folder by editing the ExplorerFeatures.xml configuration file. Figure 33, page 73 illustrates a sample ApplicationXtender browsing feature in Outlook Explorer. 72 EMC ApplicationXtender for Microsoft Office, Concepts Guide

73 Configuring a Business Use Case Figure 33. Microsoft Outlook Explorer: ApplicationXtender browsing feature Note: Although the ApplicationXtender folders use the standard Outlook folder icon, they are not actually Outlook mail folders; they are not stored on the Microsoft Exchange Server. If you have enabled customizations for the business use case, end users can add queries to the ApplicationXtender folder by using: For Office 2007, Tools > Options > ApplicationXtender Browsing from the Outlook menu For Office 2010, File > AppXtender > Settings and selecting the EMC ApplicationXtender Browsing tab, as shown in Figure 34, page 74. As with all user customizations to an add in, changes are saved in a file on their local machine. Enabling customizations for a business use case, page 86 provides more information. EMC ApplicationXtender for Microsoft Office, Concepts Guide 73

74 Configuring a Business Use Case Figure 34. Outlook Explorer: ApplicationXtender browsing settings Tip: You can use this Outlook user interface rather than configuring the browsing feature in the XML file. The following browser options are available: Thin View: If checked, the query results are displayed in the Web Access thin client mode. Otherwise query results are displayed in the Web Access interactive client mode. Search All Revisions: If checked, the query searches all revisions of documents in the specified content type. Otherwise, the query searches the current revision of documents in the specified content type. Add Query: Click this option to add a query. After adding a query, you can right click the EMC ApplicationXtender folder (in Figure 33, page 73) and select Refresh. The new query will then appear in the Explorer reading pane. When users open the EMC ApplicationXtender folder (in Figure 33, page 73), the display shows the list of ApplicationXtender queries that users can access. Selecting for a query in the list or 74 EMC ApplicationXtender for Microsoft Office, Concepts Guide

75 Configuring a Business Use Case double clicking the highlighted row displays query results in a Web Access browser window, as shown in Figure 35, page 75. Figure 35. Outlook browsing: query results Selecting in the Outlook folder view displays the criteria associated with the selected query, as shown in Figure 36, page 75. Figure 36. Outlook browsing: query criteria The Outlook Explorer features section of the EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides more information. EMC ApplicationXtender for Microsoft Office, Concepts Guide 75

76 Configuring a Business Use Case Insert from scan feature If scan is enabled, a new Ribbon element is added into the Outlook Explorer ribbon for inserting a scanned image. Figure 37. Scan button on the Outlook ribbon The scanned image can be inserted into the current , meeting, appointment, or contact. Export Microsoft Outlook items to ApplicationXtender feature AXO provides an export feature that lets users export Outlook items (mail, appointments, meeting requests, and contacts) from the Outlook Explorer window to ApplicationXtender. The basic add in for Outlook includes configuration for the ApplicationXtender export feature. The add in creates an Outlook folder named AutoUploadToAX, as shown in Figure 38, page 77. This folder is configured to copy Outlook mail attachments to the ApplicationXtender content type SCRIPTS in the AppXtenderDEMO store. Because the configuration specifies that the folder is monitored, attachments in the folder are uploaded to the document repository automatically. 76 EMC ApplicationXtender for Microsoft Office, Concepts Guide

77 Configuring a Business Use Case Figure 38. Microsoft Outlook Explorer: ApplicationXtender export feature (automatic move) The basic add in also configures the Inbox folder to copy Outlook messages and attachments to the SCRIPTS content type. However, because the basic configuration for the Inbox folder specifies that the folder is not monitored, users would have to copy Outlook items from the Inbox to ApplicationXtender manually, as shown in Figure 39, page 78. EMC ApplicationXtender for Microsoft Office, Concepts Guide 77

78 Configuring a Business Use Case Figure 39. Microsoft Outlook Explorer: ApplicationXtender export feature (manual copy) If desired, you can modify the default configuration for the export feature by editing the ExplorerFeatures.xml configuration file. The first step is to configure upload (export) settings including the item type or types to be exported, the export format, the target ApplicationXtender store and content type, and the mapping between Outlook fields and ApplicationXtender content type properties. This mapping allows Outlook to provide values for ApplicationXtender properties when items are exported from Outlook to ApplicationXtender, which in turn allows ApplicationXtender to store items as ApplicationXtender documents. Configuring export settings also includes specifying save options for each allowed item type. For example, you can specify that each uploaded item always creates a new ApplicationXtender document. Alternatively, you can specify that, if the new document has the same index record as an existing document, the new document creates either a major or minor revision of, or is merged with, the existing document. After you configure export settings, you associate the saved settings with one or more top level personal folders in the Outlook Explorer navigation pane. Folder configuration includes specifying whether the folder should be monitored and whether items should be copied to the repository or moved. Alternatively, users can copy or move Outlook items to ApplicationXtender manually. If you have enabled customizations for the business use case, end users can configure additional export settings by using: For Outlook 2007, Tools > Options > Upload For Outlook 2010, File > AppXtender > AppXtender Options 78 EMC ApplicationXtender for Microsoft Office, Concepts Guide

79 Configuring a Business Use Case to display the Upload to ApplicationXtender tab in the Outlook Options menu, as shown in Figure 40, page 79. They can then associate the new upload configuration with an Outlook folder by using Outlook Folder Properties. As with all user customizations to an add in, user defined export settings are saved in a file on their local machine. Enabling customizations for a business use case, page 86 provides more information. Figure 40. Outlook 2007 Explorer: Upload to EMC ApplicationXtender settings EMC ApplicationXtender for Microsoft Office, Concepts Guide 79

80 Configuring a Business Use Case Figure 41. Outlook 2010 Explorer: upload to ApplicationXtender settings Tip: Rather than configuring the export to ApplicationXtender feature in the XML file, you can use the Outlook user interface as in Outlook Explorer, page 72. An alternative to mapping Outlook fields to ApplicationXtender content type properties is to index Outlook items into ApplicationXtender by using Outlook form data. In this case, AXO retrieves document properties from the fields in the Outlook form. You configure this feature by creating an ApplicationXtender content type with properties that are identical to the controls in the form. IMPORTANT: Because ApplicationXtender saves property names in uppercase characters (for example, LAST NAME), form control names must be in uppercase characters. Otherwise, the names are not considered identical. Note: AXO cannot retrieve data from built in Outlook forms. If you want to use a built in form to index Outlook items, modify the form first, then publish your custom form to Outlook using a new name. AXO supports only Outlook text box and list box form controls. In addition, AXO retrieves data only from the first page of the form. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides more information. Outlook ad hoc export feature When an Outlook folder is not configured for upload, AXO still shows the Copy & Move to ApplicactionXtender menu items. When the user first clicks on these buttons, AXO pops up the Advanced Upload setting dialog to allow the user to select options for the upload item and upload item format, as shown in the red rectangle, and disables all other inputs. 80 EMC ApplicationXtender for Microsoft Office, Concepts Guide

81 Configuring a Business Use Case Figure 42. Upload Document Setting: ad hoc configuration After the user selects the upload item and upload item message format and clicks OK, AXO saves the configuration with only the item and message format information, and with a fixed name AXO ad hoc configuration. The next time the user publishes a document, it will not pop up this dialog to let the user select again; instead, the user can go to Options to configure this ʺAXO ad hoc configuration.ʺ Then AXO will display the formal publish wizard, as shown in Figure 43, page 82. EMC ApplicationXtender for Microsoft Office, Concepts Guide 81

82 Configuring a Business Use Case Figure 43. Publish to EMC ApplicationXtender Now the user can follow the wizard step by step to select the Store and Content Type, and enter meta data for the new document or element, to finish the publishing operation. In AXO Options Upload to EMC ApplicationXtender if the name of the item is ʺAXO ad hoc configuration,ʺ all inputs are disabled except the upload item and upload item message format, so that the user can edit only these two options. Outlook inspector In addition to the functionality described in Common functionality, page 27, AXO provides an attach files feature for Outlook Inspector. This feature, which is available in the basic add in for Outlook, lets users attach an ApplicationXtender document to a new or reply e mail. After performing a query in Outlook Inspector, users select the desired document from the result set and select Attach. They then choose to attach the entire document or specify a page range. Other configuration options, such as selecting the rendering format (either PDF or XPS) are also available. Figure 44, page 83 illustrates a sample user interface for the ApplicationXtender attach files feature in Outlook Inspector. 82 EMC ApplicationXtender for Microsoft Office, Concepts Guide

83 Configuring a Business Use Case Figure 44. Outlook inspector: Attaching an ApplicationXtender document to an e mail If desired, you can modify the default configuration for the attach files feature by editing the InspectorBusinessUseCase.xml file. The Outlook Inspector features section of the EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides more information. The Outlook Inspector also provides the ability to save Outlook items to ApplicationXtender. This feature, which is provided in the basic add in for Outlook, is configured by using the export feature described in Export Microsoft Outlook items to ApplicationXtender feature, page 76. The InspectorBusinessUseCase.xml file provides example XML. Choosing the features for a business use case The XML for AXO work items determines the appearance of the user interface elements and their associated behavior. Default user interface elements and their associated behavior are defined in the example business use case. Each user interface element is associated with a different type of business work item, which has its own set of XML attributes and elements. You can customize the user interface elements by adding, modifying, or deleting the XML for business work items, as EMC ApplicationXtender for Microsoft Office, Concepts Guide 83

84 Configuring a Business Use Case desired, in the copy of the business use case example file. Alternatively, you can configure some AXO features, such as the browsing and export features for Outlook Explorer, by using the user interface. Browse ApplicationXtender documents feature, page 72 and Export Microsoft Outlook items to ApplicationXtender feature, page 76 provide more information. Many work item components can be reused across different business use cases/add ins. For example, you could create a single layout for an ApplicationXtender document container view by using the ApplicationXtender Document Container View work item and reuse it in multiple Microsoft Word add ins by copying the associated XML into each business use case. IMPORTANT: Identifiers for shared feature configurations must be unique across all business use cases. The Enabling customizations for a business use case, page 86 provides recommendations on creating unique names for AXO work items. Defining interaction between business use case features An important step in configuring a business use case involves identifying which feature work items (user interface elements) should be included in the business use case and defining the interaction that should occur between them. Feature work items interact with one another by using configurable events. Work items initiate events, which in turn trigger actions. Every action must specify a target, which identifies the work item upon which the action will be performed. You can also pass data from one work item to another, either as a literal string or as a named piece of data. When you configure an action to pass data, you specify that the results of the action should be stored as a specific name. You can then configure another work item to act on the named data. An example of work item interaction that you must configure for each business use case is the interaction between the Query and Result Set View work items. Because the goal is to pass query results from the Query work item to the Result Set View work item for display, the Query work item always saves query results as a named piece of data, QueryResults. This allows you to pass the results to a target work item that you have defined in the business use case XML file. In the example XML below, the Query work item named BasicContentManagement.QueryWorkItem initiates the event OnQueryComplete after the search query completes. This event triggers two actions: show view and show result (ignore the first one for purposes of this example). The ShowResult action displays the result set in the target BasicContentManagement.ResultSetWorkItem, which is defined in the Result Set work item section of the business use case XML file Refer to the bold text in the example below:. <QueryWorkItem id="basiccontentmanagement.queryworkitem" version="2.0" Workspace="QueryWorkspace"> <Events> <Event Name="OnQueryComplete"> <PerformAction Action="ShowView"> <Argument id="view" Source="Literal">BottomView</Argument> </PerformAction> <PerformAction Action="ShowResult" Target="BasicContentManagement.ResultSetWorkItem"> <Argument Source="WorkItemData" id="queryresults" /> </PerformAction> </Event> </Events> <QueryDefinition LogicalOperation="And"> 84 EMC ApplicationXtender for Microsoft Office, Concepts Guide

85 Configuring a Business Use Case <Store>AppXtenderDEMO</Store> <ContentType>HR</ContentType> <FullTextSearch FullTextSearchOp="AllWords" DefaultValue="" EnableThesaurus="true" /> </QueryDefinition> </QueryWorkItem> <WpfViewerWorkItem id="basiccontentmanagement.wpfviewerworkitem" Version="2.0"> <WindowMode>Modeless</WindowMode> </WpfViewerWorkItem> <ResultSetWorkItem id="basiccontentmanagement.resultsetworkitem" version="2.0" Workspace="ResultsWorkspace">..... </ResultSetWorkItem> In summary, named data is passed from the Query work item to the Result Set work item in this way: The work item initiating the event is BasicContentManagement.QueryWorkItem. The event is OnQueryComplete. The action is ShowResult. The target is BasicContentManagement.ResultSetWorkItem. As with all other business use case configuration, you configure the interaction between work items in the business use case XML file by using XML attributes and elements. AXO provides a predefined set of valid events and actions for work items. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides more information. Loading a business use case When you configure an add in, you can define a default business use case that opens automatically when users launch the Microsoft Office application/add in. If you need to configure more than one business use case for an add in, you can configure the Microsoft Office Button (for Office 2007), or by using the Office 2010 File > ApplicationXtender backstage, to display the additional business use cases. Each time a user launches a different business use case, the preceding business use case closes. The add in refreshes the user interface, including the Microsoft Office Ribbon, to reflect the configuration defined in the XML file for the new business use case. You can also configure a business use case to load automatically based on a Microsoft Office document or template, by specifying the name of the business use case as the value for a custom property in the Office application. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system provides more information. EMC ApplicationXtender for Microsoft Office, Concepts Guide 85

86 Configuring a Business Use Case Enabling customizations for a business use case You can control whether end users have the ability to modify default user interface settings for a business use case by using the DisableCustomizations attribute for the BusinessUseCase element in the business use case XML file. Setting this attribute to false allows users to save any changes they made to the user interface for the business use case, such as query or result set preferences. When a user closes the business use case or exits the Microsoft application, custom changes are saved in one or more files on the user s local machine. The location for custom files, which is referred to as the user s personal configuration cache, depends on the user s operating system: For Windows 2003/XP machines, custom files are saved in C:\Documents and Settings\<username>\Application Data\ApplicationXtender\AXTO. For Windows Vista/Windows 7 machines, custom files are saved in C:\Users\<username>\AppData\Roaming\ ApplicationXtender\AXTO. In addition to allowing users to save customizations to a business use case, setting the DisableCustomizations tag to false lets you configure AXO features for Outlook Explorer using the Outlook user interface rather than the XML configuration file. Outlook Explorer, page 72 provides more information. IMPORTANT: If you customize an Outlook business use case by using the Outlook user interface, ensure that you copy the contents of the custom XML files in your personal configuration cache and replace the relevant sections in the base XML configuration file before generating and deploying the Outlook add in to users. Understanding the importance of configuration versioning If you have enabled customizations for a business use case, as described in Enabling customizations for a business use case, page 86, be aware that configuration files in the user s personal configuration cache are always loaded before the base configuration XML files provided in the AXO deployment package. If you subsequently redeploy the add in package, only the base configuration XML files are updated on the user s machine. This means that, even if you make changes in your business use case (for example, renaming a store in a Login work item), if users previously saved their credentials, a saved copy of the old version of the Login work item with the old store name resides in their personal configuration cache. Because the configuration is loaded from the personal configuration cache first, the updates to the base configuration files are ignored when the business use case is loaded. You can avoid version conflicts such as this by using configuration versioning whereby you assign a version number to each business use case and each work item in the XML file. The AXO configuration service checks the version number when it loads configuration items to ensure that old versions of configuration XML that may exist in an end user s personal configuration cache are ignored after updating the deployment package. To use configuration versioning, you must declare the new version of the updated business use case in two places before redeploying your deployment package. First, update your business use case 86 EMC ApplicationXtender for Microsoft Office, Concepts Guide

87 Configuring a Business Use Case XML to reflect the new version. Then update your add in configuration to specify the version of the business use case you want to load. The Technical Notes section of the EMC ApplicationXtender for Microsoft Office Release Notes provides more information. Specifying unique identifiers for shared features Identifiers for shared feature configurations must be unique across all business use cases. Otherwise, custom files can be overwritten when users work with multiple business use cases. For example, if a user modifies the login configuration for business use case A and subsequently modifies the login configuration for business use case B, the configuration for business use case A is overwritten if both Login work items have the same identifier. One recommendation for ensuring unique identifiers is to prepend the name of the business use case to the ID of each feature work item in the XML file. For example, the BasicContentManagement.xml file for the basic Word add in prepends BasicContentManagement. to the ID of each work item. The period character (.) serves as a path separator. When a user modifies a work item in this business use case, the add in creates a BasicContentManagement directory in the user s personal configuration cache and places the custom XML file there. In this example, if a user opens the Basic Content Management business use case from the Word add in and selects the Save Credentials option on the Login dialog box, a file named LoginWorkItem.xml is created in the BasicContentManagement directory. Saving the file in this way ensures that it will not overwrite the login file for any other business use case. Example XML for an AXO business use case The following example XML defines an AXO business use case that you can use with any supported Microsoft Office application. This example business use case, (BasicContentManagement.xml), which is installed with AXO, is configured to use CM security and is designed to work with the AppXtenderDEMO store. It allows users to perform a full text search of the HR content type in the ApplicationXtender repository based on the following document properties: Last name First name Hire date Employee ID Documents that meet the search criteria are displayed in the Results view within Word. By default, the search results display eight documents per page and are sorted in descending order based on last name. Because end user customizations are enabled for this business use case, users can modify the default settings specified in the business use case and save their changes to a custom XML file on their local machine for future sessions. From the Result Set View, users can view a non Office document or open an Office document, as appropriate, by using a context menu. All ApplicationXtender supported documents can be opened EMC ApplicationXtender for Microsoft Office, Concepts Guide 87

88 Configuring a Business Use Case in the WPF Viewer. Non Office documents can also be rendered in PDF format in a new window within Word. Figure 45, page 91 illustrates the user interface associated with this example business use case. AXO configuration files, page 24 provides a list of configuration files that you can use for demonstration purposes or as models for creating your own add in solutions. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help that is installed with AXO provides detailed configuration information. Note: Indentation and line breaks shown in the example XML files in this document are not necessary in the XML file, but have been added to show the logical structure. Some line endings have been broken to fit the text to the page. <?xml version="1.0" encoding="utf 8"?> <BusinessUseCase xmlns=" id="basiccontentmanagement" OfficeApplication="Word Excel Outlook PowerPoint" Version="2.0" DisableCustomizations="false"> <Views> <View id="leftview" Dock="left" Width="280" Caption="Content Management"> <TabWorkspace id="lefttabworkspace"> <Tab Caption="Login" id="logintab"> <Workspace id="loginworkspace" Dock="top" Height="220" /> </Tab> <Tab Caption="Query" id="querytab"> <Workspace id="queryworkspace" Dock="fill" /> </Tab> <Tab Caption="Properties" id="propertiestab"> <Workspace id="propertiesworkspace" Dock="fill" /> </Tab> </TabWorkspace> </View> <View id="bottomview" InitiallyVisible="false" Dock="bottom" Height="225" Caption="Results"> <Workspace id="resultsworkspace" Dock="fill" /> </View> </Views> <WorkItems> <DocumentPropertiesWorkItem id="basiccontentmanagement.properties" Workspace="PropertiesWorkspace" Version="2.0"> <Events> <Event Name="OnElementDoubleClicked"> <PerformAction Action="OpenDocument"> <Argument Source="WorkItemData" id="selectedelement"/> </PerformAction> </Event> </Events> <DocumentElements Visible="true"> <ContextMenu> <MenuItem Label="Open in Office" Image="FileOpen"> <PerformAction Action="OpenDocument"> <Argument Source="WorkItemData" id="selectedcontentitem" /> </PerformAction> </MenuItem> <MenuItem Label="Open in WPF Viewer" Image="GroupPresentationViews"> <PerformAction Action="ShowWpfViewer" Target="BasicContentManagement. WpfViewerWorkItem"> <Argument Source="WorkItemData" id="selectedcontentitem" /> </PerformAction> </MenuItem> </ContextMenu> </DocumentElements> <DocumentProperties Visible="true"> <ShowStatus>true</ShowStatus> 88 EMC ApplicationXtender for Microsoft Office, Concepts Guide

89 Configuring a Business Use Case <ShowIndexProperties>true</ShowIndexProperties> <ShowCommonProperties>true</ShowCommonProperties> <ReadOnly>false</ReadOnly> </DocumentProperties> </DocumentPropertiesWorkItem> <DocumentContainerViewWorkItem id="basiccontentmanagement.dcvcontrol" Version="2.0"> <RenderMode>PDF</RenderMode> <ShowIn>NewWindow</ShowIn> <Layout> <PdfMode> <ShowScrollbars>true</ShowScrollbars> <ShowToolbar>true</ShowToolbar> <ViewMode>Default</ViewMode> <PageMode>Default</PageMode> <LayoutMode>TwoColumnLeft</LayoutMode> <Zoom>50.0</Zoom> </PdfMode> </Layout> </DocumentContainerViewWorkItem> <LoginWorkItem id="basiccontentmanagement.loginworkitem" Version="2.0" Workspace="LoginWorkspace"> <Events> <Event Name="OnLoginSuccess"> <PerformAction Action="SelectTab"> <Argument id="tab" Source="Literal">QueryTab</Argument> </PerformAction> </Event> </Events> <Store Name="AppXtenderDEMO" IntegratedSecurity="false"> <AutoLogin>false</AutoLogin> <AllowPasswordSaving>true</AllowPasswordSaving> </Store> <Layout Visible="true"> <ShowStore>true</ShowStore> </Layout> </LoginWorkItem> <QueryWorkItem id="basiccontentmanagement.queryworkitem" Version="2.0" Workspace="QueryWorkspace"> <Events> <Event Name="OnQueryComplete"> <PerformAction Action="ShowView"> <Argument id="view" Source="Literal">BottomView</Argument> </PerformAction> <PerformAction Action="ShowResult" Target="BasicContentManagement. ResultSetWorkItem"> <Argument Source="WorkItemData" id="queryresults" /> </PerformAction> </Event> </Events> <QueryDefinition LogicalOperation="And"> <Store>AppXtenderDEMO</Store> <ContentType>HR</ContentType> <FullTextSearch FullTextSearchOp="AllWords" DefaultValue="" EnableThesaurus="true" /> </QueryDefinition> </QueryWorkItem> <WpfViewerWorkItem id="basiccontentmanagement.wpfviewerworkitem" Version="2.0"> <WindowMode>Modeless</WindowMode> </WpfViewerWorkItem> <ResultSetWorkItem id="basiccontentmanagement.resultsetworkitem" Version="2.0" Workspace="ResultsWorkspace"> <Events> <Event Name="OnResultDoubleClicked"> <PerformAction Action="OpenDocument"> <Argument Source="WorkItemData" id="selectedresult" /> EMC ApplicationXtender for Microsoft Office, Concepts Guide 89

90 Configuring a Business Use Case </PerformAction> </Event> <Event Name="OnGridViewSelected"> <PerformAction Action="ChangeViewDock"> <Argument Source="Literal" Name="Dock">Bottom</Argument> <Argument Source="Literal" Name="View">BottomView</Argument> </PerformAction> </Event> <Event Name="OnVerticalViewSelected"> <PerformAction Action="ChangeViewDock"> <Argument Source="Literal" Name="Dock">Right</Argument> <Argument Source="Literal" Name="View">BottomView</Argument> </PerformAction> </Event> </Events> <Store>AppXtenderDEMO</Store> <ContentType>HR</ContentType> <ShowThumbnail>true</ShowThumbnail> <ShowEntries>false</ShowEntries> <ResultsPerPage>8</ResultsPerPage> <ShowStatus>true</ShowStatus> <Fields> <Field Name="LastName"> <AssociatedProperty Name="LAST NAME" ContentType="HR" /> </Field> <Field Name="FirstName"> <AssociatedProperty Name="FIRST NAME" ContentType="HR"/> </Field> <Field Name="HireDate"> <AssociatedProperty Name="HIRE DATE" ContentType="HR"/> </Field> <Field Name="EmployeeID"> <AssociatedProperty Name="EMPLOYEE ID" ContentType="HR"/> </Field> </Fields> <Layout> <Columns> <Column SortOrder="Descending" Header="Last" Field="LastName" Width="100" SortPriority="0" Visible="true" /> <Column Header="First" Field="FirstName" Width="100" Visible="true" /> <Column Header="ID" Field="EmployeeID" Width="100" Visible="false" /> <Column Header="Hired" Field="HireDate" Width="100" Visible="false" /> </Columns> </Layout> <ContextMenu> <MenuItem Label="Open in Office" Image="FileOpen"> <PerformAction Action="OpenDocument"> <Argument Source="WorkItemData" id="selectedresult" /> </PerformAction> </MenuItem> <MenuItem Label="Open in WPF Viewer" Image="GroupPresentationViews"> <PerformAction Action="ShowWpfViewer" Target="BasicContentManagement. WpfViewerWorkItem"> <Argument Source="WorkItemData" id="selectedresult" /> </PerformAction> </MenuItem> <MenuItem Label="Open as PDF" Image="FileOpen"> <PerformAction Action="ShowDocument" Target="BasicContentManagement.DCVControl"> <Argument Source="WorkItemData" id="selectedresult" /> </PerformAction> </MenuItem> <MenuItem Label="Show Properties" Image="PropertySheet"> <PerformAction Action="ShowView"> <Argument id="view" Source="Literal">LeftView</Argument> </PerformAction> 90 EMC ApplicationXtender for Microsoft Office, Concepts Guide

91 Configuring a Business Use Case <PerformAction Action="SelectTab"> <Argument id="tab" Source="Literal">PropertiesTab</Argument> </PerformAction> <PerformAction Action="ShowProperties" Target="BasicContentManagement. Properties"> <Argument Source="WorkItemData" id="selectedcontentitem"/> </PerformAction> </MenuItem> </ContextMenu> </ResultSetWorkItem> </WorkItems> </BusinessUseCase> User interface produced by the example business use case XML file Figure 45, page 91 illustrates the user interface produced by the BasicContentManagement.xml business use case XML file for Word. Figure 45. Basic business use case for Microsoft Word EMC ApplicationXtender for Microsoft Office, Concepts Guide 91