Indicates the digital signature operation to perform when used in conjunction with the signData object, or the object to link to when used in conjunction with the traverse object.Reference_Syntax.signData.operation = “sign | verify | clear”Reference_Syntax.traverse.operation = “next | up | down | left | right | back | first”
For digital signatures (using the signData object):
• Add an XML signature to the XML data being submitted. This operation does not modify the application’s active document.
• Verifies an XML signature. If the verification fails, the submission processes are canceled and the application issues a message indicating why the submission failed. This operation is performed before any signature is created or cleared.
• Removes an XML signature, if it exists, from the XML data being submitted. This operation does not modify the application’s active document and is performed before any signature is created. For object-linking (using the traverse object):
• next (default)Used when the user presses the Tab key or enters the final character in a fixed-width field. However, the same chain of next links is also traversed by the screen reader when reading the form. Defaults to left-to-right top-to-bottom order.The chain of next links can include boilerplate objects, but these objects cannot accept input focus. Therefore, when advancing focus to the next form object, tabbing continues until an object that accepts input focus is reached. You must ensure that the form design does not present a non-terminating loop.This property is used only when the container is a subform or subform set. The link points to the object that gains focus when the container is entered. In effect the container delegates focus via this link. Defaults to the first container that is a child of this container, in top-to-bottom left-to-right order.