search results

(...) abases have been transferred to the StandAlone installation. Additionally, during the change, you can refactor the implemented applications by facilitating the configuration or completing the process documentation .   4. Preparing new servers for WEBCON BPS StandAlone migration (inplace migration is not recommended) This will eliminate e.g. a risk of error caused by uninstalling SharePoint. & (...)

(...) , POST, PUT, PATCH or DELETE). In this case, we use the GET method. In the “Custom headers” tab, you can add additional header parameters according to the requirements included in the documentation of the selected API (in this case – host and API key). In the “Filter mode” tab, you have two options – Using BPS and Using Web Service. Filtering on the BPS side will cau (...)

(...) e AD, Google – BPS Auth Preparation As an example, a configuration with Azure AD authentication was presented. The configuration for other providers is available in the official project documentation  https://oauth2-proxy.github.io/oauth2-proxy/docs/configuration/oauth_provider.   nnsm installation nssm is used as a tool for installation nginx and oauth2-proxy as a Windows (...)

(...) nment. WEBCON BPS refers to loadbalancer which is responsible for directing traffic to individual Solr nodes.   It is important to properly set up ZooKeeper Ensemble according to the Solr documentation -> Ensemble configuration Solr is configured to pass the appropriate connection values to ZooKeeper -> Using the -z Parameter with bin/solr After starting Solr, change the security settin (...)

(...) a button in the form bar. This button can be used to launch a specific WEBCON BPS workflow, which can be a sub workflow of the current Workflow. It can also link to other relevant information, e.g., documentation for the process or guidelines that should be taken into consideration before submitting the form. Workflow automation becomes easy when you use it. The button can be available on all steps of the (...)

(...) veral options in the form field configuration: Description – a description that will appear in the tooltip for a user. It should be short, understandable, and contain useful tips. documentation – a detailed description of individual form fields operation. This description will be transferred to the documentation that can be later generated from Designer Studio.      (...)

(...) ch engine not to include special characters used between quotation marks and treat them as values to search for. Complete list of the operators supported by the engine is located in SOLR technical documentation : https://lucene.apache.org/solr/guide/7_5/the-standard-query-parser.html   Search mechanics in WEBCON BPS 2019 WEBCON BPS system operation characteristics causes search results to (...)

(...) } } }   Realm configuration and application registration in Keycloak Server Log in to the Keycloak administration console, create a new realm and user based on the product documentation -> https://www.keycloak.org/docs/latest/getting_started/index.html#creating-a-realm-and-a-user. Next, register the application client. Go to the Clients tab -> Create, and in the “Clie (...)

(...) It can be used to assign a task or in an action that grants privileges.  Fig.9 Configuring roles when they are represented by their corresponding business rules   The rule documentation should accurately describe its role so that you can tell what the rule does without checking its configuration. Thanks to this, it will be enough to display the list of rules and their description to (...)

(...) BPS e.g. item list name from which the described item list columns come from 4.    ObjName – system object name (e.g. ApplicationName, AppStartName, DocTypeDescription, WorkFlowdocumentation Description).  5.    Value – the element name determined by a user 6.    Order – the order of the widgets located on the dashboard 7.   &nbs (...)

(...) Applies to version: 2025 R1 and above; authors: Pawe Fijał, Krystyna Gawryał   Related documentation A detailed description of the functionalities mentioned herein and their configuration can be found in the following sections of the WEBCON BPS Help: Authentication providers | WEBCON BPS   Introduction WEBCON BPS allows for selecting an Authentication provider and (...)

(...) cess. After receiving the first HTTP request, the portal process will be restarted. The recommended parameter setting for production environments is 0 (no process termination when idle). Microsoft documentation   Recycling   Application pool setting. By default, recycling is set as a fixed interval of 1740 minutes. Such setting  triggers  a periodic Recycle of the pool appl (...)

(...) ems will be employed to each system? Which form values should be transferred to external systems? Does the Customer have its interface prepared? Is the Customer able to deliver data transfer documentation ? Are integrations with other systems planned? Study cycle requirements The Integrator takes part in analytical integration talks. The Customer/Integrator verifies the data structure (...)

(...) is possible, but you need to disable the TSQL_SCALAR_UDF_INLINING (Scalar UDF Inlining) option. This option is enabled by default when changing the compatibility level to SQL Server 2019 Microsoft documentation The impact of the TSQL_SCALAR_UDF_INLINING parameter on the operation of WEBCON BPS Scalar functions defined in WEBCON BPS mostly perform conversion or formatting operations on single values. T (...)

(...) essing queries to act differently. This may lead to performance changes (both positive and negative), as well as changing how certain parts of WEBCON BPS work.   In the Compatibility Level documentation , Microsoft suggests that databases of existing applications should use the Compatibility Level for which they were designed and optimized, even if that level is lower than that of the installed SQL s (...)

(...) set up as a choice field returning the following data (IDs of respective options are important here):   Figure 3. Choice field configuration     The Autenti REST API documentation states that once a  GUID is returned by the system, the document was uploaded properly into the company’s internal database. Therefore, the user is blocked from progressing forward until a (...)

(...) send it further, for example, to the financial department, to place an order for the requested equipment.   Summary The WEBCON BPS Word Modern add-in supports the process of generating documentation in an enterprise, so that it is no longer necessary to manually complete and duplicate standard documents. The use of ready-made templates automates the process, and the other features offered by the (...)

(...) Applies to version: 2022 R1 and above; author: Łukasz Maciaszkiewicz Introduction Efficient documentation management is key to the proper functioning of a company. In addition to their proper registration in the system, the incoming documents must be quickly accessible in their original, hardcopy version. To streamline their flow and storage WEBCON BPS offers printout a barcode label functionality all (...)

(...) es they make will be visible to others in real time.   The present article describes this new feature on the example of a process in which an advertising agency employee prepared marketing documentation requested by a client (a Word document called "Product series advertisement" and an Excel document called "Promotional campaign slogans"). The author would like to share the prepa (...)

(...) Applies to version: 2025 R1 and above, author: Krystyna Gawryał   Related documentation A detailed description of the functionalities mentioned herein and their configuration can be found in the following sections of the WEBCON BPS Help: History | WEBCON BPS Form fields | WEBCON BPS   Introduction Instance history is an area where the user can check what actions were (...)