Knowledge Base

The Invoke of PowerShell action doesn't support return of parameters and that's why a workaround needs to be used. Invoke of REST web services supports input and output parameters and that's where PowerShell Universal brings the magix. This nice software enables one to create endpoints for PowerShell scripts. This article describes a working example for the whole setup.

Do you need to provide documents to external parties for a given process? Then you should take a look at this one-click solution to generate a .zip.

A (short) list of No-Go's and recommendations for new WEBCON BPS power users.

This article provides an overview of the various types of timeouts in WEBCON BPS, illustrated through practical examples. It covers timeouts in automations, service operations, HTTP requests, and T-SQL transactions. The article also distinguishes between configurable timeouts and those imposed by the system’s infrastructure.

We designed an application in which the initial situation had to be documented using up to eight images (each up to 5 MB in size). We couldn't reduce the image sizes, as we needed the ability to zoom in on details in case of damage assessments.

To prevent these images from unnecessarily taking up space in the workflow history, we came up with the idea of transferring them to the attachments section instead. Since no further processing was required - the images were purely for documentation - this was a suitable solution. The file names of the images could be derived from the values stored in the picture field.

Tutorial to disable the alert:
"You are leaving the form with unsaved data. All unsaved data entered on the form will be lost. Do you wish to continue?"
This may be needed in special use cases where no instances shall be created and respective no data needs to be saved.

This article describes how to design dashboards using the new design grid, efficiently add and configure widgets, and organize the dashboard space in a functional and aesthetic way.

The WEBCON BPS system is natively integrated with the Active Directory (AD) service. Basic functionality of WEBCON BPS includes actions that allow managing AD resources directly from workflows. This article covers actions that enable the management of users and groups.

This article provides a detailed guide to integrating WEBCON BPS with Autenti. It outlines the document signing process and demonstrates the configuration of a sample workflow, which includes sending a document for signature and retrieving the signed version.

Integration of different systems has become a key element for the effective operation of an organization. WEBCON BPS has been providing advanced capabilities in this regard for years through its standard, public REST API. However, in response to the need for more flexible and faster to deploy integrations, we have provided User Defined API – functionality that allows users to define their own dedicated REST API endpoints in the context of a specific application and process. This allows external systems to easily communicate with WEBCON BPS.