search results

(...) 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 (...)

(...) 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 (...)

(...) lies to version: 2022.1.x and above, author: Krystyna Gawryał   Introduction Users who participate in a business process take on specific roles: there are those responsible for creating documentation , registrants, acceptants, and employees who carry out tasks assigned to them or who are otherwise affected by the process. In WEBCON BPS, the form fields that store information about a person are: (...)

(...) ntroduction The overarching idea of workflow in WEBCON BPS is to exchange written information between system users and perform related tasks, such as reading, updating or modifying data on a form. documentation in the workflow consists not only of workflow instances and filled out forms, but also files with various extensions (e.g. .docx, .txt, .xls, .pptx, .pdf, .png.) added to the instance as attachments. (...)

(...) prise prepared the application prototype "Execution of Investment Projects" in WEBCON BPS Designer Desk. According to the design, this application is to be used by the Principal to complete documentation regarding various stages of investment, and to make adequate settlements.   Fig. 1a. Main panel of the application prototype in WEBCON BPS Designer Desk     Fig (...)

(...) gner Desk tool. The projects were evaluated by the representatives of the University and WEBCON workers. Our implementation specialists gave priority to projects with complete and understandable documentation that could serve as a basis for process implementation. The prizes consisted of small gifts, and each awardee also had the opportunity to attend a job interview and potentially an internship at (...)

(...) asis of which processes will be designed, create prototypes of document workflows (using "drag and drop") test and modify prototypes, design analyses and reports, generate prototype documentation , publish the prototype in WEBCON BPS Designer Studio, communicate easily with implementation and IT departments.   From November 2023, our offer will include the training: &ldquo (...)