search results

(...) rdquo; represents the displayed name. The first part, “ID”, represents a unique value. It is the element most frequently used in SQL queries designed to filter results displayed in picker fields populated with values from a specific data source. Such filtering is often employed to exclude irrelevant information, presenting only what is of interest to the user in forms, reports, picker fields (...)

(...) to use the platform, detailed descriptions of the functionalities and options available in the system with examples of their use, configuration information, as well as easily accessible lists of form fields , actions, functions, and rules that are or may be needed when creating applications. The online help document is also a perfect solution for those who are just starting their adventure with WEBCON (...)

(...) ersion 2023 R3 introduced the ability to use the CONCAT function within the LIKE function to create advanced filter conditions on Data sources. This is particularly applicable when configuring Choice fields , allowing the list of returned values to be limited to those required by the user. This article provides a description of the functionality along with a business case for its use.   Bas (...)

(...) licking the Scan QR code button (available in the Edit connections window and quick menu after logging into Portal) and by pressing the QR code icon available in applicable elements of the form (form fields ) and Portal (search box). After directing the camera towards the code, the scanner automatically recognizes the code and processes the encoded value appropriately. Searching by QR codes Us (...)

(...) guished by the triangle brackets) is meant to act as a filter on top of the list of synchronized users - used to filter away unneeded accounts.   In Person or group form fields , it is now possible to select a data source and configure a filter on the side of the form field (just like it is possible with the Choice field). So as to not manually create data sources fo (...)

(...) nistrator. This means that, quite literally, they have a broader view. With access to the full configuration of Designer Studio at the global and application levels, they can see buttons, options, or fields that are either invisible or inactive for citizen developers with Application administrator privileges. Furthermore, among other things, they have the ability to manage data sources created by other (...)

(...) nd 2D codes Determining exact device location Biometric authorization WebView WEBCON BPS Portal Scanning barcodes and 2D codes and inputting informationstored in them into form fields Recording voice memos Determining approximate location Capturing photos and adding them as attachments Browser Authentication   Mobile application architectu (...)

(...) een them) The applications interact with each other. For instance, a workflow in one starts a sub-workflow in another process, which in turn updates the first one. The applications include choice fields , which are used to connect other workflows/display data from them using BPS internal views. READ MORE: HERE

(...) style="text-align: left; padding-right: 10px;"> <p>[|Recipients|]</p> <p>[|Systemfields |]</p> <p>[|Formfields |]</p> </td> </t (...)

(...) heir performance, leading to increased productivity and customer satisfaction. In short, gamification is an effective technique to foster positive behaviors and achieve specific objectives in various fields . The simplest method to implement a gamification system would be the collection of points (XP) when certain activities are met in WEBCON BPS processes. One of the processes frequently u (...)

(...) or most users, more complex JSON structures, e.g. with one-to-many relations, will be a challenging task. So we decided to add a JSON-builder, that generates the structure based on the form fields . It is quite simple, but it also groups fields to its nearest grouping element (group, tab). Also, item lists, data tables, and data rows are supported. For most scenarios, this should be sufficient. (...)

(...) s, should we need to return to them.   E-mail contents We can strictly control what is sent in e-mails (standard and custom). There is an interesting option in the configuration of form fields : Never show in e-mail notifications. It’s worth noting that technical fields also won’t be included in e-mails. In the template configuration on a process, and in the action that s (...)

(...) nd suggestions, as well as keyboard-based sorting of results.   Fig. 6. Mouse-free navigation through the global search page On the form, users will be able to navigate editable input fields , Menu buttons, and select Paths in a similar manner. It will also be possible to set focus on the Info panel, Attachments and Comments sections and their respective elements.   Fig. 7. N (...)

(...) form an authentication operation. Select the API definition in the upper right corner of the screen. In the Account section, select Try it out and fill in the grant_type, client-id, and client_secret fields with data from the API application configured earlier in Portal. Copy the generated token. Set the API beta definition and click Authorize. Enter “Bearer” in the Value field and then th (...)

(...) mation on potential follow-up recruitment. Accordingly, a form based on the 70/30 template was prepared in the "Supplementing information" step, which includes selected data presentation fields .   Fig. 6. Form configuration in the “Supplementing information” step   In WEBCON BPS Portal, the form is structured as follows:   Fig. 7. Example of (...)

(...) are Widgets? In the context of a form, a Widget is a form field that presents numerical data defined by the user in an appealing way. It belongs to the Data presentation group and, like other form fields in this group, operates in the read-only mode, meaning it is not possible to edit its value at the form level. What sets it apart from other form fields is its appearance; the values are presented in (...)

(...) pective of the Head of the Department, it does not seem necessary to include them all. Therefore, leave only the [System] Instance number and [System] Step columns, and proceed to adding process form fields . In the described examples, these will include: “Requesting person”, “Defective product”, “Client”, and “Product value”.     Pl (...)

(...) checkbox has been selected in the prototype path configuration in Designer Desk), actions, Choice field (regardless of its behavior, i.e. Dropdown, Popup search window, or Autocomplete), or form fields that belong to the Data presentation group, business rules, data sources (except Fixed values list).   Summary The functionality of creating a list of tasks for execution can prov (...)

(...) ld, it still works and it can help others: If you are providing multilingual user interfaces this post can provide you with little helpers to generate SQL statements: For multilingual choose fields . Multilingual icons   If you aren’t interested in these then you can still take a look at the SQL command stubs: Get workflow data Get item list data Join workflo (...)

(...) s the time to fiddle around with the css. You can read up on it in this post: Revised changing left/right layout This is the revised version because the version in 2021 didn't use HTML fields as they haven't been available.