EMC ApplicationXtender forMicrosoft Ofﬁce...EMC® ApplicationXtender®forMicrosoft Ofﬁce Release6.512010Update— ConceptsGuide P/N300010584 A02 EMCCorporation CorporateHeadquarters:

EMC®

ApplicationXtender® for MicrosoftOffice

Release 6.51— 2010 Update

Concepts Guide

P/N 300010584A02

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748‑91031‑508‑435‑1000www.EMC.com

Copyright© 2008‑2010 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 changewithout notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONSOR WARRANTIES OF ANY KINDWITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLYDISCLAIMS 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.

Table of Contents

Preface ................................................................................................................................. 9

Chapter 1 Introduction to AXO .................................................................................... 11What is AXO?................................................................................................... 11Who can use AXO? ........................................................................................... 12Office Business Application developers.......................................................... 12IT workers ................................................................................................... 12Knowledge workers...................................................................................... 13

AXO terminology and concepts ......................................................................... 13

Chapter 2 Architectural Overview ................................................................................ 17AXO components ............................................................................................. 17AXO setup program ..................................................................................... 17AXO Visual Studio Add‑In............................................................................ 18

AXO architecture.............................................................................................. 20Configuration and deployment process: basic method .................................... 20Configuration and deployment process: AXO Visual StudioAdd‑In utility ............................................................................................... 22

AXO configuration files .................................................................................... 24Configuration files for Microsoft Word........................................................... 24Configuration files for Microsoft Excel ........................................................... 25Configuration files for Microsoft PowerPoint .................................................. 25Configuration files for Microsoft Outlook....................................................... 26

Chapter 3 AXO addin functionality ............................................................................. 27Overview ......................................................................................................... 27Common functionality ...................................................................................... 27Launching an AXO add‑in ............................................................................ 28Logging in to an ApplicationXtender store ..................................................... 28Opening a default business use case .............................................................. 29Querying documents in the ApplicationXtender repository ............................. 29Viewing an ApplicationXtender result set for a predefined query .................... 30Viewing document properties and indexes..................................................... 30Scan a paper document and publish it to ApplicationXtender.......................... 30Viewing ApplicationXtender documents/document containerswithin Microsoft Office ................................................................................. 31Opening ApplicationXtender documents/document containerswithin Microsoft Office ............................................................................. 32Viewing ApplicationXtender content in a Web Access browser.................... 32Viewing ApplicationXtender content in the WindowsPresentation Foundation Viewer................................................................ 33

Working with document and element versions ............................................... 34Protecting ApplicationXtender content by using EMCDocumentum IRM Services for ApplicationXtender........................................ 35Exporting protected ApplicationXtender content ....................................... 35

EMC ApplicationXtender for Microsoft Office, Concepts Guide 3

Table of Contents

E‑mailing protected ApplicationXtender content ....................................... 37User interface elements that support IRM functionality ............................... 38For more information................................................................................ 38

Publishing Office documents to ApplicationXtender ....................................... 39Browsing content for a website ...................................................................... 39Submitting ApplicationXtender content to a business process.......................... 39Deleting ApplicationXtender documents/document containers........................ 40

Microsoft Outlook Explorer functionality ........................................................... 41Ribbon‑based log viewing and configuration...................................................... 41Ribbon options in Word, Excel, and PowerPoint, for AXO logging ................... 42Ribbon options in Outlook for AXO logging................................................... 43

Chapter 4 Licensing and Security ................................................................................ 45Licensing considerations ................................................................................... 45Planning and implementing security.................................................................. 45Configuring authentication and selecting a security provider .......................... 46Granting access privileges to end users .......................................................... 46

Enabling automatic login .................................................................................. 47

Chapter 5 Designing the addin ................................................................................... 49Components of an add‑in.................................................................................. 49Design considerations ....................................................................................... 49Basic XML for an AXO add‑in ........................................................................... 50User interface produced by the example add‑in XML file .................................... 51

Chapter 6 Configuring a Business Use Case ............................................................... 55Components of a business use case .................................................................... 55Views component ......................................................................................... 55Ribbon component ....................................................................................... 56Dynamic ribbon elements – example code ...................................................... 59ApplicationXtender content management features.......................................... 61Login feature............................................................................................ 61Query feature ........................................................................................... 62Defining queries ................................................................................... 64Using template or form data as input to a query ..................................... 64

Result Set feature...................................................................................... 64Document properties feature ..................................................................... 67Document container view feature .............................................................. 68Web Access feature ................................................................................... 69Publish feature ......................................................................................... 70Browser feature ........................................................................................ 71

Outlook‑specific features............................................................................... 72Outlook Explorer...................................................................................... 72Browse ApplicationXtender documents feature ...................................... 72Insert from scan feature ........................................................................ 76Export Microsoft Outlook items to ApplicationXtender feature................ 76Outlook ad hoc export feature ........................................................... 80

Outlook inspector ..................................................................................... 82Choosing the features for a business use case ..................................................... 83Defining interaction between business use case features...................................... 84Loading a business use case .............................................................................. 85Enabling customizations for a business use case ................................................. 86Understanding the importance of configuration versioning ................................. 86

4 EMC ApplicationXtender for Microsoft Office, Concepts Guide

Table of Contents

Specifying unique identifiers for shared features ................................................ 87Example XML for an AXO business use case ..................................................... 87User interface produced by the example business use case XML file..................... 91

Chapter 7 Getting Started with AXO ............................................................................ 93Creating and deploying an AXO add‑in ............................................................. 93Configuring a business use case......................................................................... 94


Table of Contents

List of Figures

Figure 1. Visual Studio Add‑In ............................................................................................ 19Figure 2. AXO configuration process: basic method .............................................................. 21Figure 3. AXO deployment process: basic method ................................................................ 22Figure 4. AXO configuration/deployment process: using the AXO Visual Studio

Add‑In............................................................................................................. 23Figure 5. The Scan menu ..................................................................................................... 31Figure 6. WPF Viewer user interface .................................................................................... 34Figure 7. AppXtender tab.................................................................................................... 34Figure 8. Modify tab ........................................................................................................... 35Figure 9. Microsoft Word add‑in with IRM protection........................................................... 36Figure 10. Protect option dialog box ...................................................................................... 37Figure 11. Attachment Property dialog box ............................................................................ 38Figure 12. Start Business Process context menu ...................................................................... 40Figure 13. AppXtender ribbon............................................................................................... 41Figure 14. Modify tab ........................................................................................................... 41Figure 15. Microsoft Office 2010 File menu............................................................................. 51Figure 16. Microsoft Office 2010 file menu after login ............................................................. 52Figure 17. Microsoft Office 2010: open from EMC ApplicationXtender dialog box .................... 53Figure 18. Microsoft Office 2010: Publish to EMC ApplicationXtender dialog box .................... 54Figure 19. View containing a tabbed workspace ..................................................................... 56Figure 20. Example Office ribbon for Outlook Inspector.......................................................... 57Figure 21. Example Office ribbon with query entry fields........................................................ 57Figure 22. Dynamic ribbon elements...................................................................................... 60Figure 23. Login dialog box................................................................................................... 62Figure 24. Query dialog box.................................................................................................. 63Figure 25. Result Set view: grid layout................................................................................... 65Figure 26. Result Set view: vertical layout .............................................................................. 66Figure 27. Document properties ............................................................................................ 67Figure 28. Document elements .............................................................................................. 68Figure 29. Document container view ..................................................................................... 69Figure 30. Publish to ApplicationXtender: Save options.......................................................... 70Figure 31. Publish to ApplicationXtender: Document properties ............................................. 71Figure 32. Browser feature .................................................................................................... 72Figure 33. Microsoft Outlook Explorer: ApplicationXtender browsing feature ......................... 73Figure 34. Outlook Explorer: ApplicationXtender browsing settings ....................................... 74Figure 35. Outlook browsing: query results ........................................................................... 75Figure 36. Outlook browsing: query criteria........................................................................... 75


Table of Contents

Figure 37. Scan button on the Outlook ribbon ........................................................................ 76Figure 38. Microsoft Outlook Explorer: ApplicationXtender export feature

(automatic move).............................................................................................. 77Figure 39. Microsoft Outlook Explorer: ApplicationXtender export feature (manual

copy) ............................................................................................................... 78Figure 40. Outlook 2007 Explorer: Upload to EMC ApplicationXtender settings....................... 79Figure 41. Outlook 2010 Explorer: upload to ApplicationXtender settings................................ 80Figure 42. Upload Document Setting: ad‑hoc configuration .................................................... 81Figure 43. Publish to EMC ApplicationXtender ...................................................................... 82Figure 44. Outlook inspector: Attaching an ApplicationXtender document to an e‑mail ............ 83Figure 45. Basic business use case for Microsoft Word ............................................................ 91


Table of Contents

List of Tables

Table 1. Terminology: comparison of ApplicationXtender to Microsoft Office ....................... 14Table 2. Microsoft Word basic configuration files ................................................................ 24Table 3. Microsoft Word out–of–the–box configuration files ................................................. 25Table 4. Microsoft Excel basic configuration files ................................................................. 25Table 5. Microsoft Excel out‑of‑the‑box configuration files ................................................... 25Table 6. Microsoft PowerPoint basic configuration files........................................................ 25Table 7. Microsoft PowerPoint out‑of‑the‑box configuration files.......................................... 26Table 8. Microsoft Outlook basic configuration files............................................................. 26Table 9. Microsoft Outlook out–of–the–box configuration files ............................................. 26


Preface

This guide describes EMC® ApplicationXtender for Microsoft Office concepts and providesinformation on how to plan for an implementation. In this guide, the product nameApplicationXtender for Microsoft Office is referred to as AXO.

The screen captures in the AXO documentation are examples and may vary from the actual productscreens.

Intended audienceThis guide is intended for business application architects, designers, or developers who areresponsible for using the AXO software to create custom business solutions for their users byintegrating ApplicationXtender content management functionality with Microsoft Office 2007 and2010 client applications. The guide is also intended to assist IT administrators who are responsible forplanning 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 MicrosoftOffice systems.

In addition to this guide, the documentation set for EMC ApplicationXtender for Microsoft Officeincludes:

• 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 helpsystem from the Windows Start menu.

Revision historyThe following changes have been made to this document.


Preface

Revision date Description

May 2010 Initial publication

December 2010 Updated to include support for Microsoft Office 2010


Chapter 1Introduction to AXO

