Skip to main content link. Accesskey S
  • Anonymous
  • Log on
  • Help
  • IBM logo
  • IBM Forms wiki
  • All Wikis
  • Home
  • Community Articles
  • Product Documentation
  • Learning Center


Search

Advanced Search

Categories

Tag Cloud

  • 3.0
  • 3.5
  • 3.5.1
  • 4.0
  • 4.0.0.1
  • 4.0.0.2
  • 8.0
  • accessibility
  • actions
  • API
  • app dev
  • button item
  • buttons
  • C
  • certificates
  • COM
  • compute
  • computes
  • configuring
  • creating
  • defining
  • demonstration
  • demos
  • deployment
  • deployment scenario
  • design
  • design tips
  • Designer
  • designing
  • dev guide
  • develop
  • developing
  • differences between Webform Server and Viewer
  • education
  • Enablement
  • enterprise
  • error messages
  • events
  • field
  • field item
  • FileNet
  • filtering
  • form
  • formatting
  • forms
  • forms experience builder
  • Forms Services Platform
  • FSP
  • functions
  • getting_started
  • Help
  • IBM Forms
  • images
  • installing
  • integrating
  • integrating, 4.0.0.1
  • items
  • JAVA
  • JavaScript API
  • language
  • languages
  • layout
  • lf_intro
  • math functions
  • methods
  • new_user
  • options
  • P8
  • performance
  • pipelines
  • pipes
  • printing
  • programming
  • Properties
  • samples
  • services
  • signature item
  • signatures
  • spec
  • string functions
  • strings
  • StrJava
  • submissions
  • table
  • tables
  • text
  • training
  • translation
  • Turbo
  • turbo_media
  • tutorials
  • utility functions
  • video
  • Viewer
  • viewer package
  • Webform Server
  • WebformServer
  • XFDL
  • XForms
  • XPath
InformationInformation
You are currently viewing machine translated content. IBM translation might be available. Click IBM Translated Product Documentation to see what is available.X


Home > Best Practices for Form Design > Sign item positioning information
Rate this article 1 starRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

Sign item positioning information 

expanded Abstract
collapsed Abstract
No abstract provided.



Item positioning specifies where each item is displayed on a form. When creating signature filters, always ensure that you secure the positioning information of all of your form items. Even items that you have omitted from your signitems option should have a signoptions or signoptionrefs option filter that keeps their item positions. While itemlocation is the most obvious option that contains positioning information, there are other options that could potentially effect the location, size, or appearance of an item, such as size, visible, or scrollhoriz and scrollvert. The Designer automatically secures these options, unless you choose otherwise.

Setting signatures to sign positioning information helps prevent someone from using unsigned items and options to obscure signed items. If items are obscured, readers could potentially misunderstand what they are signing. This may allow users to repudiate their signed forms based on an incorrect perception of what they were signing.

Consider an online insurance policy application. If a flaw in a signature filter permitted someone to obscure contract terms that are crucial to the user’s understanding, the contract could be successfully challenged.

There are two types of positioning information: absolute and relative. Absolute positioning requires that you position items using x and y coordinates in pixels. The relative positioning scheme, however, places items in relation to other items. If you use relative positioning, you must sign the anchor item so that it cannot be moved. If someone moves an unsecured anchor item, it automatically displaces all of the items that are dependent upon it for positioning information. Regardless of the type of item positioning you use, you must secure the positioning information or a malicious user could displace form items and obscure important information.

Using this practice allows you to lock down the appearance and location of items that otherwise cannot be signed. For example, you might exclude certain compute items with an omit filter. However, to prevent malicious modification of those items, you can specify options to secure using the keep filter.

Note:
You should set signatures to sign all item positioning information, regardless of whether positioning is absolute or relative. However, whenever practical, you should use absolute rather than relative positioning.

Example


The following diagrams illustrate a portion of a brokerage application form. In this form, the check boxes and fields are positioned below the anchor labels using relative positioning. These anchor labels are not secured by a signature filter. As you can see in the second diagram, LabelB and its dependent items have been moved to obscure LabelA and its dependent items.



For example, in the following code the signature filter omits LabelB but keeps its itemlocation:
    <signitemrefs>
    <filter>omit</filter>
    <itemref>PAGE1.LABELB</itemref>
    </signitemrefs>
    This signitemrefs option omits LABELB from the signature filter.
    <signoptionrefs>
    <filter>keep</filter>
    <optionref>PAGE1.LABELB.itemlocation</optionref>
    <optionref>PAGE1.LABELB.size</optionref>
    <optionref>PAGE1.LABELB.fontinfo</optionref>
    <optionref>PAGE1.LABELB.visible</optionref>
    <optionref>PAGE1.LABELB.value</optionref>
    </signoptionrefs>
    This signoptionrefs option secures LABELB's itemlocation.






Usage notes

If you use an omit signature filter, you automatically secure the form's item positioning, except for those items you specifically exclude. If you do exclude some items with an omit filter, pair it with a keep filter to secure the item positioning information.

Itemlocation is not the only option that can potentially affect the location, size, or appearance of an item. If an item is omitted from the signature filter, you should consider adding all of these options to a keep filter. These options include:
  • itemlocation
  • fontinfo
  • labelfontinfo
  • size
  • visible
  • value
  • scrollhoriz
  • scrollvert
  • fontcolor
  • labelfontcolor
  • bordercolor
  • labelborderwidth
  • thickness
Exceptions to this practice

There are no exceptions to this practice.

expanded Article information
collapsed Article information
Category:
Best Practices for Form Design, Forms Designer, Webform Server, Forms Viewer, Signature Best Practices,
Tags:
security, signatures

This Version: Version 10 March 29, 2011 2:50:45 PM by Neal A Timpe  IBMer

expanded Attachments (0)
collapsed Attachments (0)

 


expanded Versions (10)
collapsed Versions (10)
Version Comparison     
Version Date Changed by               Summary of changes
This version (10) Mar 29, 2011 2:50:45 PM Neal A Timpe  
9 Dec 2, 2010 6:09:40 PM Jack Mitchell  
8 Apr 15, 2009 5:11:42 PM Deanna Drschiwiski  
7 Apr 7, 2009 6:47:35 PM Deanna Drschiwiski  
6 Sep 8, 2008 6:11:44 PM Deanna Drschiwiski  
5 Jul 7, 2008 12:50:08 PM Deanna Drschiwiski  
4 Jul 7, 2008 12:26:59 PM Deanna Drschiwiski  
3 Jun 12, 2008 2:11:18 PM Adam Kozyniak  
2 Jun 10, 2008 6:23:55 PM Adam Kozyniak  
1 Jun 9, 2008 7:01:07 PM Adam Kozyniak  
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedSubscribe to RSSHelpAbout
  • All Lotus and WebSphere Portal wikis
  • IBM developerWorks
  • IBM Software support
  • IBM Social Business User Experience Blog
  • IBMSocialBizUX on Twitter
  • IBMSocialBizUX on Facebook
  • Lotus product forums
  • IBM Social Business UX blog
  • IBM Collaboration Solutions
  • Recently added feedRecently added
  • Recently edited feedRecently edited
  • Recently added comments feedRecently Added Comments
  • Wiki Help
  • Forgot user name/password
  • Wiki design feedback
  • Content feedback
  • About the wiki
  • About IBM
  • Privacy
  • Contact IBM
  • IBM Terms of use
  • Wiki terms of use