
Currently docuflow has an endpoint to create a request to sign documents and send them to multiple users to sign the file. 

Note: If the document assigning sign request is in a specific folder under root. Specify the root folder id in box Configuration.

Sign Documents

type

Value should always be set to "box" to let docuflow know which configured content system to search.

selectedCMS

Json Array of strings (each index being a seperate line). 

Or can take a single string value "singleLineExample"

body

Number of days from today the sign request is valid for. Example: 5


dueDate

Array of strings of recipients of the task (email id)

*User may require permissions to file before being able to be assigned a sign request.

recipients

If true, signed document and signing log is stored in the same location as source file (destination id auto filledis generated by middleware).

If false, Signed Document and signing log is stored in the destination location.


enableSameDestination

location where the signed document and signing log is stored (Only when enableSameDestination is false)


destinationId

taskType

Use case scenario: Store signed document and signing log where orginal document is.

When the enableSameDestination is set to true the signed document and signing log will be stored in the same location as source file (i.e; the parent folder of id)


Number of days from today the sign request is valid for.


Use case scenario: Multiple Sign Recipients.

The request can be sent to multiple signers. If one signer declines the request the whole request will be cancelled.


Tasks

Sign (available version > 6.6.5)

docuflow BAPI Web Services

docuflow Guides

Welcome

What's New

docuflow for Box

docuflow for Microsoft

Untitled

docuflow for FileNet

Repository Specific Guides

Purpose of Guide

Customer Resources Required

Configuration Overview

Viewing and Attachment List Options

DocManager

Custom API Usage

Choice Lists

Workflow Connect

AuditLink

DocMigrator

Accounts Payable

Publisher

System Messages

Utilities: CMS Load (Beta)

Utilities: Link Maintenance

Utilities: Metadata Push (MDPro)

Utilities: Cleaning Gateway Errors

Utilities: Archiving Gateway Data

Utilities: Attachment List Dashboard

Working with the API Gateway and SCRUD Test Harness

Solution Guide

Class/Method Plug-In’s

docuflow BADI’s

SCRUD API’s

Ping and Load API's

docuflow SCRUD Web Services

Useful / Common docuflow Methods

Overall CMS API Notes

SAP Code Vulnerability Analyzer (CVA)

log4j Update

Developers Guide

Release Schedule

Source Code Review

Vulnerability Assessment

Security Testing

Managing Security Issues

VersaFile Release Management

Middleware

Change Log

Agnostic Guides