search results

(...)     Configure the send document for signature action. Here it is triggered at “Manager approval” step. On “Approve” intermediate path add “Approve” automation including the trigger SDK action.     Figure 6. Configuration of the send document action   Configuration of the subsequent action sections is presented below: &n (...)

(...) ał   Introduction WEBCON BPS allows you to create templates that will then be used to automatically generate standard documents containing the data entered on the form. Previously, such automation was only possible with the Word Classic add-in for MS Word, but now the all new add-in: Word Modern is available, which can also be used in Microsoft Word Online and Microsoft 365 Word on Window (...)

(...) y point, enter the below rule in the “Availability restriction” field. The rule controls the button availability, making it visible only for the document entry point. Select “New automation ” in the selection tree.         Enter the automation name and move the pointer over the black arrow stretching between the “Start” and “ (...)

(...) hared with them, return the task to the author, or accept the documentation after making changes. To download all changes made in OneDrive back to the BPS database, it is necessary to create a new automation based on the Finish editing a file using OneDrive action. In the present case, it will be added to the "Accept" path:     After following the path, the action will (...)

(...) before, during, and after action execution.   Action execution modes 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 trans (...)

(...) Applies to version: 2022.1.x and above, author: Krystyna Gawryał   Introduction Menu button is a button available in the top bar of a form in WEBCON BPS Portal, used to trigger automation s added by the user globally or in a particular workflow step. Choosing this form of triggering automation s allows you to maintain a high level of readability of the form – an automation (including one (...)

(...) allows you to convert PDF files and scanned documents into their editable form. When the action is configured On attachment add, it is not required to go through the path or additionally trigger the automation with the Menu button. The text layer will be prepared automatically when the attachment is added and, depending on the settings, the original file will be replaced by its editable equivalent or saved (...)

(...) rtal   The user planned that in the "Completing documentation" step, the system will verify if at least 2 attachments have been added to the form. With Edit mode, they can view the automation that checks whether that condition has been met. All they need to do is click on the cogwheel icon in the top right corner of the step. Fig. 11. Preview of the automation defined on the & (...)

(...) ccess to the three sharing actions belonging to the “Privileges and sharing” group: Share workflow instance, Share task, and Stop sharing. The actions can be embedded in: process automation s (the “System settings” button → the “automation s” node in the selection tree), workflow automation s (as actions inserted globally in the workflow or in a particular s (...)

(...) but there are a few situations that have arisen that warrant special coverage – and special treatment.   The Problem Consider the workflow below. The path named Start executes an automation that starts several subworkflows. The workflow then waits at the Wait until all new sub-workflows are finished step until all workflows end positively, any end negatively, or it is clear that there a (...)

(...) an application that supported one of the document flows used at the university. During two meetings with students of the "Accounting and Controlling" major, we talked about process automation , implementation design, change management, and the changing model of a manager and an employee in business (Citizen Assisted Development). There was a high interest in topics related to: (...)

(...) information and document management” course, we conducted workshops with students. After a short introduction on the most important features of LCAP platforms that facilitate the design and automation of processes - we moved on to practice. Students of Computer Science and Econometrics, who learned the BPMN notation describing processes, this time had to translate it into the language of BPS. P (...)

(...)   While not explicitly necessary, you may well wish to something like list of the choices each task assignee made to the workflow instance’s Comments field. You can do this by adding an automation to the On entry event of the Workflow Control step. It needs one Change value of single field action configured to set the value of the built-in [System] Comments field to equal the outcome of a busi (...)

(...) ologies (ICT) with the expectations of the labor market.  During the conference, Aleksandra Słuszniak, Digital Transformation Director at WEBCON, presented on the topic "Low-code process automation – changes in labour market trajectories". During her lecture, Ola emphasized how Low-code platforms are expanding the IT job market to professionals with diverse educational backgroun (...)

(...) lity of path transition authorization affects how automatic subpath transitions are handled, i.e. when an instance is started in a new workflow or subworkflow, for example, by triggering an action or automation . Therefore, it is necessary to follow these configuration rules: It is not recommended to configure additional authorization for path transitions in subworkflows (None). However, if the user (...)

(...) , the employee who earned the XP, and the XP's value. Here's what an XP instance looks like: This is what the global XP report looks like: 2. Global XP- awarding automation To easily incorporate the XP functionality into any already digitized process, we created a global automation that receives the necessary data as parameters and creates an XP instance. (...)

(...) ist This action removes all rows from the Item list specified in the configuration. The action also removes rows that are not visible in approval mode. This action is not available from the global automation level. Action configuration and execution example The action configuration window simply requires the user to indicate the Item list to be removed.   Once the menu button is (...)

(...) s are grouped by default according to the application to which they belong. However, please note that the list can also contain elements that do not belong to any specific application, such as global automation s and business rules. These elements are grouped in a separate node and are visible only to system administrators. You can freely modify this default grouping method using the Filter editor… op (...)

(...) ntegrated login is used in the SQL connection parameters). The PowerShell action can only be executed in the context of a workflow instance, so it is not possible to add such an action in cyclical automation . This simplifies configuration because it always provides access to {WFD_ID}, so you can easily retrieve information about attachments to the current workflow instance from the database. To execute s (...)

(...) 2.1.4.127 version to 20225.1.1.105. I will just copy the headlines of this post and the related one about upgrading to 2023. Upgrade WEBCON BPS 2022 to 2025 Updating reports and dashboards automation session execution cleanup SDK Migration Deactivate standard push notifications Process license instead of single solution license Create new custom themes Verify updated item list actions (...)