For SAP Cloud ALM teams

Cloud ALM documents, stored in your SharePoint.

DocSync connects SAP Cloud ALM to a SharePoint library you already own. Keep the files, version history and everyday work in SharePoint, with the documents linked to Cloud ALM.

How it works

Start in either tool. Keep one file.

Upload to a project first. Associate the document with a requirement, process or other object afterwards.

Illustration · example dataProject → file → association
Green: original file in SharePointDashed blue: link in SAP Cloud ALM
SAP Cloud ALMS4 Rollout · project
Link to the file in SharePoint
Order to Cash design.docx
7-13Project document

First: a document in the project. Then: its association.

You associate it with↗ 3-118 · Credit check
SharePointYour library
Order to Cash design.docx

Create a document in your Cloud ALM project and upload its file.

Illustrative timing. Cloud ALM uploads are immediate. SharePoint imports and association updates run every 5 min by default.

See the real integration →
What needs to be connected?

An Entra ID app with access to the selected SharePoint site (Sites.Selected), a destination in your Cloud ALM subaccount and the required API permissions. DocSync connects the two through CMIS and Microsoft Graph.

Explore the full SharePoint library example

What your team sees in SharePointExample data

SharePointSearch this library
CALM Documentation
CloudALM›S4 Rollout›Procesos›14-2 - Order to Cash
Filled in by DocSync from Cloud ALM
NameModifiedModified ByDocumentIDTypeStatusOwnerCloud ALM link
docxOrder to Cash design.docx2 hours agoAna OrtegaOrder to Cash design7-13Functional SpecificationIn Reviewana@example.com
xlsxCredit limits mapping.xlsxYesterdayJun LeeCredit limits mapping7-21DefaultIn Progressjun@example.com
pdfOTC workshop sign-off.pdf3 days agoMarta SilvaOTC workshop sign-off7-30Project DocumentationReleasedmarta@example.com
Upload in Cloud ALM → stored in SharePoint in about 1 s Columns, folder and link filled seconds later Full version history kept in SharePoint

Your SharePoint library

One stored file

Your permissions and policies

What happens when

Every Cloud ALM action has a SharePoint answer

Tested against a live Cloud ALM tenant, one case at a time.

In Cloud ALM you…In SharePointWhen
Upload a file to a documentThe file is stored in <project>/<object> with its real name, columns and a link back to Cloud ALMat once
Replace the fileA new SharePoint version of the same file; the history stays completeat once
Assign it to a requirement, process or testThe file moves to that object's folderevery 5 min
See metadata, deletions and file locks
In Cloud ALM you…In SharePointWhen
Change title, status or ownerThe columns followevery 5 min
Delete itMoved to the project's Eliminados folder; restoring it moves it backevery 5 min
Delete it permanentlyThe file is removedat once
Discard a draft with a fileThe file is removed; nothing is left behindat once
Try to change a file someone checked out in SharePointRefused, and the document is tagged as locked until check-inat once
From SharePoint

Start in SharePoint, finish in Cloud ALM

Upload, edit or check out. Your team can keep working in SharePoint.

Upload in SharePoint

A file in a project folder becomes a Cloud ALM document. Assign it to an object in Cloud ALM and its folder follows.

Check out to lock it

Checking out a file blocks changes from Cloud ALM. Check it back in to allow changes again.

Sign where the file lives

Use your existing SharePoint signature and approval tools. DocSync does not sign documents.

See all actions from SharePoint
In SharePoint you…In Cloud ALMWhen
Upload a file into a project folderA new document (title = file name, source External) with the file as its attachment; no second copyevery 5 min
Upload it into an object folder, a requirement's for instanceThe same, and the document gets the assignment of the documents already in that folderevery 5 min
Edit the file and save itCloud ALM downloads the edited versionat once
Check the file outChanges from Cloud ALM are refused; the document is tagged as lockedat once
Check it in againThe tag is removed and Cloud ALM can change the file againevery 5 min
Admin console

Every file, its state, and what to do

One page for the people who run the integration: the state of every file, warnings that say how to fix them, the activity log and a one-click sync.

The console, with example dataExample data

