(...) 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 (...)
(...) ocess Link – leads to workflow instance (if the search result belongs to the dictionary based on a WEBCON BPS process) Field name – displays the Form field names in which the searched values were found (in this case name and surname) Value – displays the values which matched the searched keywords Dictionary – displays the name of the personal data dictionary in which the (...)
(...) tion shows how to have the workflow whichever one of two paths receives a majority (> 50%) of votes, with a tie going to whichever path has been set to be the default: The path ID values can be obtained from the Object browser tree as shown above, or by the rules editor’s autocomplete feature as shown below: While not explicitly necessary, you may well wish to (...)
(...) reamline data searching and make queries more efficient, the WEBCON BPS platform introduced indexed choice columns. Databases in WEBCON BPS In the WEBCON BPS platform the picker field values entered in the form are saved in the database table WFElements in columns whose names begin with “WFD_AttChoose(…)”. For example, in the screenshot below, you can see a Choice fiel (...)
(...) 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. Basic definitions and functional assumpti (...)
(...) ers and their translations: "#", "$$", "|;". Rating scale In the case of this form field, questions and the descriptions of the minimum and maximum scale values can be translated. This is visible after switching to the advanced configuration of the form field in Designer Studio – Translations icons are now available next to the listed elements: (...)
(...) eading the value stored in the code. Inserting the value stored in the QR code into a form field or column The mobile application also enables scanning QR codes and entering their values directly into form fields. The functionality is available for devices equipped with a camera. To be able to retrieve value from a QR code, you need to configure an applicable form field or col (...)
(...) identify any case, the ELSE case will be used. SWITCH Operator Value assigned to case Each case may be associated with a value. The result of the condition will be compared with these values (from left to right). If a match is found, the matching case will be used. If the result doesn’t match any case, the ELSE case will be used. For example, the Current user variable re (...)
(...) e users and groups shown across the system. The main purpose of this is to: Exclude certain accounts synchronized to the WEBCON BPS users cache (e.g. test accounts, guest accounts). Limit the values available in Person or group fields (e.g. according to an attribute like location or position). The default filter is IS ACTIVE – which returns active accounts (COS_IsActive=1). (...)
(...) l e-mails sent by the system will be redirected to the dedicated mailbox (without spamming our users with e-mails from the test environment). Make sure any global and process constants have correct values . Make sure data source connections have correct values . Analyze whether any of your deployed applications have any connection or reference to the production database. Once all this is d (...)
(...) u how Playwright could be useful. Changes: Tab support Collapsed group support Provide step id instead of the title to verify it Define whether a field should be required Check field values without setting them If you are interested in this or other things you could ask me them during my next Ask Me Anything YouTube live event on 14th May. If you want to know more you can either h (...)
(...) iginal Webcon picker would be nice) The type of JSON can be Standard or Custom Standard: Uses the JSON-builder Custom: Use your custom JSON Define your custom JSON. You can use field values the way you are used to. Name of the root element Only needed, when the root of the JSON structure is an array of elements Mode: you can choose between Create and Overwrite If (...)
(...) Applies to version: 2023 R3 and above; author: Krystyna Gawryał Introduction In WEBCON BPS, it is now possible to perform automated operations on the rows, columns, and values of the Item list. Previously, these operations were executed using the Change item list values action, with the final result determined by the mode chosen by the configurator. However, version 2023 R3 introduced s (...)
(...) , and the length of the session that is made available via public link. Of course, System defaults will be used by default, if we switch this to User defined we will be able to fully control these values to adhere to our security policies and good practices. Cookies expire after 14 days by default, and Sliding expiration resets the expiration time for a valid authentication cookie if a request (...)
(...) to complex. Once the script is created, the columns from the SQL output are mapped to the itemlist to ensure accurate data transfer. Alternatively, static initialization involves specifying the exact values with which the itemlist should be populated each time. By choosing the appropriate initialization mode and data population method, you can tailor the itemlist to effectively support your workflow. (...)
(...) on import via API To initiate a default application import, use the CMD command prompt to open the BatchImportApp console application. Then, enter all the required parameters with their respective values . The order of the parameters in the command is arbitrary. Fig. 4. Example of a command for the default import of an application Successful application import is indicated by (...)
(...) 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 a visually appealing format intended to draw the user's attention. The combination of the aforementioned visual format and the ability to present data against other values makes (...)