This chapter introduces the EMC ApplicationXtender for Microsoft Office (AXO) software. Itdescribes the purpose of AXO, identifies the intended users, and introduces terminology andconcepts. 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 tointegrate 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 userinterface of Microsoft Office. AXO supports and extends the concept of OBAs by providing a set ofcomponents and tools to develop add‑in software solutions for ApplicationXtender integrationwith Microsoft Office.

AXO provides:

• Access to core ApplicationXtender functionality from within supported Microsoft Office clientapplications

• Custom business solutions based on ApplicationXtender that minimize end‑user operationsfor 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 supportedMicrosoft Office applications. In addition, you can configure an add‑in to provide highly customizedfunctionality by using one or more business scenarios, or business use cases. A business use casesupports a specific business process or activity performed by end users. The goal is to customize eachsolution to support only tasks required to complete a specific business activity, thereby reducing thenumber of end‑user actions required to perform routine operations.


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 typespecific. You can use these add‑in solutions with minimal configuration or create new solutions usingAXO configuration components. AXO also provides example business use case configuration filesthat you can modify for your use. AXO configuration files, page 24 provides a list of example filesprovided 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 performtheir jobs.

Office Business Application developers

OBA developers are responsible for customizing the AXO components to create add‑in solutionsfor specific user groups and Microsoft Office applications. The primary customization task involvesdesigning and configuring business use cases based on business process or user needs. AXO providesexample business use case configuration files that you can modify for your use. The content ofthe configuration files determines the appearance and behavior of ApplicationXtender functionsinside Office applications.

For example, as an OBA developer, you could design a business application solution for MicrosoftWord that allows users to complete weekly status reports using aWord template. After users completethe status reports, they would publish them to the ApplicationXtender repository for historicalpurposes. During the configuration process for this solution, you would include only user interfaceelements that support the creation and submission of status reports. By customizing the solution tosupport 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 moreinformation.

IT workers

IT workers and OBA developers use the AXO functionality to create AXO add‑in solutions for Officefor deployment to various work groups within the company. Add‑in solutions are generated usingboth 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 distributionusing either the company’s website or network file share. This implementation strategy allows OBAdevelopers to perform a centralized customization that can be distributed from a single location as


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 updatesautomatically, thereby resolving potential update and upgrade issues.

In some companies, the tasks of the OBA developer and IT worker may be performed by the sameperson.

The EMC ApplicationXtender for Microsoft Office Deployment Guide provides details on deployingAXO add‑in solutions.

Knowledge workers

Microsoft Office application end users, who are generally knowledge workers or business officers, usethe customized functionality delivered by AXO add‑in solutions to perform routine and ad hoc tasksrequired by their business operations. They use ApplicationXtender functions that are integratedinto Office applications and customized for a specific business activity. These users may performthe 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 contentmanagement 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 conceptsThe AXO software and documentation introduces common content management terminology. InAXO, an ApplicationXtender data source is referred to as a store, an ApplicationXtender applicationis referred to as a content type, and an ApplicationXtender document is referred to as a documentcontainer. The term ApplicationXtender repository is synonymous with store.

AXO uses Microsoft Office terminology for document‑related items rather thanApplicationXtender‑specific terminology because end users may not be familiar withApplicationXtender. 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 PDFsor other file formats.


Introduction to AXO

Table 1. Terminology: comparison of ApplicationXtender to Microsoft Office

ApplicationXtenderterm/concept

ComparableMicrosoft Officeterm/concept

Description in ApplicationXtender

Document None A file or group of files stored in anApplicationXtender application and identifiedby index information. Each page of anApplicationXtender document is a single object,such as a scanned image file or a word processingdocument. Each ApplicationXtender documentis a combination of objects, each stored as a pagewithin the document. For instance, a documentfor a hospital patient might include scannedadmission forms, a doctor’s report in MicrosoftWord format, and an x‑ray image file. A singleApplicationXtender document can contain onepage or thousands of pages.

In AXO, a document container holds elements,which can be either Microsoft Office documents orpages of other document formats.

Page Microsoft Officedocument or a singlepage of anotherdocument format(for example, PDF)

A single object or entity, such as a scannedimage file or a word processing document.ApplicationXtender supports multiple objecttypes in a document. A page can come from oneof many different sources. For example, a verylong word processing file is considered a page byApplicationXtender. A page could also be a singlescanned image, a 30‑minute video clip, or an audiorecording.

When you create a document in ApplicationXten‑der, the object added as the new document is thefirst page of that document. Up to 250,000 pagescan be attached to a document. The same indexrecord is attached to all of the pages (objects) in asingle ApplicationXtender document.

In AXO, an ApplicationXtender page is referredto as an element. Each Office document is a singlepage/element.


Introduction to AXO

ApplicationXtenderterm/concept

ComparableMicrosoft Officeterm/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 informationpertaining to documents can be stored. This groupof field definitions is used by ApplicationXtenderwhen storing index information within anapplication.

In AXO, ApplicationXtender index propertiesare referred to as document properties. Microsoftdocument properties, formerly called ODMAproperties, are referred to as common properties inAXO.

Because AXO relies on Microsoft technology, you should also be familiar with the following Microsoftterminology:• Office Business Applications (OBAs)

An Office Business Application (OBA) is a composite application that uses applications withinthe Microsoft Office System (such as Outlook, Word, or Excel) as the front end for a Line ofBusiness (LOB) application.

Note: All new ApplicationXtender documents created from Microsoft Office 2007 and 2010applications 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 deploymenttechnology that allows you to create self‑updating Windows‑based applications that can beinstalled and run with minimal user interaction.

A ClickOnce application can be installed on an end user’s computer and run locally even whenthe computer is offline, or it can be run in an online‑only mode without permanently installinganything on the end user’s computer.

The EMC ApplicationXtender for Microsoft Office Deployment Guide provides more information onhow 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


Introduction to AXO

Office Open XML (commonly referred to as OOXML or OpenXML) is an XML‑based file formatspecification for electronic documents, such as spreadsheets, charts, presentations, and wordprocessing documents.


Chapter 2Architectural 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 componentsAXO components are provided in two setup programs: AXO and the optional AXO Visual StudioAdd‑In. The EMC ApplicationXtender for Microsoft Office Release Notes provides a list of softwarethat must be installed before running the AXO and AXO Visual Studio Add‑In setups. The EMCApplicationXtender for Microsoft Office Installation Guide provides installation procedures.

AXO also provides tools that allow OBA developers to localize the text in the user interface providedby AXO solutions. After signing the files containing the localized text, OBA developers submit thefiles to EMC to be signed. Upon receipt of the EMC‑signed files, OBA developers then deploy thelocalized solution. Contact your EMC representative for details about how to use the language packfeature. In addition, AXO 6.5 2010 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 andcustom user interface elements. ApplicationXtender feature work items are customizable andconfigurable user interface parts that can be used for various business use cases. You cancustomize the presentation and behavior of each ApplicationXtender work item to make itsuitable for a particular business use case. The goal is to minimize end‑user actions required toperform specific business functionality. An ApplicationXtender feature work item addresses only


Architectural Overview

user interface views while the business logic and data objects in AXO are provided through aconnection 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 fordemonstration purposes. The example add‑ins, which are designed to work with theApplicationXtender demo database, contain core ApplicationXtender content managementfunctionality. 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 itemsto 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 developingyour own custom solutions. These samples showcase the ApplicationXtender features thatare provided with AXO.

— Out‑of‑the‑box versions of all of the above, which allow going directly to a simple productionsystem 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 AXOadd‑ins at your site.

• Log tool (AXOLogsTool.exe)

Windows tool that collects log information for AXO add‑ins. Copy this file to the machine onwhich the AXO add‑in is installed, and then run it. provides more information.

AXO Visual Studio AddIn

AXO provides a graphical user interface (GUI) for creating and publishing ClickOnce packages forAXO add‑in solutions for supported Microsoft Office applications. This GUI tool, which is an add‑inpackage to Microsoft Visual Studio 2008 and 2010, standard editions, lets OBA developers configureAXO business use cases and add‑in solutions using a visual designer. It provides an alternative toconfiguring 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 MSBuildprocess

• Comments, samples, and user prompts in the XML schema

The AXO Visual Studio Add‑In also validates the configuration and provides syntax help.



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 bymaintaining a record of locations and versions of published packages.

The following figure shows the AXO Visual Studio Add‑In.

Figure 1. Visual Studio AddIn

The online help that is installed with the utility provides procedures on using the AXO Visual StudioAdd‑In. You can access the help from the Windows Start menu as well as from the Help menu inthe add‑in.

Note: As an alternative to installing and using the AXO Visual Studio Add‑In to configure andpublish AXO solution packages, you can create XML files manually by using an XML editor anddeploy the XML files by using the procedures in the EMC ApplicationXtender for Microsoft OfficeDeployment Guide. You can also import XML files into the AXO Visual Studio Add‑In by using theprocedures in the online help for the add‑in. However, AXO release 5.40 and 6.0 XML files are notsupported in AXO 6.5 due to changes in the XML configuration objects.



AXO architectureAXO uses a multi‑tier architecture in which the AXO add‑in communicates with the applicationserver by using ApplicationXtender Web Services at the back end. Therefore, ApplicationXtenderWeb Services must be installed before configuring AXO components. It is recommended that youinstall ApplicationXtender Web Access .NET, which installs ApplicationXtender Web Services inintegrated 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 softwareand hardware required for using AXO.

The AXO architecture provides components that support the tasks of configuring and deploying AXOadd‑in solutions. Two options are available for performing these tasks: using an XML editor (basicmethod) and using the AXO Visual Studio Add‑In utility (visual designer) provided by AXO. Thefollowing 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 configurationand deployment of AXO XML files. Configuring the AXO files includes specifying availablefunctionality as well as the default layout for the user interface. It also includes specifying customerApplicationXtender data, which includes the address for the ApplicationXtender Web Access Serverand the names of the ApplicationXtender stores and content types that users can access from theadd‑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 providesprocedures on configuring AXO components.

Figure 2, page 21 illustrates the AXO configuration components and demonstrates how they interactwith one another. As shown in the diagram, the OBA developer configures an AXO add‑in solutionby modifying example AXO configuration files.



Figure 2. AXO configuration process: basic method

The output of the AXO configuration process is a configured add‑in solution, which serves asinput to the AXO deployment process along with the configured deployment definition file. Thedeployment 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 Officeapplication.

