Home / Knowledge Base

In WEBCON BPS the individual 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. Tasks in the system can be assigned to the specific users, defined at the level of a specific workflow. However, when the company structure changes, then it will be necessary to make additional changes in the workflow configuration in WEBCON BPS Designer Studio.

WEBCON BPS allows you to start workflows in several ways. In addition to a manual start by the user, instances can also be launched by the system using dedicated actions. The "Start a subworkflow" action allows you to start a workflow within the same application. By using them you can start only one workflow instance – in this case it will be creating an additional task in the Design process. The "Start a subworkflow (SQL) action allows you to start a workflow instance(s) within the same BPS application and differs from the previous with its “Data” tab, and in that it is not possible to save and store the IDs of started workflow instances in form fields.

One of the methods to start a bpm workflow in WEBCON BPS is to use REST API BPS. It can be especially useful in situations such as:

1) Data exchange between different WEBCON BPS instances – e.g., there is an internal application for your organization and a public application available for your clients.
2) Data exchange with external systems e.g., CRM, ERP.

To give you an idea of how you can use it, let us show you how the REST API can be used to start a workflow in the design process.

There are situations in which, after going through a path, you will need to go back to one of the previous steps of the workflow e.g. when the form has been incorrectly completed or you forgot to add an attachment to the instance. The article describes two basic configuration methods: Moving back an instance to the defined step and Moving back an instance to the previous step using the “Back to the previous step” predefined option. Using using more advanced types of configuration e.g. using the system step where, on the appropriate condition, the instance moves back to the defined step – you can create intricate combinations specifically tailored to your scenario.

Setting up default values in form fields is one of the most basic and easy things that we can do to facilitate and improve the user experience of working with forms in the WEBCON BPS system. The following article describes the various methods used to configure the default values and examples of use. There are a lot methods for setting the default values of form fields and each of them has its use in different scenarios. However, its is important to remember that the configuration under the hood should also be kept as simple and efficient as possible, so that it is easier to reconfigure in the future and so that it does not negatively impact loading times.

WEBCON BPS allows us to manage our company and streamline the assignment of tasks by design workflows. A workflow is a sequence of steps that an instance of the workflow must complete in order to fulfill its business goal. Such a workflow facilitates and optimizes work by clearly specifying the order in which steps must be completed and who they must be completed by. In Designer Studio, a workflow consists of steps and transition paths connecting individual steps.

If the organization uses the single-on with ADFS and we want the authentication process in the WEBCON BPS application to be “transparent/invisible?” for users or we want to make the application available to users outside the domain – there is an option to register WEBCON BPS Portal in ADFS and enable such authentication. The user has the ability of selecting the method of authentication. If the Azure Active Directory and WEBCON BPS Auth authentication providers are activated in WEBCON BPS, additional buttons will appear here.

WEBCON BPS applications can be made available in several different languages. Users who use Portal and can select one of them – currently six languages are available: Polish (pl-PL), English (en-US), German (de-DE), French (fr-FR), Italian (it-IT), Russian (ru-RU). There is also the ability to create own translation for language which is not available on the list by using WEBCON BPS Translator at https://bpstranslator.webcon.com. With this method, you can turn off any number of languages and leave only the ones you want your users to select.

In WEBCON BPS 2020, a new method of creating translations for data values in picker fields has been added. To simplify the process of translation, you can use data source columns. To create a data source for translation, you can use the functionality of dictionary processes. First create a Dictionary Process from the wizard in Designer Studio. By default, the dictionary process has only three form fields – let’s add additional fields for storing various translations: Name PL, Name EN, Name DE.

In WEBCON BPS 2020, it is now possible to display form field in groups horizontally. The group with horizontal arrangement can contain a maximum of three fields. This option is available only in the MODERN form. To be able to horizontally display the form fields in groups, go to the group configuration and check the “Horizontal arrangement of form fields in group” option. After checking this option, the fields in groups with up to 3 form fields will be displayed horizontally. If you add another form field into the group – the view will automatically change to vertical.