search results

(...) Now there are 3 circles showing new tasks, all taks and overdue tasks. In my environment there are tasks that should be marked as postponed - some tasks should be separated from the normal ones, as users intentionally know they will do some task in the future, but don't want to mix these tasks with the current ones. There could be an action that would mark a task as postponed and another one marking as nor (...)

(...) There are three basic modes for executing actions: Standard behavior: action is executed precisely where the automation flow was triggered; Pending in transaction: the execution of action is postponed until at the end of transaction, after all actions in the automation are executed. If any operation within the transaction fails, the action is not executed either. This rule also applies the other w (...)

(...) given database. Another type of actions controlled by the service are the “On Timeout” actions. In this case, once you enter a step with the “On timeout” action, the action is postponed in the database and executed by the service responsible for the respective role after the time specified in the action elapses.  Apart from the aforementioned actions, the service executes opera (...)

(...) ution at specific hours TYPE: MINUTE, HOUR A day is considered to be as many hours as the timer activation period is defined for. If the timer activation time is outside these hours, it will be postponed to the next such period.   Examples Timer activation hours: 10:00 AM – 3:00 PM, execution based on the form field date Start date: May 1, 2025, 8:30 AM; Current date: May 1, 20 (...)

(...) lags of the tasks to which they are assigned, both from the document and from a properly configured report. Currently, WEBCON BPS distinguishes two types of task marking: Flagged (Fig. 1.) postponed (Fig. 2.)   Fig. 1. “Flagged” task   Fig. 2. “postponed ” task   Providing users with the option to flag tasks does not require (...)

(...) tep. According to an old documentation 'On exit' actions should be executed first and should not be dependent on the path, that was taken. Unfortunately the action 'Remove privileges' is always postponed and removes all the privileges / tasks which were set on path, which is not the expected behaviour. Is there any way to execute this certain action before any other actions? Thanks a lot in a (...)