Figure 3, page 22 illustrates the AXO deployment components for a basic (manual) deploymentscenario and demonstrates how they interact with one another. As shown in the diagram, the ITworker generates and deploys the add‑in solution to a location that users can access, either a websiteor network file share. Knowledge workers then navigate to this location and install the initialversion of the add‑in on their workstations. Updated add‑in packages at the deployment locationare installed on end‑user workstations automatically when users launch the associated MicrosoftOffice application. The EMC ApplicationXtender for Microsoft Office Deployment Guide provides moreinformation.



Figure 3. AXO deployment process: basic method

Configuration and deployment process: AXO VisualStudio AddIn utility

As an alternative to the basic configuration and deployment process flow, OBA developers can createand publish add‑in deployment packages by using the AXO Visual Studio Add‑In utility. Thisutility provides Visual Studio projects that can be used to develop AXO business use cases and



AXO add‑in solutions. Figure 4, page 23 illustrates the configuration and deployment process thatuses the AXO Visual Studio Add‑In utility. As the diagram indicates, the deployment process flowis slightly different from the manual AXO configuration/deployment process. For example, whenusing the add‑in to deploy AXO packages, it is not necessary for OBA developers to understand thedeployment definition file. As with the manual process, add‑in deployment packages are madeavailable to users on either a website or network file share.

Figure 4. AXO configuration/deployment process: using the AXO Visual Studio AddIn

The online help for the AXO Visual Studio Add‑In utility provides more information.



AXO configuration filesAs mentioned in AXO components, page 17, the AXO setup program installs example XMLconfiguration files. You can use these files with minimal configuration or create custom add‑insolutions for your end users.

The tables in the following sections identify the basic and out‑of‑the‑box configurationfiles for each supported Microsoft Office application as well as the directory path in whichthey are installed. The basic and out‑of‑the‑box configuration files are prototypes thatcan be adapted to your own specific needs. Additional sample XML files are installed inC:\Program Files\ApplicationXtender\AXO\Configurations\Samples.

Chapter 5, Designing the add‑in and Chapter 6, Configuring a Business Use Case provide the contentsof 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 forWord, 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 valueof AppXtenderDEMO for the repository, and ContentType (from the repository) of HR. Thisconfiguration is for demonstration and experimentation. It can be adapted to your needs if youfind it applicable.

• The Out‑of‑the‑Box configuration (ContentTypeFree.xml) does not predefine the values for Storeand ContentType, and allows users to select from dropdowns based on available repositoriesand their associated content types. After providing the AX server name in the XML file, thisconfiguration can be deployed with no further changes in a production environment. The AXODeployment 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 inC:\Program Files\ApplicationXtender\AXO\Configurations\Basic\Word.

Table 2. Microsoft Word basic configuration files

To configure this component Use this XML file

Example AXO add‑in for Microsoft Word AXTOWordAddIn.xml

Basic business use case BasicContentManagement.xml

Example business use case that demonstrates variousAXO features including a ribbon‑based query

AXTOFeatures.xml

Configuration files for the out‑of‑the‑box add‑in for Microsoft Word are located in C:\ProgramFiles\ApplicationXtender\AXO\Configurations\Out_Of_The_Box\Word.



Table 3. Microsoft Word out–of–the–box configuration files


Example AXO add‑in for Microsoft Word AXTOWordAddIn.xml

Out‑of‑the‑box business use case ContentTypeFree.xml

Configuration files for Microsoft Excel

Configuration files for the basic add‑in for Microsoft Excel are located inC:\Program Files\ApplicationXtender\AXO\Configurations\Basic\Excel.

Table 4. Microsoft Excel basic configuration files


Example AXO add‑in for Microsoft Excel AXTOExcelAddIn.xml



AXTOFeatures.xml

Configuration files for the out–of–the–box add‑in for Microsoft Excel are located in C:\ProgramFiles\ApplicationXtender\AXO\Configurations\Out_Of_The_Box\Excel.

Table 5. Microsoft Excel outofthebox configuration files


Example AXO add‑in for Microsoft Excel AXTOExcelAddIn.xml


Configuration files for Microsoft PowerPoint

Configuration files for the basic add‑in for Microsoft PowerPoint are located inC:\Program Files\ApplicationXtender\AXO\Configurations\Basic\PowerPoint.

Table 6. Microsoft PowerPoint basic configuration files


Example AXO add‑in for Microsoft PowerPoint AXTOPowerPointAddIn.xml



AXTOFeatures.xml



Configuration files for the out‑of‑the‑box add‑in for Microsoft PowerPoint are located in C:\ProgramFiles\ApplicationXtender\AXO\Configurations\Out_Of_The_Box\PowerPoint.

Table 7. Microsoft PowerPoint outofthebox configuration files


Example AXO add‑in for Microsoft PowerPoint AXTOPowerPointAddIn.xml


Configuration files for Microsoft Outlook

The configuration files for the basic add‑in for Microsoft Outlook are named differently than for theother Office applications. They also contain different information, to accommodate the differencesbetween Outlook and the other Office applications. The Outlook configuration files are located inC:\Program Files\ApplicationXtender\AXO\Configurations\Basic\Outlook.

Table 8. Microsoft Outlook basic configuration files


Example AXO add‑in for Microsoft Outlook AXTOOutlookAddIn.xml

Basic business use case for Outlook Inspector InspectorBusinessUseCase.xml

Configuration file for Outlook Explorer ExplorerFeatures.xml

Configuration files for the out–of–the–box add‑in for Microsoft Outlook are located in C:\ProgramFiles\ApplicationXtender\AXO\Configurations\Out_Of_The_Box\Outlook.

Table 9. Microsoft Outlook out–of–the–box configuration files


Example AXO add‑in for Microsoft Outlook AXTOOutlookAddIn.xml

Configuration file for Outlook Explorer ExplorerFeatures.xml


Chapter 3AXO addin functionality

This chapter provides a high‑level overview of the AXO add‑in functionality available for supportedMicrosoft 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 isinstalled with AXO provides details on configuring an add‑in.

OverviewAXO lets you create custom add‑in solutions that incorporate ApplicationXtender contentmanagement functionality into Microsoft Office‑based add‑ins. You determine both the functionalityand 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 usingan AXO add‑in. AXO gives you the flexibility to tailor each add‑in solution to a specific businessdepartment or group of users.

The remainder of this chapter provides a high‑level overview of the functionality available for AXOadd‑in solutions. The EMC ApplicationXtender for Microsoft Office Configuration Reference online helpsystem 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 coreApplicationXtender content management functionality directly from the Microsoft Office Button(for Office 2007), or from the Office 2010 File > ApplicationXtender backstage, by using the add‑inXML file. This option lets you deploy ApplicationXtender functionality with minimal configuration.Chapter 5, Designing the add‑in provides more information.

Common functionalityAXO 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 OutlookExplorer‑specific functionality.


AXO addin 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 addin

With the exception of Microsoft Outlook add‑ins, which are launched automatically when users openOutlook, 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‑relatedbutton from the ribbon, for example, Login or Business Applications. This design reduces theinitialization time for the Microsoft Office application. It is possible to configure an AXO add‑in tostart automatically, by using the <DefaultBusinessUseCase> parameter in the AXTOxxxxAddin.xmlfile, where xxxx is Word, Excel, or PowerPoint. The EMC ApplicationXtender for Microsoft OfficeConfiguration 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 contentmanagement system from within a Microsoft Office application. You can define multiple Login



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 concurrentconnections to the ApplicationXtender store with the same login credentials. This means that, whenusers launch more than one Microsoft Office application at the same time, they can use the AXOlogin 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 thesame credentials to connect to the store within Excel. Sharing a server session does not consume anadditional ApplicationXtender license.

The session sharing feature is disabled by default. To enable this feature, configure the Web Accessserver setting InterAppAxSessionSharing in the Office application configuration files provided byAXO. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help systemprovides 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 casethat opens automatically when users launch the Microsoft Office application/add‑in. You can alsoconfigure an AXO add‑in to open a business use case based on association with a Microsoft Officedocument 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 accessthe additional business use cases by using the Microsoft Office Button (for Office 2007), or byusing the Office 2010 File > ApplicationXtender backstage.. The add‑in configuration section ofthe EMC ApplicationXtender for Microsoft Office Configuration Reference online help system providesmore information.

Querying documents in the ApplicationXtenderrepository

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 searchcriteria for the query. For example, you can configure a Query dialog box that allows users to changeproperties (index values) before they run the query. You can even specify which properties users areable to change. Alternatively, you can allow users to run a predefined query from the Office ribbonwithout 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 EMCApplicationXtender for Microsoft Office Configuration Reference online help system provides moreinformation.



Viewing an ApplicationXtender result set for apredefined query

Following the execution of a document query, end users need to review, analyze, and research thelist of ApplicationXtender documents that met the specified search criteria. The AXO Result SetView function provides this capability. As with other AXO work items, you can customize theResult Set View options in advance for each business use case. For example, you can customize theResult Set View to change the orientation of the search results. Result Set feature, page 64 provides asample 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 ApplicationXtenderdocument container when users save a local copy of a Microsoft Office document/page that is part ofthat document container, the reference information is also saved as document properties in the localdocument. The reference information includes the ApplicationXtender store name, content type, anddocument container ID, among other things. Saving the reference information creates an associationbetween the ApplicationXtender document container and the local copy of the document page. Whena user opens the document from a Microsoft Office application on a machine on which AXO isinstalled, 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 documentis maintained provided new pages are not added to the ApplicationXtender document. If theassociation is broken, users can cancel the upload process or upload the local copy as a new page ofthe ApplicationXtender document.

The Reference feature is configured at the AXO add‑in solution level by using the XML tagTrackLocalDocument. The EMC ApplicationXtender for Microsoft Office Configuration Referenceonline 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 toApplicationXtender

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.



Figure 5. The Scan menu

The Scan option is also available from within the WPF Viewer in the Scan Tab. Refer to the AXOonline help for details on setting up scan functionality.

Viewing ApplicationXtender documents/documentcontainers within Microsoft Office

After end users perform a query using an AXO add‑in, they can select a document element fromthe result set for viewing. AXO provides the ability to view ApplicationXtender document pages of



different formats without exiting the Microsoft Office application. Documents can be rendered inone of the following formats:• Native Microsoft Office (for ApplicationXtender documents that are entirely in Office format).Opening ApplicationXtender documents/document containers within Microsoft Office, page32 provides details.

• Web browser by using either the ApplicationXtender Web Access thin client or IRC (InteractiveRich Client). Viewing ApplicationXtender content in a Web Access browser, page 32 providesdetails.

