search results

(...) ng through the “Signed” path.   Fig. 3. The form with a signed document   Configuration A simple workflow of signing a document has been created using the SDK actions dedicated to the integration with DocuSign.   Fig. 4. The signing document workflow   The first step is to add the “SendEnvelope” action which allows you to send (...)

(...) tem by using the designated Portal interface. In version 2020.1.3., a new functionality for managing BPS groups and users has been added to supplement this process. This articles described how the actions related to the BPS groups can be used.   Workflow configuration and creating an example BPS group A BPS group was created with two users:   Fig. 1. Users in the “Ma (...)

(...) window view with the bar, it is also possible to do this by using the arrows on the keyboard.   Description of shortcuts available in the Menu under the right mouse button Many of the actions that can be performed by clicking on an element in WEBCON BPS Designer Studio with the right mouse button, have a keyboard shortcut assigned. The shortcut information can be found in the right part o (...)

(...) V_ADMIN_Timeouts – the view with statistics of timeouts created in the system   Action logs view One of the views created by the system is the view showing the logs of the actions performed. It is available under the “WFLogs” name and contains the same information as in the “WFActionExecutions” table (see -> WFAction Executions table description (...)

(...) generation workflow   The form of Certificate generation is presented below:   Fig. 4 Certificate generation form   Action configuration There are four defined actions : On Training workflow Action which starts one Certificate generation subworkflow per participant. On Certificate generation workflow Action which generates certificate in MS (...)

(...) you more control over the notification you send. Standard notifications Standard notifications are sent to the people actively participating in the process and they are informing about typical actions such as receiving tasks, notification about the start or finish the workflow. In such cases, it is worth preparing a template with translations.   Fig. 3. An example of using the actio (...)

(...) commended time of 15 minutes stated by Microsoft is the maximum possible delay. Oftentimes, the team can be formed after only 5 minutes have elapsed. For team creation, we can use the same type of actions as when creating a new group – Calling the REST Web Service. The same connection was used in the action, but the data in the other tabs will change. The first change is the address of the calle (...)

(...) which the file ID is stored Item URL (AttText3) a field in which the file name ([$FileRef]) variable) is stored   After moving to the next step, the workflow has the following actions defined: Update status – updating the Status column in the library Insert BPS link – saving the link to the WEBCON BPS instance Download document – an actio (...)

(...) dd-in - document version comparision.     Configuration of the “Generate a Word file” action The action of generating a Word file is configured in the “actions ” tab in the step settings. Let’s add this action at the node on the path of the “Contract generation” path. The configuration of the action does not change depending on the se (...)

(...) hod of communication, and the use of electronic mail accompanies us both at work and in private contacts. Very often it facilitates problem solving and speeds up decision making. There are several actions in WEBCON BPS used to send e-mail notifications: Send a standard e-mail – a standard e-mail, a notification is defined as an action or on a given path, without the ability of individual c (...)

(...) oyee registration – a workflow allows you to register an employee to the newly created department.   Fig. 2. The Employee registration workflow   The created hyperlink actions allow: On the Register department workflow -> a person who registering the department has the ability of opening a new form (Employee registration) while passing specific form fields. On t (...)

(...) Applies to version: 2020.1.x and above; author: Dawid Golonka   Introduction The processes designed in WEBCON BPS use the e-mail sending actions in their workflows – e.g. e-mails about active tasks waiting for the user or e-mails containing various reports. The configuration of sending e-mails was described on the technical blog -> E-mails and templates in BPS. WEBCON (...)

(...) dent sub-workflows, they can be separated into two individual but still related processes. Make sure that creating the fields that are used only for calculating other form fields or controlling the actions (e.g. technical fields) is justified. In most cases, the value from this field (if it is not used in many places) can be directly downloaded and saved in the business rules. Instead of the data tab (...)

(...) Learn” path you can teach the program. In this way the system learns how to analyze vendor invoices based on the NIP distinguisher.   Summary This article described three types of actions use when configuring OCR AI. Careful planning of the workflow steps and actions and using the OCR AI Projects, can facilitate document handling and improve daily tasks.

(...) Applies to version 2020.1.x, author: Dawid Golonka   Introduction actions are commonly used in WEBCON BPS to design the processes and individual workflows. They are performed without any user interaction and defined on the transition paths or steps. An example actions perform such activities as calculating the field value, making an entry to AD, sending an e-mail. While working wi (...)

(...) in the following articles: Substitutions in WEBCON BPS - configuration Substitutions in 2019 version (webcon.com)   One of the options for setting the substitutions is to use the actions in the “Substitutions” category in WEBCON BPS Designer Studio.   Configuration The user may use two predefined actions – Add a substitution and Remove a substitution. (...)

(...) tep, there is a black arrow pointing in the opposite direction to the direction of the path. It means that at a given step a path moves back the workflow to the previous step has been defined. Two actions can be used to configure the path: Assign to users who completed tasks in previous step – a system will automatically recognize who completed the task in the previous step and reassign th (...)

(...) might be prepared a choice field that will automatically fill the related form fields via it’s advanced configuration d) In some cases, the setting of the default values can be replaced by actions set to trigger on a path if: The values are downloaded by using network services (web services) The default values are not necessary for a person who is currently performing a task The defa (...)

(...) ic archived workflow instance. To do this, open the selected instance in administration mode and then grant the appropriate privileges (Read only, Administrator) by clicking the “Administration actions -> Privileges” button. Fig. 7. Adding privileges via form   To add Custom privileges of report visibility, in the configuration window in the “User privileges” (...)

(...) eturn to re-check or signed contracts are blocked by the archive department. Have every step and path been used – we can see if there are some obsolete steps or paths What and how many actions have been executed – an incorrectly written condition can make it so that the action is not used at all. How many instances were processed during a given period – by checking (...)