General

From version 2020.1.3.321 there is the ability of defining additional http headers returned in responses from the web server. This functionality can be used e.g. to increase the level of security of WEBCON BPS Portal. This is especially important when BPS Portal is publicly available on the Internet. To define headers, go to WEBCON BPS Designer Studio -> System settings -> Global parameters. The presented example is only the presentation of the possibilities of the new WEBCON BPS functionality. The configuration is not a model for the used configuration – it should be adjusted individually to the needs and recommendations of administrators.

Apart from standard options for adding users to the system, such as synchronization with AD or/and AAD, WEBCON BPS allows you to manually add a user. All users added in this way can log in to the system via BPS Auth., be granted privileges, and can be assigned tasks in the system. To save time, you can use the ability of adding more users from an Excel file. To add users, prepare an Excel file based on the defined template. This template can be downloaded from WEBCON BPS Designer Studio – go to the System settings tab -> BPS users list and click the Download template button. The system will download the Excel file with the defined columns in user data that should be entered.

Every installation of WEBCON BPS is unique, and may face certain challenges not covered here. Therefore, this document should be treated a general set of guidelines and not universal dogma. The scenario presented here was tested and used to deSharePointize our Support Portal http://support. webcon.com.

SSL Offloading (SSL Termination) is the process that allows you to transfer the encryption and decryption of the SSL connection through Reverse Proxy Server that is located “in front of” the application server. It is mainly used to relieve Web Server from performing these costly operations for the processor. To enable the correct operation of the SSL Offloading process with WEBCON BPS, add an additional parameter to the configuration file of WEBCON BPS. You can find this file in the standard location - „C:Program Files (x86)WEBCONWEBCON BPS Portal” or through IIS by selecting Server -> Sites -> WEBCONBPS -> Explore.

Working with attachments is one of the basic functionalities in WEBCON BPS. Some processes such as document repository are only used to catalog and make files available to selected users. In others, the attachments may be of secondary importance. For example, when you want to work on a file together with your client, a good solution may be the integration of WEBCON BPS with file storage such as One Drive or Google Drive. It allows you to avoid situations where you have several different versions of the same document because the changes made by you and by the client are not merged. The standard action available in WEBCON BPS allows integration with many external software providers such as Google Drive. You can use it to transfer files or maintain an active access token.

The instance number is a unique string of characters in the system (e.g. EXP/2020/09/00002) that uniquely identifies each workflow instance, and it is created when the instance is first saved. This number will always refer to the same instance and there is no option to change them, even by administrators. A properly configured structure of the instance number facilitates searching for instances (without knowing their ID number) and viewing reports. This article describes the methods of configuration the instance number and the advantages of defining appropriate signatures. Instance numbers can be defined on two different levels – workflows or form types, however only one of them will be set by the system (if both are defined at the same time, the instance will be assigned the number defined in the form type).

The article describes the functionality of inheriting the global form settings and form field definition in WEBCON BPS. Global template inheritance – this setting the order of form fields according to the process tree. This means that the order of the form fields in the group and columns on the item list configured in the process correspond to their location on the global form template. Breaking form settings inheritance is most often used to change the settings of the form fields’ order on steps or item list settings. However, if you decide to overwrite the form field settings – it is a good practice to describe it in the form field documentation.

This article is an extension of Translation of WEBCON BPS Portal user interface content and contains more information about language configuration in WEBCON BPS Designer Studio such as system language setting, mass notification language setting (since BPS 2020.1.3 version), application language setting and notification language setting for new users (since BPS 2020.1.3) version. WEBCON BPS allows you to both force one system language and select the language by a user. Both approaches have pros and cons that need to be considered before deciding which solution to use. On the one hand, we can impose a standard that will create a fully uniform environment, on the other hand, we can translate each application independently, adapting to the needs of end-users.

The following article is an extension of the Lunchtime article – see: Lunchtime application. The “Lunchtime” application has been enhanced with dictionary processes that allow you to pay for meals with money previously paid into your personal account. Extending the “Lunchtime” app with the pre-paid function is a good solution for people who want to avoid paying for the delivered food every time. It is also a great convenience for the person who manages such a workflow. The pre-paid solution can also be applied to other workflows in the company. Wherever there is an employee’s account and some form of regular deposits – the traditional way of paying can be replaced with a pre-paid.

Since the introduction of WEBCON BPS Portal, sometimes on the form or on Portal itself , it was possible to observe pop-ups that inform about the error and their identifier. But they very often did not give enough information, even after clicking the button to show details from the event preview. From version 2020.1.3.277, the error description from the event log has been made available in Designer Studio, which contains much more information to help find the cause more efficiently.