(...) 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 (...)
(...) 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). (...)