(...) Applies to version: 2017.1.x and above; author: Krzysztof Gaszczyk WEBCON BPS is a great tool to create and use constant values. There are two types of constant s: Global and Process. This article presents configuration and practical use of both of them. Global constant – this constant is visible across the whole system. It is frequently used when the value is present in many processes an (...)
(...) where low-code has identical challenges as code, one of those issues is Magic Numbers. This post is rather for beginners, those starting their WEBCON journey. It focuses on the importance of using constant s instead of typing numbers directly in filters, rules, and queries. This leads to easier maintenance and helps with understanding what some pieces of configuration do faster. If you want to learn (...)
(...) Hi, I use process level constant s when I need to generate MS Word attachments. This gives me consistency when transferring processes between DEV / TEST / PROD. I don't have to think about replacing the name /DOCTEMP/f8e86bc...e967af9b62 with another guid in appropriate action. The same I wanted to do for generating MS Excel attachments. Unfortunately I get the error: WebCon.WorkFlow.Common.Exceptions.Wor (...)
(...) on farms (DEV/TEST/PROD) with the same application (6 servers in total). Our deployment chain is from Farm1 (DEV), which is the application source to all other servers. We have defined a global constant for Portal Url, which is used in whole application (for redirects and so on). This scenario works fine on one farm. Is it possible to find out within a businessrule (or maybe SDK rule), which (...)
(...) Hello folks, We have used constant s which contain SQL queries for calculated report collumns a couple of times already, so this does work. But i now have a query which works perfectly when added into the calculated collumn directly, but no longer works when stored in a constant . (img attached) Through logs we found that he has a problem seemingly with strings, but we found no way to baypass that. (...)
(...) Hi, I'm finally taking the time to add this user voice. I think it was in BPS 2020 or 2021 where the option was added that a constant in a business rule would be displayed in the format Group:constant (1). Right clicking on the name of the constant would show a context menu with all constant s in this group (2). This was similar to the one which is displayed if you right click on the choose field to s (...)
Error: [Quote] Error occured during business rule evaluation. String values cannot be multiplied at: Evaluation requested at: Evaluation node: Operator (+) at: Evaluation node: Operator (*) at: Evaluation node: Operator (*) [/Quote] What I have : -process static A -process static B -process static C -process static D attribte a,b,c attribute a,b,c is changing dynamically vs It
constant s - add info is always treated as TEXT or add option to set type of constant s https://docs.webcon.com/docs/2024R1/Studio/Process/Process_Variables#konfiguracja-sta%C5%82ej
(...) Hi, We try a REST Web service call like this: - global constant for REST Web service base URL, as https://something.com - global constant for REST request suffix, like api/webcon/action - other global constant s, for Bearer etc - at app level we configure a template - Invoke REST Web service based on previous defined constant s We use those global constant s just to have separate value se (...)
(...) Is it possible to use process constant in js mode, same way as we would use it in form rule ?
(...) urrently reaching max # of Choose fields in my process. Trying to avoid future troubles I'm adding new workflows in a new process, and this leads to massive amount of duplicates of: business rules, constant s, automations (fortunately not form rules). Let's say i have a business rule which contains some users call it 'Manager Role' - inside of the app, there are many manager roles, but lets make it si (...)
(...) Hi, is it possible to change dynamically every year the date in a constant , so that I won't have to change it manually? Thanks in advance for your informations. Monica
(...) Hi, unfortunatelly global "objects" (business rules, form rules, constant s, automations) have no app binding functionality as data sources have. Some global constant s, business or form rules and automations may contain critical data (e.g. api tokens) that should not be useable by all devs with studio access. An option to set an object as protected and enabling an app binding to allow the usage would (...)
(...) alization, remember that the column names of the returned query are the same as the column names of the item list. Static initialization is a good solution where the data to be loaded is known and constant . If you need to load data dynamically, select the SQL setting and properly create a query, and the data source (optionally). Loading the data source other than default one takes time when loading the (...)
(...) , you should use the instance ID that contains a group of tasks (Instance number). Fig. 5. Process contant - Maximum number of tasks per person A good practice is to use constant s in processes – they allow for wide parametrization and also protects you against the need to change the parameter value in all places where it is used. Next, configure the “Queue or a (...)
(...) Dictionary to store information about car fleet – the dictionary stores data such as brand, model, car description and their status (active/inactive. The set of data on individual cars is constant , and the need to add or deactivate the car takes place several times a year. The completed dictionary looks like this: Fig. 2. The dictionary storing information about car fleet & (...)
(...) Fig. 6. Integration key The integration key is used in every action that calls Autenti REST API so it is the best to save them in a safe but accessible place – e.g. in the process constant s. For more information about storing data in WEBCON BPS Designer Studio see: Global constant s and rules. In the next section let’s configure the selection of the attachment that has to (...)
(...) n API Settings – enter the integration key assigned to a given AdobeSign account. This key is required in the configuration of all actions in this plugin, so it is a good idea to define it as a constant in the process. Attachment selection – indicate: The method of attachment selection -> based on the attachment’s category or SQL query The technical form fields to which the (...)
(...) In the “DocuSign API settings” section, enter the DocuSign account parameters that allow the use of APIs. This data is necessary for all SDK actions so you can enter them as constant s in the process. In the “Attachment section”, define the method of attachment selection (by Category or SQL query) and technical form fields to which the ID of the signed documen (...)
(...) name to change. The column names referring to the form field values are analogical to the names of these form fields on the form – this increases the readability of the preview The view is constant ly updated by the system, always provides a preview of the current configuration b) The V InlineBUsinessRUlesUsages view This view contains information about using business rules. It (...)