search results

(...) ponent installation This step displays the list of components that will be changed. If you are installing components that were not previously present, you will be asked to specify the installation path for them. After clicking the "Next" button, the installation of components in a newer version will begin. When updating the WEBCON BPS Search Server component, the installer may ask (...)

(...) TE functions. Both of these functions take the OAuth2 Authentication form field as a parameter. To ensure that the user does not forget to log in, it is possible to embed the following code in the path parameters. With this procedure, the user is prompted to log in while going through the path . Fig. 7. Example of using the IS AUTHENTICATED and AUTHENTICATE functions   Another inte (...)

(...) UI of WEBCON BPS 2025 requires changes to my user improvements. I have focused on the ones which I'm using the most and I hope those are also those, which others use. Breadcrumb Colorize path s Missing comment handler Modal dialog Uniform save experience If you have no idea what these are, you can watch this updated video:   The issue which occurred in the video w (...)

(...) their identity based on an additional authorization operation This article describes Access Authorization to a form field. The configuration of the authorization methods themselves is shared with path transition authorization. Access authorization is in many ways a continuation of that feature. The terminology and approach are carried over.   Configuration and operation principles Th (...)

(...) the content database from which to retrieve the attachment data $attachmentDbName – name of the database where the attachment files are stored (attachment or content database) $tempFolderpath – location of the technical folder for temporary files (will be removed after the script execution) $zipFilepath – the full path , including the name of the ZIP archive where the result (...)

(...) yed in the report are assigned to the current user, in addition, some of them have flags. Fig. 4. Flagged and postponed instances visible in the report   The user can open the quick path menu by selecting one or more instances from the report, and click the appropriate option to flag the selected workflow instances.   My tasks In the My Tasks section, it is possible to (...)

(...) BCON BPS SMS notifications | WEBCON BPS   Introduction SMS notifications in WEBCON BPS are one of the methods for additional authentication of user operations, e.g. when authorizing path transition or access to confidential form data. This article provides instructions on how to configure an SMS gateway that allows sending short text messages with authorization codes from the system. (...)

(...) e a new site. Right-clicking Sites displays the option to add a new site. You can give your site any name you like. It is important to correctly point to the created application pool and the physical path where the Public Forms mechanism was extracted. Proper addressing configuration in the Binding tab is also crucial.   Fig. 6. Example configuration of a created site   Comm (...)

(...) SDK Migration Deactivate standard push notifications Process license instead of single solution license Create new custom themes Verify updated item list actions Type error when executing a path Instance start buttons Empty report tiles REST and business rules   Updating to BPS 2023 Calculated columns for Choose fields New database field Breaking change d (...)

(...) Translating multilingual fields In Portal, it is now possible to use AI to translate individual text fields related to process configuration elements, such as the names of form fields, steps, and path s in the Process design, as well as the names of reports, their columns and views, and the names of dashboards and their widgets. This means that you can use the functionality for all fields marked wi (...)

(...) o consoloe if (isDebug) { obj = JSON.parse(sessionStorage.getItem('WebconBPS_FormIsDirty')); console.log(obj); } Then simply add this form rule to all places (style and behavior in fields, path s, ...) where you expect triggers which could lead to the"unsaved data alert.

(...) udes two defined actions: sending a document to Autenti, sending a request to return the document along with the status. The Timer mechanism is also employed to automatically trigger the path responsible for checking the document's signature status in Autenti every hour.   Business case For demonstration purposes, a simplified document workflow will be used, consisting o (...)

(...) ion of a new AD user. The form on the first step requires entering the details of the person for whom the account is to be created:   The Manage users action is triggered on the Create path . The configuration of this action is shown in the screenshot below:   In the Select operation section, it is possible to choose the operation mode, i.e., user edition, creation, or (...)

(...) sage: “The wait operation timed out”, and the automation will be rolled back. A simple scenario to reproduce this behavior involves placing the Change value of single field action on a path transition, where an SQL COMMAND rule executes for longer than 30 seconds. For testing purposes, the WAITFOR DELAY command can be used, as shown in the screenshot below.   Fig. 1. Conf (...)

(...)  to set the structure in the value mapping. Now do the mapping as follows: Workflow The final step is to configure the workflow in the Workflow Designer. The Start button has a default path "Calculate" in Wizzard Mode assigned to the current user leading to the start button again and the automation is added: path automation The configuration of the path 's action (...)

(...) robably have run into a timeout. While you may have come up with a similar solution  Define a single sourth of truth to identify the next batch of elements Process the elements on the path to a flow control This will use a for each with collection type 'data source'. Yes, I don't use an item list. Check if every element was processed If this is not the case, move the (...)

(...) ueries using the WITH clause are no longer supported, as they are blocked and may lead to errors in some environments. It is now possible to select intermediate nodes (e.g., teams), even when using path -based configurations.   Equivalence of both configuration methods Currently, both configuration methods — using either ParentID or path s — function in a similar way. In bo (...)

(...) button from being incorrectly displayed in later steps, which may lead to faulty behavior.   #{FLD:10523}#  =  Picture field: [Picture (max. 5000 KB)] #{PH:2526}#  =  path : [HIDDEN: Save Picture after JS downscaling] <script src="https://unpkg.com/pica@8.0.0/dist/pica.min.js"> // https://app.unpkg.com/pica@8.0.0/files/LICENSE // MIT License // Copyright ( (...)

(...) . A graphical representation of the process is shown in the screenshot below:   After attaching the invoice to the form, the user proceeds along the "Extract invoice data" path , where automation consisting of several actions is triggered:   A key component is the "Extract invoice data" action (action type: Change value of single field). Its configur (...)

(...) ite an extensive documentation of the public links function, reading about it and personal experience is something different.  For example, edit privileges don't necessarily show the path buttons. You can find my notes about it in this post.