search results

(...) Fig. 2. Example of Instance history   History contains information about the instance, its workflow, and operations performed on it by users. Unless an appropriate visibility restriction rule has been defined, History also displays the names of all form fields along with the values entered for them, even if the user has set these fields as invisible in the Field matrix. Note: History d (...)

(...) ues in “Data table”, “Data row”, “Chart”, or “HTML” form fields. Additionally, archiving does not include custom controls, as well as form and business rule s.     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 vi (...)

(...) processes and any changes to them can be successfully transferred between those environments thanks to the built-in application import/export mechanism. However, there are some exceptions to this rule , where the changes made will not be transferred from one environment to another, unless an appropriate approach is taken. This issue concerns changes in global elements and non-standard operation of (...)

(...) . 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 rule s based on actual data entered by users. Associated modules: “AI”.   Workflow instance archiving There are two dedicated actions in WEBCON BPS that provide archiving (...)

(...) nctions should be used instead of standard retrievers, similar to the Comment system field. After expanding the branch of the Multiple lines of text form field with Append mode enabled in the Edit rule window, the following additional functions are displayed: Text of the last entry – returns the value of the last entry in the field, Date of the last entry – returns the date of t (...)

(...) he “Name” column and specify the form field containing the value in the “Source field” column. Configuration of the “Request body” tab   Business rule s 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 (...)

(...) 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 rule s 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 GU (...)

(...) 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, rule s, 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 &quo (...)

(...) erations quickly. Detailed information on the “Calculated floating-point value” column is available here: https://community.webcon.com/posts/post/using-calculated-columns/196   rule editor You can 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 wher (...)

(...) sharing expiration time (in days)” option allows you to specify the number of days after which sharing will be deactivated. You can also define or calculate the number of days using a business rule inserted in the field mentioned above. The “Sharing” section lets you enable the public link functionality   Note that checking the button itself will also modify the co (...)

(...) the abovementioned instance in the read-only mode. The information on the group member who executed the task is presented indented below the group name.   The GROUP MEMBERS business rule The assigning tasks to groups functionality applies to the whole process and all instances run within its framework. Nevertheless, it is possible to apply locally a different approach, i.e. assign (...)

(...) ach Process. To accurately measure time for each indicator, we can measure the passage of time according to one of three Operating modes: in Calendar Days, Working days, or according to a Business rule .   The latter two options have their own extra configuration sections to further customize their calculations. Calculate based on calendar days – The simplest and most self (...)

(...) ct the following option from the drop-down list:   After a while you will see a warning as below. Click Switch to make Linux container support possible.   As a rule , container is a non-persistent object. Therefore, care must be taken to ensure that data are not lost when the container is disabled. In Docker Desktop, this is ensured by the Docker Volume component (...)

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

(...) 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 rule s 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 no (...)

(...) 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 rule s 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 com (...)

(...) 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 rule s that can be reused repeatedly. At a high level, it looks like this:   Part One: Business rule s with SQL Queries You will need to create three business rule s. “Vote C (...)

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

(...) 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 rule s, form rule s, 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 re (...)