• Windows Presentation Foundation (WPF). Viewing ApplicationXtender content in the WindowsPresentation 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 thedocument should appear in the current workspace or in a new window. You can also allow usersto check out the document for editing rather than restricting them to viewing a read‑only versionof the document. The EMC ApplicationXtender for Microsoft Office Configuration Reference online helpsystem provides more information.

Opening ApplicationXtender documents/document containerswithin Microsoft Office

AXO provides the ability to open ApplicationXtender documents that are in Office format using theMicrosoft Office application. When end users open an Office document from the ApplicationXtenderResult 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 achecked‑out document in Office, a user can publish the document to ApplicationXtender. PublishingOffice 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 Accessbrowser window within Microsoft Office. Users can retrieve, view, and manage content fromApplicationXtender content types using this feature. Web Access feature, page 69 provides moreinformation.

Note: It is recommended that you avoid using the Web Access feature when configuring AXO add‑insfor Microsoft Excel. Web Access feature, page 69 provides more information.



Viewing ApplicationXtender content in the Windows PresentationFoundation Viewer

The Windows Presentation Foundation (WPF) image viewer provides the same functionality asApplicationXtender Desktop and Web Access for viewing document containers and elements in anAXO add‑in. The WPF Viewer provides tabs for managing the content displayed in the viewer. Userscan 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 forOCR‑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 theopened 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. Althoughdocuments scanned into the viewer are not yet published to the AX repository, the are availableto 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.



Figure 6. WPF Viewer user interface

The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system providesdetailed configuration information for the WPF Viewer.

Working with document and element versions

Users can view version control history for ApplicationXtender documents and elements by usingdocument container (ApplicationXtender document) functionality. Users can also open a page inanother document version. The AppXtender tab of the ribbon provides options for working withdocument and element versions, as shown in the following figure.

Figure 7. AppXtender tab



The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system providesdetailed configuration information for document containers and for the ribbon.

Users can also work with document container element versions (ApplicationXtender documentpages) in the WPF Viewer. TheModify tab of the WPF Viewer work item provides options forcreating and deleting document container elements and element versions, as shown in the followingfigure. 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 33provides additional description of the new WPF Viewer component. The EMC ApplicationXtender forMicrosoft Office Configuration Reference online help system provides detailed configuration informationfor the WPF Viewer.

Protecting ApplicationXtender content by using EMCDocumentum IRM Services for ApplicationXtender

AXO provides support for EMC Documentum IRM Services for ApplicationXtender. If IRMprotection is enabled for an ApplicationXtender application (content type) in ApplicationXtenderApplication Generator, AXO displays user interface elements that allow users to apply IRMprotection to ApplicationXtender content for the application. Users can perform the following taskswhen working with content for IRM‑enabled content types:• In Microsoft Outlook, when users attach ApplicationXtender content to an e‑mail, the optionRestrict access to sensitive information is displayed. By selecting this option, users can e‑mail aprotected version of the content as an attachment rather than the original content.

• In Microsoft Word/Excel/PowerPoint, when users open an ApplicationXtender document elementfrom the repository, the ribbon button Protect Element is displayed. Users can protect and save alocal copy of the document by clicking the button.

Note: The IRM server does not support protecting documents in Office 2007 and 2010 format, forexample, .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 thedocument. If IRM is enabled for the ApplicationXtender application (content type), the ribbon button



Protect Element on the AppXtender tab is enabled; otherwise this button is greyed‑out. Whenenabled, this button allows users to apply IRM protection to an Office document that has beenretrieved from the ApplicationXtender repository by AXO. Users can then save the protected copy ontheir local machine. The original ApplicationXtender document in the repository is not changed.

Figure 9. Microsoft Word addin with IRM protection

Once a user has chosen to protect the current document by using IRM, AXO determines whether thedocument 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 protectthe 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 choosingfrom a list of policies created by an administrator on the IRM Server. Each policy specifies whocan access the content, the actions they can perform on it, and how long they can access it. Userscan also modify the default access control for the selected policy and specify the output directoryfolder for the exported document by using this dialog box. A sample Protect Option dialog box isshown in Figure 10, page 37.



Figure 10. Protect option dialog box

Emailing protected ApplicationXtender content

Users can also e‑mail protected ApplicationXtender content from an AXO add‑in for MicrosoftOutlook. Figure 11, page 38 shows the user interface changes required in order to provide IRMfunctionality to e‑mail an ApplicationXtender document as an attachment in Microsoft Outlook.



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 ProtectionOption (AppGen)

Restrict the access toexported document(checkbox status)

Office button (Print,Save as, Send)

Ribbon button(Protect Element)

Disabled Hidden Enabled Disabled

Optional Enabled Enabled Enabled

Required Checked anddisabled (mandatoryprotection)

Disabled Enabled

For more information

The following table lists the documentation that provides more information on IRM support.

For information on Refer to

Understanding ApplicationXtender‑specificrestrictions for IRM and high‑level tasks forenabling IRM protection for ApplicationXtendercontent

ApplicationXtender Release Notes andApplicationXtender Concepts and Planning Guide



For information on Refer to

Installing and configuring the IRM Server IRM Server Installation Guide for Windows

Creating and managing IRM users and groups,including the account ApplicationXtender usesto connect to the IRM Server

IRM Server Administrator’s Guide

Defining IRM policies for ApplicationXtender IRM Server Administrator’s Guide

Enabling IRM Services for ApplicationXtender ApplicationXtender Core ComponentsAdministrator’s Guide

Publishing Office documents to ApplicationXtender

AXO provides configuration work items that allow end users to publish Microsoft Office documentsto the ApplicationXtender repository without exiting the Microsoft Office application. You canconfigure 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 MicrosoftOffice application. For example, you can configure the browser feature to display the home page ofthe company website. Browser feature, page 71 provides a sample user interface.

Submitting ApplicationXtender content to a businessprocess

AXO provides an integration with ApplicationXtender Workflow Manager that lets users submitApplicationXtender documents to a business process from within an AXO OBA. When you use aResult Set work item in a business use case XML file for a workflow‑enabled content type, AXO addsa context menu item named Start Business Process to the context menu that appears when usersright‑click the selected document in the Result Set View. In addition, each predefined businessprocess displays as a sub‑menu under Start Business Process. By clicking one of the businessprocesses on the menu, users can start the selected document on that business process. The newoption displays only if workflow is enabled for the ApplicationXtender application (content type)in ApplicationXtender Application Generator. No additional XML configuration is necessary toprovide workflow functionality for a content type.

Figure 12, page 40, illustrates the Start Business Process option on the context menu for the ResultSet. In the sample dialog box, three business processes are defined for the content type associatedwith the selected document: process 1, process 2, and process 3.



Figure 12. Start Business Process context menu

Deleting ApplicationXtender documents/documentcontainers

The AppXtender tab of the ribbon provides options for managing document containers. Users candelete 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.



Figure 13. AppXtender ribbon

TheModify tab of the WPF Viewer work item provides options for managing document containerelements, as shown in the following figure.

Figure 14. Modify tab

Viewing ApplicationXtender content in the Windows Presentation Foundation Viewer, page 33provides more information on the WPF Viewer component, and the EMC ApplicationXtender forMicrosoft Office Configuration Reference online help system provides detailed configuration informationfor the WPF Viewer.

The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system providesdetailed configuration information for document containers and documents.

Microsoft Outlook Explorer functionalityMicrosoft Outlook 2010 Explorer includes a ribbon. The AXO add‑in functionality for MicrosoftOutlook 2007 Explorer varies from that provided for the other supported Microsoft Office 2007 and2010 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 OutlookExplorer 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, meetingrequests, or contacts) to ApplicationXtender

Outlook‑specific features, page 72 provides more information for both Outlook 2010 and Outlook2007.

Ribbonbased log viewing and configurationAXO has ribbon options that allow viewing and configuration of AXO logs from within MicrosoftOffice applications (Word, Excel, PowerPoint, and Outlook).



Ribbon options in Word, Excel, and PowerPoint, forAXO logging

The Add‑Ins tab in the Office Ribbon now includes selections for setting up AXO logging, as shownin 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 AXOlogging system.

• AXO Logging Settings: Click this button to display the AXO Logging Settings dialog, whichcontrols logging defaults.

The AXO Logging Settings dialog presents options for setting logging defaults.



The options are:• Enable File Listener: This checkbox causes log information to be written to the log file specifiedin the “Log File Name” option. If this option is left unchecked, then log information will not becollected.

• Enable Event Log Listener: When this checkbox is checked, the AXO log information will bewritten as a Windows event log, and the user can view the event logs via the Windows EventViewer.

• 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) inuse when you opened the logging settings dialog. The path for the AXO Excel log is shown. Toedit the path for Word or PowerPoint or Outlook, you must access this screen from the ribbonwithin 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 tracingevents to be logged. When selected, the trace events selected in the Trace outputs list arelogged.

• Trace outputs: Items selected for this option are logged when Activity Tracing is selected in theSeverity 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 sameas described previously for the Microsoft Office Applications.

AXO ribbon options for logging in Outlook 2010:



AXO ribbon options for logging in Outlook 2007:


Chapter 4Licensing 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 yourEMC price guide for the appropriate model number to purchase the license.

Licensing considerationsWhen a user is running multiple Microsoft Office applications simultaneously, AXO allows theapplications to share the same ApplicationXtender Web Services session and, consequently, thesame license.

Each time users log in to an AXO add‑in, they consume an ApplicationXtender seat license bycreating an ApplicationXtender Web Services session. Because users often leave Microsoft Officeapplications open for extended periods of time (for example, Outlook), ApplicationXtender licensescould be tied up and unavailable for use by other users. To avoid this problem, you can configurethe add‑in to automatically log a user out of an ApplicationXtender Web Services session. Afterlogout, consumed Web Services licenses are released back into the pool of licenses. You can alsoconfigure a warning to users that they will be logged out automatically if they remain inactive for aconfigurable amount of time.

The add‑in configuration section of the EMC ApplicationXtender for Microsoft Office ConfigurationReference online help system provides more information.

Planning and implementing securityAXO add‑in modules use the security that is already in place for existing ApplicationXtender datasources (stores). Planning for and implementing ApplicationXtender security includes the followingtasks:• Configuring authentication and selecting a security provider

• Granting access privileges to end users


Licensing and Security

This guide provides a brief overview of security. The EMC ApplicationXtender Concepts and PlanningGuide provides additional planning information for security and to the EMC ApplicationXtender CoreComponents Administrator’s Guide provides procedures for implementing security.

