WELCOME TO THE COMMUNITY
find what you are looking for or ask a new question

search results

for step

(...) d path and the user will be provided with a summary.     You should remember that: a quick path will be available only when all marked instances are at the same step . instances are processed individually – an error in one instance does not interrupt processing of the remaining elements. When elements are processed, a browser window should stay open. (...)

(...) es Once the task is completed and the path is traversed, the workflow instance is marked as Modified by the Substitute and forwarded to the person to whom the task is assigned in the next workflow step , or proceeds to the final step . Tasks completed under a Substitution are always signed with the Substitute's name. This is visible in the Instance history: Fig. 23. Instance history &nd (...)

(...) igner) will help keep large batches of actions organized. Conditions within automations can be used to either supplement or replace existing execution conditions – similarly to a Flow Control step , they can direct automations to carry out different sets of actions depending on some condition. In earlier versions, the execution conditions did the heavy lifting in terms of determining which acti (...)

(...) reasons, for example, may turn into an overdue task, the CPO can easily plan the department dynamics, support the performance of the department workers and  monitor their progress. The first step when preparing a mass e-mail notification is to create an e-mail notification template. Mass e-mail notification template In the “System Settings”,  “Global Parameters& (...)

(...) oved leaves in the absence process, but there are more possibilities - the process described below allows you to manage employees from the level of the production line. Application At the first step , a line supervisor assigns tasks to employees, completes necessary data (such as line number and production type), and starts an instance.   Fig. 1. An example application instance (...)

(...) tity. Figure 1 presents the exemplary configuration for WEBCON BPS PL business entity.    Fig. 1. Business entity configuration in WEBCON BPS Designer Studio   The next step is to create BPS groups and assign users their users. See: BPS groups in Standalone installation type. Figure 2 presents the list of created groups. When configurating groups the following format (...)

(...) ilustrated on the example of entering an invoice document into an external system.  An invoice is registered and approved in the WEBCON BPS system. In the "Accounting Verification" step an invoice entry into the external system is invoked. The user invokes the entry by using the WEBCON BPS system.  Such entry is made by invoking a synchronous WEB Service at the "Entry i (...)

(...) ;Field matrix - setting the "Justification of need" form field   Fig. 9. Field matrix - setting the "Department Head's consent" form field   The next step is to set the rule limiting the requiredness of the "Justification of need" form field in the "Editability and requiredness" tab.The rule below returns TRUE when the total order a (...)

(...) n. The process consists of two workflows: Marketing offer workflow – the workflow is used to start and monitor ongoing marketing campaigns. A user registers a new campaign and in the next step fills out the details of the offer. If you follow the Offer created path by using the for each operator and the Start a subworkflow action, the Marketing request subworkflow will be started for each (...)

(...) n of Autenti and properly modify the addresses provided in this screenshot.    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 &n (...)

(...) Templates. A panel will appear on the right side of the document, from which select your preferred Applications and Processes/Form Types, as well as form fields.     The next step is to create a printout with the indicated form fields. The new Word document will be a template on which you can enter any formatted text. In the described example, it is the text of the equipment p (...)

(...) er] command to USE [Name_base] in the script.   Since only performance is considered here, change the @CreateJobs parameter to NULL and run the script by selecting Execute. The next step is to create a new job, which can be easily done from the interface:     In the General tab, change the name of the job to one that suggests what it does, such as ‘Mainte (...)

(...) ield. Now, click the “Execution conditions” tab. It is also possible to choose icon of the new button and specify the message displayed before and after proper action execution. These step s are skipped in the discussed example.       To make the button available only for the document entry point, enter the below rule in the “Availability restriction (...)

(...) client. The client can view the schedule, but cannot sort the item list, as the schedule is fixed and cannot be modified in any way. A simple four-stage workflow is defined. It begins with a start step where the schedule is drafted and then transits to an intermediary step where it is either accepted or rejected. The process workflow for credit installment schedule   Apart from pi (...)

(...) The author would like to share the prepared documentation with their colleagues from the creative department so that they can proofread it and make any changes thereto / give suggestions. In the next step , the documentation will be forwarded to the supervisor for review. The process used in the business case is as follows:     The designed process assumes that during the revi (...)

(...) e integration can be found on our GitHub. Each connector represents a context for obtaining data: User or Application In this article, we will go over the latter method in detail. The list of step s to achieve this is as follows: Download the connectors and place them into the “Custom connectors” repository of the Power BI installation folder. Set up an API application in th (...)

(...) Timeout actions An “On timeout” automation is a specific action trigger. An automation of this sort executes actions after a specific time elapses, e.g. from the moment of entering a step . The time after which an automation of this sort is run can be calculated based on more complex conditions that can also refer to form field values. The whole configuration allowing users to define t (...)

(...) on: 2025 R1 and above, author: Krystyna Gawryał   Introduction Instance history is an area where the user can check what actions were performed in the Workflow. History details the step s taken by the user and the paths they took to complete the assigned task and finish the workflow. This article summarizes the most important information on the Instance history in WEBCON BPS Porta (...)

(...) for application management” option available in the installer window allows users to move to database creation.       Then, go to the “Database creation” step available on the left, select “Archive Databases” (related to specific content database), and click “Create archive database”. The “Database creation” node (...)

(...) ettings.       Next, go to the Mail tab, select Customize actions, and check the box next to WEBCON BPS Add-In.     After going through the above step s, the Outlook Modern add-in is ready for use in the web application.   Installation in the desktop application There are several ways to install the add-in (manifest) in Microsoft 365 d (...)