search results

(...) docs/2024.1/api-registration-and-authentication#get-access-token in Postman to api/oauth2/token , example: { "grant_type": "client_credentials", "client_id": "XXX", "client_secret": "XXX", "scope ": "HighTrust.Elements.ReadWrite.XXX } I recived error: { "error": "invalid_request" }

(...) tName" - "guid":"...", "svalue": "115#ElementName", "value": [{"id": "115"}] - "guid":"...", "svalue": "115#ElementName", "value": [{"id": "115", "name": "ElementName"}] Can it be caused by "scope / permission" issues? I do not have any trouble GETting elements with given IDs in API: > Public API GET /api/data/v6.0/hightrust/db/1/elements/80 → 200 OK > Public API GET /api/data/v6.0/hightrust (...)

(...) Hi all! Is there an easy way to list all the privileges (and scope s) for applications, processes, associated form types, dasboards and reports? Maybe someone already wrote a query for that or can point us in the right direction? Thanks a lot in advance & best regards, Nik

(...) Hi all! I am trying out the new user defined API in 2025 R2. I have a client application with application context and added the scope App.UserDefAPI.ReadWrite.All (according to documentation this is necessary to get access to endpoint with automation). In addition the REST API client is application admin, can start new workflows and so on... What I am trying to do is a POST to an automation (...)

(...) Hi, it would be great if an option is added to exclude processes from the analytics overview. I tried to "remove" those by entering a date far in the future for this flag: Limit the scope of analytics data – parameter is used to limit the scope of processed data available in the Analytics reports. If this option is activated, all measures of analytical reports will not be calculated for workflow i (...)

(...) rights. Therefore, it would be highly beneficial to introduce an additional, intermediate layer of privileges. Perhaps the solution could be a privilege level equivalent to System Administrator scope d to a given database? This way, each business department would have its own dedicated database, and the central System Administrator would only oversee the overall database infrastructure.

(...) posed Solution: “Change Commit Dialog” Introduce a lightweight, optional dialog when saving changes, inspired by commit workflows in modern version control systems like GIT. Core elements: - scope Type (mandatory) Automatic assignment to the environment with different scope s of changelog details. Testers need more detailed information about changes from dev to test for quality management. Com (...)

(...) the token request) Example token request: POST /token Authorization: Basic base64(client_id) Content-Type: application/x-www-form-urlencoded grant_type=password&username=USER&password=PASS&scope =default Currently, WEBCON BPS does not support this OAuth flow in its REST authentication configuration. Problem: Because of this limitation, we are forced to implement an additional proxy / (...)

(...) 7 Email: office@webcon.com Tel.: +48 12 443 13 90 (“Personal data controller” or “Data controller” or “WEBCON”) For matters related to the scope of personal data processing, the user may contact the Controller by: sending a request/ demand via e-mail to the following address: office@webcon.com sending a request/ demand by traditi (...)

Up to date as of June 17, 2026 The security of our platform is of utmost importance. We monitor the net for news on emerging vulnerabilities, run security audits, and react to issues raised by our clients. We constantly update WEBCON BPS to remove any known security vulnerabilities. On this page, we will compile information regarding security vulnerabilities detected in the system.