Cloud ALM ↔ SharePointv0.7.1 · running since 16 Nov, 10:30
2 warnings Sync now Sign out
DocumentsWarnings 2ActivitySettings
Documentsread 16 Nov, 11:42Refresh
142 All136 Synced1 Not confirmed2 Locked1 Pending upload1 Rejected1 Deleted
FileStateCloud ALM documentCALM statusOwnerVersionModified
Order to Cash design.docx/S4 Rollout/Procesos/14-2 - Order to CashSynced7-13 · Order to Cash designFunctional SpecificationIn Reviewana@example.com4.0182 KB16 Nov, 09:10Ana Ortega
Credit limits mapping.xlsx/S4 Rollout/Requerimientos/3-118 - Credit checkLockedby Jun Lee7-21 · Credit limits mappingDefaultIn Progressjun@example.com2.064 KB16 Nov, 08:47Jun Lee
Cutover plan.docx/Not confirmednot confirmed by Cloud ALM yet (document still a draft?)—1.096 KB16 Nov, 11:20Marta Silva
server-cert.cer/S4 Rollout/BacklogRejectedno permitido en Cloud ALM: server-cert.cer—1.02 KB15 Nov, 17:05Jun Lee
warning
File type not accepted by Cloud ALM · Documents
/S4 Rollout/Backlog/server-cert.cer
What to do: Rename it to an accepted type (retried automatically) or move it out of the project folder.
Warnings say what to do Details per file: versions and history Sync one file, or release it from quarantine
What you get

Built for the people who run it

  • Your library, your rules. Files stay in your SharePoint, under your retention and permissions.
  • No duplicate. One file, one place; Cloud ALM reads it from SharePoint.
  • Folders that mirror Cloud ALM. By project, then process, requirement, task or test.
  • Columns people can filter. Document ID, title, type, status, owner and a link back.
  • Two-way. Drop a file into a project folder and it becomes a Cloud ALM document.
  • Nothing deleted by guesswork. A file Cloud ALM stops reporting goes to quarantine, never to the bin.
  • Admin console. Every file with its state, warnings with what to do, activity, one-click sync.
  • Least privilege. One SharePoint site, and only the Cloud ALM API scopes it needs.
Pricing

One price per tenant, no charge per user

Essential

€490 /month

One project team.

  • 1 Cloud ALM tenant
  • Up to 20 projects
  • Support 8×5, 2-day response
  • Updates and backups included
Discuss this plan →

Professional

€990 /month

Several projects in parallel.

  • Up to 100 projects
  • Support 8×5, 8-hour response
  • Onboarding session included
  • Updates and backups included
Discuss this plan →

Enterprise

€1,890 /month

Groups and regulated environments.

  • Unlimited projects
  • 24×7 support option
  • Test environment
  • Annual security review
Discuss this plan →

Indicative prices, excluding VAT. Annual billing includes two months free. Confirm tenant coverage, setup costs and backup scope in the proposal. Support times refer to the initial response, not resolution. Migration is quoted separately.

Questions

Before you connect

The essentials for your project and IT teams.

Where are the files stored?

In your SharePoint library. Cloud ALM reads the attachment through DocSync; it does not require a separate file copy in an SAP BTP document service.

What needs to be configured?

An Entra ID application with access to the selected SharePoint site, a destination in the Cloud ALM subaccount and the required Cloud ALM API permissions. We can review the setup in the demo.

Is every change immediate?

File uploads and replacements are handled at once. Metadata, associations and other background updates are reconciled every five minutes by default. The action tables above explain each case.

Does DocSync sign documents?

No. Files remain available to the signature and approval tools you use in SharePoint. Those tools and your configuration determine the signature process.

What will we cover in the demo?

An upload from Cloud ALM, the file and its columns in SharePoint, version history and the admin console. We will also review your prerequisites and deployment questions.

In design

Moving from Solution Manager?

DocSync Migration will rebuild your Solution Manager documentation in Cloud ALM, with the files in SharePoint. We are looking for pilot customers.

  1. Inventory. A report of what you have and what is worth moving.
  2. Structure. Projects and process hierarchy recreated node by node, original IDs kept as reference.
  3. Documents. Created in Cloud ALM with type and state, files placed in SharePoint.

See DocSync in action

Thirty minutes to see the upload, the SharePoint file and version history. Tell us about your project and we will arrange the demo.

Write to us hello@docsync.cloud
Open in mail app