search results

(...) l life cycle of an application in a company – from prototyping in WEBCON BPS Designer Desk, through development in WEBCON BPS Designer Studio, to using the final version after deployment in the prod uction environment.   How it works – business case Application prototype in WEBCON BPS Designer Desk Person responsible for the implementation of a new process in an enterprise (...)

(...) here exist any common approaches / tools / patterns for transferring workflow data between different environments. We have an on-premise environment for DEV (with internal AD) and an environment for prod (which resides in Azure VM and connects to Azure AD). What are your experiences to sync data, e.g. from prod to DEV or TEST between different environments (different ADs) and is there even an easy (...)

How does one go about creating separate environments for different purposes

(...) like some query actions. But is there an official listing of what is not allowed in SaaS? Because Building and Testing a project on-premise, and having no way of knowing if something will break on prod because of that is not acceptable. Is there a way to test for it? Or at least have something to read through to workaround this from the start(dev), and not when it is deployed on live... Best (...)

(...) In our attempt to move to the cloud I need to update our webcon database to the latest version that supports GCC. I do not want to install this on prod and we don't have a proper dev env setup for this (Yet). To get the db upgraded, I am trying to migrate our existing prod WebCon instance, data and all to a new dev host (basically making a 1:1 prod :dev environment). Is there a "supported" metho (...)

(...) s combined from the process name and the process ID. The process ID is of course always different in the three different environments. This means that after each transport from the Dev/Test to the prod environment, the attributes, tables or view names of the SQL queries affected must be changed to suit the respective environment. ((Otherwise, an SQL query will not work at all, or worse, incorrect d (...)

(...) We have two attachment databases, one for testing and one for prod uction: BPS_Content_Att_test BPS_Content_Att_test2 BPS_Content_Att BPS_Content_Att2 In this application we use BPS_Content_Att_test2 for testing and BPS_Content_Att2 for prod uction. Unfortunately we don’t have a database with identical name, so when we import from test to prod uction, the default attachment database specified (...)

(...) Is there any way to compare the prod uction and Test environments? To compare the configurations of the same process between systems? In order to track changes. Do you have any SQL, etc.? Do you use github or something else?

(...) Hi I'm looking for steps or best practices how to do it correctly - restore db prod on test env ?

(...) ropriate path:   Fig. 6. The rule configured in the "Queue or assign" step   The condition checks if the number of all tasks in the selected group is less than the prod uct of the number of employees in this group and the process constant, that means the maximum number of simultaneous tasks for an employee. If so, the task is assigned to one of the employees of this (...)

(...) you to set the cell style, as well as special display functions.   Business case An example that presents the advanced functionality of reports coloring is the process of listing stored prod ucts (e.g. bicycle models). Each workflow instance represents a warehouse with the serial numbers of its prod ucts. The warehouse can be closed (e.g. when it is full) preventing the insertion and remov (...)

(...) cond reason is to allow the configuring person to test the system and verify the content of all the e-mail notifications. On development and test environments, this mode usually remains on even after prod uction starts.   How to enable the deployment mode? The simple process of reporting expenses has been created.   Fig. 1. The Expense report workflow   After reg (...)

(...) form for the above instance (Fig. 4) – Infiniti registered car.   Fig. 6. The SQL query – storing data about the instance   In this SQL query the “Year of prod uction” and “Fuel type” form field values are saved in the “ID#Name” format – also known as the “BPS format”, it is the combination of the value’s (...)

(...) in the footer. The footer content should be added by clicking on each column separately. An example configuration and the result after generating the Word file:     DEV/TEST/prod behavior There are cases when you want to e.g. include an URL address in the template. A highly recommended way to create a template is to use the configuration compatible with DEV/TEST/prod envir (...)

(...) names. The default value is set by providing an ID to correctly save the name translations. ID is stored in a process constant which allows you to enter the different values depending on the DEV-TEST-prod environment, and use them in other places in the process configuration.   Fig. 8. The default value of the “Invoice type” form field   Invoice number & (...)

(...) will be updated at the same time. We do this for improving application performance and preventing situations in which too many actions or operations (at the same time) will cause a timeout. In the prod uction environment you must assess  what quantity of instances can be reasonably updated at the same time. You should take into account the number of actions on the path, possible integrations wi (...)

(...) lel by many people (or teams) there is often a need for two types of processes to coexist within one environment – supported by the export/import mechanism and those implemented directly in the prod uction environment. In this situation we cannot block the environment from editing. To ensure consistency and make it more difficult to unintentionally modify the process imported into prod uction e (...)

(...) Applies to version: 2019.1.4.x and above; author: Wacław Stawiarski   WEBCON BPS 2019 is our first prod uct that can operate without SharePoint in what we call a Standalone version. In the year 2019 the Standalone version was gradually improved with mechanisms emulating/replacing functionalities of the full installation – especially those regarding the operations of the SharePoint f (...)

(...) at Studio has access to the SQL server. To allow it, open the TCP port (by default it’s port 1433). When Designer Studio establishes a connection with the SQL server, it checks the available prod uct licenses. In order to connect with the license service, open the appropriate port (by default it’s TCP 8002). The server name has to be solvable by Designer Studio. If the provided elements (...)

(...) to change the default WEBCON logo and the looks of the menu:   to the brand new look:     Summary Theme created on one of the environments: developer, test or prod uction can be easily copied across all the other thanks to import and export functions.   Choosing “Export” will generate a .json file.   After copying the file t (...)