search results

(...) dquo; field.   Fig.1. The “Parameters” tab   This field allows you to set an additional validation when going through a given path. You can include both the form rules (global and process), business rules (global and process) and a JavaScript. If you do not want to use the predefined rules – there is the ability of writing your own condition.   Bus (...)

(...) de menu on the application’s page by using the “>” button.     Form view The mobile form contains all features of the desktop version including any form rules that are used to modify the form e.g. coloring form fields. By opening the information panel in the workflow, you can open also a preview of the process workflow on the mobile devices.   (...)

(...) ent” tab allows you to use the variable editor during editing, which is available in the right panel of this window. Thanks to this, in the HTML editing mode you can e.g. customize the business rules or embed images.   Fig. 6. The content edition – using the business rules   Another tab allows you to preview the message. In this example, the “Image code&rdquo (...)

(...) ields or controlling the actions (e.g. technical fields) is justified. In most cases, the value from this field (if it is not used in many places) can be directly downloaded and saved in the business rules . Instead of the data table, you can use the item list which will replace several form fields with columns. However, using this method regularly and adding multiple item lists to bypass the limits, (...)

(...) guration and form type indicated in the first tab.The values of form fields can be inserted by using various variables, e.g. values from the parent workflow instance :   Or business rules :     The “Start a subworkflow (SQL)” action This action allows you to start a workflow instance(s) within the same BPS application and differs from the previous (...)

(...) he default value settings   For each type of form field (except for charts and data table and rows), you can define the default value. You can use the values of other form fields, business rules , context variables, fixed values and data sources in the configuration. Setting the default value of the form field will take place: At the first step, where the form field is visible (this als (...)

(...) e: Entering the numbers of connected orders Entering amounts on the form, which is displayed in two lines Entering the bank account number divided into several values   B) Form rules that allow you to display/hide the “OCR Train” button     Examples of use: Selecting users responsible for marking fields as “for learning” The (...)

(...) ve amount compared to other orders, or vacation requests spanning a very long period time. Launching analysis of the anomalies will automatically create a process description – a set of AI rules  based on real data entered by users. A set of AI rules is created by using artificial intelligence. A random sample of data is selected for the process, based on current and historical instan (...)

(...) process and application configuration. Both translations in the process configuration and in the language pack can be done partially or not done at all. This is why in the system there are strict rules defining which text will be displayed to the user if the phrase doesn’t currently have a translation in the currently chosen interface language: For language package translations (and als (...)

(...) ions due to creating/moving multiple workflow instances at the same time. The speed of creating/updating 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 s (...)

(...) tasks are easy to manage and their assignment, as well as execution, are simple and clear. For more information, see: Task assignment Predefined task assignment Task assignment - business rules   Parallel tasks Clicking on the transition path button finishes the task of the logged-in user or of the person who was substituted. If other users have unfinished tasks on this step t (...)

(...) flow graphic presentation Form types and acronyms Instance number Form field summary Process privileges Workflow steps   Moreover: Constants (local and global) Business rules Action patterns   Filling in the documentation After generating documentation in WEBCON BPS Designer Studio, you will get a ready documentation template which you should fill in. He (...)

(...) efault from the basic form. There is the option to break this inheritance and separate configuration for the compact form. In the same way you, can manage the compact form behavior using the form rules . By default, they are inherited from the basic form, but you can break the inheritance.   System configuration -> Global parameters -> Required mobile application security level (...)

(...) k details” on the form   You can configure the task description in the same place where the task assign is configured. In the description, you may use the form field values, business rules or context variables.   Fig. 5. The configuration of the task name and description   In the same way you can configure the task description in the “Create a task&rdqu (...)

(...) “Active” checkbox you can edit the approval settings. In the “People that have rights to accept” section you can define all approvers. They can be defined based on the column rules in the item list (the “Dynamically” option). In this case, the “Approver” column stores the approvers’ data, so the picker value should be set to ‘login’. It (...)

(...) s you to send e.g. picture form field content Any text content other than in the above sections   Fig. 21. Send file - Request body tab   There are three business rules that can be seen in the screenshot above. The “Att: ID” rule is the basis for the others. It contains a SQL query that returns the ID of the last added attachment added to the current ins (...)

(...) nd relate it with the current instance. Value – this field defines the value set after execution of the action. In this field you can use all functions and form fields available for business rules e.g. arithmetic operations, SQL expressions and form fields available on the form. Error message – this field defines the error message displayed when there is a missing value error. It is (...)

(...) e HTML language on the form. The HTML form field can be defined as adding a custom HTML code to the standard code of the WEBCON BPS form. The best solution is to use this form field with the new form rules in JavaScript mode. Form rules in JavaScript mode have been enhanced with the following function: MoveToNextStep – go through the path InvokeMenuAction – invoke the menu butto (...)

(...) other fields. To correct calculations, remember to properly set their order. This article describes several examples of dynamic field calculation, and then in a tabular form the order od execution of rules for both the Modern and Classic form ha been presented.   Description of the functionality Below two examples of dynamic field calculation have been described. The text field from (...)

(...) dash; information about the configuration of action group buttons from the top menu WFActionButtons – information about the configuration of action buttons from the top menu WFActionBusinessrules - information about the configuration of business rules used in the action configuration WFTimeoutActions – it links actions with cycles in which these actions are executed   f) (...)