DOCSLIB.ORG

Best Practices Document for Designing Forms Version 0.4

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Best Practices Document for Designing Forms Version 0.4 Best Practices Document for Designing Forms Version 0.4 Best Practices for Designing Forms Page 1 of 48 Adobe XFA Training Materials Copyright 2005 Adobe Systems Incorporated. All rights reserved. NOTICE: All information contained herein is the property of Adobe Systems Incorporated. No part of this publication (whether in hardcopy or electronic form) may be reproduced or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written consent of the Adobe Systems Incorporated. PostScript is a registered trademark of Adobe Systems Incorporated. All instances of the name PostScript in the text are references to the PostScript language as defined by Adobe Systems Incorporated unless otherwise stated. The name PostScript also is used as a product trademark for Adobe Systems’ implementation of the PostScript language interpreter. Except as otherwise stated, any reference to a “PostScript printing device,” “PostScript display device,” or similar item refers to a printing device, display device or item (respectively) that contains PostScript technology created or licensed by Adobe Systems Incorporated and not to devices or items that purport to be merely compatible with the PostScript language. Adobe, the Adobe logo, Acrobat, the Acrobat logo, Acrobat Capture, Distiller, PostScript, the PostScript logo and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Apple, Macintosh, and Power Macintosh are trademarks of Apple Computer, Inc., registered in the United States and other countries. PowerPC is a registered trademark of IBM Corporation in the United States. ActiveX, Microsoft, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. UNIX is a registered trademark of The Open Group. All other trademarks are the property of their respective owners. This publication and the information herein is furnished AS IS, is subject to change without notice, and should not be construed as a commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or inaccuracies, makes no warranty of any kind (express, implied, or statutory) with respect to this publication, and expressly disclaims any and all warranties of merchantability, fitness for particular purposes, and no infringement of third party rights. Best Practices for Designing Forms Page 2 of 48 Table of Contents Overview............................................................................................................................. 5 Software Components..................................................................................................... 5 Steps to render a form:.................................................................................................... 6 Best Practice #1: Use Relative Binding Whenever Possible .............................................. 7 Relative versus Full Binding........................................................................................... 7 Best Practice #2: Use Flow Content Subforms whenever possible .................................... 9 Positional Content Subforms .......................................................................................... 9 Flow Content Subforms ................................................................................................ 10 Repeatable Subforms .................................................................................................... 12 Best Practice #4: Use Subforms to Structure Form Content............................................. 14 Best Practice #5: Use Picture Masks for Universal Formatting ....................................... 16 Picture Masks................................................................................................................ 16 Determining the locale of the form............................................................................... 16 Best Practice #6: Use Fonts that ensure accurate output and minimal output size........... 18 Overview of Font Selection .......................................................................................... 18 Best Fonts to Ensure Output Target Support ................................................................ 20 Embedded Fonts and Output Stream Size .................................................................... 20 Best Practice #7: Ensure Forms are Accessible................................................................ 21 Overview of Accessibility............................................................................................. 21 Designing Accessible Forms......................................................................................... 23 Checkboxes and Radio Buttons .................................................................................... 23 Best Practice #8: Use Dynamic Properties to Bind Data to a List.................................... 24 Best Practice #9: Useful Online References ..................................................................... 27 Adobe “eRoom”............................................................................................................ 27 Adobe Web Site ............................................................................................................ 27 Adobe LiveCycle Online Help...................................................................................... 27 Best Practice #10 – Use the Hierarchy View to Select Form Content.............................. 28 Best Practice #11 - Designing an Accessible Multi-line Table ........................................ 29 Step 1: Turn off table generation option...................................................................... 30 Step 2: Create the data bindings.................................................................................... 31 Step 3: Create the Header Subform .............................................................................. 31 Step 4: Create Captions for Header Subform ............................................................... 32 Step 5: Remove the captions from the DATA subform................................................ 33 Step 6: Set the Accessibility Role for the Subforms..................................................... 33 Step 7: Allow the table to span multiple pages............................................................. 34 Step 8: Set the Header to appear on each page ............................................................. 36 Step 9: Arrange the position and size of the fields ....................................................... 36 Best Practice #12 – Designing an Accessible Multi-line Heterogeneous Header Table .. 41 Best Practice #13 – Designing Accessible Nested Tables................................................ 43 Best Practice #14 – Designing Accessible Horizontal Tables.......................................... 44 Best Practice #15 – Designing Accessible Tables with “Out of place” Rows.................. 46 Best Practice #16 – Designing Accessible Tables with a large number of data fields ..... 48 Best Practices for Designing Forms Page 3 of 48 Document History: Version Number Date Released Comments 0.1 August 16, 2005 First release 0.2 September 26, 2005 Added examples of how to design accessible tables and incorporated suggestions from various colleagues and SAP personnel. 0.3 November 18, 2005 Added additional examples and made minor updates 0.4 December 5, 2005 Updated with comments from SAP The latest version of this document can be accessed from the Adobe ERoom. The URL for this document is: https://eroom.adobe.com/eRoom/fid302/SAPAdobe/0_7b81 The ERoom location is: SAP/Adobe Alliance -> Trollinger/Package 2B -> Trollinger Package 2B Documents of Record -> Document Library Best Practices for Designing Forms Page 4 of 48 Overview The purpose of this document is to outline the best practices to follow when designing forms using Adobe LiveCycle Forms Technology. An explanation of the software components that are used to create and render a form is the best way to start to understand the practices outlined in this document. As you can see from the diagram below, a form consists of a set of XML files that are combined by the Adobe Document Services. In the same way that it is not necessary to understand the mechanics of an automobile to drive one, it is not necessary to view or edit XML files in order to use the Adobe LiveCycle Products. However, possessing a good understanding of the operations taking place behind the scenes is essential if you wish to become a good form designer. Adobe Designer Form Layout XDP:XDP Template subform Template (XDP) pageset subform config schema Data (XML) datasets Configuration ADS XCI PCL, Application PostScript or or Database ZPL Software Components Name Description Adobe Designer Adobe LiveCycle Designer – a Graphical User Interface application for creating template (XDP) files ADS Adobe LiveCycle Document Server – takes a template, XML data and configuration settings and renders the form to PDF, PCL, PostScript or ZPL. Application or Database An application or database that exposes data via XML Best Practices for Designing Forms Page 5 of 48 Steps to render a form: Step Description Define XML Data Decide on what data structure will be exposed by the application or database and used by the template Design template Drag
Load more

