Skip to main content link. Accesskey S
  • Log In
  • Help
  • IBM Logo
  • IBM Forms wiki
  • All Wikis
  • All Forums
  • Home
  • Product Documentation
  • Community Articles
  • Learning Center
  • IBM Redbooks
Community Articles Product Documentation Learning Center IBM Redbooks This category All IBM Forms 4.0 documentation IBM Forms Server 4.0 API documentation Custom Search Scope...
Search
Community Articles > Best Practices for Form Design > General Form Design Best Practices > Correct validoverlap to sign forms
  • New Article
  • Share Show Menu▼
  • Subscribe Show Menu▼

About the Original Author

Adam Kozyniak
Contribution Summary:
  • Articles authored: 115
  • Articles edited: 103
  • Comments Posted: 0

Recent articles by this author

Specify type for public data

When creating or marking data as public in the Designer, specify the data type using a Model Item Property. Example Below are some examples of Model Item Property data types: xforms:bind nodeset"instance('INSTANCE1')PAGE1ffloat" type"xsd:float" xforms:bind xforms:bind ...

Do not cross reference types when mapping data

When mapping data, do not crossreference data types. Data should be mapped type to type, for example string to string rather than string to integer.

Do not create submission or cancellation buttons for forms used in FileNet

A Lotus form imported into FileNet is submitted using the SaveLaunchComplete buttons located in the FileNet toolbar. The form itself should contain no submission or cancellation buttons. When creating a form for FileNet using the Designer, do not insert submission or cancellation buttons into ...

Toolbar differences between Lotus Forms and FileNet

When rendering forms, toolbar hotkey accessibility differs between Lotus Forms and FileNet. Lotus Forms accessibility also varies based on the browser. FileNet eForms use Java Script key listeners, which means toolbar hotkeys will always be Ctrl + Alt + key. Lotus Forms forms use the HTML based ...

Use ufv_settings to hide Lotus Forms menu

When a form is created for use in FileNet, use the ufvsettings in the Designer to turn off the menu toolbar. Forms rendered in FileNet use the FileNet toolbar to control form submission. The menu used by Lotus Forms is not required and should be turned off. Example ufvsettings menu ...

Community articleCorrect validoverlap to sign forms

Added by Adam Kozyniak | Edited by IBM contributor Jack Mitchell on December 2, 2010 | Version 8
  • Edit
  • More Actions Show Menu▼
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars
expanded Abstract
collapsed Abstract
No abstract provided.
Tags: overlap test, security, signatures, validoverlap



The validoverlap feature adjusts the tolerance of the overlap test between signed and unsigned items performed by the Viewer when signing items. The overlap test looks for signed items that overlap unsigned items. You should always follow the best practice of signing as much of the form as possible. This means that if your form fails the overlap test, you should first consider whether you can sign additional items to correct this problem.

Lines can often cause problems. In general, you should either sign all lines in the form, or sign none of the lines in the form. This will help you avoid problems with lines that overlap each other. If you choose to sign none of the lines in the form, you may need to adjust the placement of some lines to prevent them from overlapping with other items, such as fields. While this may seem like a lot of work, it's preferable to signing the overlapping line. Signing the line may create more problems than it solves, as the line may overlap with a number of other lines which may overlap with further lines, and so on. Because of the work involved in determining which lines need to be signed, it's best to avoid this scenario if possible.

Because unsigned items might be moved later to reveal information that changes the meaning of the form, the overlap test prevents the user from signing these forms. However, in some cases the overlap is very slight and should be allowed. If you still find that you cannot sign your form because of overlapping items, you should adjust the validoverlap setting by small increments (such as 1 or 2 pixels) until you can successfully sign the form, or until you reach an overlap of 8 pixels.

Usage Notes


Never set the validoverlap to allow more than 8 pixels of overlap. If you find that you still cannot sign your form with an overlap of 8 pixels, the form should be redesigned so that items do not overlap as much. Using a larger validoverlap increases the risk that a malicious user could successfully modify a signed form.

The validoverlap can also be set as low as 0 (zero) pixels. The default of 2 pixels accounts for the size of a border, which is included in the size of each item, even if the border is not drawn.

Exceptions to this practice


There are no exceptions to this practice.

  • Edit
  • More Actions Show Menu▼


expanded Attachments (0)
collapsed Attachments (0)
Edit the article to add or modify attachments.
expanded Versions (8)
collapsed Versions (8)
Version Comparison     
VersionDateChanged by              Summary of changes
This version (8)Dec 2, 2010 3:43:53 PMJack Mitchell  IBM contributor
7Apr 15, 2009 5:12:53 PMDeanna Drschiwiski  IBM contributor
6Sep 8, 2008 12:47:44 PMDeanna Drschiwiski  IBM contributor
5Jul 4, 2008 4:11:19 PMDeanna Drschiwiski  IBM contributor
4Jul 4, 2008 1:27:17 PMDeanna Drschiwiski  IBM contributor
3Jun 12, 2008 2:44:32 PMAdam Kozyniak  IBM contributor
2Jun 10, 2008 7:36:32 PMAdam Kozyniak  IBM contributor
1May 27, 2008 6:34:22 PMAdam Kozyniak  IBM contributor
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 ConnectedHelpAbout
  • IBM Collaboration Solutions wikis
  • IBM developerWorks
  • IBM Software support
  • Twitter LinkIBMSocialBizUX on Twitter
  • FacebookIBMSocialBizUX on Facebook
  • ForumsLotus product forums
  • BlogsIBM Social Business UX blog
  • Community LinkIBM Collaboration Solutions
  • Wiki Help
  • Forgot user name/password
  • Wiki design feedback
  • Content feedback
  • About the wiki
  • About IBM
  • Privacy
  • Accessibility
  • IBM Terms of use
  • Wiki terms of use