WELCOME TO THE COMMUNITY
find what you are looking for or ask a new question

search results

for Operator

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

(...) I'm trying to make it work, but all entities (users, and groups) are being synchronized as groups. From the error log it seems like Webcon is generating LDAP query with an error - the OR - | - Operator seems to be in wrong place: - (8/12/2024 8:29:33 PM) Searching LDAP://ldap-server:389/DC=ldap,DC=goauthentik,DC=io?uid,gidNumber,objectClass,accountExpires,adspath,cn,company,comment,countryCode,d (...)

(...) error is thrown. Could we please get a flag to define, that this check should be executed? This would allow upgrading old processes for which this flag would be false by default. Adding the if Operator or an execution condition to each Add attachment action is not something I would like to do. Not only because of the effort but because there are now two places which need to be maintained. Here's (...)

(...) sts all 10 reports from the last month. 2. The BPS data source has columns including: ID, Signature, Author, Company, etc. 3. In the cyclic action, I added automation and the "Execute for everyone" Operator , where I indicated the above-mentioned BPS data source. 4. There is automation in the Operator that starts a new cycle (Start a subworkflow). I have 4 actions here because when I start a new element (...)

(...) Error: [Quote] Error occured during business rule evaluation. String values cannot be multiplied at: Evaluation requested at: Evaluation node: Operator (+) at: Evaluation node: Operator (*) at: Evaluation node: Operator (*) [/Quote] What I have : -process static A -process static B -process static C -process static D attribte a,b,c attribute a,b,c is changing dynamically vs Item List (...)

(...) erson from form (who is BPS user) What I did: 1. automation where I have a) Set local variable "Manager" from form atribiute (user with BPS account) 2. For each item list row: a) I thing about Operator "Condition" - how to do check condition ? to receive true or false and then if: false >> should be ease - assign subflow to "Manager" true >> ship non BPS users and assign to bps user ... (...)

(...) to read through: https://webcon.com/wp-content/uploads/2024/11/Changelog_2025_1_1_23_EN.pdf What are your thoughts on changes? Which ones are yours favourite? :) For me - ALL TRUE, and ANY TRUE Operator s sounds great! So many nested boolean logic to update ;)

(...) Hello, It seems that row coloring in report views does not work for calculated columns. When I open configuration for row coloring and choose one of the calculated columns, the Operator field becomes inactive and sais . Use of calculated columns would be nice to color the whole row, not only a column value (lamp).

(...) [Location] Process attributes > Attribute of a Select type using a BPS data source > Filtering section [The bug] In a data source filter, when using the ALL_TRUE Operator , the WHERE condition in a generated query is prematurely simplified, what results in an SQL error. [Workaround] Chain AND Operator s. [Fix] Please fix the SQL translation of the ALL_TRUE Operator :)

(...) ganizationStructure WHERE COS_BPSID = '##currentloginname##') To avoid performance issues, it would be great if we had the possibility to use a business rule to provide a filter value. Maybe the Operator s of the standard filter could be extended with an "Is in" option and the value with the possibility to also use a business rule instead of a fixed value? It should be available for SQL and SOLR based (...)