Skip to Content

The purpose of this document is to provide a basic  level of information to help you perform form customization.

 

The Form structure can be divided in 3 parts.

  1. Page Header.

     Company logo

     Document type name.

 

2.      Page Body.

Sender and receiver address.

Document information.

 

3.       Page Footer.

 

 

formoverview.PNG

The Master Pages of Adobe LiveCycle Designer often contain placeholders for the header and footers of the Form Master Template. Master Page is different from the  Form Master Template.

 

 

Master Page

  • Master Page is equal recurring layout for every page (like PowerPoint Master Layout)
  • Usually there are 2 master pages: one for the first page, the other for the following pages
  • Placeholder for data like company logo, header and footer that can be maintained within the Master Template Maintenance.

 

 

masterpage.PNG

 

Tool Introduction

  •     Library.
  •     Hierarchy.
  •     Data View.
  •     Editor for Scripting.

 

Toolinstruct.PNG

Library

  • Available objects to be used on the form template.

 

Hierarchy

  • The hierarchy shows the objects from the library, that have been assigned to the Master Pages or Design View.
  • bdyMain = objects used in Design View
  • Structure Nodes can be Subforms or Tables
  • Objects shown in the hierarchy have logic or data bindings to fields from Data View

 

Data View

  • Data view has the data source that can be assigned to the form, Those fields could be assigned to “used” objects in Hierarchy.

 

 

Editor for Scripting

  • The Scripting is used to put simple/complex logic into “used” objects , E.g. show data only if data are available like fax information of responsible employee.

You can use two scripting languages within ALD:  FormCalc  or JavaScript.

 

EditoScript.PNG

 

 

 

Best Practices for Frequent Use Cases

  • Add new Tex Field 2/2.
  • Assign Data Binding to Text Field.
  • Changing Font Size and Style.
  • Renaming Fields 2/2.
  • Change Presence of Fields (Hide/Unhide)

 

Add new Tex Field 1/2

addfield1.PNG

 

Add new Tex Field 2/2

addfield2.PNG

 

Assign Data Binding to Text Field.

 

DBinding.PNG

 

Changing Font Size and Style.

 

fontsize.PNG

Renaming Fields 1/2

Changename1.PNG

Renaming Fields 2/2

Changename2.PNG

 

Change Presence of Fields (Hide/Unhide)

Hide.PNG

 

This is a little overview of the tool.

 

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. David Maher

    Hi Julio

    Thanks for this overview – I’m doing an implementation where we want the invoice to provide detail at the product category level only. ie we have a category called “labour” which might have 10 line items but the client only want to show their customer the total values of the product category, not the discrete line items – is this possible in Lifecycle Designer?

    Cheers,

    Dave

     

    (0) 

Leave a Reply