Configuring authentication and selecting a securityprovider

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 authenticationcredentials 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 fromtheir current Windows session. You can allow users to log in to the add‑in automatically or byreentering 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 ApplicationXtenderuser name and password.

You can also use other security models supported by ApplicationXtender, for example, adirectory service security provider that uses LDAP. The Security Providers section of the EMCApplicationXtender Concepts Guide provides more information, as does the Implementing Securitysection 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 privilegesaccording to the user name. Security profiles contain information pertaining to a user’s specificprivileges within the ApplicationXtender content management system. Security profiles areconfigured fromwithin the ApplicationXtender Application Generator (ApplicationXtender AppGen)module, following standard user and group security rules. ApplicationXtender AppGen offers threelevels of security (application, functional, and document) to prevent unauthorized users from gainingaccess to sensitive information stored in the ApplicationXtender content management system.



Enabling automatic loginAXO provides the capability for end users to access different ApplicationXtender stores withouthaving to log in to ApplicationXtender multiple times. You configure automatic login for anApplicationXtender 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, youcan configure the AXO add‑in to allow the end user to log in to ApplicationXtender by usingthe current user credentials.

• In an ApplicationXtender environment that uses a non‑Windows security model, you canconfigure 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 logincredentials can be used in any AXO add‑in and Microsoft Office application that runs on behalfof the user.

You can also configure an add‑in to allow the user to log in again as a different ApplicationXtenderuser and either save or not save the newly‑provided credentials.

Automatic login is configured by using the AXO Login work item. The EMC ApplicationXtender forMicrosoft Office Configuration Reference online help system provides configuration details for theLogin work item.




Chapter 5Designing the addin

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 addinThe add‑in is an XML file that integrates ApplicationXtender content management functionality witha supported Microsoft Office 2007 or 2010 application. You can configure an AXO add‑in to providebasic ApplicationXtender content management functionality (login, open from ApplicationXtender,scanning and inserting from a scan, and publish to ApplicationXtender, ) directly from the Officemenu. Optionally, you can configure one or more business use cases for an add‑in, each of whichis designed to address a particular business solution. Chapter 6, Configuring a Business Use Caseprovides more information.

Design considerationsBefore configuring an AXO add‑in for Microsoft Office, decide whether users require basic access toApplicationXtender content management functionality or a custom business solution. Consider thefollowing:

• 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 inconjunction 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 applicationrequires the add‑in.

• The functionality required to support the business process or task


Designing the addin

Identify which ApplicationXtender content management and Microsoft Office features arerequired 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 usingApplicationXtender, if necessary.

Basic XML for an AXO addinAXO provides basic example add‑in solutions for each supported Microsoft Office application.The following example XML represents the AXTOWordAddIn.xml file in the C:\ProgramFiles\ApplicationXtender\AXO\Configurations\Basic\Word install directory, which defines thebasic add‑in for Microsoft Word. You could also use this XML file without modification for MicrosoftExcel and PowerPoint add‑ins as well; duplicate XML files are supplied in their respective installdirectories. The EMC ApplicationXtender for Microsoft Office Configuration Reference online help systemprovides a description of the basic example XML for Microsoft Outlook.

The example add‑in configuration file shown below adds menu commands for basicApplicationXtender content management functionality (open, publish, scan if a scanner driveris installed, and login) to the Microsoft Office 2007 Button menu, and the Microsoft Office 2010File menu. Note the XML elements in bold text below in the file text below. The add‑in alsoprovides access to two business use cases from the Office File menu: AXO Features and Basic ContentManagement. Chapter 6, Configuring a Business Use Case shows the basic example XML for anAXO business use case.

Note: Indentation and line breaks shown in the example XML files in this document are not necessaryin the XML file, but have been added to show the logical structure.<?xml version="1.0"?><AXTOWordAddIn Version="2.0" xmlns="http://www.emc.com/AppXtender">

<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 outofthebox Business Application</Description><Image>AXTO_AxLogoBlueBorder</Image>

</BusinessUseCase></BusinessUseCases><ApplicationXtenderServerUrl>http://localhost/AppXtender</ApplicationXtenderServerUrl><SessionTimeout>60</SessionTimeout><OpenOptions Allow="true" /><PublishOptions Allow="true" /><EnableScan>true</EnableScan><LoginOptions ShowMenu="true">

<Store Name="AppXtenderDEMO" IntegratedSecurity="false" /></LoginOptions>

</AXTOWordAddIn>


Designing the addin

User interface produced by the example addinXML fileThe basic example XML for the add‑in for Word adds commands to the Microsoft Office 2010File menu (or to the Office 2007 Button menu) to enable users to access basic ApplicationXtendercontent management functionality: Open, Publish. Login, and Business applications. The exampleXML 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 andPublish commands, as shown in and Figure 18, page 54, respectively.


Designing the addin

Figure 16. Microsoft Office 2010 file menu after login

When users select the Open from EMC ApplicationXtender command, AXO displays a dialog boxby the same name, as shown in Figure 17, page 53. This dialog box allows users to search theApplicationXtender 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 querywithout viewing the search criteria.


Designing the addin

Figure 17. Microsoft Office 2010: open from EMC ApplicationXtender dialog box


Designing the addin

The Publish to EMC ApplicationXtender command allows users to index and save Microsoft Officedocuments to ApplicationXtender. Users can choose to save an Office document to the repository as anew 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 forsaving and checking out ApplicationXtender documents.


Chapter 6Configuring a Business Use Case

This chapter provides an overview of the process for configuring an AXO business use case forMicrosoft 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 caseAn AXO business use case is an optional configuration (XML) file that addresses a particular businesssolution based on an integration of ApplicationXtender content management functionality and asupported Office 2007 or 2010 application. The business use case configuration file defines how anOffice application interacts with the ApplicationXtender content management system. Each businessuse case is comprised of the following top‑level components: views, ribbon, and ApplicationXtendercontent management features. The configuration options for these components define the appearanceof the add‑in within the Office application.

Unless otherwise noted, the screen captures presented in this chapter represent the user interfacethat is created by using the basic configuration files provided with AXO. You can customize thesefiles to reflect your specific business process and ApplicationXtender environment. The EMCApplicationXtender for Microsoft Office Configuration Reference online help system provides detailedinformation on configuration options.

Views component

The views component defines the properties of custom business use case view panes (referred to astask panes in Microsoft Word documentation) on the Microsoft Office application interface. You canconfigure a view pane to allow users to change the location or width of the view.


Configuring a Business Use Case

Each view contains one or more workspaces. A workspace is the area within which users performtasks such as in to the ApplicationXtender store or running a query when using an AXO add‑in. Aview can have unlimited workspaces; however, too many workspaces in an add‑in can cause the userinterface to appear cluttered and unusable. You can configure one of two types of workspaces, eithera standard or a tabbed workspace. As the name implies, a tabbed workspace is represented in theuser interface with a named tab that identifies the purpose of the workspace. Figure 19, page 56shows 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 theApplicationXtender content management functionality in an AXO add‑in. ApplicationXtendercontent management features, page 61 provides more information.

Ribbon component

The ribbon is a standard Microsoft Office component that controls the actions users can perform fromthe Microsoft Office Fluent Ribbon. AXO provides configuration options for the ribbon to supportApplicationXtender‑specific functionality. These options allow you to customize the ribbon for aspecific business use case. Following customization, the ribbon represents all available actions, bothstandard Office and ApplicationXtender‑specific, that a user can perform within the add‑in when thebusiness use case is active.

You can associate AXO feature work items with standard Microsoft Office Ribbon elements by usingthe business use case XML file. For example, you can configure a ribbon tab for ApplicationXtenderthat contains buttons for launching a query, displaying the search results, and openingApplicationXtender documents, as shown in Figure 20, page 57. The configuration file for the basicbusiness use case for Outlook Inspector, InspectorBusinessUseCase.xml, provides example XML.



Figure 20. Example Office ribbon for Outlook Inspector

You can also configure the ribbon to display entry fields for specifying search criteria, as shownin Figure 21, page 57. The example AXO file AXTOFeatures.xml described in AXO configurationfiles, 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‑inribbon. When end users open an ApplicationXtender document within this business use case, anAppXtender 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, doesnot contain the ribbon component.

The following table identifies and describes the function of each Ribbon button. All of these buttonsare available on ribbon defined in the basic content management XML.



Ribbon element Description

Save Save the document to ApplicationXtender

Save As Choose a document format to save locally

Replace Element Replace an element in an existingApplicationXtender document

New Revision Update revision numbers

New Element Version Save to ApplicationXtender as a new version ofthe current element

New Document Save to ApplicationXtender as a new document

Edit/Read‑only Lock/Unlock the currently openedApplicationXtender document

Check Out/Check In Check out/Check in the currently openeddocument

Undo Check Out Undo the current check out

View Document Versions View the currently opened ApplicationXtenderdocument versions

View Element Versions View the currently opened ApplicationXtenderdocument element versions

Delete Document Delete the document from ApplicationXtender,including all versions

Delete Document Version Delete the latest document version fromApplicationXtender

Delete Element Delete the document element fromApplicationXtender

Delete Element Version Delete the latest version of the documentelement from ApplicationXtender

Document Information ApplicationXtender version information for thecurrently opened document

Protect Document Protect the document by using EMC Documen‑tum IRM Services for ApplicationXtender

The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system providesApplicationXtender‑specific configuration information. See also the Microsoft documentation forstandard Office Ribbon configuration information.

If you installed the AXO Visual Studio Add‑In, you can design AXO ribbons using the VisualRibbon Designer. This designer leverages the Windows Presentation Foundation (WPF) ribbon. TheWPF ribbon follows the Microsoft Office Fluent user interface and provides components to buildan Office style ribbon.

Launch the AXO ribbon designer from the context menu for a ribbon .xml file in a BusinessUseCaseproject. The online help for the designer provides more information.



Dynamic ribbon elements – example code

AXO supplies example XML code for including ribbon elements for content types, query types, and soon. 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 ofC:\Program Files\ApplicationXtender\AXO\Configurations\Basic

contain the example code. Now OBA developers do not need to hand‑code all theContentTypes/queries/ and so on into the ribbon XML, and changes in the Content Managementsystem 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|AppXtenderDemoAll valid content types in AppXtenderDemo store

Query|AppXtenderDemo|HRAll valid queries in HR content type in AppXtenderDemo store

DocumentContainerAll valid content types in all logged in stores

