Using-Designer.Pdf

Total Page:16

File Type:pdf, Size:1020Kb

Using-Designer.Pdf Using Designer AEM 6.3 Forms Legal notices For legal notices, see http://help.adobe.com/en_US/legalnotices/index.html. Last updated 4/26/17 Contents Welcome to Designer . 1 About Designer . 1 Using Designer in the SAP environment . 1 Using Designer in different spaces . 2 New features in Designer . 2 Render XFA forms as HTML5 forms . 2 Support for Turkish Lira locale . 2 Support for Japanese Postal barcode . 3 Accessibility Checker . 3 Add document title to the PDF title bar . 3 Support for Hindi language . 3 New features in Designer . 3 Preview your XDP forms in HTML in Designer . 3 Preview your XDP forms in HTML in forms manager . 4 Accessibility Checker . 4 Add document title to the PDF title bar . 4 Where to find documentation, samples, and tutorials . 4 Get started with samples and tutorials . 5 Add calculations to forms . 5 Enhance forms by using scripts . 5 Getting Started . 7 About forms . 7 Interactive forms . 7 Non-interactive forms . 8 Print and fill forms . 8 About form designs . 8 Form design layouts . 9 i Fixed layout . 9 Flowable layout . 9 Parts of a form design . 10 Master pages . 10 Pages . 11 Content areas . 11 Subforms . 11 Tables . 12 Field objects . 12 Boilerplate or static objects . 13 Installing and configuring Designer . 13 Configuring JVM settings . 13 Looking at the workspace . 14 About editors . 14 About palettes . 17 Customizing the workspace . .23 Managing library palettes . 28 Steps to creating a form design . 33 Basic steps to creating a form design . 33 Plan the form design . 33 Create the form design . 34 Save the form design . 35 Preview and test the form design . 36 Publish the form . 36 Distribute the form . 36 Create Form Designs . 37 Create, open, and save . 37 Creating forms . 37 Considerations for creating forms for use with Acrobat and Adobe Reader . 39 Adding details about the form . .40 To set user permissions on a PDF form . 42 Saving forms . 42 Opening forms . 44 Selecting the Acrobat and Adobe Reader target version . 45 Saving forms for Acrobat and Adobe Reader . 46 Distributing forms . 46 Publishing forms . 47 Creating and managing templates . 49 Creating and managing templates . 50 Page layout . 55 Setting up pages . 55 Using master pages . 57 Specifying white space around the edges of a form . 60 Headers, footers, and other background items . 62 Assigning additional master pages to complex form designs . 62 ii Applying master pages to forms whose number of pages vary . 64 To use the first master page one time only . 65 Controlling the order and visibility of pages . 66 Setting page break controls . 67 Styles . 69 To sort the style sheets in the Style Catalog . 70 To select a default style sheet for new forms . 70 To add a style sheet to a form . 71 To create a new style sheet . 71 To embed a style sheet . 71 To extract styles to a new style sheet . .72 To remove a style sheet . 72 To replace a style sheet . 72 To edit a style sheet file . 73 Create a new style from an object . 73 Creating a new style for an object type . ..
Recommended publications
  • WEKA Manual for Version 3-7-8
    WEKA Manual for Version 3-7-8 Remco R. Bouckaert Eibe Frank Mark Hall Richard Kirkby Peter Reutemann Alex Seewald David Scuse January 21, 2013 ⃝c 2002-2013 University of Waikato, Hamilton, New Zealand Alex Seewald (original Commnd-line primer) David Scuse (original Experimenter tutorial) This manual is licensed under the GNU General Public License version 3. More information about this license can be found at http://www.gnu.org/licenses/gpl-3.0-standalone.html Contents ITheCommand-line 11 1Acommand-lineprimer 13 1.1 Introduction . 13 1.2 Basic concepts . 14 1.2.1 Dataset . 14 1.2.2 Classifier . 16 1.2.3 weka.filters . 17 1.2.4 weka.classifiers . 19 1.3 Examples . 23 1.4 Additional packages and the package manager . .24 1.4.1 Package management . 25 1.4.2 Running installed learning algorithms . 26 II The Graphical User Interface 29 2LaunchingWEKA 31 3PackageManager 35 3.1 Mainwindow ............................. 35 3.2 Installing and removing packages . 36 3.2.1 Unofficalpackages ...................... 37 3.3 Usingahttpproxy.......................... 37 3.4 Using an alternative central package meta data repository . 37 3.5 Package manager property file . 38 4SimpleCLI 39 4.1 Commands . 39 4.2 Invocation . 40 4.3 Command redirection . 40 4.4 Command completion . 41 5Explorer 43 5.1 The user interface . 43 5.1.1 Section Tabs . 43 5.1.2 Status Box . 43 5.1.3 Log Button . 44 5.1.4 WEKA Status Icon . 44 3 4 CONTENTS 5.1.5 Graphical output . 44 5.2 Preprocessing . 45 5.2.1 Loading Data .
    [Show full text]
  • Tinkertool System 7 Reference Manual Ii
    Documentation 0642-1075/2 TinkerTool System 7 Reference Manual ii Version 7.5, August 24, 2021. US-English edition. MBS Documentation 0642-1075/2 © Copyright 2003 – 2021 by Marcel Bresink Software-Systeme Marcel Bresink Software-Systeme Ringstr. 21 56630 Kretz Germany All rights reserved. No part of this publication may be redistributed, translated in other languages, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of the publisher. This publication may contain examples of data used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. The publisher may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Make sure that you are using the correct edition of the publication for the level of the product. The version number can be found at the top of this page. Apple, macOS, iCloud, and FireWire are registered trademarks of Apple Inc. Intel is a registered trademark of Intel Corporation. UNIX is a registered trademark of The Open Group. Broadcom is a registered trademark of Broadcom, Inc. Amazon Web Services is a registered trademark of Amazon.com, Inc.
    [Show full text]
  • 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]
  • 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]
  • User Interface Specification for Interactive Software Systems
    User Interface Specification for Interactive Software Systems Process-, Method- and Tool-Support for Interdisciplinary and Collaborative Requirements Modelling and Prototyping-Driven User Interface Specification Dissertation zur Erlangung des akademischen Grades des Doktor der Naturwissenschaften (Dr. rer. nat.) Universität Konstanz Mathematisch-Naturwissenschaftliche Sektion Fachbereich Informatik und Informationswissenschaft Vorgelegt von Thomas Memmel Betreuer der Dissertation: Prof. Dr. Harald Reiterer Tag der mündlichen Prüfung: 29. April 2009 1. Referent: Prof. Dr. Harald Reiterer 2. Referent: Prof. Dr. Rainer Kuhlen Prof. Dr. Rainer Kuhlen For Cathrin Acknowledgements I thank my advisor, Prof. Dr. Harald Reiterer, for more than 6 years of great Prof. Dr. Harald Reiterer teamwork. Since I joined his work group as a student researcher, his guidance and friendship have helped me to reach high goals and achieve scientific recognition. I thank Harald for his creative contributions and his unfailing support, which made him the best supervisor I could imagine. Every time I read the Dr. in front of my name, I will think about the person who made it possible. It was Harald! Moreover, I thank him for teaching me many skills, of which especially purposefulness and per- suasive power opened up a world of possibilities. Among the other researchers in the human-computer interaction work group, spe- My colleague and friend Fredrik cial thanks are due to my colleague Fredrik Gundelsweiler. Fredrik and I started working for Harald at the same time, and since then we have shared many experi- ences. I worked with Fredrik at Siemens AG in Munich, and we both gained interna- tional work experience during our stay at DaimlerChrysler AG in Singapore.
    [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]
  • (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]
  • Vtpin: Practical Vtable Hijacking Protection for Binaries
    VTPin: Practical VTable Hijacking Protection for Binaries Pawel Sarbinowski Vasileios P. Kemerlis Cristiano Giuffrida Vrije Universiteit Amsterdam Brown University Vrije Universiteit Amsterdam [email protected] [email protected] [email protected] Elias Athanasopoulos Vrije Universiteit Amsterdam [email protected] ABSTRACT 1. INTRODUCTION VTable hijacking has lately been promoted to the de facto technique The recent advances in software hardening have undoubtedly for exploiting C++ applications, and in particular web browsers. made exploitation a challenging craft [45]. Yet, despite the plethora VTables, however, can be manipulated without necessarily corrupt- of defenses in place [37], attackers still find ways to compromise ing memory, simply by leveraging use-after-free bugs. In fact, in essential commodity software, like web browsers [5,6]. Modern the recent Pwn2Own competitions all major web browsers were exploits are highly sophisticated and typically leverage a variety of compromised with exploits that employed (among others) use-after- different vulnerabilities to bypass established protections, such as free vulnerabilities and VTable hijacking. address space layout randomization (ASLR) [42], non-executable In this paper, we propose VTPin: a system to protect against memory [12], and sandboxing [18]. To this end, temporal safety VTable hijacking, via use-after-free vulnerabilities, in large C++ errors, and particularly use-after-free vulnerabilities, are becoming binaries that cannot be re-compiled or re-written. The main idea be- a key component of the attackers’ arsenal [1,2,7,8]. Interestingly, hind VTPin is to pin all the freed VTable pointers on a safe VTable exploiting use-after-free bugs does not require corrupting memory; under VTPin’s control.
    [Show full text]
  • United States Patent (19) 11 Patent Number: 6,061,061 Conrad Et Al
    US006061061A United States Patent (19) 11 Patent Number: 6,061,061 Conrad et al. (45) Date of Patent: *May 9, 2000 54) COMPUTER SYSTEM WITH GRAPHICAL 2693810 6/1991 France. USER INTERFACE INCLUDING SPRING LOADED ENCLOSURES OTHER PUBLICATIONS 75 Inventors: Thomas J. Conrad, San Jose; Yin Yin tiMy“M ft WindowSTM 7 User’sSer's Guide.Oude, MiMicroSOIL ft UorporaC Wong, Menlo Park, both of Calif. “Screen Dumps from Microsoft WindowsTM v3.1.” 73 ASSignee: Apple Computer, Inc., Cupertino, Microsoft Corporation, 1985-1992, pp. 1-10. Calif. Jeff Johnson, et al., “The Xerox Star: A Retrospective,” Computer, Sep. 1989, pp. 11-27. * Notice: This patent is subject to a terminal dis- Brad W. Myers, “Window Interfaces, A Taxonomy of Win claimer. dow Manager User Interfaces.” IEEE Computer Graphics and Applications, Sep. 1988, pp. 65-83. 21 Appl. No.: 08/889,719 “Automatic Window Management Mode.” IBM Technical 9 Disclosure Bulletin, vol. 35, No. 4B, Sep. 1992. 22 Filed: Jul. 8, 1997 (List continued on next page.) Related U.S. Application Data Primary Examiner-Crescelle N. dela Torre 63 Continuation of application No. 08/482,186, Jun. 7, 1995, Attorney, Agent, or Firm Blakely, Sokoloff Taylor & Pat. No. 5,680,562, which is a continuation of application Zafman No. 08/076.253, Jun. 11, 1993, Pat. No. 5,583,984. (51) Int. Cl. ................................................ G06F 15/00 57 ABSTRACT 52 U.S. Cl. ............................................. 345/340; 345/348 A new behavior in a graphical user interface allows the user 58 Field of Search ..................................... 345/340, 326, to open and close enclosures, while dragging an object.
    [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]