(...) t small changes. These small changes can be tracked via our changelog (available at the bottom of this page), which compiles a list of all modifications made to a major version over its lifecycle . Our latest major release is 2026.1 – [Whitepaper – Business overview] WEBCON provides full technical support for our two latest major versions. (...)
(...) t small changes. These small changes can be tracked via our changelog (available at the bottom of this page), which compiles a list of all modifications made to a major version over its lifecycle . Our latest major release is 2026.1 – [Whitepaper – Business overview] WEBCON provides full technical support for our two latest major versions. (...)
(...) Fig. 1. Workflow in the “Recruitment” process Due to the unique nature of each stage of the advertisement publication process and the individual periods within its life cycle , a different form was created for each workflow step. The Form templates functionality was leveraged to prepare these forms. Configuration A new Form template parameter has been added (...)
(...) t small changes. These small changes can be tracked via our changelog (available at the bottom of this page), which compiles a list of all modifications made to a major version over its lifecycle . Our latest major release is 2026.1 – [Whitepaper – Business overview] Important: Before upgrading from one complete version to another (eg from 2019 (...)
(...) tion Timers are elements that allow you to define the frequency with which the associated actions are performed. Thanks to them, it is possible to define the start time and the possible repetition cycle of such actions. In WEBCON BPS 2025 R1, numerous changes and improvements have been made to the operation of Timers (previously known as Timeouts). This article describes these changes to the time (...)
(...) Search Server configuration) 7. (Optional) Update the IIS site bindings if the site hostname changes You may need to restart the site for the changes to take effect. 8. Recycle the application pool in IIS At this point, access to Portal and Designer Studio should be restored. 9. (Optional) Replace the services in the configuration if they did not use the &qu (...)
(...) ID – ID of the BPS content database. The default value is 1. Fig. 11. Entering environment variables After entering and saving the data, it is recommended to recycle the pool on which Public Forms is running. Start and configuration of the form The next step is to prepare the form. When you open the Public Forms site, you will see a login window. (...)
(...) tion – a workflow that supports users in planning and preparing for upcoming meetings. The goal of the overall process is to provide comprehensive support throughout the client meeting lifecycle — from capturing meeting outcomes, through drafting notes and communication, to planning subsequent interactions. Workflow 1: Meeting notes The first workflow is designed to pro (...)
(...) t small changes. These small changes can be tracked via our changelog (available at the bottom of this page), which compiles a list of all modifications made to a major version over its lifecycle . Our latest major release is 2026.1 – [Whitepaper – Business overview] Important: Before upgrading from one complete version to another (eg from 2021& (...)
(...) figured AI Agents, grouped by the processes to which they belong. For each AI Agent, the report also displays the associated step, a workflow, and the current status. This supports governance and lifecycle management of AI Agent configurations. Live job queue—a real-time list of jobs currently being processed or awaiting execution. Each entry includes context as well as the job waiting ti (...)
(...) ations, processes and workflows. To get an overview one can create an MSSQL data query with the current database as connection and the following SQL query. It returns in the first column if the cycle is active or not. Then there are several columns containing GUID, ID and name of the associated application group, application, process and workflow. Next there are all columns of the excecution (...)
(...) s, we have to use "select top " and run global action more often (eg. in every 10 minutes) Earlier (before BPS 2020), it was a once a day run. Proposal: have new GA setting to specify number of cycle s it should perform after triggered by schedule. This way we can split big transactions, but still keep once a day schedule for global actions. (I know execution condition on action is a workaround, b (...)
(...) ) to see whether it is today or in the past and then send an email to the author of the instance. However, I don't really know how to do this. I assume that I can do this with a Global Action - cycle Action. But I don't know which Webcon action I can use for this. (What I already have is a "BPS internal view" of all instances from the process. With this I could filter on the reminder date, but I (...)
Hello, I have a global cyclical action that does some things. And in "Error handling" section i've got an automation that sends a customized email It was working fine in 2022, stopped working after upgrading it to the newest 2023 version. Currently it is impossible to do such scenario. I've also tried invoking a REST API but it also fails. Those automation put somewhere else (not in cyclical
(...) r a documentation of a system. For this I need the text in markdown format/notation/language (I'm not sure what the correct word is for this). What I need on top of the "actual document" is the life-cycle of the single articles/pages, i.e. the development of the content (history) and the review and approval steps before it is published. My idea was to move the entire life-cycle into Webcon and afte (...)
(...) ven after stopping and restarting (which reset the count to 0), it still didn't work. I had to create a new GLOBAL ACTION, deactivate the old one, and then everything worked fine again. Since the cycle is set to every 15 minutes, this error will likely recur after approximately 1.87 years. Question: Could you please confirm if the maximum execution count is 65,536? USER VOICE: Could you suggest (...)
(...) 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, I use 4 different paths. This is due to the fact that sometimes I assign a task to one person, and sometimes to two pe (...)
(...) hived items forces organizations to use workarounds, such as keeping items in the production database longer than necessary. - This reduces security, slows down the system, and complicates data lifecycle management. [Problems resulting from the current lack of functionality] - No controlled access to the archive – users must either have global permissions or none at all. This limits precisio (...)
(...) the database upgrade. Currently we only have the information that the upgrade started: 17-01-2026 16:00:11 msg: Scripts are loaded src: DBUpdateControl 17-01-2026 17:21:24 msg: AppPool WEBCONBPS recycle src: IISManager It would be nice to have an output like - 17-01-2026 16:00:11 Script 7703 \t Change picker columns length from 1000 to 4000 \t Database: BPS_Content_X Start time\t 16:34:21 \t (...)
(...) to "Minutes". I tried different combinations of options and the only one was: - First activation > Start date: Immediate or Step entry date > Offset 0 day > Interval 75 Minutes - Repeat in cycle s: yes > Number of executions 2 (finite number) This way the 1st activation is immediatly and the 2nd and last 75 min later. How can I achieve that there is only one activation with an offset (...)