search results

(...) on. In the Authentication section, enable support for ID tokens. After saving the configuration, the created application is ready for use. From the Overview tab, copy the Tenant ID and client ID values that are required to configure authentication on the WEBCON BPS side.   Registering the Microsoft Entra ID user list synchronization application The next step is to create a s (...)

(...) ment use every day the dedicated "Sales" application on the WEBCON BPS platform. This application allows them to register orders, oversee their execution, and manage relationships with both client s and suppliers. Since the department employees frequently use various reports in their daily tasks, it was decided to streamline their work by making all reports available in one place within the app (...)

(...) ON ATF_ATTID = ATT_ID              AND ATF_Version = ATT_FileVersion              AND ATT_IsDeleted = 0              AND ATT_WFDID = {WFD_ID}" try {     $connection = New-Object System.Data.Sqlclient .SqlConnection     $connection.ConnectionString = $connectionString     $connection.Open()     $command = $connection.CreateCommand()     $command.CommandText = $query     $reader = $command. (...)

(...) As the producer of WEBCON BPS, we strive to provide our client s and partners with the best possible software. With each release, the platform is developed according to the highest industry standards and subjected to rigorous testing procedures to ensure stability, reliability and security. Starting from the WEBCON BPS 2025 version, each major release of the platform (e.g., WEBCON BPS 2026 R (...)

(...) up an App registration to upload documents to SharePoint using REST actions in WEBCON.  Since WEBCON BPS 2025 does not support certificate authentication I had to persuade SharePoint to allow client id/secret authentication.  Maybe I did something wrong, but I also was not able to use the build in OAuth authentication option. Therefore, I added an example on how to get and use the access t (...)

(...) release added a new SDK type the “CustomRESTAuthentication”. This allows us to implement our own authentication options. I made use of this to add support for accessing SharePoint using client id/certificate instead of client secret. A few features I implemented: Providing custom body and headers Reusing the access token Reusing the proxy   You (...)

(...) cker container   This article focuses on the first option – direct installation in IIS. The described scenario assumes the preparation of an external site that will allow potential client s to request contact for more detailed information. The functionality prepared in this way will be able to be embedded into the site as an IFrame.   Fig. 1. Diagram showing the communi (...)

(...) of the exported automation must be modified. If the automation definition contains references to Connections, any sensitive data present in their configuration, such as user logins and passwords, client secrets, etc., will be removed during export.   Loading an automation definition from a file To import the "Automated company fleet management" automation into the TEST enviro (...)

(...) it available to a selected group of users (especially external users), who should only have access to the shared application without knowing it operates within the full WEBCON BPS portal. This allows client s or partners to access the functionality they need in a simple, clear manner without access to other areas of the platform. This solution is particularly useful when a brand or business department (...)

(...) tances, synchronize data in real time on a large scale, and respond to system events, then the functions of the public REST API will prove essential. Another scenario is the development of complex client applications or external portals that make extensive use of data from WEBCON BPS and require constant, direct communication with multiple objects and structures. In such cases, a public REST API offe (...)

(...) ollowing details, as shown in the screenshot: User – the email address associated with the Autenti account used for integration, Password – the password for the Autenti account, client ID – the value provided by Autenti for integration purposes, client Secret – the API secret key provided by Autenti, Authentication service URL – https://api.accept.autenti.net/ (...)

(...) PS Portal, the user's browser sends HTTP requests to the IIS server, which hosts the WEBCON BPS application. The server is responsible for processing these requests and returning responses to the client (the user’s browser). IIS has its own configurable timeout for handling individual requests, which is set to 120 seconds by default. If processing a request takes longer than this limit, the se (...)

(...) or application proxy. You can find a documentation for this from WEBCON here. The most relevant screenshots for the necessary data for the configuration of the WEBCON MSSQL connection are: client (application) ID Secret value MS Fabric Admin Center Go to the MS Fabric Admin Center and search for "Service principals can call Fabric public APIs" in the "Tenant se (...)

(...) . Meeting preparation – a workflow that supports users in planning and preparing for upcoming meetings. The goal of the overall process is to provide comprehensive support throughout the client meeting lifecycle — from capturing meeting outcomes, through drafting notes and communication, to planning subsequent interactions.   Workflow 1: Meeting notes The first workflow (...)

(...) pared to rigid text formulas. {   "Name": "WebCon.Workflow.Module.Identity.AccountController",   "MessageTemplate": "Incorrect password for user '{UserLogin}'.",   "UserLogin": "t.green",   "client IP": "192.168.1.0",   "CorrelationId": "a987763c-3e5c-42eb-bade-76a6e35cb3df" }   Examples of Popular Sinks Serilog allows logs to be sent to multiple destinations simultaneously using (...)

(...) AI Agent’s decision logic and processing context:  Fig.2. AI Processing Inspector    Technical architecture  The solution is implemented as a lightweight, client -side visualization layer that operates directly on top of WEBCON’s native platform infrastructure. It is not a built-in dashboard, but a configurable extension that requires explicit setup with (...)

(...)   Tracing Module’s name Remarks ASP .NET Core Instrumentation   Sqlclient For Portal and Service it is possible to view SQL queries. Httpclient   WCF client Integration with Service (...)

(...) n, and forwards requests to IIS and then to the .NET application, in this case WEBCON. In such a setup, it is essential not only to route traffic correctly, but also to preserve information about the client ’s original request. Microsoft explicitly states that applications running behind a proxy or load balancer must receive information about the original scheme, host, and client address. Otherwise (...)

(...) t Online connections, it is necessary to create an application in the Microsoft Entra ID environment in advance. This is because configuring OAuth 2.0 authentication requires providing the Tenant ID, client ID, and a certificate, all of which are available only within an application registered in Entra ID.   Microsoft Entra ID Environment Configuration Application registration A new app (...)

(...) WEBCON. Two connections must be created: connection with the PEM key – in this connection, enter the base URL of the service instance and provide the private key in .PEM format in the client Secret field. Fig. 6. Connection with the PEM key   second connection – in this connection, enter both URLs and complete the client ID and client Secret fields. (...)