Push Status Nodes

This section describes the critical status nodes, labeled for single or multiple signature workflows as applicable.

<PackageDetail>

This node contains information about the package, including metadata if configured.

<Status>

The current status of the package.

<Initiator>

Displays the username of the initiator for multi-signature workflow packages. The initiator may not always be the account used to submit the package. The initiator receives the completed workflow package after all signings are complete or a rejection by one of the signers.

<Signers>

Displays for multi-signer workflow only. All <Signers> and their corresponding information display under this node.

<Signer>

Displays the following elements for each signer:

• <Order> This is the order value for the signer: 1 means the first signer, 2 means the second and so on.
• <Name> The name of the signer (from the participant information in the multi-signature workflow package within SDX).
• <Email> The username of the participant (typically used as the username in SDX for the user).
  • Additional information exists for a signer after the signer has received the SDX package. The first signer always has additional information; the second signer has additional information after the first signer signs, and so on.
  • If a signer rejects a SDX package, the transaction stops and later signers do not receive the package. Additional information is detailed in this node, but keep in mind that not all fields exist for every package. The best practices for XML parsing should be followed.
• <Id> The ID of the sub-package that was sent to the signer as part of the multi-signature workflow in SDX.
• <Status> The current status of the recipient or the signer. If the signer is the currently active signer, this status also displays in the <PackageDetail> element. See Push Status Triggers, earlier in this guide, for more information.
• <Expired> The time the package expires (in Eastern U.S time). If a package has expired, this time will be in the past.
• <Recipient> The recipient account for the signer (may match the <email> account, but may not if the account has aliases attached to it [advanced users only]).
• <Received>>The time that the recipient account received this package (in Eastern U.S time).
• <Viewed> The time that the recipient last viewed the package. This node is blank if the package has not been viewed.
• <Purged> The time that the package content was purged from the vault. This node is blank if the package content has not been purged.
• <Recalled> The time that the package was recalled. This node is blank if the package has not been recalled (advanced users only).
• <Signed> The time that the recipient signed the package. This node is blank if the package has not been signed.
• <Rejected >The time that the recipient rejected the package. This node blank if the package has not been rejected.
• <PaperRequested>The time that the package was sent to paperout account for printing. If the skin is configured to support this, then paperout for the multi-signature workflow package occurs when the user does not consent to e-Sign. Rejecting a package does not cause a paperout.
• <DirectToPaper> The time that the package was sent directly to the paperout account. This node is blank if the package was not originally sent straight to the paperout account (advanced users only).
• <PaperCompleted> The time that a package sent to the paperout account was printed.
• <PaperNote> A free-text note added by the printing process.
• <Consented>The time that the recipient consented to process the package electronically. This node is blank if the recipient has not been consented to the package.

<PackageStatus>

This node contains the package status value for the current recipient. For a multi-signature workflow package, this is the active signer.

<Signer>

• Repeats the <Signer> information (described on the previous pages).
• In addition, the following workflow-specific elements display:
  • PushedToVault:The time the PushedToVault call was made via SDX Webservices. This value has no bearing on SDX processing and is for third-party informational purposes only.
  • PushedToVaultNote: A free-text note added by calling the appropriate call in SDX Webservices. This value has no bearing on SDX processing and is for third-party informational purposes only.
  • Expired: The time that the workflow package expired. If this node is blank, the package has not expired.