Introduction and Overview
docuflow is an SAP certified suite of functionality that provides integration between SAP and content services repositories.
This integration includes document storage, linking, bi-directional metadata transfer, process and workflow automation, as well as ArchiveLink processing. Line of business solutions (such as Accounts Payable) and additional add-ons (such as SAP DMS integration and AuditLink bundle creation) can be leveraged in addition to the baseline functionality.
The docuflow offering consists of two separate integration options or approaches that can be used independently or in combination to provide the best value for your implementation:
1. docuflow ECM
Leveraging components both inside (SAP transport component) and outside the SAP boundary (middleware component), docuflow ECM provides the most powerful and flexible SAP to content services integration options. Enhanced user-based storage and linking, no-code bi-directional metadata transfer and workflow triggering, all supported by comprehensive SAP based administrator workbench monitoring, utilities, user delete link request management, Audit and Compliance bundle creation, and reporting functions are just some of the highlights.
In addition, docuflow provides a robust SAP based migration tool that handles migration of content from any ArchiveLink, File, or SAP database (both attachments and notes) source to Box.
docuflow ECM also provides a powerful Content API set of SAP BAPI’s to allow the customer perform full SCRUD (Search, Create, Read, Update, and Delete) functionality to fulfill any custom requirements within the SAP boundary.
2. docuflow Content Server
Based on the SAP ArchiveLink framework, the docuflow Content Server (middleware component only), provides SAP message output, document storage, print list support, data archiving, and other standard ArchiveLink functionality from SAP to your content services platform.
Which docuflow approach and tool is utilized depends on the integration pattern/add-on required:
*put your mouse over the below table to scroll left/right
| Box Tasks Integration | Box Sign Integration | Web Services Integration | Business Document Storage | Enhanced Business Document Storage | Enhanced SFO/GOS Attachment List | SAP Outbound Metadata Transfer | SAP Inbound Metadata Transfer | Migration Utilities | Federated Services | Administrator Workbench | Message Output Storage | Print List Storage | Data Archiving (ADK) | Enhanced Inbound Processing | Inbound SAP DMS Integration | Outbound SAP DMS Support | Bi-Directional Workflow Integration\Process | Dynamic Folder Creation | Delete Link Management | AuditLink | TrackLink Workflow | Accounts Payable | Box SAP Content API |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
docuflow ECM | x | x | x | x | x | x | x | x | x | x | x | x | | | x | x | x | x | x | x | x | x | x | x |
docuflow Content Server | | | | x | | x | x | | | | | x | x | x | | | x | | | | | | | |
Figure 1: Toolset vs. Integration Pattern
Reasons you may need to use content server:
- SAP message output without ECM plug in
- ADK data archiving
- Fiori apps using document service (ie: without SFO/GOS functionality)
- Outbound DMS
- Any other application or 3rd party that relies on ArchiveLink directly