Recommended publications
  • Acrobat Application Security Guide (All Versions)
    Acrobat Application Security Guide (all versions) Acrobat® Family of Products © 2012 Adobe Systems Incorporated. All rights reserved. Adobe Application Security Guide for the Adobe® Acrobat Family of Products. If this guide is distributed with software that includes an end user agreement, this guide, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by any such license, no part of this guide may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Adobe Systems Incorporated. Please note that the content in this guide is protected under copyright law even if it is not distributed with software that includes an end user license agreement. The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational content contained in this guide. Please remember that existing artwork or images that you may want to include in your project may be protected under copyright law. The unauthorized incorporation of such material into your new work could be a violation of the rights of the copyright owner. Please be sure to obtain any permission required from the copyright owner. Any references to company names in sample templates are for demonstration purposes only and are not intended to refer to any actual organization.
    [Show full text]
  • Best Practices for Model-Driven Development with Adobe® Livecycle® ES2 Guides Guiding People Through the Data Capture Experience
    Adobe LiveCycle ES2 Technical Guide Best Practices for Model-Driven Development with Adobe® LiveCycle® ES2 Guides Guiding people through the data capture experience. Introduction Background Guides in Adobe LiveCycle ES2 are Flash Player compatible wizard-like panels that help guide people through a data capture experience. Guides can dynamically change and adapt based on input data to ensure that only relevant questions are asked and accurate data is captured. These rich and engaging experiences help reduce transaction abandonment rates that are prevalent with more complex data collection interfaces. In LiveCycle ES2, Guides use the concept of model-driven development, which is the next level of abstraction in writing software applications. This abstraction offers improved productivity and makes applications that are higher in quality and easier to create, compared to lower-level development techniques. Model-driven development separates the data structures and constraint logic from the user interface and display logic. Models can then be shared and reused by other applications that capture, display or process the same data. The previous incarnation of guides was known as “form guides,” and used an XDP form as both the model and host of the form guide definition. Form guides were built directly in LiveCycle Designer, and were rendered by LiveCycle Forms into a SWF (pronounced “swiff”) file for display in the Flash Player. With the release of LiveCycle ES2, the Guide Builder tool has been moved to LiveCycle Workbench and a new application model has been introduced. The application model (.fml) is created in the Data Modeler tool, which is also a new part of the LiveCycle Workbench in ES2.
    [Show full text]
  • Adobe Systems FY2006 10-K/A
    UNITED STATES SECURITIES AND EXCHANGE COMMISSION Washington, D.C. 20549 ________________ FORM 10-K/A (Amendment No. 1) ________________ (Mark One) [X] ANNUAL REPORT PURSUANT TO SECTION 13 OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934 For the fiscal year ended December 1, 2006 OR [ ] TRANSITION REPORT PURSUANT TO SECTION 13 OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934 For the transition period from to Commission file number: 0-15175 ADOBE SYSTEMS INCORPORATED (Exact name of registrant as specified in its charter) Delaware 77-0019522 (State or other jurisdiction of (I.R.S. Employer incorporation or organization) Identification No.) 345 Park Avenue, San Jose, California 95110-2704 (Address of principal executive offices and zip code) (408) 536-6000 (Registrant’s telephone number, including area code) Securities registered pursuant to Section 12(b) of the Act: Title of Each Class Name of Each Exchange on Which Registered Common Stock, $0.0001 par value per share The NASDAQ Stock Market LLC (NASDAQ Global Select Market) Securities registered pursuant to Section 12(g) of the Act: None Indicate by checkmark if the registrant is a well-known seasoned issuer, as defined in Rule 405 of the Securities Act. Yes [X] No [ ] Indicate by checkmark if the registrant is not required to file reports pursuant to Section 13 or Section 15(d) of the Act. Yes [ ] No [X] Indicate by checkmark whether the registrant (1) has filed all reports required to be filed by Section 13 or 15 (d) of the Securities Exchange Act of 1934 during the preceding 12 months (or for such shorter period that the registrant was required to file such reports), and (2) has been subject to such filing requirements for the past 90 days.
    [Show full text]
  • Docusign SOAP API Developer Guide
    Information Guide 1 DocuSign SOAP API Developer Guide 221 Main Street, Suite 1000, San Francisco, CA 94105 Ι Tel. 866.219.4318 Ι www.docusign.com Ι © DocuSign, Inc. DocuSign SOAP API Developer Guide 2 Copyright ©2003-2016 DocuSign, Inc. All rights reserved. For information about DocuSign trademarks, copyrights and patents refer to the DocuSign Intellectual Property page (https://www.docusign.com/IP) on the DocuSign website. All other trademarks and registered trademarks are the property of their respective holders. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of DocuSign, Inc. Under the law, reproducing includes translating into another language or format. Every effort has been made to ensure that the information in this manual is accurate. DocuSign, Inc. is not responsible for printing or clerical errors. Information in this document is subject to change without notice. DocuSign API Developer Guide June 3, 2016 If you have any comments or feedback on our documentation, please send them to us at: [email protected]. Summary of changes for this version: Added tabOrder property to the Tab element that allows senders to set the order in which tabs are shown to users on a page when signing. Note that this option is not available for all account plans. Update the note for the CorrectAndResendEnvelope method to say if automatic reminders are enabled for the envelope, then resending the envelope resets the automatic reminder date and the resend date is used for determining when to send reminder messages.
    [Show full text]
  • Designer Scripting Reference
    Designer Scripting Reference AEM 6.2 Forms Legal notices For legal notices, see http://help.adobe.com/en_US/legalnotices/index.html. Last updated 5/24/16 Contents About the Scripting Reference . 1 Subforms and containers . 1 Version mapping to the XML Forms Architecture (XFA) . 2 XML Form Object Model Class Hierarchy . 3 object class . 3 list class . 4 treeList class . 5 tree class . 5 node class . 6 container class . 8 content class . 9 model class . 10 textNode class . 11 Scripting Objects . 13 arc . 13 area . 14 assist . 15 barcode . 16 bind . 18 bindItems . 19 bookend . 20 boolean . 21 border . 22 break (deprecated) . 23 breakAfter . 25 breakBefore . 26 i button . 28 calculate . 28 caption . 29 certificate . 31 certificates . 31 checkButton . 33 choiceList . 34 color . 35 comb . 36 command . 37 connect . 37 connectionSet . 39 connectString . 39 contentArea . 40 corner . 41 dataGroup (deprecated) . 42 dataModel . 43 dataValue . 44 dataWindow . 45 date . 46 dateTime . 47 dateTimeEdit . 48 decimal . 49 defaultUi (deprecated) . 50 delete . 51 desc . 52 digestMethod . 53 digestMethods . 54 draw . 55 dSigData . 57 effectiveInputPolicy . 59 effectiveOutputPolicy . 59 encoding . 60 encodings . 61 encrypt . 62 event . 63 eventPseudoModel . 64 exclGroup . 66 exData . 69 execute . 70 exObject . 71 extras . 72 field . 73 fill . 78 filter . 79 float . 80 ii font . ..
    [Show full text]
  • What's New in This Release
    What's New in this Release Scorpio includes new features and enhancements in the following product areas: ■ Interaction with other technologies and Adobe products ■ Administration and Configuration ■ Debugging ■ Language Enhancements ■ Arithmetic and string operations ■ Database access ■ Generating reports and presentations ■ OEM support Page 1 of 24 Interaction with other technologies and Adobe products Feature/Tag Description AJAX UI support Several new features have been added that take advantage of AJAX capabilities. The following new tags let you control the layout and behavior of your application: • The cflayout tag can create four types of layout regions. • The cflayoutarea tag defines the regions contained inside a layout created by a cflayout tag. • The cfwindow tag creates a pop-up window in the browser that you can programmatically show and hide. • The cfpod tag creates a region with an optional title bar. • The cfmenu tag creates a horizontal or vertical menu with optional submenus. • The cfmenuitem tag creates an entry in a menu. A menu item can be the root of a submenu. • The cftooltip tag lets you specify an optionally HTML-formatted tool tip that appears when the user moves the mouse pointer over the items defined by any tags in the cftooltip tag body. The cfgrid tag now has an html attribute value of AJAX that creates a dynamic HTML grid. The grid can optionally use a bind expression (see below) to dynamically fill and update the grid contents. The grid can optionally be divided into pages with each page contents retrieved from the server when the user requests the specific page, thereby improving initial load time.
    [Show full text]
  • 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
    Case 3:16-cv-04144-JST Document 49 Filed 11/15/16 Page 1 of 38 1 2 3 4 5 6 7 8 UNITED STATES DISTRICT COURT 9 NORTHERN DISTRICT OF CALIFORNIA 10 SAN FRANCISCO COURTHOUSE 11 12 ADOBE SYSTEMS INCORPORATED, a Case No.: 3:16-cv-04144-JST 13 Delaware Corporation, [PROPOSED] 14 Plaintiff, PERMANENT INJUNCTION AGAINST DEFENDANT ITR 15 v. CONSULING GROUP, LLC, AND DISMISSAL OF DEFENDANT ITR 16 A & S ELECTRONICS, INC., a California CONSULTING GROUP, LLC Corporation d/b/a TRUSTPRICE; SPOT.ME 17 PRODUCTS LLC, a Nevada Limited Liability Honorable Jon S. Tigar Company; ALAN Z. LIN, an Individual; 18 BUDGET COMPUTER, a business entity of unknown status; COMPUTECHSALE, LLC, a 19 New Jersey Limited Liability Company; EXPRESSCOMM INTERNATIONAL INC., a 20 California Corporation; FAIRTRADE CORPORATION, a business entity of unknown 21 status, FCO ELECTRONICS, a business entity of unknown status; ITR CONSULTING 22 GROUP, LLC, a Texas Limited Liability Company; RELIABLE BUSINESS PARTNER, 23 INC., a New York Corporation; LESTER WIEGERS, an individual doing business as 24 ULTRAELECTRONICS; and DOES 1-10, Inclusive, 25 Defendants. 26 27 28 - 1 - [PROPOSED] PERMANENT INJUNCTION & DISMISSAL – Case No.: 3:16-cv-04144-JST Case 3:16-cv-04144-JST Document 49 Filed 11/15/16 Page 2 of 38 1 The Court, pursuant to the Stipulation for Entry of Permanent Injunction & Dismissal 2 (“Stipulation”), between Plaintiff Adobe Systems Incorporated (“Plaintiff”), on the one hand, and 3 Defendant ITR Consulting Group, LLC (“ITR”), on the other hand, hereby ORDERS, 4 ADJUDICATES and DECREES that a permanent injunction shall be and hereby is entered against 5 ITR as follows: 6 1.
    [Show full text]
  • (Acrf.Pdf) Using SAS Program, FDF Files, Excel and Javascript in Acrobat Chen-Jung Wu, Firma Clinical Research
    PharmaSUG 2021 - Paper AP-071 An efficient method to review annotation and create bookmark for case report form (acrf.pdf) using SAS program, FDF files, excel and JavaScript in Acrobat Chen-Jung Wu, Firma Clinical Research ABSTRACT A common method to annotate case report form (acrf.pdf) is to use Acrobat comment tool to draw box and add text; however, this method is time consuming. If the case report form is changed due to protocol amendment, it may need another round to annotate manually. Besides, regular SDTM process involves several people to prepare the package including case report form so it always has some inconsistent issues related to typo, font size and font style. Therefore, converting annotation to excel can help to fix typo issue and update wording quickly; comparing the excel with the metadata in xpt and define.xml. Moreover, making use of excel to remap annotation to migrate page to new version of case report form is another efficient method if there are any changes for case report form due to the protocol amendment. INTRODUCTION A case report form is a paper or electronic questionnaire specifically used in clinical trial research. Figure 1. an example of a blank CRF page. An annotated case report form (acrf.pdf) is a blank CRF with annotations that document the location of the data with the corresponding names of the datasets and the names of those variables included in the submitted datasets. Figure 2. an example of an annotated CRF page for SDTM For annotating case report form (acrf.pdf) with related SDTM variables (Figure 3), it is time consuming.
    [Show full text]
  • What's New in Adobe Digital Enterprise Platform Document
    Discover What’s New in Adobe Digital Enterprise Platform Document Services Designer 10.0 Niall O’Donovan | Assure Dynamics © 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Niall O’Donovan at www.assuredynamics.com © 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 2 Customer experience management does not start here © 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 3 Customer experience management does not even start here © 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 4 Customer experience management starts here! © 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Awesome new features in Designer 10.0 . Add Flash content to a form. Control object formatting using style sheets. Access Solutions, such as Interactive Statements. More new features are included, but we'll discuss those later. © 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 6 Flash in Adobe XML Forms Architecture (XFA) is easy! © 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 7 Developing Flash for XFA © 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 8 Working with Flash in XFA Set the URL for the swf Set image, swf deactivated Settings for interacting with swf © 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 9 Getting started Adobe Digital Enterprise Platform Document Services - Designer 10.0 . Designer includes a new Flash Field object. Requires Acrobat or Adobe Reader 10 or later (preferably 10.1 or later). Set Target Version option to Acrobat and Adobe Reader 10.0 or later. Save form as Adobe Dynamic XML Form (*.pdf). Adobe Flash Builder 4.5.0 .
    [Show full text]
  • Implementing Forms, Workflows, and E-Signatures with Adobe Experience Manager Forms a Best Practices Guide
    Implementing forms, workflows, and e-signatures with Adobe Experience Manager Forms A best practices guide May 2017 TABLE OF CONTENTS 3 Transform enrollment with Adobe Experience Manager Forms 4 Design forms quickly for multiple channels and devices 7 Scale for multiple brands and regions 8 Produce a document of record to meet compliance objectives 9 Go paperless with e-signatures 10 Process submitted forms efficiently 12 Empower mobile workers on tablets or smartphones 13 Measure and optimize form experiences 15 Additional resources 2 Transform enrollment with Adobe Experience Manager Forms Adobe Experience Manager Forms helps government agencies, financial organizations, and other regulated industries streamline application enrollment, process submissions efficiently, and enable dynamic, personalized correspondence for standout customer experiences across any device or channel. Experience Manager Forms works seamlessly with Adobe Marketing Cloud solutions to transform disjointed customer journeys into connected and consistent experiences Read this customer story to find out how a South across multiple channels. African financial institution cut unnecessary steps and increased form completion. In this guide, you will find useful tips on creating simple to complex forms across the enterprise for various devices and channels, meet Adobe Experience Manager compliance goals and efficiently connect form data to backend systems. Forms was a major force in simplifying how we interact You will also learn how to setup analytics for forms and optimize with customers. We can cut experience via A/B testing seven-step processes down to four steps with more control over each form. Additionally, we output completed forms to PDF, giving the customer a copy to help ensure accuracy and add a layer of hands-on service.
    [Show full text]
  • Accessibility Best Practices for Adobe Livecycle Designer ES3 V10.0
    Accessibility Best Practices For Adobe LiveCycle Designer ES3 v10.0 CONTENTS 1.0 Introduction 1.0 Introduction An accessible form is one that almost everyone can use, 2.0 Best practices for including those who may have disabilities that affect how they creating forms are able to interact with the form on the computer screen. Users 3.0 Techniques for testing with visual impairments or reduced mobility, for example, are form accessibility still able to use accessible forms. 4.0 Mapping between Adobe LiveCycle Designer includes a number of features and guidelines and best capabilities that enhance the usability of forms for users with practices various disabilities, and that assist form authors in creating PDF forms that are more accessible to people with disabilities. 5.0 Useful links Building accessibility into forms not only allows the widest possible audience for content, it is a requirement when supplying documents in regions where compliance with accessibility standards is mandated. In the United States, for example, accessibility standards such as Section 508 of the Rehabilitation Act exist to ensure that information technology is available to all users, including government employees with disabilities and members of the public with disabilities that consume government services. LiveCycle Designer helps developers comply with the requirements mandated by accessibility standards. Its component-based approach enables form builders to take advantage of built-in accessibility features. LiveCycle Designer also provides support for creating accessible XHTML files (using LiveCycle Forms) and PDF forms. Accessible PDF forms include a complete logical structure plus additional information about a document’s contents to increase accessibility.
    [Show full text]
  • Sell and Succeed 3 REASONS to CALL Three Reasons to Call: Customers Who Currently Do Not Own Acrobat What to Ask What to Say
    Sell and Succeed 3 REASONS TO CALL Three reasons to call: Customers who currently do not own Acrobat What to ask What to say Do you need to reduce costly paper-based Acrobat X helps your team eliminate paper-based processes. Automate multistep tasks into 1 processes and speed decision-making in guided actions. Save time with shared reviews. Create PDF forms that can be filled out your organization? quickly. Streamline approval processes with digital signatures. Do your employees need to share Use Acrobat X to protect and share information. Apply passwords to control document information more securely with internal and access. Set permissions to restrict specific actions (for example, printing, copying, or altering 2 external teams? PDF files). Redact sensitive text and images. Remove hidden information (for example, metadata and bookmarks) with one-click document sanitization. Do your teams need to deliver high-impact Deliver high-impact communications by combining a wide range of content in a PDF communications to colleagues, customers, Portfolio. Customize with new layouts, visual themes, and color palettes. Insert audio, Adobe 3 and partners? Flash® Player compatible video, and interactive media into PDF files for seamless playback in Adobe Reader.®* * Adobe Reader 9 or later required 3 Three reasons to call: Customers with a previous version of Acrobat What to ask What to say Is your organization updating hardware, Acrobat X supports the latest operating systems and software applications, including: operating systems, or office applications? • Microsoft Windows® 7 32- and 64-bit editions • Microsoft Office 2010 1 • Mac OS X v10.6 • AutoCAD® 2010 • Internet Explorer 8 • IBM Lotus Notes 8.5 • Firefox 3.6 Do you want your employees to work Improve project collaboration with Acrobat X.
    [Show full text]