Query|AppXtenderDemoAll valid queries in AppXtenderDemo store

The AXTOFeatures.xml business use case configuration file includes the configuration of thesebuilt‑in AXO ribbon elements.



Figure 22. Dynamic ribbon elements



ApplicationXtender content management features

End users interact with ApplicationXtender by using AXO work items. The business use casecontains 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 usedwith Word, Excel, and PowerPoint. Publish feature, page 70 and Browser feature, page 71 providemore information.

In addition to ApplicationXtender content management features and common features, AXOprovides features specific to Microsoft Outlook, as described in Outlook‑specific features, page 72.

The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system providesmore information.

Login feature

The Login feature allows end users to log in to the ApplicationXtender content management systemfrom within a Microsoft Office application. You can define multiple Login work items for a businessuse case, each of which is associated with a different ApplicationXtender store. You can configurelogin properties for each store such as layout style for the Login dialog box, security settings, and theuser interface that displays following successful login. You can also specify whether users are loggedout 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 ApplicationXtenderStore 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 contentmanagement system.



Figure 23. Login dialog box


Query feature

The Query feature allows end users to search the ApplicationXtender repository. This featuresupports the same query functionality that is available in ApplicationXtender Desktop. For example,users can search for documents by using both ApplicationXtender document properties (indexvalues) and common properties such as Title, Subject, or Author. Users can also use full‑text searchand logical operators. The ApplicationXtender Document Manager User’s Guide provides detailedinformation on performing queries.

Figure 24, page 63 illustrates sample user interface for querying content in an ApplicationXtenderrepository. Note that ApplicationXtender properties appear in all uppercase characters on theQuery 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 identifythe required data type for each field.



Figure 24. Query dialog box

You can configure the add‑in to use values from Microsoft Office documents as search criteria for aquery. Using template or form data as input to a query, page 64 provides more information. You canalso allow users to perform a query from the Office Ribbon rather than using the query dialog box.



Defining queries

AXO add‑ins support multiple ways of defining queries. The method you use depends on severalfactors including how much control you want to give users to modify the query. For example, youcan 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 tochange. Alternatively, you can allow users to run a predefined query from the Office Ribbon withoutdisplaying the search criteria.

You can configure the business use case XML to display the following types of ApplicationXtenderqueries:• 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 privateuse.

The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system providesinformation 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 DocumentQuery. 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 thatusers do not have to learn how to use ApplicationXtender. Instead, they are able to use their existingknowledge of the standard form to execute a search.

The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system providesinformation 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 aMicrosoft 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.



Figure 25. Result Set view: grid layout

