Abstract: Systems and techniques for storing an electronic document signed during an electronic document signing process. A computing device receives an electronic document that includes content within a content area, an image field positioned on the content area, and a cross sign field positioned partially on the image field and partially on the content area. The computing device receives an image to populate the image field and a signature to populate the cross sign field. The computing devices creates a first signature portion and a second signature portion by splitting the signature. The image is modified with the first signature portion and the content area is modified with the second signature portion. The computing device stores the electronic document by storing a file having separate elements, the separate elements including the modified content area and the modified image, without including the complete signature, unaltered content area, or unaltered image.

Abstract: A user manipulates a document using a desktop computer with a large screen. Upon deciding to sign the document, the user invokes a “Sign with Mobile” workflow that causes a two-dimensional barcode to be displayed. Using a signature acquisition application executing on his or her smartphone, the user scans the displayed barcode and creates an electronic signature by snapping a photograph of a conventional pen-and-paper signature or by detecting a handwritten signature drawn on a touch sensitive surface. The signature acquisition application sends the resulting electronic signature to the desktop computer, for example via an electronic signature server. The user is then able to apply the electronic signature to the document as desired.

Abstract: An electronic signature system includes infrastructure for securely managing document preparation during signing workflows through the assignment of permissions to users that control user actions to add, remove, and/or edit documents in a document package as part of an electronic signing workflow. The permissions may be assigned based on roles given to each user, and used to manage the signing workflow and user accesses to the document package. The electronic signature system determines whether to authorize the contributors to add, remove, and/or edit documents during the workflow according to the assigned permissions of each user. Document metadata is captured that identifies users and/or user groups associated user actions on particular documents. Access to those documents may be restricted using the document metadata. Once the document package is prepared, the document package is provided to a signer for review and for an electronic signature of documents of the document package.

Abstract: Systems and techniques for storing an electronic document signed during an electronic document signing process. A computing device receives an electronic document that includes content within a content area, an image field positioned on the content area, and a cross sign field positioned partially on the image field and partially on the content area. The computing device receives an image to populate the image field and a signature to populate the cross sign field. The computing devices creates a first signature portion and a second signature portion by splitting the signature. The image is modified with the first signature portion and the content area is modified with the second signature portion. The computing device stores the electronic document by storing a file having separate elements, the separate elements including the modified content area and the modified image, without including the complete signature, unaltered content area, or unaltered image.

Abstract: A user manipulates a document using a desktop computer with a large screen. Upon deciding to sign the document, the user invokes a “Sign with Mobile” workflow that causes a two-dimensional barcode to be displayed. Using a signature acquisition application executing on his or her smartphone, the user scans the displayed barcode and creates an electronic signature by snapping a photograph of a conventional pen-and-paper signature or by detecting a handwritten signature drawn on a touch sensitive surface. The signature acquisition application sends the resulting electronic signature to the desktop computer, for example via an electronic signature server. The user is then able to apply the electronic signature to the document as desired.

Abstract: An electronic signature comprises an authenticated audio and/or visual recording of a spoken assent that conforms to a pre-established phrase. Alternatively, an electronic signature comprises an authenticated visual recording of a series of physical gestures that conforms to a pre-established sequence. Rules are established with respect to how the assent is to be recorded and authenticated. These rules, as well as the document itself, are provided to a document recipient. If the document recipient assents to the document, an audio and/or visual recording of the assent is generated. Location information that defines or approximates the geographical location where the document recipient recorded the assent is also optionally recorded as well. Once recorded, the assent can be authenticated using any of a variety of suitable authentication processes. An authenticated assent can be considered a legally binding electronic signature that forms a part of, or is otherwise associated with, the document.

Abstract: An electronic signature comprises an authenticated audio and/or visual recording of a spoken assent that conforms to a pre-established phrase. Alternatively, an electronic signature comprises an authenticated visual recording of a series of physical gestures that conforms to a pre-established sequence. Rules are established with respect to how the assent is to be recorded and authenticated. These rules, as well as the document itself, are provided to a document recipient. If the document recipient assents to the document, an audio and/or visual recording of the assent is generated. Location information that defines or approximates the geographical location where the document recipient recorded the assent is also optionally recorded as well. Once recorded, the assent can be authenticated using any of a variety of suitable authentication processes. An authenticated assent can be considered a legally binding electronic signature that forms a part of, or is otherwise associated with, the document.

Abstract: Many computer applications involve event driven programming. Unfortunately, it may be burdensome on application developers to develop event handlers in unmanaged code for all relevant events within their computer application. For example, when using COM objects in connection with event handling, the burden of lifetime management may be placed on the application developer. Accordingly, one or more systems and/or techniques for event handling in unmanaged code are disclosed herein. A delegate comprising a first interface and a second interface is provided. The delegate may receive event data from a software platform connected to the first interface and may notify a function of a process connected to the second interface. The delegate self destructs when both the computing platform and the process have released their connections to the respective interfaces, thus mitigating manual coding of lifetime management functionality within the process.

Abstract: Various embodiments provide techniques and processes for defining elements of a user interface (UI) using a tree of objects created based on a markup language. In some embodiments, a client application provides markup that defines one or more aspects of a UI to an application programming interface (API). The API parses the markup to determine a namespace and one or more UI elements defined by the namespace. Instances of the UI elements are created, and properties of the UI elements are set on the instances. A user interface may then be displayed that includes the instances of the UI elements.

Abstract: Various embodiments provide techniques and processes for defining elements of a user interface (UI) using a tree of objects created based on a markup language. In some embodiments, a client application provides markup that defines one or more aspects of a UI to an application programming interface (API). The API parses the markup to determine a namespace and one or more UI elements defined by the namespace. Instances of the UI elements are created, and properties of the UI elements are set on the instances. A user interface may then be displayed that includes the instances of the UI elements.

Abstract: Many computer applications involve event driven programming. Unfortunately, it may be burdensome on application developers to develop event handlers in unmanaged code for all relevant events within their computer application. For example, when using COM objects in connection with event handling, the burden of lifetime management may be placed on the application developer. Accordingly, one or more systems and/or techniques for event handling in unmanaged code are disclosed herein. A delegate comprising a first interface and a second interface is provided. The delegate may receive event data from a software platform connected to the first interface and may notify a function of a process connected to the second interface. The delegate self destructs when both the computing platform and the process have released their connections to the respective interfaces, thus mitigating manual coding of lifetime management functionality within the process.

Abstract: Various embodiments provide techniques and processes for defining elements of a user interface (UI) using a tree of objects created based on a markup language. In some embodiments, a client application provides markup that defines one or more aspects of a UI to an application programming interface (API). The API parses the markup to determine a namespace and one or more UI elements defined by the namespace. Instances of the UI elements are created, and properties of the UI elements are set on the instances. A user interface may then be displayed that includes the instances of the UI elements.