search results

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