search results

(...) BPS can be used as an efficient document management system. This article describes how to use barcodes to scan PDF files and paper documents and have them automatically added to your WEBCON workflows ' instances.  Common business scenarios for using barcodes include: Having a PDF document or a paper document and scanning its barcode to relate it with an existing workflow ins (...)

(...) Applies to version: 2020.1.x and above; author: Franciszek Sakławski   Introduction When designing the processes and individual workflows in WEBCON BPS, it is good to know how the data is stored in the tables, what are the relations between them and how individual information is displayed on the form. This article describes the Calendars table.   Table description (...)

(...) Applies to version: 2020.1.x and above; author: Wojciech Kołodziej   Introduction When building business processes in WEBCON BPS and designing workflows – big or small – you may find that you need to pass information between two workflows . One of the simplest ways to pass information from the current form to one in another workflow is by using the Hyperlink action. Hyperlinks (...)

(...) 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 B (...)

(...) you can check the date and time of granting the privileges and refresh information about them.   Form privileges in the workflow To grant the privileges for the individual forms in the workflows , select the specific workflow on the “Associated form types” tab. If the workflow uses from several types of forms, you can grant the privileges for each type separately.   (...)

(...) ) SQL table structures.   Limit tables   Global form fields The limit of global form fields applies to the entire system configuration. Regardless of the number of processes, workflows and their form fields, there can be only as many global fields as specified in the table below:   Global field type Maximum amount Date field 5 (...)

(...) 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 with (...)

(...) “move back” paths is used, then have execution conditions on other actions return “False” if the value of that technical field is “1”. Cancellation of related subworkflows Additional integration actions. If integration is used in the workflow (e.g. SAP entry, update, cancellation)

(...) Applies to version: 2020.1.x and above; author: Dawid Golonka     Introduction In WEBCON BPS you can create simple workflows consisting of several steps and form fields, but you can also use the subworkflows mechanism. The following article describes the action connected to subworkflows – “Update related workflow instance”. This action allows you to change the v (...)

(...) Applies to version: 2020.1.x and above; author: Franciszek Sakławski   Introduction WEBCON BPS allows us to manage our company and streamline the assignment of tasks by designing workflows . A workflow is a sequence of steps that an instance of the workflow must complete to fulfill its business goal. Such a workflow facilitates and optimizes work by clearly specifying the order in which s (...)

(...) figuration 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 – the task is assigned only to the users (...)

(...) the ABBYY FineReader 11 component. FineReader is a program for converting scanned documents 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, creating a folder called “ABBYY” in the WEBCON BPS installation folder is necessary.     (...)

(...) took into account the changes made to it (according to Figure 6).   Summary Changing the users in the group (AD, SharePoint, or BPS) does not require additional changes in the workflow/workflows configuration compared to assigning tasks to the specific users. You need to remember that all changes in groups will affect new instances/task assignments but they will not modify the tasks that are (...)

(...) Applies to version: 2020.1.x and above; author: Paweł Drab   When creating large and complex processes, problems with workflows becoming too complicated can often appear, which can be problematic especially for end-users. To check if our process requires reconstruction and simplification, we recommend making an audit of such workflow.   Why should we do a workflow audit? A wor (...)

(...) Applies to version: 2020.1.x; author: Marcin Wiktor   Introduction For applications with a large number of interconnected workflows there is often a problem with performance these applications due to creating/moving multiple workflow instances at the same time. The speed of creating/updating sub-workflows depends on many factors such as the type of the form, the amount of data/actions/ru (...)

(...) s. We can transfer any number of attachments in this way. We also have the ability to copy image files (e.g. screenshots) by using the system clipboard. This functionality can be used in workflows where the user is required to attach some sort of screenshot (e.g. in support processes).   How do you add any image to the workflow instance? After copying the image to the system clip (...)

(...) Content of the documentation Each documentation generated in Designer Studio consists of the following elements: Basic information (process name, version, author, modification date, etc.) workflows and form types in the process Basic process configuration (which includes information about business entity, substitutions and implemented GDPR solutions) Workflow graphic presentation For (...)

(...) ) Number of steps in given workflow (every path transition is recorded in 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): (...)

(...) e application elements is as follows:   Native part: Profiles, logins and PIN security support Main panel of the application Navigating by report views Searching Starting new workflows Application, processes and instances lists preview Log history Searching instances by barcodes/2D codes (only iOS) PUSH notifications (only iOS) Webview Authentication Forms of t (...)

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