search results

(...) ł   Related documentation A detailed description of the functionalities mentioned herein and their configuration can be found in the following section of the WEBCON BPS Help: timer | WEBCON BPS   Introduction timer s 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 st (...)

Hi, during a call yesterday we realized, that a time previously timeout is executed after 10 minutes by default, if it runs into an error. This includes "Element was checked out" errors. While I agree that this may be a good thing for the production environment, but a pain in all others. Unfortunately my user voice was set to "Not now", but maybe it can be revisited now. https://commun

(...) Hi everyone, We're working on a process in WEBCON where we need to display a countdown timer on a form. Specifically, we want the timer to be shown in the [time until next adjustment] field, counting down to the next scheduled update. The timeout is set to update the [value] field, and the countdown should dynamically reflect the remaining time until that happens. Has anyone implemented something (...)

(...) thCheck = function(object) { let integerRange = new IntergerRange(object); object.value = integerRange.getValue(); } nxWebcon.integerRange.debounce = function(func, timeout = 300){ var timer ; return (...args) => { clearTimeout(timer ); timer = setTimeout(() => { func.apply(this, args); }, timeout); }; } nxWebcon.integerRange.processChanges = nxWebcon.integerRange (...)

(...) Fig. 1. Workflow diagram   The process includes two defined actions: sending a document to Autenti, sending a request to return the document along with the status. The timer mechanism is also employed to automatically trigger the path responsible for checking the document's signature status in Autenti every hour.   Business case For demonstration purpos (...)

(...) p; Workflow Service Services operations timeout in seconds This parameter defines the maximum number of seconds allowed for operations executed by the Workflow Service, which includes: timer -based actions, cyclical actions, handling of HotFolders and HotMailBoxes (monitoring, starting instances, attaching to instances based on barcodes), default path transitions from steps such as (...)

(...) ach with collection type 'data source'. Yes, I don't use an item list. Check if every element was processed If this is not the case, move the workflow instance to a temporary step A timer aka timeout will trigger the path again This is the automation for processing the elements: If you are interested in the details you can read up on it here.

(...)   The AI PROMPT rule is also used to generate article reviews in the "Review" step. In this step, the "Set review" action (type: Change value of single field) runs on a timer , automatically initiating the creation of the review by the AI.   In this case, the AI PROMPT function generates the review text based on the content of the "Content" fo (...)

(...) ect. at WebCon.WorkFlow.BusinessLogic.Automations.Engine.AutomationEngine.RunErrorFlowCollectionAsync(AutomationEvaluationParameters parameters, AutomationWithParameters automation, AutomationRuntimer esult currentFlowResult, CancellationToken cancellationToken) at WebCon.WorkFlow.BusinessLogic.Automations.Engine.AutomationEngine.RunAutomationWithoutResultCleanAsync(IAutomationWithExecutionCon (...)

(...) Hi, I have a process that use API to send data to another system. I have a patch in WebCon to check status, based on the feedback, process moves to the next step or waits another hour on the timer . I want to change this. I found this option in WebCon API: Path that will be used by element PATH /api/data/v6.0/db/{dbId}/elements/{id} But my second system don't have a PATH method. Do you hav (...)

(...) eted scheduled task should be deleted to keep the Task Scheduler clean and avoid clutter. Timeout Handling (Step X): To manage exceptions or unexpected failures, you can configure a timeout using a timer action on the waiting step, which redirects to an error-handling path if the job doesn't complete within a defined timeframe (e.g., 24 hours). Refer to the attached diagram for a high-level concept (...)