search results

(...) author: Dawid Golonka   Introduction WEBCON BPS offers a variable returning information whether a form is opened in the mobile app. This information can be used within the created form rules to adapt its view to the mobile app specification. The variable’s name is “Is this a mobile device?” and it works only within the “WEBCON BPS” mobile app.   E (...)

(...) onfiguration where database name (except ID and acronym) appears, changing service configuration, changing portal configuration, changing queries in: data sources, actions, business rules (SQL COMMAND), in locations where it is not possible to choose the <current database> option or where the query contains direct reference to the database.   If the problem appli (...)

(...) Applies to version: 2022.1.1 and above; author: Krystyna Gawryał   Introduction Form rules , as the name suggests, are rules that define the behavior and appearance of form elements. The vast range of available options such as functions, operations, integrations, and operators allows a user to create more or less complex rules , depending on the user’s needs. When working with form (...)

(...) m the form. If you want the appearance of the form to be dynamic and responsive, i.e. to change depending on the entered value, path transition or page refresh, then it will be beneficial to use Form rules . If, on the other hand, you want the appearance of the workflow instance to remain unchanged regardless of the actions taken, i.e. to be static, then you should use the options offered by the Styl (...)

(...) users who are or were assigned tasks in the workflow.   Fig. 14a. Instance history visible to administrator   User who edits/edited the instance Unless appropriate rules have been defined for individual form fields to restrict their visibility on the form, a user with an assigned task as part of an instance in History will see exactly the same data as administrator, (...)

(...) ues in “Data table”, “Data row”, “Chart”, or “HTML” form fields. Additionally, archiving does not include custom controls, as well as form and business rules .     The visibility of an archived instance is another important matter. In such case all the fields visible just before the instance is moved from the content database will be vis (...)

(...) the behavior of the entire process in different places of the system, and their impact on the process is general and complex. Examples of such elements include data sources, global constants, global rules , and global fields.   Fig. 1. “VAT” global constant used in the cost invoice process     Exporting and importing changed global elements If the user i (...)

(...) . an order for a much higher amount than the previous ones, or holiday requests for a very long time. Running the AI analysis allows for creating automatically process description – a set of AI rules based on actual data entered by users. Associated modules: “AI”.   Workflow instance archiving There are two dedicated actions in WEBCON BPS that provide archiving f (...)

(...) he “Name” column and specify the form field containing the value in the “Source field” column. Configuration of the “Request body” tab   Business rules in JSON - grid Another change consists in adding the “Business rule” column for the JSON - grid request in the “Request body” and “Response” tabs. This change a (...)

(...) emplates, as it groups all the form field tags in one place and thus significantly reduces the time needed to look for them in the system.   GUID identifier in HTML template The general rules for identifying item list, data table, and data row form fields in HTML templates using the GUID identifier are discussed below. Note that form fields of other types cannot be identified with the GUI (...)

(...) At this stage, the technical team implements the user's concepts, i.e. prepares the application for production deployment. In other words, developers extend the project by configuring actions, rules , form field visibility and requiredness settings, as well as default values and data sources for it, so as to turn it into a fully working application.   Fig. 3. Configuration of " (...)

(...) an easily create arithmetic operations in the WEBCON BPS system using the rule editor. To access the rule editor, click the ellipsis button in the upper-right corner of the fields where you can enter rules . This tool is not required to create arithmetic operations, but makes it much easier, especially in the case of more complex operations. The rule editor window   The rule editor wi (...)

(...) . One of the modifications involves access to three sharing actions and the ability to insert the “Share” button directly in the form. Other modification is the appearance of new business rules . The aforementioned configuration elements are discussed below. Context variables Once you check the public link functionality, the business rule editor is expanded with new context variables. (...)

(...) ount for reading data from the database already existed in earlier versions of the system, but now it is created by default. Thus, bps_user is the standard account in the context of which SQL COMMAND rules and all queries using the Default connection are executed, e.g. when configuring selected form fields or actions, executing or testing SQL queries with the use of <Current BPS database>. (...)

(...)   Introduction The logic behind the execution of tasks by service is a multi-faceted and complex issue. When planning tasks, application designers are often unaware of the mechanisms and rules used by the service. To fill this gap, this article describes the elements affecting the sequence in which the service executes its tasks.   Content databases The databases that store i (...)

(...) companies by offering, among other things, the possibility to send (via dedicated actions) Email notifications in multiple languages at the same time. However, the functionality is subject to certain rules that may require the user to take additional actions or, for example, affect the visibility of people exchanging correspondence. This article describes the dependencies that apply when sending not (...)

(...) ata How to obtain information about all personal data usage in the system   It is important to note that GDPR introduces changes in personal data protection, but does not impose strict rules that must be adhered to in a specific company. The solution presented in the following article is not an A-Z guide but rather a suggestion. You can base your own configuration on it so that your comp (...)

(...) ossible to get the desired voting-style behavior from WEBCON BPS using one or two SQL queries together with a Workflow Control step. Moreover, the SQL queries can be encapsulated onto global business rules that can be reused repeatedly. At a high level, it looks like this:   Part One: Business rules with SQL Queries You will need to create three business rules . “Vote Co (...)

(...) scriptions of the functionalities and options available in the system with examples of their use, configuration information, as well as easily accessible lists of form fields, actions, functions, and rules that are or may be needed when creating applications. The online help document is also a perfect solution for those who are just starting their adventure with WEBCON BPS or who would like to get t (...)

(...) the functionality along with a business case for its use.   Basic definitions and functional assumptions LIKE and CONCAT are functions that can be used in WEBCON BPS to create business rules , form rules , SQL queries, and to retrieve values from data sources. CONCAT combines text values into a single string and is available among the functions dedicated to text. With CONCAT you can ret (...)