(...) umber of processes, workflows and their form fields, there can be only as many global fields as specified in the table below: Global field type Maximum amount date field 5 Text field 10 Picker field 10 Form fields The following table presents the limits of a single process. The number of workflows in (...)
(...) red document. This means that while most invoices have a similar pattern, the location of the fields on the document may differ. An invoice from one contractor may have a tax identification number or date of issue given elsewhere than an invoice from another contractor. However, the program assumes that incoming invoices from the same contractor will be built according to the same scheme. Therefore, i (...)
(...) ldquo;Always to” field or a dynamic selection can be set based on the form field or the item list column (the action is executed only on the first login, the others are skipped). Substitution date – enter the start and end date of the substitution. The date can be selected from the calendar or can be entered manually. Advanced options – the configuration of the action can be (...)
(...) alse” if the value of that technical field is “1”. Cancellation of related subworkflows Additional integration actions. If integration is used in the workflow (e.g. SAP entry, update , cancellation)
(...) escribes the different methods to set the default value by using a simple cost invoice form. Fig. 6. An example of form with the default values Created by and Created date – this form fields are set with default values. “Created by” is currently log in user and “Create date ” is current date . The default value is filled in even though (...)
(...) Applies to version: 2020.1.x and above; author: Filip Jawień Update 2021.2 This option was once limited to 3 form fields, that is no longer the case. You can experiment with any number of fields. Introduction In WEBCON BPS 2020, it is now possible to display form field in groups horizontally. The group with horizontal arrangement can contain a maximum of three fields. This option (...)
(...) ed “ABBYY” folder in the WEBCON BPS installation folder. Then, launch the WEBCON BPS installer – if the software is already installed, select the “Update or expand an existing WEBCON BPS installation”. If the WEBCON BPS is not installed, select the “New installation of WEBCON BPS”. In the “Component selection” step in the (...)
(...) add users) Moving to the previously created instance, you can see that the tasks assigned at the “Implementation” step remained unchanged. At this step, a user completes the date and sends the instance for verification. According to the presented workflow, the user at the “Verification” step has the ability to approve changes which causes completing the workflo (...)
(...) ore advanced analysis. a) Filter – you can choose which instances will be checked Above ID – only instances with WFD_ID higher than the specified one will be selected date from/date to – only instances processed in the specified workflow will be analyzed All – all instances created in the specified workflow will be checked b) Disp (...)
(...) you to quickly find important information in your processes. The Suggested report shows instances that can be the most important for the user. These instances are designated based on the date of the last modification and the modifying person. In the report we find all instances which have been assigned to the user and have been modified by the user. The shorter time since the last modific (...)
(...) translations for one of the supported languages. User defining the process in WEBCON Designer Studio can translate for example: form field names (in the example above date , Owner, Contractor, Signature), path names (Register), application names (My company), application abbreviation names (AG), process names (Agreement), form type names (Agreement), workflo (...)
(...) figuration will work as intended, but it may provide us with several problems. This mechanism is quite complicated and difficult to maintain. If we want to make any changes, it will be necessary to update the workflow. For example, if you want to add a reverse path to the Front office, adding extra steps will be necessary to assign a task to the appropriate group. For the sake of simplicity, we can (...)
(...) ackground by the WEBCON BPS service. Some time may pass between entering a value into the system by the user (via saving some data on the form) and creating a new index in the SOLR database for the update d workflow instance. It depends on: server load and the number of instances in the queue – the more instances must be processed, the more time it will take to update the last instance in the que (...)
(...) sub-workflows depends on many factors such as the type of the form, the amount of data/actions/rules, the speed of response from external sources, server load or overall performance. When trying to update tens of sub-workflows the maximum execution time (timeout) may be exceeded. The case below shows us how can we deal with this problem by using only the standard WEBCON BPS functionalities. You ca (...)
(...) ach dictionary process, a predefined data source returning all dictionary elements is automatically created. The structure of the source contains all form fields defined in the process and is update d whenever the configuration of the dictionary process is changed. The dictionary process uses only one Start step, and in WEBCON BPS Designer Studio we cannot add any further steps to the workflow (t (...)
(...) N BPS Designer Studio. It is very simple: Download the installer compatible with the version of the WEBCON BPS installed on the server, Open setup.exe file and choose “Installation or update of WEBCON BPS Designer Studio”, The installer will check if there is any version of Designer Studio currently on the machine. If we have a newer version of Designer Studio installed, the inst (...)
(...) Displays a panel which presents all document versions. It contains information about version number, element step in which it the document is, the user who made changes and about the modification date . Two buttons are available: Show differences – displays information about changes made between the current document and the one chosen from the version history. Clicking (...)
(...) de a substitution for ourselves or for someone else. In the other case system, administrator privileges are required. The view displays four columns: replaced person, start date , end date and substitute. Settings are changed via a button in the upper right corner of the screen. Modifying/creating reports is available to a user who has Portal designer privileges. (...)
(...) ; Content of the documentation Each documentation generated in Designer Studio consists of the following elements: Basic information (process name, version, author, modification date , etc.) Workflows and form types in the process Basic process configuration (which includes information about business entity, substitutions and implemented GDPR solutions) Workflow graphic (...)
(...) ns, docx, pdf, tiff, xlsx) As an example, we will use a form made up of 20 form fields (all of them are required): 3x Choice field (1x dropdown, 1x autocomplete, 1x SharePoint Picker) 3x date & time 3x Floating-point number 1x Integer number 3x Single line of text 3x Multiple lines of text 2x Person or group picker 1x Yes/No choice 1 item list comprised of 5 column and 5 (...)