For SAP Cloud ALM teams

Cloud ALM documents, stored in your SharePoint.

DocSync connects SAP Cloud ALM to a SharePoint library you already own. No SAP BTP document service, no second copy of your files, no new place for your team to work.

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
The problem

Cloud ALM has no file store of its own

To attach a file to a requirement, a task or a test case, Cloud ALM needs a document repository behind it. The usual answer is a separate SAP BTP service, and that comes at a cost.

Another subscription

A paid document service on SAP BTP, on top of the Microsoft 365 licences you already have.

A second copy

Project documents live outside SharePoint, with their own lifecycle and their own permissions.

Outside your governance

Retention, sensitivity labels and sharing policies stop applying once the file leaves Microsoft 365.

How it works

Connect once, then keep working as usual

DocSync speaks CMIS, the interface Cloud ALM uses for external repositories, and stores everything through Microsoft Graph. Cloud ALM does not know the difference.

  1. Connect

    An Entra ID app with access to one site only (Sites.Selected), and a destination in your Cloud ALM subaccount.

  2. Work in Cloud ALM

    Upload, replace and delete files as you do today. Each file lands in SharePoint, in its project and object folder.

  3. Stay in step

    Titles, status, owners, assignments and deletions are brought in line every 5 minutes. Files added by hand in SharePoint become Cloud ALM documents within minutes.

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

Your team can keep working in SharePoint. DocSync turns their files into Cloud ALM documents and respects what they do with them there.

Upload in SharePoint

Drop a file into a project folder and it becomes a Cloud ALM document, with the file attached. In Cloud ALM you assign it to a process, requirement, task, test case or library, and the file moves to that folder.

Check out to lock it

While a file is checked out in SharePoint, for a review or a signature, Cloud ALM cannot replace, rename, move or delete it. The document is tagged BLOQUEADO SHAREPOINT until the file is checked in.

Sign where the file lives

The files stay in SharePoint, so they can go through the electronic signature and approval tools your organisation already uses there, with SharePoint's version history and audit trail. Useful where documents must be signed, as in healthcare and other regulated work. DocSync does not sign documents itself.

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.
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.
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

Professional

€990 /month

Several projects in parallel.

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

Enterprise

€1,890 /month

Groups and regulated environments.

  • Unlimited projects
  • 24×7 support option
  • Test environment
  • Annual security review

Indicative prices, excluding VAT. Annual billing includes two months free. Migration is quoted per project.

See it with your own tenant

Thirty minutes: upload a file in Cloud ALM, watch it land in SharePoint, ask anything.

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