search results

Applies to version: 2026 R2 and above; author: Łukasz Maciaszkiewicz   Related documentation A detailed description of the functionalities mentioned in this article, along with their configuration, can be found in the following articles:   https://community.webcon.com/posts/post/opentelemetry-in-webcon-bps/403/3 https://community.webcon.com/posts/post/opentelemetry-

(...) ist of data necessary for BPS to identify the user. “Profiles” and “email” are already added by default. For other OpenID server implementations, you may need to add different Scopes . After completing the configuration, save the settings and restart the portal application pool. It is also necessary to grant permissions for the Google account. To do this, go to the list of B (...)

(...) cation will obtain data (we will assign privileges later). Client ID: Keep this! You will need it later. Client Secret: Generate and keep this! You will need it later. Application permissions (Scopes ): App.Odata.Read.All     To finish setting up the API Application, place the Login from its configuration into the privilege settings of every application and process you wis (...)

(...) . With this feature, the system will immediately load the necessary configuration. It remains to fill in the Client ID and Client Secret of the Azure application. Authentication takes place within Scopes , in accordance with the OAuth2 standard. The list should include: openid email profiles Fig. 5. Authentication configuration in Designer Studio   Based on the authentica (...)

(...) will generate a Client ID and allow you to generate a Client Secret, which should be kept safe as it will not be possible to view it again.   Configuration of application permissions (Scopes ) In order for the application to execute automations, such as creating new workflow instances, it is necessary to assign appropriate permission Scopes . For operations related to creating and modif (...)

(...) Auth2: register an API Application in the Administration Panel, set the type to Authorization Code, and add the MCP client redirect URI (e.g., Claude redirect URI). It is important to configure the 6 Scopes shown below. Start the MCP server in the application settings. Enable separately: General MCP Server (optional), and Application-specific MCP Server. Verify available tools by (...)

(...) Hi all! Is there an easy way to list all the privileges (and Scopes ) 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

(...) m trying to do is a POST to an automation endpoint, which starts another workflow in its automation (very simple). But all I am getting is, regardless of what I do: { "description": "Invalid Scopes ", "guid": "48078ebb-424f-4a0f-9a27-7e67e408e148" } The guid cannot be found in designer studio, there is also no automation log. Remark: The endpoint with a datasource works fine. Did I (...)

(...) log 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 Scopes of changelog details. Testers need more detailed information about changes from dev to test for quality management. Common users need details about new features, changes and bugfixes for daily usage. (...)