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 > Use omit rather than keep for signature filters
Rate this article 1 starRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

Use omit rather than keep for signature filters 

expanded Abstract
collapsed Abstract
No abstract provided.



When creating signature filters, use the omit flag rather than the keep flag. Digital signatures with omit flags sign everything in the form except those elements that you specifically exclude.

Consistently using this practice prevents you from accidentally excluding items and options that should be signed. If you don't sign the proper form items and options, the form is vulnerable to malicious alteration. In turn, this may lead to forms that will not withstand scrutiny.

When setting filter options with the Designer, omit is the default flag. Accepting this default ensures that users sign everything except the items and options you specifically exclude.

If you rely on keep filters, you must specify each item and option the signature is to sign. This increases the risk that you will miss an item or option you intended to include in the signature. Also, using keep filters could subsequently allow someone to add to the form's contents without breaking the signature. This is prevented if you use omit filters.

Note:
Filters which use the keep or omit flag include signitems, signoptions, signgroups, signdatagroups, signitemrefs, signoptionrefs, and signpagerefs.

Example


There are certain options that form designers must always omit in a form. If you create your forms using the Designer, it automatically creates the signoptions filter for you. These options are triggeritem and coordinates. Both of these options are normally updated after the form is signed. For example, triggeritem is set when you submit the form, even if you have already signed it.

The following code depicts an omit filter that excludes triggeritem and coordinates:

<signoptions> 

  <filter>omit</filter> 

  <optiontype>triggeritem</optiontype> 

  <optiontype>coordinates</optiontype> 

</signoptions>


This construction creates a filter that excludes a minimum of information from the signed form. In general, this is a good practice when creating filters.

Note:
When omitting items from the signature, ensure that you secure their positioning information.

Exceptions to this practice


An exception to this practice may occur when you are filtering multiple and overlapping signatures. You should generally use omit for the form’s primary signature, but you can use keep for a secondary signature if it signs only the primary signature.

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

This Version: Version 7 March 21, 2011 3:47:06 PM by Neal A Timpe  IBMer

expanded Attachments (0)
collapsed Attachments (0)

 


expanded Versions (7)
collapsed Versions (7)
Version Comparison     
Version Date Changed by               Summary of changes
This version (7) Mar 21, 2011 3:47:06 PM Neal A Timpe  
6 Dec 2, 2010 6:11:44 PM Jack Mitchell  
5 Apr 15, 2009 5:12:39 PM Deanna Drschiwiski  
4 Sep 8, 2008 6:14:43 PM Deanna Drschiwiski  
3 Jun 12, 2008 2:12:18 PM Adam Kozyniak  
2 Jun 10, 2008 6:25:25 PM Adam Kozyniak  
1 Jun 9, 2008 6:26:46 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