latest posts

Hi all,
I’m running into a strange issue with SharePoint integration in WEBCON and wanted to check if anyone else has seen something similar.
I’m using Azure App with certificate-based (app-only) authentication (SharePoint API, Application permission: Sites.ReadWrite.All with Admin Consent, not delegated).

✅ What works

Connection to SharePoint works
General communication works
Folder creation in document library works


❌ What doesn’t
When using “Add an attachment to a list”, the file upload fails with:
401 Unauthorized


🔍 Logs / details
From WEBCON:
Execute WCFCsomService .../AddAttachmentToSPList
Error in On path action Add attachments to Extranet (Step: Signing → Prepare for mailing)
The remote server returned an error: (401) Unauthorized.

Stack trace:
System.Net.WebException: (401) Unauthorized
at Microsoft.SharePoint.Client.SPWebRequestExecutor.Execute()
at Microsoft.SharePoint.Client.File.SaveBinary(...)
at WebCon.WorkFlow.CSOM.Sharepoint.AddAttachmentToSPListCsomProxy.AddToDocumentLibrary(...)


🧠 Observations

Authentication clearly works (since folder creation succeeds)
The error happens specifically at:
File.SaveBinary()


So it looks like the issue is tied specifically to the file upload step


⚠️ Important detail
If I switch to a service account (username/password), the exact same action works perfectly and uploads files without any problems.
However, due to upcoming Microsoft authentication policy changes, we must use certificate-based auth only (introduced in newer WEBCON versions like BPS 2026).

❓ Questions

Has anyone successfully used “Add attachment to list” with certificate (app-only) auth?
Any recommended workaround (without switching auth type)?


Any insights or confirmations would be really appreciated 👍

Did you find a way around it ?

Hello Patryk,
Error could be related with Your access token. Did You try to create a new one?

Best regards,
Paweł

Hello,
Problem could be related with proxy settings, user authentication, and antivirus settings themselves. Analyzing this isn't easy.
First, please try clear the browser cache. Use different browser, such as Edge, without any add-ons. If there's an antivirus installed, remove it for testing. Further analysis should involve network administrators.

Best regards,
Paweł

Thats what I've tried. Action Change field value [System] comment. But this does not work.
Although the timer is configured with "Path transition after action call", it seems that the action is executed AFTER the path transition...

Will take a look into your post about getting the current comment.

Thanks!
Ernst

Hi Ernst,

while I haven't tried it you could add an action to the timer which set's the comment.

Otherwise you could use this approach to check in a validate action if the user added a new comment:
Get current comment
https://daniels-notes.de/posts/2024/current-comment
I'm not sure, whether this still works in the latest version.

I don't see any other option beside the already mentioned option to create new paths. Would still be better then adding a flow control, which handles the "is system user" and executes a path with/without comment required. :)

Best regards,
Daniel

I have a Step with a "cancel" path. On this path I have enabled "comment required" => User always should enter a comment if he is cancelling the workflows.

Now I have a "housekeeping" timer in that step.
The timer exections an action (Change field value => [System]Comment) and has path transistion after action execution "cancel"

=> Timer throws an error: field validation "Comment" on path "cancel".

1. idea:
I make a special cancel-path for the timer => problems:
* I have more such steps => would result in many workaround paths
* Some cancel path do have flow-control behind, to determine the correct final step

2. Idea:
I disable "comment required" in that path and create a form-rule which checks if the user is a real user or the system-user. Then checking the comment => found no way (via form-rule) to check if the user has entered a comment or not. Could be doable via JS I guess, but want to avoid that.

Any solutions, ideas?

Thanks Ernst

Hi everyone,
It seems like this icon is only on the versions preceding the workflow GUI rehaul, we couldn't get it to display in 2025.2.1.*
In the old workflow designer paths which were 'hidden', were not showing up in the designer studio diagram view, you had to look for them in step configurations (this would explain Filips findings)

Hi Filip,
I'm not 100% sure but that's what it looked like in my tests ;)

Hi. Are you sure? https://kb.webcon.pl/kroki-systemowe-jak-dzialaja/
There we've got one path from the start step.