search results

(...) ns thereof. Despite indicating several columns (Fig. 4), in the drop-down list only the “Season of the year” column will be displayed (Fig. 5). By activating “Query data source if variable s return empty values” checkbox one can decide whether to set an Empty element display name – placeholder text introduced in this field will be displayed when no value is selected. By act (...)

(...) ossible to end the main automation flow prematurely (with an appropriate error message and error code) if the defined conditions are not met.   Local parameters and additional context variable s – many action implementations relied on technical fields, whose purpose was to store or ‘hold on’ to a value that can then be recycled into other actions. While technical fields ca (...)

(...) ions are available: basic and advanced. By applying the basic edit mode, the system administrator can manage the content of an e-mail notification and layout of e-mail notification contents, by using variable s, such as: e-mail notification header, language of the e-mail notification header, task details etc. A company logo and colour of the e-mail notification header the system administrator will be able (...)

(...) possible to define a business rule that will return any collection.   For Data Source and Attachments collections, the collection values are in a separate group in the Values list in the variable Editor.   Fig. 3. Collection columns for data sources and attachments   After expanding the symbol of three dots and selecting the Properties option, the user can add a (...)

(...) plates in MS Word that include data from forms designed in WEBCON BPS. A template prepared in this way can be used, for example, in a Word file generation action. In order to be able to use variable s relating to form fields and other contextual variable s of WENCON BPS, an add-in for MS Word is required. This article describes the process of downloading and installing the Word Modern add-in, w (...)

(...) ophes. The “{SFD:315}” refers to the “Price” column defined earlier for the item list and can be replaced with any column with numerical values. It is also possible to use the variable s editor on the right to edit the query and insert respective values.   SQL expression editor.     Click “OK” button and press “Save & publish p (...)

(...) he new column and enter an SQL formula that returns a text value in the form of month names. In the present case, this will be the Month name (User language) column.   #{USERLAN}# is a variable that will keep the month display names matching the user interface language.   Check the defined calculated column so that it is available in the default view:     a (...)

(...) anatory, choose the License type and the User Identifier. For example, we can store the BPS ID in a technical form field after adding the user to the AD, then pass it forward to this action as a variable . If it is a Single-Solution Access License, we also need to specify the process to which the license is assigned (an additional tab appears as seen in the image below).   Configura (...)

(...) workflow. Here, you can append e-mail content to the workflow as an “.eml” file. It is also possible to define a template specifying which files are additionally downloaded. The available variable s can be previewed in the context-sensitive help. Fig. 5. Context-sensitive help for the “Additional attachments filter” field   There are no additional files downloade (...)

(...) workflow. Here, you can append e-mail content to the workflow as an “.eml” file. It is also possible to define a template specifying which files are additionally downloaded. The available variable s can be previewed in the context-sensitive help. Fig. 5. Context-sensitive help for the “Additional attachments filter” field   There are no additional files downloaded (...)

(...) workflow. Here, you can append e-mail content to the workflow as an “.eml” file. It is also possible to define a template specifying which files are additionally downloaded. The available variable s can be previewed in the context-sensitive help. Fig. 5. Context-sensitive help for the “Additional attachments filter” field   There are no additional files downloade (...)

(...) ase: calculating the cost of insurance policy In this example, the application is used by an insurance company to calculate the cost of insuring a car belonging to a requesting person. A number of variable s specified in individual form fields is taken into consideration when calculating the cost of insurance policy. The final price is displayed in the “Cost of insurance” form field after en (...)

(...) ty to insert the “Share” button directly in the form. Other modification is the appearance of new business rules. The aforementioned configuration elements are discussed below. Context variable s Once you check the public link functionality, the business rule editor is expanded with new context variable s. The Is instance shared? variable is added to the “Information” group in (...)

(...) st will be opened by clicking the All submitted change requests button in the user panel. It is important to remember that in the custom handling mode it is possible to create a link using context variable s relating to the change request, such as change request ID, title, date of registration, etc. The change request window with the “Active - custom handling” option selected   (...)

(...) s finished. This means that in graphical controls on the form and Dashboards that present performance indicators will not display this value until it finishes calculating. There are additional variable s in the editor to aid in this rule calculation: Indicator start date – date and time (according to the database time) of the Start performance indicator action execution. Start value &n (...)

(...) dash; the image based on which the container is run; choose the version corresponding to the WEBCON BPS version, --env-file solr_env.dist – the Solr container will be run with the environment variable s defined in this file. Currently, this is only a limitation on the RAM used. It is possible to configure additional variable s, --mount source=solr-bps,target=/var/solr – mapping the created v (...)

(...) x code. Again, select Barcode from the left menu, place it at the desired location on the label. In the window that appears, configure barcode data as {DBCODE}{WFD_ID} (it is important to include the variable referencing the database acronym  {DBCODE}):   Define the barcode type by selecting Data Matrix in the Barcode tab. As with the previous code, define its size by specifying t (...)

(...) he transition path, configure an action searching the dictionaries and saving results to the Item list. An example is shown below:   In the advanced mode, it is possible to compare the variable s found in the ‘column ID’ and ‘Searched data’ configuration fields. This is important when analyzing how the ID’s of fields in which results are saved are transferred &n (...)

(...) entifier. The calculated columns names differ from the picker field columns only by the added “_ID” suffix, i.e. “WFD_AttChoose1_ID”. By using its name (or a corresponding variable in the variable s editor in Designer Studio), the column can then be used in an SQL query to retrieve the data specified in it. The SQL query referring to the indexed choice column and used for (...)

(...) arent workflow path but is enabled in the subworkflow path, sharing the location data will be required. Furthermore, user location data at the time of path traversal can be collected using context variable s. Those variable s are available in the Location node of the expression editor. There are four such variable s available: – {CURRENT_LOCATION} – information about geographical longitude (...)