search results

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

(...) ransitions are handled, i.e. when an instance is started in a new workflow or subworkflow, for example, by triggering an action or automation. Therefore, it is necessary to follow these configuration rules : It is not recommended to configure additional authorization for path transitions in subworkflows (None). However, if the user wants to configure a separate authorization for a subpath transi (...)

(...) ions are displayed in the language selected in the User profile in Portal. Values selected on the form for a Choice list that are available in other parts of the system (e.g. in Reports, My tasks, rules , and Mass notifications) are also displayed in the language currently set in Portal. However, this does not apply to previously saved instances – once the translations have been configured, the (...)

(...) r form fields, attempting to enter a link to an instance into the Choice field using a QR code would result in the insertion of an identifier for that instance. The SCAN QR, SHOW QR and HIDE QR rules You can control the input of values into form fields or columns through QR codes using form rules .  The SCAN QR rule enables you to specify a relevant form field or column for which the QR (...)

(...) ach Existing button () in the Data Sources tab and select the respective source in the newly opened window.   Adding an existing public data source   Global form fields, rules , and constants The last issue that deserves attention is the handling of elements with a “global” status, such as form fields, rules , or constants. While the citizen developer, actin (...)

(...) m the configuration of the main form. However, it is possible to break the inheritance and configure the compact form independently. - You can control the behavior of the compact form through form rules . By default, the configuration of such rules is inherited from the settings of the main form, but, similar to the first case, it is also possible to break the settings inheritance; security lev (...)

(...) hose issues is Magic Numbers. This post is rather for beginners, those starting their WEBCON journey. It focuses on the importance of using Constants instead of typing numbers directly in filters, rules , and queries. This leads to easier maintenance and helps with understanding what some pieces of configuration do faster. If you want to learn why you should change this: to this: &nb (...)

(...) ate one. There, you can store relevant information about employees, as well as their XP or badges that they can later boast about. In their profile, we added an HTML field where, using a few business rules , we easily displayed in a somewhat non-standard WEBCON manner, some interesting details about the employee. This would have been substantially more challenging without the new performa (...)

(...) according to the application to which they belong. However, please note that the list can also contain elements that do not belong to any specific application, such as global automations and business rules . These elements are grouped in a separate node and are visible only to system administrators. You can freely modify this default grouping method using the Filter editor… option in the context (...)

(...) h Business administrator privileges. In addition to detailing the specifics of the aforementioned mode, the article addresses the process of granting Business Administrator privileges and configuring rules that include the Is admin mode active? variable.   Who is the Business administrator? In simplest terms, the Business administrator in the WEBCON BPS platform is the individual with the (...)

(...) ware that this change will have consequences. This global setting will result in collecting a large number of entries, making it more difficult to find relevant information.   Modifying rules in the Nlog section The configuration above specifies what information is saved and at what level, while the Nlog library determines how this information is recorded. It collects entries, proces (...)

(...) to the list, set them as default value : Ordinal number, and change the configuration as in the attached screenshots. ID: T_ID:     Next, we create 2 JavaScript form rules FRJ_Moveable_List_ID_SET   FRJ_Moveable_List_Delete: We add in the configuration of the change item list: - Deselect showing system ID - We set the FRJ_ (...)

(...) d. Additionally, the interface allows for navigation between document pages, providing flexibility and control over the entire signing process. To configure this solution, three essential business rules are required: Attachment Retrieval Rule: This rule gathers the names, IDs, and content of the attached documents.     CODE:     2. Signatory Ide (...)

(...) thentication provider and, after the user has logged in, displays the corresponding status. JavaScript – in JavaScript mode, the control for the form field is not displayed. Instead, all Form rules (and JavaScript) work, including the GetToke rule, which allows you to programmatically retrieve the access token issued during user authentication. In this case, the authentication may take place &q (...)

(...) possible experience for everyone, we kindly ask that you adhere to the guidelines listed below. By participating in the forum, you acknowledge that you have read and agree to follow the established rules . You also agree to keep forum discussion limited to topics best suited for this type of medium. We wish for this forum to be a place where our partners, clients, acquaintances, and anyone interested (...)

(...) t this is error prone. In my opinion the applications are not related, if they only share elements defined in system settings, data sources or plugins. Examples: - Globals -- constants -- business rules -- form rules fields -- fields - Data source -- Dictionaries -- Templates - SDKs If the export hits one of these elements no further related elements should be gathered. Best regards, Daniel