search results

(...) emplates, adapting to both dark and light modes presents a unique set of complications. This adaptation is crucial because it significantly affects the readability and visual appeal of your emails, depending on the user's preferred theme settings. Here’s an exploration of the challenges and considerations when designing for both modes: Understanding User Preferences: The primary challenge in (...)

(...) Item list. The rows are identified on the basis of unique values specified in the Unique value mapping field. At least one of the above options must be selected for the action to be executed. Depending on the type of changes made to the Item list, the action log displays data on the number of rows updated, added, or removed. Action configuration and execution example The action was confi (...)

(...) electing the theme, the default theme is restored. The window also has an educational function: there are universal prompts for the user to resize the screen using the mouse or keyboard, which vary depending on the operating system used. To display the accessibility icon in the top menu in Portal, it is necessary to check the dedicated Accessibility button box in WEBCON BPS Designer Studio (System set (...)

(...) e that these kind of things are documented. What would be the benefit of having an application: When something is automated, it can be tested, and therefore there's lest to document. Depending on the setup you may have the same processes in multiple databases but these have different configuration. Business entities, connections, global costants etc.. We have a version history for t (...)

(...) GET ATTACHMENTS function), or entered manually as one of the function arguments. You can optionally specify the maximum number of words in the summary, thus customizing its length.   Depending on the length of the source text, the execution time of the rule with the AI TEXT SUMMARY function may increase.   AI SENTIMENT ANALYSIS The AI SENTIMENT ANALYSIS function allows you to (...)

(...) of operation. We can decide whether the API should enable the triggering of automation, retrieve data from an existing data source or perhaps return information about a specific workflow instance. Depending on the selected mode, the rest of the configuration will be slightly different. In the case of automation, we create a sequence of actions on the appropriate tab that will be executed when the API (...)

(...) , the instance is routed to the final step. Otherwise, the item will return to the Awaiting for signatures step. The system can return different statuses: PROCESSING – decisions are still pending from some participants, COMPLETED – all participants have signed the document, REJECTED – at least one participant refused to sign. In the Awaiting for signatures step, configure (...)

(...) lements (widgets) on a dashboard. In WEBCON BPS 2025 R2, the design grid consists of 12 columns that define the width of individual widgets, and a variable number of rows that are dynamically added depending on the number and size of embedded elements. This allows the dashboard’s length to automatically adjust to its content.   Thanks to the design grid, it’s possible to precisely (...)

(...) sts HTTP requests can be divided into two categories: those defined by users in the Invoke REST web service action and the system-generated requests, which are not configurable and are triggered depending on the functionalities being used. The execution of the Invoke REST web service action is forcibly terminated after 100 seconds. Operations that time out in this way return the error message: &quo (...)

(...) . In this case, we were allowed to reduce the resolution of the image already at its initial save within the document template. We chose a maximum resolution of Full HD – 1920x1080 pixels, depending on the image orientation. This prevents the image from unnecessarily occupying space in the workflow histories. Our solution was JavaScript. We used an older version of the Pica library by Vita (...)

(...) sing change from January 1, 2026  – WEBCON version 2026.1.4 overhauls the licensing model. After upgrading the environment, it is necessary to download the license package again. Depending on the environment configuration and the licensing model used so far, different system behavior scenarios may occur after the upgrade. In particular, in environments that previously used legacy user (...)

(...)     "restrictedToMinimumLevel": "Fatal"   } }   OpenTelemetry Any tools using the OpenTelemetry standard. Different tools may support different combinations of Metrics/Traces/Logs depending on requirements and preferences. Tools can also interoperate; for example, logs sent to Loki can be visualized using Grafana. Multiple OpenTelemetry exporters can also be active at the same time, (...)

(...) the model.   Business case: Cost invoice registration   For the purpose of this example, a process for registering and approving cost invoices with a conditional workflow depending on the invoice amount has been designed. Ultimately, it is intended to streamline and partially automate the invoice approval workflow. The process consists of six steps: entering the invoice data (...)

(...) r higher, the license package must be downloaded, even if its contents (e.g. the number of licenses) have not changed. This is because the package may be supplemented with additional feature flags (depending on the agreement terms) that control the availability of selected functionalities. Missing these flags may result in limitations to system elements that were available before the upgrade and should r (...)

(...) ariations — using transparency. In the attribute settings, set the background color using rgba, where the a value controls transparency. And that’s almost it. Almost, because depending on the Webcon version, the platform applies this value slightly differently in HTML classes. For attribute group coloring, in version 2025, you need to pay attention to the repeated color in the C (...)

(...) er This mode is associated with a specific application and is based on API Definitions – each tool corresponds to a specific API Definition. Both read and write operations are possible (depending on configuration), and the tools reflect the business logic of the application. Each active API Definition defined within the process can be automatically exposed as an MCP tool: the tool na (...)

(...) be better if the available space is used. I already added a style overwrite for this. 3. If single row editing is used it would be better to display the icon on the left instead of the right side. Depending on the width of the item list the user needs to scroll and if you are unlucky the displayed info panel may hide the icon. Of course, I can't replicate the later case any more. Off topic It's nice t (...)

(...) ll for common users. In order to give users a more simple look of what happened so far in the workflow, I created a datasource that should work for all workflows and translations. Values are shown depending on the users browser language. It simply shows which step was left with which path, by which user, at what time. I present this in an SQL-grid in the forms where I think it will be helpful to the (...)

(...) Hi. I'm looking for a solution to hide rows of a list element depending on the value of a list element column. I.e. for a task list I would like to have the row visible for everyone, until the checkbox "done" ist set "true". I tried with the "Acceptance" function (see Acceptance.png), but the issue is that I can make the column visible for a (single) defined user, but not for multiple users. Any ideas (...)

(...) Hello all, my first post here. :) I have an issue with creating parralel tasks that should all be required. The user has 3 checkboxes on the form. Depending on which of them are checked, there should be created a specific task for each in a single step. The tasks are being created in the action of "Approve" path of the previous step. It's all fine for now. (ex. if (checkbox1) -> create Task1 etc.) T (...)