search results

(...) Fig. 1. The instance view in the compact form   Description A simple invoice cost workflow was created. It consists of three steps – Registration, Waiting for scan and Archived. A document can be registered both with a scan or without a scan.   Fig. 2. Invoice workflow   The global form template is the default template used at every step. Below there is a glob (...)

(...) u to generate the Word files that can include data entered on the form. This functionality is useful in various processes such as contracts, vacations, and orders, where it is necessary to submit the document for signature. The following article describes the method of WEBCON BPS add-in installation, template preparation and action configuration for generating a .docx document . An example template was bas (...)

(...) this article.   The workflow configuration A simple “Press release review” workflow was created used to efficiently oversee the creation and publication of various text document s.   Fig. 8. The configuration of the “Press Release Review” workflow   The e-mail template configuration The dedicated e-mail template and e-mail sending acti (...)

(...) Applies to version: 2020.1.x and above; author: Konrad Wojtycza   Introduction WEBCON BPS can be used as an efficient document management system. This article describes how to use barcodes to scan PDF files and paper document s and have them automatically added to your WEBCON workflows' instances.  Common business scenarios for using barcodes include: Having a (...)

(...) go through to reach the next step. However, when going through the system step, not the user but the system moves the instance to the next step after executing the appropriate action e.g. receiving a document scan. A path which the instance went through is called the default path – you can select them when configuring the path.   Configuration To set the default path, enter the path co (...)

(...) t: IListViewCommandSetExecuteEventParameters): void {      switch (event.itemId) {        case ’COMMAND_1′:          // Start workflow          // Generate document  Link          const absoluteUrl:string = this.context.pageContext.site.absoluteUrl;          const docBPSName:string = event.selectedRows[0].getValueByName(‘FileLeafRef’); (...)

(...) after applying the layer. In the next step, read the TAX ID – this is important because the invoice template is checked by tax id. The OCR program treats the invoice as a semi-structured document . This means that while most invoices have a similar pattern, the location of the fields on the document may differ. An invoice from one contractor may have a tax identification number or date of issu (...)

(...) Generation Templates” button. Fig. 6. The “File Generation Templates” option   On the right there is a menu in which you must indicate the application, process and document type from which the data for printing will be loaded. Fig. 7. The selecting process window   The next step is to create the printout. Fig. 8. The printout template   (...)

(...) to both users.     This configuration should not be used on the transition path or in the action where, in the previous step, the user didn’t have any active tasks (e.g. document registration, system step, waiting for subworkflows, positive and negative final steps, steps related to the scan or OCR processing).   Assign to users who completed tasks in previous step (...)

(...) .1.x and above; author: Michał Lalewicz   Introduction The following article describes how to install the ABBYY FineReader 11 component. FineReader is a program for converting scanned document s and PDF files into editable form. It is also responsible for generating a text layer on the attachments in workflows.   Installation Before starting the installation process, creat (...)

(...) dividual steps require tasks to be performed by a specific user or group of users. The appropriate design of a process and the correct assignment of tasks can improve the performance of daily duties, document processing and company management. The article describes the idea of assigning tasks to groups – on the example of BPS groups, available from the 2019 version. Detailed information about groups (...)

(...) sponsible for marking fields as “for learning” The ability to hide learn fields if the recognized values are compatible with the expected ones, e.g., with the values of suppliers’ document s or rules set in the process   C) The designation of the learning buttons is “remembered” until the learning OCR action is triggered. All fields marked by the user as &lsq (...)

(...) (timeout) may be exceeded. The case below shows us how can we deal with this problem by using only the standard WEBCON BPS functionalities. You can create a queuing mechanism that will update ten document s at a time.   Business case We want to create the application “The settlement of business expenses” that will allow our employees to settle individual business expenses. Due (...)

(...) o with REST API. We can also use it to: Download and modify attachments Delete instances Download tasks for users Download information about processes and a lot more  The full document ation in the swagger form is available at: [Portal_address]/api and in the version with SharePoint at: [Portal_address]/webconbps

(...) Applies to version: 2024 R1; authors: Przemysław Sierant, Krystyna Gawryał   Related document ation A detailed description of the functionalities mentioned herein and their configuration can be found in the following sections of the WEBCON Help: Widgets Dashboards   Description of the functionality From version 2020 R1 of WEBCON BPS we have the possibility to embed Po (...)

(...) process will appear on the screen. The only difference compared to the standard process is the Instance number, which is its GUID by default. This option is available only in dictionary processes and document template processes.     After entering the process name and completing the remaining information, click OK to create a new dictionary process. After creating the dictionary (...)

(...) t a HTTP method, if creating a new user set it to POST:     Next step is transferring the user object in JSON format, form field list of the user workflow is available in Graph document ation.     If you want to transfer response data to the BPS instance a Response tab configuration is also required. When invoking Graph, value loading will fail if the JSON (...)

(...)   Below you can see the form view in the described „Acceptance” step.     The task was assigned to all users in the Approvers group. After accepting the document by one of them, it stays in the same step, waiting for the second approver to complete the task. The form will display a different icon next to the name of the user who completed the task:   (...)

(...) the instance’s history) Number and type of actions used in the system (e-mails, changing field values, launching subworkflows) Average size and number of attachments per workflow instance (document scans, docx, pdf, tiff, xlsx) As an example, we will use a form made up of 20 form fields (all of them are required): 3x Choice field (1x dropdown, 1x autocomplete, 1x SharePoint Picker) (...)

(...) It is used to search for all elements such as: those returned in the “Search application” and “Search in navigation” search windows instances created in WEBCON BPS document s attached to the workflows You can search for document s by the content of the document or attachment without worrying that you do not know the instance’s signature or the attachment’ (...)