Figure 26, page 66 illustrates a sample Result Set View configured to display entries in verticalcolumns (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 symbolappears 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 fieldsMIDDLE INIT and JOB CODE below each entry. Tooltips identify the data that is displayed inthe additional fields.



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 usermachine; 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 theirlocal machine for future sessions.

The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system providesinformation on configuring Result Set Views.



Document properties feature

The Document Properties feature, displayed by right‑clicking a document in the result set andselecting 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 userinterface for viewing document properties.

Figure 27. Document properties

You can also configure the Document Properties feature to display elements for an ApplicationXtenderdocument container. Figure 28, page 68 illustrates a sample user interface for viewing documentelements. Click Views to determine how the document elements are displayed. The current viewshows Thumbnails.



Figure 28. Document elements

Document container view feature

The Document Container View feature allows end users to view ApplicationXtender documentcontainers that are in a non‑Office format from within a Microsoft Office application. After runningan ApplicationXtender query from the add‑in, users select a document container to view from theResult Set View. The add‑in renders the document by using the <RenderMode> defined in thebusiness use case XML file: PDF, XPS, or Web Access browser. Figure 29, page 69 illustrates a sampleuser interface for viewing document containers in PDF mode.



Figure 29. Document container view


Web Access feature

The Web Access feature allows end users to view ApplicationXtender content in a Web Accessbrowser window within Microsoft Office. You can configure the Web Access browser window todisplay ApplicationXtender search criteria, query results, and document content. If the end user hasalready logged in to the store using the AXO add‑in, the Web Access browser shares the sessionrather than requiring the user to log in again.

The EMC ApplicationXtender Web Access User’s Guide provides information on performing end‑usertasks in the Web Access browser window.

Note: When users work with workbooks in an AXO add‑in for Microsoft Excel, Excel attempts tokeep the cursor focus on the workbook in the user interface rather than on the fields in the WebAccess browser window. As a result, it is recommended that you avoid using the Web Access featurewhen configuring AXO add‑ins for Microsoft Excel. Alternatively, users can close or minimize theactive Excel workbook before attempting to input values in the Web Access browser window fields.



Publish feature

The Publish feature allows end users to publishMicrosoft Office documents to the ApplicationXtenderrepository. 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 choosehow 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 toApplicationXtender.

Figure 30. Publish to ApplicationXtender: Save options

After specifying how the document should be saved, the user chooses the content type and specifiesvalues 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 propertyfields, including tooltips that identify the required data type for each property, as shown in Figure31, page 71.



Figure 31. Publish to ApplicationXtender: Document properties

AXO presents scan results in the WPF viewer. The scan tab in the document viewer contains aPublish 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 MicrosoftOffice. For example, you can configure the browser feature to display the home page of the companywebsite. Figure 32, page 72 illustrates a sample user interface for viewing website content in abrowser window within Microsoft Office.



Figure 32. Browser feature


Outlookspecific 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 viewsearch 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 OutlookExplorer navigation pane. This folder serves as a container for ApplicationXtender queries, bothpredefined and/or new. You can configure the queries that display in this folder by editing theExplorerFeatures.xml configuration file.

Figure 33, page 73 illustrates a sample ApplicationXtender browsing feature in Outlook Explorer.



Figure 33. Microsoft Outlook Explorer: ApplicationXtender browsing feature

Note: Although the ApplicationXtender folders use the standard Outlook folder icon, they are notactually 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 theApplicationXtender 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 withall user customizations to an add‑in, changes are saved in a file on their local machine. Enablingcustomizations for a business use case, page 86 provides more information.



Figure 34. Outlook Explorer: ApplicationXtender browsing settings

Tip: You can use this Outlook user interface rather than configuring the browsing feature in theXML 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 specifiedcontent type. Otherwise, the query searches the current revision of documents in the specifiedcontent type.

• Add Query: Click this option to add a query. After adding a query, you can right‑click the EMCApplicationXtender folder (in Figure 33, page 73) and select Refresh. The new query will thenappear in the Explorer reading pane.

When users open the EMC ApplicationXtender folder (in Figure 33, page 73), the display showsthe list of ApplicationXtender queries that users can access. Selecting for a query in the list or



double‑clicking the highlighted row displays query results in a Web Access browser window, asshown 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, asshown in Figure 36, page 75.

Figure 36. Outlook browsing: query criteria

The Outlook Explorer features section of the EMC ApplicationXtender for Microsoft Office ConfigurationReference online help system provides more information.



Insert from scan feature

If scan is enabled, a new Ribbon element is added into the Outlook Explorer ribbon for inserting ascanned image.

Figure 37. Scan button on the Outlook ribbon

The scanned image can be inserted into the current email, meeting, appointment, or contact.

Export Microsoft Outlook items to ApplicationXtender feature

AXO provides an export feature that lets users export Outlook items (mail, appointments, meetingrequests, and contacts) from the Outlook Explorer window to ApplicationXtender. The basicadd‑in for Outlook includes configuration for the ApplicationXtender export feature. The add‑increates an Outlook folder named AutoUploadToAX, as shown in Figure 38, page 77. This folder isconfigured to copy Outlook mail attachments to the ApplicationXtender content type SCRIPTSin the AppXtenderDEMO store. Because the configuration specifies that the folder is monitored,attachments in the folder are uploaded to the document repository automatically.



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 tothe SCRIPTS content type. However, because the basic configuration for the Inbox folder specifiesthat the folder is not monitored, users would have to copy Outlook items from the Inbox toApplicationXtender manually, as shown in Figure 39, page 78.



Figure 39. Microsoft Outlook Explorer: ApplicationXtender export feature (manual copy)

If desired, you can modify the default configuration for the export feature by editing theExplorerFeatures.xml configuration file. The first step is to configure upload (export) settingsincluding the item type or types to be exported, the export format, the target ApplicationXtender storeand content type, and the mapping between Outlook fields and ApplicationXtender content typeproperties. This mapping allows Outlook to provide values for ApplicationXtender properties whenitems are exported from Outlook to ApplicationXtender, which in turn allows ApplicationXtender tostore items as ApplicationXtender documents.

Configuring export settings also includes specifying save options for each allowed item type. Forexample, you can specify that each uploaded item always creates a new ApplicationXtenderdocument. Alternatively, you can specify that, if the new document has the same index record asan existing document, the new document creates either a major or minor revision of, or is mergedwith, the existing document.

After you configure export settings, you associate the saved settings with one or more top‑levelpersonal folders in the Outlook Explorer navigation pane. Folder configuration includes specifyingwhether the folder should be monitored and whether items should be copied to the repository ormoved. 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 additionalexport settings by using:• For Outlook 2007, Tools > Options > Upload

• For Outlook 2010, File > AppXtender > AppXtender Options



to display the Upload to ApplicationXtender tab in the Outlook Options menu, as shown in Figure40, page 79. They can then associate the new upload configuration with an Outlook folder by usingOutlook Folder Properties. As with all user customizations to an add‑in, user‑defined export settingsare saved in a file on their local machine. Enabling customizations for a business use case, page 86provides more information.

Figure 40. Outlook 2007 Explorer: Upload to EMC ApplicationXtender settings



Figure 41. Outlook 2010 Explorer: upload to ApplicationXtender settings

Tip: Rather than configuring the export to ApplicationXtender feature in the XML file, you can usethe Outlook user interface as in Outlook Explorer, page 72.

An alternative to mapping Outlook fields to ApplicationXtender content type properties is to indexOutlook items into ApplicationXtender by using Outlook form data. In this case, AXO retrievesdocument properties from the fields in the Outlook form. You configure this feature by creating anApplicationXtender content type with properties that are identical to the controls in the form.

IMPORTANT: Because ApplicationXtender saves property names in uppercase characters (forexample, LAST NAME), form control names must be in uppercase characters. Otherwise, the namesare not considered identical.

Note: AXO cannot retrieve data from built‑in Outlook forms. If you want to use a built‑in form toindex Outlook items, modify the form first, then publish your custom form to Outlook using a newname. AXO supports only Outlook text box and list box form controls. In addition, AXO retrievesdata only from the first page of the form.


Outlook ad hoc export feature

When an Outlook folder is not configured for upload, AXO still shows the Copy & Move toApplicactionXtender menu items. When the user first clicks on these buttons, AXO pops up theAdvanced Upload setting dialog to allow the user to select options for the upload item and uploaditem format, as shown in the red rectangle, and disables all other inputs.



Figure 42. Upload Document Setting: adhoc configuration

After the user selects the upload item and upload item message format and clicks OK, AXO saves theconfiguration with only the item andmessage format information, and with a fixed nameAXO ad‑hocconfiguration. The next time the user publishes a document, it will not pop up this dialog to let theuser 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.



Figure 43. Publish to EMC ApplicationXtender

Now the user can follow the wizard step‑by‑step to select the Store and Content Type, and entermeta‑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,ʺ allinputs are disabled except the upload item and upload item message format, so that the user canedit only these two options.

Outlook inspector

In addition to the functionality described in Common functionality, page 27, AXO provides an attachfiles feature for Outlook Inspector. This feature, which is available in the basic add‑in for Outlook, letsusers attach an ApplicationXtender document to a new or reply e‑mail. After performing a query inOutlook Inspector, users select the desired document from the result set and select Attach. They thenchoose to attach the entire document or specify a page range. Other configuration options, such asselecting the rendering format (either PDF or XPS) are also available. Figure 44, page 83 illustrates asample user interface for the ApplicationXtender attach files feature in Outlook Inspector.



Figure 44. Outlook inspector: Attaching an ApplicationXtender document to an email

If desired, you can modify the default configuration for the attach files feature by editingthe InspectorBusinessUseCase.xml file. The Outlook Inspector features section of the EMCApplicationXtender for Microsoft Office Configuration Reference online help system provides moreinformation.

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 exportfeature described in Export Microsoft Outlook items to ApplicationXtender feature, page 76. TheInspectorBusinessUseCase.xml file provides example XML.

Choosing the features for a business use caseThe XML for AXO work items determines the appearance of the user interface elements and theirassociated behavior. Default user interface elements and their associated behavior are defined inthe example business use case. Each user interface element is associated with a different type ofbusiness work item, which has its own set of XML attributes and elements. You can customize theuser interface elements by adding, modifying, or deleting the XML for business work items, as



desired, in the copy of the business use case example file. Alternatively, you can configure some AXOfeatures, 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 toApplicationXtender 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 theApplicationXtender Document Container View work item and reuse it in multiple Microsoft Wordadd‑ins by copying the associated XML into each business use case.

IMPORTANT: Identifiers for shared feature configurations must be unique across all business usecases. The Enabling customizations for a business use case, page 86 provides recommendations oncreating unique names for AXO work items.

Defining interaction between business usecase featuresAn 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 thatshould occur between them. Feature work items interact with one another by using configurableevents. 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 ofdata. When you configure an action to pass data, you specify that the results of the action should bestored 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 theinteraction between the Query and Result Set View work items. Because the goal is to pass queryresults from the Query work item to the Result Set View work item for display, the Query work itemalways saves query results as a named piece of data, QueryResults. This allows you to pass the resultsto 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.QueryWorkIteminitiates 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 ShowResultaction displays the result set in the target BasicContentManagement.ResultSetWorkItem, which isdefined in the Result Set work item section of the business use case XML file — Refer to the boldtext 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">



<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 itemsin the business use case XML file by using XML attributes and elements. AXO provides a predefinedset of valid events and actions for work items. The EMC ApplicationXtender for Microsoft OfficeConfiguration Reference online help system provides more information.

Loading a business use caseWhen you configure an add‑in, you can define a default business use case that opens automaticallywhen users launch the Microsoft Office application/add‑in. If you need to configure more than onebusiness 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 businessuse cases. Each time a user launches a different business use case, the preceding business use casecloses. The add‑in refreshes the user interface, including the Microsoft Office Ribbon, to reflect theconfiguration 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 Officedocument or template, by specifying the name of the business use case as the value for a customproperty in the Office application.




Enabling customizations for a business usecaseYou can control whether end users have the ability to modify default user interface settings for abusiness use case by using the DisableCustomizations attribute for the BusinessUseCase element in thebusiness use case XML file. Setting this attribute to false allows users to save any changes they madeto the user interface for the business use case, such as query or result set preferences. When a usercloses the business use case or exits the Microsoft application, custom changes are saved in one ormore files on the user’s local machine. The location for custom files, which is referred to as the user’spersonal configuration cache, depends on the user’s operating system:• For Windows 2003/XP machines, custom files are saved in C:\Documents andSettings\<username>\Application Data\ApplicationXtender\AXTO.

• For Windows Vista/Windows 7 machines, custom files are saved inC:\Users\<username>\AppData\Roaming\ ApplicationXtender\AXTO.

In addition to allowing users to save customizations to a business use case, setting theDisableCustomizations tag to false lets you configure AXO features for Outlook Explorer using theOutlook user interface rather than the XML configuration file. Outlook Explorer, page 72 providesmore 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 andreplace the relevant sections in the base XML configuration file before generating and deployingthe Outlook add‑in to users.

Understanding the importance of configurationversioningIf you have enabled customizations for a business use case, as described in Enabling customizationsfor a business use case, page 86, be aware that configuration files in the user’s personal configurationcache are always loaded before the base configuration XML files provided in the AXO deploymentpackage. If you subsequently redeploy the add‑in package, only the base configuration XML files areupdated 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, asaved copy of the old version of the Login work item with the old store name resides in their personalconfiguration 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 aversion number to each business use case and each work item in the XML file. The AXO configurationservice checks the version number when it loads configuration items to ensure that old versions ofconfiguration XML that may exist in an end user’s personal configuration cache are ignored afterupdating the deployment package.

To use configuration versioning, you must declare the new version of the updated business use casein two places before redeploying your deployment package. First, update your business use case



XML to reflect the new version. Then update your add‑in configuration to specify the version of thebusiness use case you want to load.

The Technical Notes section of the EMC ApplicationXtender for Microsoft Office Release Notes providesmore information.

Specifying unique identifiers for sharedfeaturesIdentifiers 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 auser modifies the login configuration for business use case A and subsequently modifies the loginconfiguration for business use case B, the configuration for business use case A is overwritten ifboth Login work items have the same identifier.

One recommendation for ensuring unique identifiers is to prepend the name of the business use caseto the ID of each feature work item in the XML file. For example, the BasicContentManagement.xmlfile for the basic Word add‑in prepends BasicContentManagement. to the ID of each work item. Theperiod character (.) serves as a path separator. When a user modifies a work item in this business usecase, the add‑in creates a BasicContentManagement directory in the user’s personal configurationcache and places the custom XML file there. In this example, if a user opens the Basic ContentManagement business use case from the Word add‑in and selects the Save Credentials option on theLogin dialog box, a file named LoginWorkItem.xml is created in the BasicContentManagementdirectory. Saving the file in this way ensures that it will not overwrite the login file for any otherbusiness use case.

Example XML for an AXO business use caseThe following example XML defines an AXO business use case that you can use with any supportedMicrosoft 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 theAppXtenderDEMO store. It allows users to perform a full‑text search of the HR content type in theApplicationXtender 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 lastname. Because end‑user customizations are enabled for this business use case, users can modify thedefault settings specified in the business use case and save their changes to a custom XML file ontheir local machine for future sessions.

From the Result Set View, users can view a non‑Office document or open an Office document, asappropriate, by using a context menu. All ApplicationXtender‑supported documents can be opened



in the WPF Viewer. Non‑Office documents can also be rendered in PDF format in a new windowwithin Word. Figure 45, page 91 illustrates the user interface associated with this example businessuse case.

AXO configuration files, page 24 provides a list of configuration files that you can use fordemonstration purposes or as models for creating your own add‑in solutions. The EMCApplicationXtender for Microsoft Office Configuration Reference online help that is installed with AXOprovides detailed configuration information.

Note: Indentation and line breaks shown in the example XML files in this document are not necessaryin the XML file, but have been added to show the logical structure. Some line endings have beenbroken to fit the text to the page.<?xml version="1.0" encoding="utf8"?><BusinessUseCase xmlns="http://www.emc.com/AppXtender" 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"/>


</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>



<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>


</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" />


</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" />



</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>


</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>



<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 examplebusiness use case XML fileFigure 45, page 91 illustrates the user interface produced by the BasicContentManagement.xmlbusiness use case XML file for Word.

Figure 45. Basic business use case for Microsoft Word



The EMC ApplicationXtender for Microsoft Office Configuration Reference online help system providesadditional example XML files.


Chapter 7Getting Started with AXO

This chapter provides high‑level steps to help you get started with AXO. It contains the followingsections:• Creating and deploying an AXO add‑in, page 93

• Configuring a business use case, page 94

Each basic AXO add‑in solution provides access to core ApplicationXtender content managementfunctionality (login, open from ApplicationXtender, and publish to ApplicationXtender). If youprefer to use the basic solution, which requires minimal configuration, read section Creating anddeploying an AXO add‑in, page 93 and skip the rest of the chapter. Otherwise, if you want to deliverhighly customized functionality to add‑in users by way of a business use case, read the entire chapter.

Creating and deploying an AXO addinThe AXO software lets you create and deploy add‑in solutions containing ApplicationXtender contentmanagement functionality for integration with supported Microsoft Office applications. Perform thefollowing high‑level steps to create and deploy an AXO add‑in:

Note: Optionally, use the AXO add‑in utility to perform steps 3 through 7. The online help providedwith the utility shows procedures.

1. Install AXO and, optionally, the AXO Visual Studio Add‑In. The EMC ApplicationXtender forMicrosoft Office Release Notes provides the list of prerequisite software and hardware required forboth the workstation where you are installing AXO and for the end‑user machines that will beusing AXO add‑ins. The EMC ApplicationXtender for Microsoft Office Installation Guide providesprocedures on installing AXO.

2. Identify the target business department or user group for the add‑in and the requiredfunctionality. Chapter 3, AXO add‑in functionality provides more information.

3. Determine whether you want to provide basic ApplicationXtender content managementfunctionality directly from the Office menu by using the add‑in configuration file or providehighly customized functionality by using a business use case. For high‑level details, refer toChapter 5, Designing the add‑in or Chapter 6, Configuring a Business Use Case, respectively.For detailed configuration information, refer to the EMC ApplicationXtender for Microsoft OfficeConfiguration Reference online help system.


Getting Started with AXO

4. Based on your decision in step 3 and the resulting configuration files, configure an add‑insolution. If you want to deploy the basic add‑in solution, locate the desired add‑in XML file(see AXO configuration files, page 24). Then edit the file to reflect customer data by using theprocedures in the EMC ApplicationXtender for Microsoft Office Deployment Guide.

5. Configure the deployment definition XML file. This file serves as input to the AXO deploymentutility, which generates a Microsoft ClickOnce package that users install. Configuring thedeployment definition file includes specifying the source directory containing the AXO add‑insto be distributed to users (for example, a directory path on your workstation). You also need tospecify the target directory where the final distribution package should be placed. The EMCApplicationXtender for Microsoft Office Deployment Guide provides more information.

6. Generate the ClickOnce (.vsto) distribution package. The EMC ApplicationXtender for MicrosoftOffice Deployment Guide provides more information.

7. Publish (deploy) the distribution package to a central location where users can access it.The location must be either a share on a network file server or a web server. The EMCApplicationXtender for Microsoft Office Deployment Guide provides more information.

8. Notify users of the availability of the distribution package and its location so they can installthe add‑in on their machines. The ClickOnce installation process integrates the AXO add‑infunctionality with the associated Microsoft Office client application. The result of the integrationis a custom business application solution that provides ApplicationXtender content managementfunctionality within the familiar working environment of the Microsoft Office application. Userscan access the add‑in functionality the next time they launch the Microsoft Office application.

Following the initial deployment of an AXO add‑in solution, you can generate and deploy updatedsolutions to end users. You can also roll back to a previous version of an add‑in from an end‑usermachine. The EMCApplicationXtender for Microsoft Office Deployment Guide provides more information.

IMPORTANT: When generating and deploying updated add‑in solutions, it is crucial that youunderstand how the AXO configuration service creates and subsequently locates files, including theuse of versioning. Understanding the importance of configuration versioning, page 86 gives somedetails, and the Technical Notes section of the EMC ApplicationXtender for Microsoft Office Release Notesprovides more information.

Configuring a business use caseA business use case is an optional AXO component that lets you deliver highly customizedfunctionality to end users. Each business use case is designed to address a particular businesssolution for a specific business department or group of users.

Configuring a business use case includes the following high‑level tasks:

1. Identify the business process, department, or user group, and Microsoft Office client applicationfor which you want to create an AXO add‑in. By customizing each AXO add‑in to a specificbusiness process, department, or user group, you reduce the time it takes end users to performtheir jobs.

2. Review the example configuration (XML) files described in AXO configuration files, page 24.AXO provides a basic and also an out‑of‑the‑box business use case configuration file for eachsupported Microsoft Office client application. In addition, sample business use cases that



showcase specific ApplicationXtender functionality are also installed. You can use the samplefiles as the starting point for developing your own business use cases, if desired.

3. Choose the business use case example that most closely reflects the business process or solutionyou want to design, then save the example as a new file name. Never modify the original examplefile. That way, if you corrupt your XML file, you can revert to the original version.

4. Review the available AXO business work items described in the Configuring a business usecase, page 94 and identify which features should be included in each business use case. AXOprovides a set of common business work items that you can use with all supported MicrosoftOffice client applications as well as a Microsoft Office client application‑specific set of objects. TheEMC ApplicationXtender for Microsoft Office Configuration Reference online help system providesdetailed configuration information.

5. Define the interaction that should occur between AXO features. Defining interaction betweenbusiness use case features, page 84 provides an overview of how features interact. The EMCApplicationXtender for Microsoft Office Configuration Reference online help system providesinformation on how to identify the communication events and actions that are valid for eachAXO business work item.

6. Specify the ApplicationXtender data store to be used for the business use case. Use the Loginwork item to define the store that users can access when working with a particular business usecase. This object also specifies security settings for both the store and the currently logged‑inuser. In addition, the Login work item produces the Login dialog box for the business use case.You can specify multiple stores for each business use case. However, the user must log in toeach store separately.

7. Optionally, configure an Office document or template for Word, Excel, or PowerPoint that canbe used to launch a specific business use case. You can create a document/template that has acustom property called AXTOBusinessUseCase where the value is the name of the business usecase XML configuration file. When users open this document from within the Microsoft Officeapplication or create a new document from the template, AXO launches the associated businessuse case. The EMC ApplicationXtender for Microsoft Office Configuration Reference online helpsystem provides more information.

8. Optionally, create a Microsoft Office form for indexing documents or Outlook items intoApplicationXtender rather than using the standard ApplicationXtender query dialog box.The Microsoft Office online help provides procedures on creating forms, and the EMCApplicationXtender for Microsoft Office Configuration Reference online help system providesprocedures on configuring Outlook forms to index Outlook items into ApplicationXtender.

9. Optionally, repeat steps 1 through 8 to create additional business use cases for the add‑in.

10. When you are finished creating business use cases for a Microsoft Office application add‑in,configure the add‑in XML file. Creating and deploying an AXO add‑in, page 93 in this guide,and the EMC ApplicationXtender for Microsoft Office Configuration Reference online help systemprovide more information.




Index

Aaccess privileges, granting, 46ApplicationXtender Web Access .NET, 20ApplicationXtender Web Services, 18, 20,

45ApplicationXtender Workflow Manager,

integration with, 39AppXtender tab, 54, 57architecture, AXO, 20attach files feature, Outlook Inspector, 82automatic login, enabling, 47AutoUploadToAX folder, 76AXO add‑in

creating and deploying, 93designing, 49functionality, 27sample XML, 50

AXO architecture, 20AXO components, 17AXO configuration files, 24AXO configuration process

basic (manual) method, 20AXO configuration service, 86AXO deployment process

basic (manual), 21using AXO Visual Studio Add‑in, 22

AXO featuresbrowse website content, 39, 71deleting ApplicationXtender

content, 40login, 28, 61open ApplicationXtender

documents, 32Outlook Explorer, 72Outlook Inspector, 82publish to ApplicationXtender, 39, 70query, 29, 62result set, 30, 64view ApplicationXtender

documents, 31, 68

view document properties, 30, 67Web Access browser, 32, 69

AXO Visual Studio add‑in, 18AXO, definition of, 11AXTOExcelAddIn.xml, 25AXTOFeatures.xml, 24, 57AXTOOutlookAddIn.xml, 26AXTOPowerPointAddIn.xml, 25 to 26AXTOWordAddIn.xml, 24 to 25

Bbase configuration XML files, 86basic (manual)

configuration process, 20deployment process, 21

basic example add‑inWord, 51

BasicContentManagement.xml, 24, 57, 87,91

browser feature, 39, 71browsing ApplicationXtender documents

from Outlook, 72business process, submitting

ApplicationXtender content to, 39business use case

ApplicationXtender contentmanagement features, 61

choosing features for, 83configuring, 55defining interaction between

features, 84example XML, 87loading, 85opening a default, 29Ribbon component, 56using configuration versioning, 86views component, 55


Index

Cchoosing features for a business use

case, 83ClickOnce technology, 15CM security, 46common properties

using as search criteria, 62viewing, 30, 67

components, AXO, 17configuration cache, personal, 86configuration files, AXO, 24configuration process for AXO

basic (manual) method, 20using AXO Visual Studio Add‑in, 22

configuration versioning, 86configuring a business use case, 55content type, definition of, 13creating and deploying an AXO add‑in, 93

Ddeleting ApplicationXtender

documents/document containers, 40deployment definition file, 21deployment process for AXO

basic (manual) method, 21using AXO Visual Studio Add‑in, 22

deployment utility, 18DisableCustomizations attribute, 86document container, definition of, 13document containers

deleting, 40viewing, 31

document elementsviewing, 67

document propertiesusing as search criteria, 62viewing, 30

documentsdeleting, 40

Eelement, definition of, 14enabling

automatic login, 47customizations for a business use

case, 66, 86 to 87events for AXO features, 84example XML

business use case, 87ExplorerFeatures.xml, 26, 72, 78exporting Microsoft Outlook items to

ApplicationXtender, 76

Fform data, using as input to a query, 64

Ggetting started with AXO, 93granting access privileges, 46

IInformation Rights Management (IRM),

support for, 35InspectorBusinessUseCase.xml, 26, 56, 83IT workers, description, 12

KKnowledge workers, description, 13

Llaunching

a business use case, 85, 95a query, 56AXO add‑in, 28

licensing, 45log tool, 18login feature, 28, 61

Mmapping Outlook fields to

ApplicationXtender content typeproperties, 78

Microsoft Excelconfiguration files, 25recommended configuration, 69

Microsoft Office Button, 27Microsoft Outlook

add‑in functionality, 41AXO features for, 72configuration files, 26mapping fields to ApplicationXtender

content type properties, 78Microsoft PowerPoint

configuration files, 25


Index

Microsoft Wordbasic sample add‑in, 50configuration files, 24

OODMA properties

See common properties, 15Office Business Application Developers,

description, 12Office Business Application, definition

of, 15open ApplicationXtender documents

feature, 32Outlook Explorer

browse ApplicationXtender documentsfeature, 72

export to ApplicationXtenderfeature, 76

Outlook Inspectorattach files feature, 82export to ApplicationXtender

feature, 83

Ppersonal configuration cache, 86planning and implementing security, 45protecting ApplicationXtender

content using IRM Services forApplicationXtender, 35

publish feature, 39, 70

Qqueries, defining, 64query feature, 29, 62

Rresult set feature, 30, 64ribbon .xml file, 58Ribbon tab, 56

Ssample XML

AXO add‑in, 50

security provider, selecting, 46sharing an ApplicationXtender Web

Services session, 45store, definition of, 13submitting ApplicationXtender content to

a business process, 39

Ttemplate, using as input to a query, 64terminology, 13tracking (reference) feature, 30

Uunique identifiers, for shared features, 87updated add‑in packages, 21uppercase characters

ApplicationXtender properties, 62, 67form control names, 80

user interface, example for Wordadd‑in, 51business use case, 91

Vversion conflicts, avoiding, 86versioning, configuration, 86, 94view ApplicationXtender documents

feature, 31, 68view document properties feature, 30, 67viewing document elements, 67Visual Studio Tools for Office (VSTO), 15

WWeb Access feature, 32, 69Windows integrated security, 46Windows Presentation Foundation

Viewer, 33workflow, integration with

ApplicationXtender WorkflowManager, 39

WPF Viewer work item, 41

XXML files, 18 to 19, 24
