(...) received” and can be caused e.g. changing the columns defined in the configuration of the action. The default error message does not indicate value that was unavailable. To avoid this, add validation before executing the action that checks the availability of each value downloaded by the query. Fig. 4. The validation checking the available values The process of delegatio (...)
(...) lled in, there is no option to move the instance to the next step. Item list (with Item list columns)– this form field is visible and required. If the item list is required to meet the validation requirements, at least one line must be added to the item list before moving to the next step. If the item list column is required, this column will be checked only when there is at least one row on (...)
(...) Applies to version 2020.1.3; author: Konrad Wojtycza One of the basic functions of WEBCON BPS forms is validating if the fields are completed correctly. This article describes the validation mechanism. The example workflow In the example “Purchase order” workflow, all validation actions were configured on the “Register” path. Fig. 1. (...)
(...) , you must create a connection to the existing SharePoint collection. Connections to SharePoint Online and On-Premises versions from SharePoint 2013 to 2019 are supported. Fig.1 validation of connection with SharePoint After starting the "Data Sources" module in Designer Studio, expand the Connections tree and go to "Connections to SharePoint" and t (...)
(...) iterion for selection of columns – define the method of assigning columns from the file to columns in the item list (headers or column’s letter) c) Import type: Stop importing on validation error - stops all import when an error is found Skip invalid rows - skips rows with errors Import invalid cells as blank - in case of an error, data import is performed and invalid (...)
(...) In the advanced configuration of the item list, uncheck the “Allow delete” option - instead of deleting rows we will mark them as inactive. On the Register path, you should add the form validation action to check the uniqueness of the instance. If the “Role” form field has been added, then in the system should be only one workflow instance with a list for an employee and one with a (...)
(...) orkflow -> Designer). On the left, there are two tabs: Steps – the stages of the workflow Actions – events executed when documents travel between steps of the workflow e.g. validation of entered data, file generation, sending notifications. You can define additional conditions for each action. Fig. 5. Workflow designer Each created project contains two default steps & (...)
(...) user can validate its correctness. Fig. 9 Overwriting an attachment with the version signed in the virtual directory Fig. 10 Digitally signed document and signature validation status Now the user can exit the external PDF editor and return to the form which now needs to be refreshed to see the changes. After doing this, you can see that the version of the atta (...)
(...) 2019.1.x and above; author: Łukasz Kraśniak Introduction Regular expressions – REGEX in short – allow to precisely describe complicated search patterns. One of many examples can be validation of provided bank account number. Whether the pattern fits the character string is mainly used during validation of so-called entry data. Regular expressions allow to check if the user data has cor (...)
(...) and optional information that will help you to add configuration components, such as: Form field Step Transition path Report BPS group Action – general Action – form validation Action – e-mail notification Hardcopy template Privileges Glossary of basic terms Below you can find a collection of basic terms used for describing WEBCON BPS environme (...)
(...) interrupt processing of the remaining elements. When elements are processed, a browser window should stay open. an error message will be displayed in the summary. In case of an action validation , the user sees the message that has been entered in the configuration of said action. By preview Quick paths are available in the preview on the right-hand side of th (...)
(...) ed document, i.a.: creation of document in the system uploading file containing document for signature checking document status sending e-mail with link for document signature two-stage validation with SMS service With the above options you can establish the following communication: Figure 1. Workflow diagram The process will include 3 defined actions: sending do (...)
(...) ctions, conditions or subrule calls, they will not be executed. The following is an example of incorrect use of the CONFIRM operator in a form rule containing a double condition. [Main PKD code validation ] is a subrule that checks whether the bidder’s main PKD code is one of the codes required in the tender procedure. [PKD code validation ] is a subrule that checks whether any of the PKD code (...)
(...) do is click on the cogwheel icon in the top right corner of the step. Fig. 11. Preview of the automation defined on the "Completing documentation" step, which includes the form validation action The Properties window also opens after selecting the workflow path. As with the form field, the user can view its Advanced settings. The Path details window is then displayed, div (...)
(...) on for path transitions in subworkflows (None). However, if the user wants to configure a separate authorization for a subpath transition, they should select periodic authorization (Require). validation will then take place, and the subpath transition will succeed only if periodic or each-time authorization (Always require) is configured also for the path in the parent workflow and that session is s (...)
(...) allowed to be uploaded. As there are other file extensions allowed in further processes, we can not only limit the extensions globally. To enforce this requirement, we first configured a validation rule, which basically did the trick. However, from a user experience perspective, it would be great if the open file dialogue would only show pdf's: How is it done: Add a Html-Field t (...)
(...) users to add tags for categorizing resources. However, in this scenario, this operation is not required and can be skipped – click the Next : Review + Create > button to proceed to the data validation window. After verifying the data, a confirmation message is displayed, and the workspace can then be created. To do this, click the Create button located in the upper-right corner – the workspa (...)
(...) e) occurs Immediately after a step is entered, and next timers are executed at a specified Interval. Another important change was the extension of the configuration associated with the handling of validation /execution errors of timer-related actions. Two additional parameters have been introduced: Acceptable number of consecutive errors (defines the number of consecutive erroneous timer executions that w (...)
(...) uments. These include: creating a document in the system, uploading the document file for signature, checking the document status, sending a document signature link via email, two-stage validation using SMS service. These functionalities enable the following communication scheme (workflow): Fig. 1. Workflow diagram The process includes two defined actions: sendin (...)
(...) as source. Otherwise WEBCON will never get a successfull connection to PSU. This article describes all steps to create a small running demo that gets two summands and returns their sum with basic validation , error/exception handling and a running sceleton for new use cases without running in all deadlocks, as I have been in the beginnings with PSU. Creating a new REST API endpoint in PowerShell Unive (...)