search results

(...) Item list is a form field displayed as a table with definable columns that contain user’s data. This form field can be edited to the extent provided by the system: users can change the column values as well as add, delete, and clone individual rows. It is also possible to independently configure the Item List columns and their parameters, including width. This article is devoted to this very (...)

(...) involves a number of operations that can potentially change the state of data available in the database. Depending on the moment of triggering an action or automation they can refer to different data values . What is equally important, the on-path transaction can involve three different automations, i.e. “On exit”, “On path”, and “On entry”.  The &ldquo (...)

(...) instance, its workflow, and operations performed on it by users. Unless an appropriate visibility restriction rule has been defined, History also displays the names of all form fields along with the values entered for them, even if the user has set these fields as invisible in the Field matrix.   Note: History does not include information on form fields from the Data presentation group and s (...)

(...) ess is archived, the parent behaves as if it never had a child. It is worth to mention here the types of data that do not undergo archiving. Those essentially include all dynamic content, such as values in “Data table”, “Data row”, “Chart”, or “HTML” form fields. Additionally, archiving does not include custom controls, as well as form and business rul (...)

(...) ictionary) database and its update. Since SOLAR database is non-relational, text indexes are built from the database instances, so it is possible to find quickly dictionary instances by entering text values . All operations that update instances in such a database are executed by a service. It is also used in searching for navigation instances in the left, upper corner of the Portal and reports in applic (...)

(...) other LDAP filters are given in Table 2 later in this article. You have also the option to specify exactly which columns will be returned from AD. To do this, check the boxes next to the preferred values in the Columns returned from Active Directory section.   In addition, to add a non-default column with an attribute value from Active Directory, click on the plus icon located on the b (...)

(...) y is started (in the discussed example it is the “Incoming correspondence” document)  You also need to select a path the uses to register the document. “Additional form field values ” – here you can assign e-mail data to respective workflow form fields, e.g. e-mail sender or title. Full list of available variables can be found in the context-sensitive help (fig. 8). (...)

(...) for which company is started (in the discussed example it is the “Cost invoice” document) You also need to select a path the uses to register the document. “Additional form field values ” – here you can assign e-mail data to respective workflow form fields, e.g. e-mail sender or title. Full list of available variables can be found in the context-sensitive help (fig. 8). (...)

(...) arcode in the .pdf file. In the discussed example it is the “Agreement” workflow document. You also need to select a path the uses to register the document. “Additional form field values ” – here you can assign e-mail data to respective workflow form fields, e.g. e-mail sender or title. Full list of available variables can be found in the context-sensitive help (fig. 9). (...)

(...) the “Request data” tab   The “JSON - grid” option can now be selected from the drop-down menu in the “Request body” tab. This option allows users to map values to be sent. Enter the name of the mapped value in the “Name” column and specify the form field containing the value in the “Source field” column. Configuration of the & (...)

(...) e HTML code in the header section should contain column names. Code: {SUBELEMHEADERTEMPLATE:GUID} {/SUBELEMHEADERTEMPLATE} Row The code of the row section must include tags referring to values of individual columns. The tags for particular columns are to be found in the HTML template generated in the Portal using the admin action. Code: {SUBELEMROWTEMPLATE:GUID} {/SUBELEMROWTEMPLATE} (...)

(...) e. prepares the application for production deployment. In other words, developers extend the project by configuring actions, rules, form field visibility and requiredness settings, as well as default values and data sources for it, so as to turn it into a fully working application.   Fig. 3. Configuration of "Check if there is an attachment" action in WEBCON BPS Designer Studio (...)

(...) Applies to version: 2022 R4 and above; author: Łukasz Maciaszkiewicz   Introduction In WEBCON BPS system applications, processing values entered by end users in forms is a fundamental function, alongside data gathering and analysis. The system offers several solutions to quickly and easily define arithmetic operations on values entered in form fields. This article provides examples on how (...)

(...) tive tasks People involved, i.e. users who completed at least one tasks on their own and whose tasks are not canceled Average task duration (applies only to completed tasks).   If no values are available for any of the parameters, the parameter will be grayed out and the information no data will be displayed for it. By default, global business administrator will see in the report the (...)

(...) sing the BPS_ID, the rule obtains data on all members of a group (this also includes members belonging to any eventual subgroups nested within the group). The user list is returned as a collection of values , i.e. ID#Name, separated with a semicolon. To use the rule, check the Business Rule checkbox (step edition → the “Paths” tab → the “Task creation” tab → the (...)

(...) a WEBCON BPS workflow The option runs a workflow (defined by a user in the Change requests workflow field) for registering external requests based on change requests. Additionally, the Form field values mapping field enables user to specify which change request information (e.g. title, ID, description) is to be transferred to the workflow form fields. As a result, a part of the form fields will be f (...)

(...) switch Docker Desktop to support Windows-type containers.   Before starting the service container, complete the service_env.dist configuration file. This file allows you to set the relevant values for environment variables and pass them to the service container. These are exactly the same values that can be set using the appsettings.json file in a standard WEBCON BPS installation. For the (...)

(...) corresponding to the technical field you created in Part One and populated in Part Two. It should be formatted as ISO (which is the default). You can find that token in the Expression editor’s values tab. {loopback_path}, {failure_path}, {success_path}, and {no_subworkflows_path} represent the paths leading away from this step. You can get their tokens from the Expression editor’s Object (...)

(...) ted Send email and Send a custom email actions. If first action is used, a standard email is sent to all users with an active task on the instance, containing information about the current form field values and selected system data. The second action offers more advanced configuration settings, including the use of a pre-designed message template, as well as the specification of Direct, CC, and BCC Reci (...)

(...) . q448 Set the label width (in dots). Q151,28 Set the form length. The first parameter (151) defines the label width, the second (28) defines the length of gaps between labels. values expressed in dots. N Clear image buffer. P1 Print image buffer.   If your print result is not satisfying, you can try to modify the speed, density, label width, label (...)