search results

(...) Applies to version: 2022.1.x and above; author: Dominika Stelmach Introduction The WEBCON BPS 2022 version introduces a new For each Operator , which allows you to configure an action, operation, or automation for each element from the selected collection.   Fig. 1. For each Operator   The Operator iterates over the collection elements, which can be an item list, any data s (...)

(...) Applies to version: 2022.1.3 and above; author: Grzegorz Straś   The SWITCH Operator allows more outcomes and conditions to be handled within the automation, when compared to the standard Condition Operator .   The condition within the SWITCH Operator is a business rule, whose result will point to the case that will be used. The case can be designated in two ways:   Var (...)

(...) There's an option to switch from horizontal to vertical layout if you click on AND/OR Operator s. Could this be extended to all other Operator s, too. :) This would reduce the scrolling and therefore improve readability a lot.

(...) Hi all! I personally think the Operator 'ForEach' is a great addition to version 2022.1.2.31, thanks to Webcon Team. Unfortunately I do not find any documentation on that, especially how to iterate over 'Any Collection' and access columns in custom action. If I select 'Any collection' and put some SQL statement in there, is there a way to access specific table columns from generated table result (...)

(...) e step in which they are located     Functions formatting the report cells Expressions In the expressions you can use defined operations and functions: *, /, +, – Operator s and other mathematical Operator s + Operator to linking the text strings Other mathematical functions described here ‘if’ function (condition, value_if true, value_if fals (...)

(...) e rest values have a shade of color with a proportionally distributed shade.       C. Conditions The Conditions mode using conditional instructions and the Operator s available depending on the data type of the selected column. In this mode you can change the color and fonts, and refer to the content of other columns (from the 2020.3 version). In the example b (...)

(...) ngine searches indexed data and as a result – what the results are. Using appropriate parameters in the query allows for more precise results.     Below you can see basic Operator s which can be used by the user while creating a search query. Action name Example How it works Basic search Invoice Returns all instances with Invoice& (...)

(...) As was the case in previous versions, not every action can be used on every trigger, so automations created on different triggers will have access to different pools of actions. Operator s – contains the Condition block that can create branching paths for the automation. Each condition is defined as a Boolean business rule that directs the automation down one of two paths. It is (...)

(...) roduction 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 Operator s allows a user to create more or less complex rules, depending on the user’s needs. When working with form rules, there may be a situation where execution of one function or subrule interrupts (...)

(...) lication. Moreover, the action operates on all attachments linked to the instance in the context of which it was called. If necessary, the action can also be called in the automation (the For each Operator ) or from the Attachments menu. In the present case, the author would like to cancel editing of only one of the attachments – the Excel document – so they should configure the action at (...)

(...) enter the actual arithmetic operation in the next field. To do that, select the first form field (the “Field 1” in this example) whose value is to be added, and then enter the arithmetic Operator (“+” in this example) and the second form field (“Field 2” in this example). The rule used in this example is shown in the screenshot below. It is important to note that arith (...)

(...) ple: CONCAT [‘WI’][‘_‘][‘Wisconsin’] returns “WI_Wisconsin”. LIKE checks whether a text (e.g. a form field value) contains the given text value. The Operator s that can be used when defining a value are: % – replaces any string of characters, _ – replaces a single character, [] – replaces a single character within the specified (...)

(...) he SHOW QR and HIDE QR rules show or hide the QR code icon in the form field or column control. (For the Item list columns, it is possible to constrain the rule operation by means of the FOR EACH ROW Operator ). Similar to the first rule mentioned earlier, the target form field is specified in the block of the rule.   QR code starting a workflow instance and redirecting to an instance QR (...)

(...) ere replaced (including added) as a result of the action.     Remove item list row The action, as the only one described here, is available only in the context of the For each Operator , where the defined Collection type is Item list. The action's operation is limited to removing the current Item list row, so there is no configuration window available for it. It is possible to c (...)

(...) rch button and a back to standard search button 2. Shows the checked fields plus the standard search box Ultimate options: - the ability to tell whether the fields should be search by the and/or Operator by the user - make the default display mode standard/advanced Search configurable

(...) ve in my automation. Unfortunately Category of the attachment is missing. I've been thinking about creating another automation, which will use `Modify attachment` action, and another `For Each` Operator to make it happen. However it is possible to have few attachments with same name, and there is no way to get correct category for them - at least I couldn't think of one. Even without the nesting (...)

(...) vice" will allow selecting one connection. This connection will be used without the context of the current business entity. The only option which would work in all cases would be to use if/switch Operator for each business entity and "duplicate" the action. At least I haven't found an alternative, if the connection has not only a different URL part but uses different credentials. Therefore it wo (...)

(...) bal level - Per process - Per workflow - For a custom notification action This would allow us to intercept all process related mails without changing the configuration itself with a lot of "if" Operator s. Besides this one other major benefit would be that we can provide our own notification type for a process. For example, we could define for a process that a "notification" is no longer a mail: (...)