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

Sign Documents

type

Value should always be set to "box" to let Link Enterprise 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.


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

Parameter name

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)


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)

Upload

Search

Create

Read

Delete

Update

FileNet Endpoints

Link Enterprise

Welcome

Technical Overview

Installation and Base Configuration Guide

SharePoint Implementation Guide

Link Enterprise for M365

Link Enterprise for S3

Repository Specific Guides

Purpose of Guide

Customer Resources Required

Configuration Overview

Viewing and Attachment List Options

DocManager

Custom API Usage

Workflow Connect

AuditLink

DocMigrator

Accounts Payable

Publisher

System Messages

Utilities: CMS Load (Unsupported S3)

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

Link Enterprise BADI’s

SCRUD API’s

Ping and Load API's

Link Enterprise SCRUD Web Services

Box Endpoints

S3 Endpoints

SharePoint Endpoints

Link Enterprise BAPI Web Services

Useful / Common Link Enterprise Methods

Overall CMS API Notes

SAP Code Vulnerability Analyzer (CVA)

log4j Update

Developers Guide

Agnostic Guides

Hardware Requirements

Unpacking ZIP Package

Initial Configuration

Start & Stop Order

Setting up Firefox Certificate

Connecting to L4i Configuration

Installation Guide

Transformations

Transformation Engine

Connectors

Connections

SSL Certificates

Configuration

Untitled

Introduction

Architecture Overview

Minimum Requirements

SuccessFactors Technical Overview

Linking SF to BTP Landscape

HTML5 Application Registrations

Extension Admin Permissions

SuccessFactors App Setup

BTP Configuration

API User

Create Pick List

Create Approval Workflow

SuccessFactors Objects

Permission Provisioning

Export Category and Document Type

Import Category and Document Types

UI Configuration

SuccessFactors Configuration

SuccessFactors