search results

(...) Hi, Current Situation: Data Sources are typically static and context-independent. Each Data Source is bound to a fixed query or API call, with no native mechanism to pass parameters dynamically. As a result, any variation in use (such as retrieving different columns, filtering by different criteria, or adapting to different workflow contexts) requires creating multiple Data Sources or embedding logic el (...)

(...) ogue with a read-only version of the workflow designer. In this mode, users could: - see the full workflow diagram - inspect steps and paths - review configuration settings of elements - analyze parameters and logic used in that version This would allow devs to fully review previous configurations even after many subsequent changes have been made. 3. Visual comparison between versions An additiona (...)

(...) Hi, an automation can have parameters with given data types. In the parameter settings there is a small icon showing the data type. When using the automation there are no icons to indicate the data type. That's why we write the data type as prefix in the parameter name as a workaround. It would be much nicer if there would be a small icon too as prefix of the name. Kind regards Sébastien

(...) ld appreciate your feedback. Regards, D. --1-- Typ: System.ArgumentException ------------------------------------------------------- Wiadomość:Cannot add to index of type WFBusinessRuleparameters entry with ID 6 Nazwa parametru: row ------------------------------------------------------- Ścieżka wywołania ------------------------------------------------------- w WebCon.W (...)

(...) Types of cookies used: “Permanent” cookies remain in the Internet browser of the device until they are deleted by the user or until the period of time pre-defined in the cookies parameters lapses. “Session” cookies remain in the browser until it is closed or you log out from the website on which they have been installed. Cookies are not used for processing or storing (...)