Applies to version 2020.1.x, author: Anna Puka Introduction Digitally signing attachments ensures the integrity and authenticity of approved documents and improves the entire approval process. This is especially important now when more and more businesses are choosing to allow remote work and have little time to implement a paperless office model. The standard WEBCON BPS fu
Applies to version: 2020.1.x and above; author: Michał Kastelik Introduction The SharePoint Framework extensions are client-side components that work in the context of a SharePoint page. They can be implemented in a SharePoint Online environment and you can use JavaScript tools and libraries to create them. This article presents the methods for starting WEBCON BPS workflows
(...) (in the "Description" field) and tick the box next to "Export as a template." If you do so, the process will be exported as a template. Every time you import a template to the target environment , a new (separate) process definition is created. It happens even if this process was previously imported and already existed in the environment. If you do not check the box "Export as a templ (...)
(...) efined outside the process (the process uses a data source, but the source is defined in the system configuration, not in the process configuration) can be safely modified after importing it into the target environment . This means that when creating a process on the DEV environment that uses an external data source, it is not necessary to know the address of this source in all environments (TEST and PROD). Configur (...)
(...) rs between DEV/TEST/PROD environments. In other words – if BPS Portal presentation layer elements will be created or modified within the application, they can be automatically moved to the target environment together with processes and applications. Application export Exporting is done in the same manner as before – by right-clicking on an application or a process (which is a part of an (...)
(...) less an appropriate approach is taken. This issue concerns changes in global elements and non-standard operation of the system when they are exported from the original environment and imported to the target environment . The present article describes this less common approach that should be used in order to successfully transfer updated global elements of a process. Global elements and their changes (...)
(...) group, more specifically, its Owner. As previously mentioned, some data is not imported, i.e. Group members are omitted during migration. However, you can create the missing elements manually on the target environment . After successfully importing the application, the tool informs about adding a BPS group: Fig. 6. Import report informing about adding a BPS group Note: transferring (...)
(...) accessed in a .txt file. Fig. 5. Information on successful application import in the CMD Import history Apart from being able to use the new/updated application on the target environment , users can now additionally check the details of an automated import that has been performed. As with the standard wizard-based import, all relevant information and logs are available in the Import h (...)
Applies to version: 2024 R1 and above; author: Konrad Keppert 1. Introduction Upgrading to a newer version is inevitable for any WEBCON BPS environment due to the acquisition of new functionalities, bug fixes, and security patches. It is therefore in the interest of the system administrator to become familiar with the capabilities of the WEBCON BPS installer and to master the procedure for
(...) e imported global automation configuration contains an Invoke REST Web service action that required a connection to an external environment to be defined. If such a connection is not available on the target environment , it must be reconfigured so that the import of the automation configuration can continue and the action will work properly later. The current step displays a table with a lis (...)
Applies to version: 2025 R2 and above; author: Jacek Język Introduction WEBCON BPS is a comprehensive platform for business process automation, within which there may be a need to isolate a specific application for a particular group of users. This is where the Application Hub functionality comes in — a mechanism that allows any WEBCON BPS application to be made available und
(...) dure The procedure assumes that one of the environments (hereafter referred to as the source environment) will be migrated into another, already operating environment (hereafter referred to as the target environment ). 1. Updating both WEBCON BPS environments to the same version All WEBCON BPS databases must have exactly the same version (down to the build number) in order to function correctly wi (...)
(...) e a development environment in house which we use to prepare application templates (products) which we transport to multiple customer environments and every time we do so the business entities in the target environment are overwritten when the business entity ID exists in both environments. Is there any possibility to prevent this form happening?
Hello Community, We have problems with the different runtime environments of the WBCON Workflow Service (under .NET Framework) and the WEBCON BPS Portal (under .NET Core) and System.Data.ODBC. I have developed an SDK plugin that integrates the NuGet package System.Data.ODBC to access ODBC data sources. The target runtime environment of the plugin package is .NET Standard 2.0, so that the