search results

(...) y, and security updates. Extended support includes only security updates.   End of support (also sometimes known as end of life) indicates that a product has reached the end of its lifeCycle , and servicing and support are no longer available for the product.   Due to the technological differences between WEBCON BPS 2021 and newer versions (e.g. how they integrate with MS Shar (...)

(...) ll 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 products (e.g. biCycle models). Each workflow instance represents a warehouse with the serial numbers of its products. The warehouse can be closed (e.g. when it is full) preventing the insertion and removal of products fro (...)

(...) nt will be rejected Document ID field name – the technical field containing an external document ID Execution time – the maximum time of the action execution In this example, the Cycle is executed once every 4 hours. In each Cycle the action checks the status of all documents included in the “Waiting for signature” step and, if their status has changed – moves the (...)

(...) res the involvement of specific employees or groups. The degree of involvement can vary from person to person – from one action and access to some resources to participate in the entire process Cycle and insight into each instance. WEBCON BPS allows you to map these conditions by using the privileges mechanism. For more information about privileges, see Tasks vs privileges. The WEBCON (...)

(...) ble situation is setting the currently logged in user as a person who recently modified the workflow instance, because such a person has the privilege to read the instance value throughout their life Cycle . Then the option of overwriting the user who modified the instance can be used. After checking this option the person entered in the “Editing user” field will have read access to the new (...)

(...) nnection diagram between processes   Let’s create the queue mechanism in such a way, that the cyclical action takes only those instances that haven’t been moved in the previous Cycle . For this purpose, we need to add a new form field – a simple checkbox technical field which will store information on whether the expense has been moved or not. By default we set it to “ (...)

(...) n of action buttons from the top menu WFActionBusinessRules - information about the configuration of business rules used in the action configuration WFTimeoutActions – it links actions with Cycle s in which these actions are executed   f) Configuration tables related to the setting of the “Configuration” section   Fig. 8. Configuration tables related to (...)

(...) do this, go to the Tools for application management and select the Search Server configuration tab:     After saving the changes, restart the WebCon BPS WorkFlow Service and reCycle the WEBCON BPS application pool.

(...) changes. These small changes can be tracked via our changelog (available at the bottom of this page), which compiles a list of all modifications made to a ‘big’ version over its lifeCycle . Our latest ‘big’ version is 2020.1 – [Whitepaper – Business overview]  Important: Before upgrading from one complete version to another (eg from 201 (...)

(...) changes. These small changes can be tracked via our changelog (available at the bottom of this page), which compiles a list of all modifications made to a ‘big’ version over its lifeCycle . Our latest ‘big’ version is 2020.1 – [Whitepaper – Business overview]  Important: Before upgrading from one complete version to another (eg from 201 (...)

(...) tatus” column is modified by a person from the “Financial administrator” field, who in the “Payment status” column indicates if the payment has been made at each billing Cycle . If a client has not paid on time, they move the instance to the “Administration” step where the subscription administrator can suspend or cancel the subscription. At this step, the admin (...)

(...) be also transferred with the use of other methods, e.g., in the form of Web service. The dictionary data is delivered from the SAP system via a web service or SQL tables according to some predefined Cycle (e.g. once per 24h, at night). This solution has some weaknesses, but sometimes the priority is to ease the load on system resources. In the case of a query for one value from the source data, p (...)

(...) Portal needs to be restarted will appear again.     In order to apply the changes, open the IIS manager in the application pools, select "WEBCONBPS" and click "ReCycle ".     Change of the authentication provider via WEBCON BPS installer  Changing the authentication provider using the installer is a fallback option in case you ac (...)

(...) icrosoft documentation   Recycling   Application pool setting. By default, recycling is set as a fixed interval of 1740 minutes. Such setting  triggers  a periodic ReCycle of the pool application during users' operation, and as a consequence, a stop of  the Portal process. The recommended setting is to set out a fixed ReCycle time for the application pool. Sta (...)

(...) Local parameters and additional context variables – many action implementations relied on technical fields, whose purpose was to store or ‘hold on’ to a value that can then be reCycle d into other actions. While technical fields can still be used for actions, automations offer an alternative: Local parameters. These parameters can be set just like technical fields (e.g. Change valu (...)

(...) er).  Requirements towards the Customer and the Integrator Below you can find some enquiries related to the system and requirements pertained to the breakdown to the respective project lifeCycle s. Sales Cycle requirements Key questions to the Customer’s ERP: What systems will be integrated with WEBCON (ERP, HR, etc.)? What integration solution method with external systems (...)

(...) returning the data to undergo archiving. The first, result column should return the ID of the instances to be archived. The query is executed within the default database. When an action is used in a Cycle , it is not possible to use the constants operating within the context of an instance. Additionally, in the case of large amount of data it is recommended to set up the SQL query to return data in sev (...)

(...) ch a solution guarantees uninterrupted system operation, also in the event of a failure. Note here that the failover procedure configuration does not support cyclical dependencies, i.e. if there is a Cycle set up in the service take-over schedule, the system does not detect it and does not hand over the roles in the event of a service failure. The “Services of which roles will be taken ove (...)

(...) ses, often without being able to view their configuration data. The present article describes the new feature from the point of view of such a business user. The following will cover the full 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 production e (...)

(...) t small changes. These small changes can be tracked via our changelog (available at the bottom of this page), which compiles a list of all modifications made to a major version over its lifeCycle . Our latest major release is 2025.1 – [Whitepaper – Business overview]  WEBCON provides full technical support for our two latest major versions. (...)