search results

(...) it can be tested, and therefore there's lest to document. Depending on the setup you may have the same processes in multiple databases but these have different configuration. Business entities, connection s, global costants etc.. We have a version history for the import in the system and not somewhere else, so we know who did it when with which configuration file.  We can keep track of al (...)

(...) ve; author: Łukasz Chechelski   Introduction The OAuth2 authentication standard is becoming increasingly popular, as it enables integration between different systems. In many cases, the connection takes place in the API → Application model, which makes authentication much easier. In this case, a predefined set of data is used – Client ID, Client Secret, and our subsequent actions ar (...)

(...) is collected in the Application Insights app, specifically in the Log Analytics workspace. To utilize this data in Microsoft Sentinel, it is necessary to configure both the OpenTelemetry tool and the connection between the Microsoft Sentinel service and the aforementioned workspace.   Configuration in the Azure platform It is a good idea to start the configuration in the Azure platform b (...)

(...) y default, this is the account on which the Workflow Service runs). The latter will be important for privileges, both to the network share and to the databases (if integrated login is used in the SQL connection parameters). The PowerShell action can only be executed in the context of a workflow instance, so it is not possible to add such an action in cyclical automation. This simplifies configuration bec (...)

(...) In the Portal address configuration, also change the Portal URL if it changes along with the machine name.   4. (Optional) Generate certificates for the new service if the Portal-Service connection is implemented using the TCP protocol This can be done in setup.exe → System management tools → Portal-Service connection configuration. If the connection is implemented using the HTT (...)

(...) ication on the BPS side. While on the Portal page, go to the Administration tab available by clicking on the user's avatar. After navigating to the Integrations tab, create a new application. The connection will be made in the context of the application. Note that the login of the created application must be in the form of a BPS ID.   Fig. 7. API application data   After savi (...)

(...) ation saved by developers, such as application status data, action results, errors, or warnings. The data stored here can help diagnose problems with the application's presentation layer and some connection -related errors. The Edge, Chrome, and Opera browsers are based on the same engine – Chromium – so their development tools (devTools) are very similar. Therefore, downloading logs from (...)

(...) ta sources, or SDK plugins. In this case, an appropriate message is displayed and the configuration of the exported automation must be modified. If the automation definition contains references to connection s, 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 (...)

(...) } public string ProductCode { get; set; } public int Quantity { get; set; } } }   In this example the application works in a very simple way: First, a secure connection to WEBCON BPS is established using the OAuth2 mechanism. Here we use an HTTP client that retrieves an access token and then sets it in the headers of subsequent requests. In the code above, your-c (...)

(...) ield will remain empty. This situation indicates a problem on the integration side and prevents the signing process from proceeding properly. The integration setup begins with configuring the REST connection to the Autenti REST API, enabling documents to be sent in PDF format.   Fig. 5. API connection configuration   You need to create a new REST Web Service connection and set t (...)

(...) lso have a 100-second timeout. An exception is the request sent to Microsoft Graph to obtain an authentication token, which has a timeout of 120 seconds. This request is sent before establishing a connection —for example, at the beginning of user synchronization with Entra ID.   Automations The configuration of an automation includes a parameter called Execution time limit, which is ac (...)

(...) 't forget to allow in the local firewall incoming request to the TCP port (default port is 5000) from your WEBCON server(s) as source. Otherwise WEBCON will never get a successfull connection to PSU. This article describes all steps to create a small running demo that gets two summands and returns their sum with basic validation, error/exception handling and a running sceleton for new (...)

(...) er a new address. Therefore, if this address is used in process configuration (e.g., in business rules, forms, or Hyperlink action/form field), it must be overwritten.   10. Updating MSSQL connection s and database names in configuration Recreating and renaming source databases in the new SQL Server instance (see points 5 and 7) affect any dedicated MSSQL connection s (MSSQL Database | WEBCON BP (...)

(...) . This article describes how to integrate a MS Fabric lakehouse via its SQL analysis endpoint. First you have to set up once the necessary Entra application registration and the WEBCON MSSQL database connection to the lakehouse SQL analysis endpoint. Then you can create as many data sources in WEBCON Designer Studio as you wish to query your tables in the lakehouse. Microsoft Entra App As you need (...)

(...) ions (up to and including 2023), the EXE file was located in the same directory as Designer Studio (not in a subfolder).   Usage After launching the tool, it is necessary to establish a connection to the configuration database of the environment. To do this, you must select the authentication method, the name or address of the SQL Server, the name of the configuration database, and the credent (...)

(...) ully configurable. It is possible (and recommended for larger systems) to store logs in a separate dedicated MSSQL database. "MSSqlServerSink": {   "Name": "MSSqlServer",   "Args": {     "connection String": "LogsDb",     "tableName": "Logs",     "schemaName": "infrastructure",     "autoCreateSqlTable": true,     "restrictedToMinimumLevel": "Warning"   } }   File A file create (...)

(...) ion form field – application examples on the WEBCON technical blog. After adding the OAuth2 Authentication field to the form, the next step is its configuration. To do this, go to the OAuth2 connection s configuration in WEBCON Designer Studio. Under Data sources → Authentications → OAuth2 User -> API, create a new authentication that will be used to confirm the user’s identity (...)

(...) zure Monitor / Application Insights is supported, but it is configured in a separate section in appsettings.json (outside the OpenTelemetry section): "ApplicationInsights": { "connection String": "<connection string z Application Insights>" } Setting only ApplicationInsights:connection String causes telemetry (traces, metrics, and logs) to be sent to Applic (...)

(...) Archive folder – for archiving processed messages, Error folder – for handling erroneous messages. On the General tab, you must also configure the inbox and outbox parameters, the connection to the Exchange server (server type and address), and provide the parameters of the user in whose context the mailbox handling MailApproval operates. Detailed information on how to complete the fi (...)

(...) erview of all workflows with such automations through all application groups, applications, processes and workflows. To get an overview one can create an MSSQL data query with the current database as connection and the following SQL query. It returns in the first column if the cycle is active or not. Then there are several columns containing GUID, ID and name of the associated application group, app (...)