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 keep to create overlapping signatures
Rate this article 1 starRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

Use keep to create overlapping signatures 

expanded Abstract
collapsed Abstract
No abstract provided.



When creating multiple and overlapping signatures, you may be able to use keep instead of omit. If you want a secondary signature to sign the primary signature, you can use keep to sign only the primary signature. For example, you could use this strategy if you wanted a manager to sign an employee's information and signature.

Why Use This Practice


This practice simplifies the creation of overlapping signatures, saving form development time. Your choice of omit or keep for secondary signatures depends on whether the secondary signatures are signing information the primary signature didn't. In general, when creating secondary signatures you should consider the following:
  • When the secondary signature signs different information than the primary signature, use omit to create the secondary signature filters
  • When the secondary signature signs the same information as the primary signature as well as the primary signature itself, you can use keep to have the secondary signature sign only the primary signature. Since the primary signature has already locked the contents of the form, the secondary signature only needs to lock the primary signature itself.

Example

The following diagrams show a form in which the first signature signs the body of the form, but not the second signature. The second signature then signs the first signature, and by extension, the body of the form. This allows the second signer to endorse the original signature.



In the following code sample, SIGNATURE1 and SIGNATURE2 are set as follows:
  • Signature1 is the primary signature.
  • Signature2 is the secondary signature and signs only BUTTON1 and its associated signature.
    • <signitemrefs</em>>
      <filter>omit</filter>
      <itemref>PAGE1.SIGNATURE2</itemref>
      </signitemrefs>
      Signature1 omits Signature2
      <signoptions>
      <filter>omit</filter>
      <optiontype>triggeritem</optiontype>
      <optiontype>security_info</optiontype>
      </signoptions>
      Signature1 also omits triggeritems, allowing the user to click buttons without breaking the signature.
      <signitemrefs>
      <filter>keep</filter>
      <itemref>PAGE1.SIGNATURE1</itemref>
      <itemref>PAGE1.BUTTON1<itemref>
      </signitemrefs>
      Signature2 keeps Button1 and Signature1







Exceptions to this practice

There are no exceptions to this practice.

Back to: Signatures

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

This Version: Version 7 March 29, 2011 2:54:20 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 29, 2011 2:54:20 PM Neal A Timpe  
6 Dec 2, 2010 6:11:22 PM Jack Mitchell  
5 Apr 15, 2009 5:12:34 PM Deanna Drschiwiski  
4 Sep 8, 2008 1:24:07 PM Deanna Drschiwiski  
3 Jun 12, 2008 2:12:05 PM Adam Kozyniak  
2 Jun 10, 2008 6:25:06 PM Adam Kozyniak  
1 Jun 9, 2008 6:31:18 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