search results

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 cha

Applies to version: 2020.1.x and above; author: Franciszek Sakławski   In WEBCON BPS 2020 a new functionality of reporting archived instances has been added. In the report configuration of WEBCON BPS Portal and BPS internal view type source, the option to indicate an archived database as a source for the report has been added. Information about the archiving mechanism can be fou

(...) rities – stores information on user privileges to archived elements.   Service role The creation of archive database itself is not enough to ensure correct operation of the archiving action . To be able to process the archive queue correctly the service needs to be assigned an additional role in its configuration. To do that, go to “System settings” and check the “Workf (...)

Applies to version: 2022.1.x and above; author: Łukasz Maciaszkiewicz Introduction WEBCON BPS uses services to run special operations that generally do not require user interaction. Unlike Portal, which acts as a host for a website, the service can have multiple roles performing calculations and executing long operations defined previously by a user. This article describes the roles the

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 instances. 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 quickl

(...) archived instances. It is a problem as we have readonly permissions granted based on instance attribute. (use case: Incoming invoice visibility for users depends on invoice types.) Proposal: in archiving action it would be nice to have a parameter to control permission inheritance. What do you think about it? Thanks!