This section describes the typical configuration required to integrate the three HTML5 applications into SuccessFactors.

Minimum Requirements

BTP Configuration

BTP Sub Account Creation

Linking SF to BTP Landscape

docuflow Guides

Welcome

What's New

docuflow for Box

docuflow for Microsoft

Untitled

docuflow for IBM

docuflow for FileNet

docuflow for S3

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

Step by Step Deployment OCP

📘Container Deployment Guide

Class/Method Plug-In’s

docuflow BADI’s

SCRUD API’s

Ping and Load API's

docuflow SCRUD Web Services

docuflow BAPI 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

SuccessFactors Technical Overview

SuccessFactors Configuration

docuflow for Integrations (d4i) Middleware Configuration

Agnostic Guide

for SuccessFactors

SuccessFactors for FileNet

SuccessFactors