search results

(...) semicolon is added to the ID of the line supervisor) and the Collection function (that returns the values from the SQL query separated by a semicolon) have been added.   Fig. 14. The rule selecting employees to display   The SQL query shown below selects the ID of the line employees:   Fig. 15. The SQL query returning employees to the default value   (...)

(...) . More information about task assignment can be found in the following articles: Assigning tasks to BPS groups BPS groups in the Standalone installation Task assignment – business rule s Parallel task assignment Predefined task assignment The “Create a task” action   Configuration of business entities and BPS groups To configure a business entity, g (...)

(...) rator   The operator iterates over the collection elements, which can be an item list, any data source, attachments added to the workflow instance, and any collection defined as a business rule .   Fig. 2. Collection type   Item list – the ability to select all available item lists in the process. All columns of the item list, excluding columns of loc (...)

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

(...) onfiguration where database name (except ID and acronym) appears, changing service configuration, changing portal configuration, changing queries in: data sources, actions, business rule s (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 appl (...)

(...) bel” menu button and restricting its availability From the 2022 R1 version the availability of the menu button triggering the “Printout a barcode label” action is determined by a rule . After its insertion, the button is visible only for the defined document entry point. Note here that without the rule inserted, the button is visible to all users and workstations, whether defined a (...)

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

(...) form.   Alternative file sharing options As mentioned above, in order to edit files via OneDrive, the user must have the appropriate permissions. There is, however, an exception to this rule . As long as the company’s appropriate security policy is met, files placed on OneDrive can be made available for editing to any users. This is possible using the Call REST Web service action. O (...)

(...) cution of action is postponed until at the end of transaction, after all actions in the automation are executed. If any operation within the transaction fails, the action is not executed either. This rule also applies the other way round: failure of an action executed in this mode prevents execution of the whole transaction; Pending after transaction: the execution of an action is postponed. The act (...)

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

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