search results

(...) ON BPS system, and indicates modules linked with particular roles and presented in the “Running modules” report. Process databases Process databases are content databases that store instance s of the processes created in the WEBCON BPS system. The majority of the service roles operate within the framework of such databases. When performing a role, a service processes the data included in (...)

(...) WEBCON BPS User CAL – the user may access all processes and applications built in WEBCON BPS (as long as they have the necessary privileges). This access involves the ability to create new instance s, edit and save them, move them to other steps via paths, and browse reports and applications. Through this license, a specific number of users (determined by the number of licenses) will be able t (...)

(...) Portal window, the content of the entered information/message is saved, and a header appears above it, stating its author and date of entry.   Fig. 2. Information saved in the workflow instance   Once the entered information is saved, editing it is no longer possible. Even if you redirect the task in the workflow to its author, the user cannot modify their entry. The user is left (...)

(...) g a button is analogous to adding a new automation:   After adding the button, configuring automation and visibility, the newly created button will appear in the menu when the workflow instance is in edit mode.   If you need to configure many automations, and thus add multiple Menu buttons, a drop-down list called User actions containing all user-defined buttons is automatica (...)

(...) not recommended to use this type of source as a dictionary for the Dropdown list.   As previously mentioned, an appropriate form has been prepared for the process. One of the workflow instance fields is a Choice field named “Participant”  fed with the newly configured data source “Most current user profiles”‚, set as a Popup search window ƒ:   The Ad (...)

(...) ased on barcodes in attachments” A workflow named “Agreement” is created where a .pdf document containing an agreement is generated. The document includes a barcode of a workflow instance in which it was created. Once a client sends an e-mail containing such an agreement, its scan along with client’s signatures is added to a workflow instance of such an agreement. Each .pdf atta (...)

(...) S is to exchange written information between system users and perform related tasks, such as reading, updating or modifying data on a form. Documentation in the workflow consists not only of workflow instance s and filled out forms, but also files with various extensions (e.g. .docx, .txt, .xls, .pptx, .pdf, .png.) added to the instance as attachments. This article describes how to present and group fil (...)

(...) ThisStep" rule This rule verifies whether an attachment is added on a particular step. The verification is executed by means of an SQL query that checks whether an attachment is added to an instance after defined time (date and time). A business rule with a conditional clause The rule is used to check an attachment is added on a particular step. An SQL query used in the rule (...)

(...) d in the "Internal control" process privilege section:   Fig. 7. After the import, the "Management Board" group again has access and edit privileges to all workflow instance s   Checking the list of BPS groups in Portal, you can see that the "Management Board" group is available again:   Fig. 8. The imported BPS group is visible in Port (...)

(...) ged by the end user in any way. A set of rules defined by the administrator is in such case applicable not only to the content of the form, but also to all system elements, e.g. actions, starting new instance s, etc. On the other hand, form rules generally form more flexible framework and give end user more freedom. The rules, which apply only to the form, potentially enable experienced end users with s (...)

(...) node is an expanded version of the previously available Insights node. The change affected not only the node’s name, but also its contents – as before, users will find Suggested workflow instance s here, as well as information about possible Anomalies. However, a brand-new Analytics option has been added here, together with a subnode called Overview. Altered side menu structure in Porta (...)

(...) ion appear to be insufficient, it is necessary to involve external experts, especially when a project or a task is non-recurrent and hiring a permanent expert is economically infeasible. To share instance s and tasks safely and conveniently, the WEBCON BPS platform is provided with the public link functionality. It allows users to share instance s or tasks quickly and seamlessly with individuals holding (...)

(...) roups, the names of group members who executed the task are presented below the group name. What is more, it is worth noting that once the task is executed, the group members can still display the instance in the read-only mode. However, it will not be available to users who left the group and, conversely, a person who joins the group after the task is executed is able to display the abovementioned ins (...)

(...) ditionally four non-editable fields below. The Related application field is automatically populated with the name of the application for which the change request is registered. A specific application instance under which a change request was registered can be accessed by clicking a link available in the Application element link field. This link can be copied and sent. The remaining two fields contain chan (...)

(...) , segments of the workflow, or the entire workflow.   In addition to configurable indicators, some standard ones were also built into the regular form (e.g. form filing time and total instance duration).   Indicators are licensed based on WEBCON Advanced Analytics Framework   Interface Changes Display elements related to performance indicators have been added to nu (...)

(...) orm all the installation steps on the same computer. By following the steps described herein, WEBCON BPS can be installed in containers on any other containerization platform (e.g. Azure Container instance s or Azure Kubernates Service).   Installation plan When installing WEBCON BPS in containers, only the database is created using the installer. Other components of the system must be dow (...)

(...) account business data stored in the database, while blocking access to tables storing strictly technical and configuration information. The bps_user is allowed to read from tables storing data of instance s and dictionaries, information about attachments, tasks, companies, currency exchange rates, translations. They can also read parts of tables that store configurations of applications, processes, wor (...)

(...) g with service and is sent to all content databases according to a configured interval (10 s by default) to determine which queues can execute tasks. As the query relates to all databases, it returns instance s available for processing in all queues from all databases. Then, the master queue informs respective queue threads (with tasks to execute) that queries assigning queue rows directly to a thread of a (...)

(...) on Email notifications in WEBCON BPS are handled via dedicated Send email and Send a custom email actions. If first action is used, a standard email is sent to all users with an active task on the instance , containing information about the current form field values and selected system data. The second action offers more advanced configuration settings, including the use of a pre-designed message templa (...)

(...) Applies to version: 2019.1.x and above; authors: Wojciech Mleczko, Krystyna Gawryał   Introduction WEBCON BPS supports barcodes as a method of identifying documents and workflow instance s. Using barcodes allows to automate the process of scanning and registering paper documents. Stickers with barcodes simplify archiving documents, and based on barcode labels it is possible to quickly find t (...)