(...) Applies to version: 2020.1.x and above; author: Anna Puka Starting from WEBCON BPS 2020, the OCR verification view is available on MODERN forms . It allows you to enable AI mechanisms in StandAlone installations. This article presents new functionalities and suggests how you can use them. The new OCR verification view introduces several additional functi (...)
(...) mplates can be stored in. It’s a good practice to add a few columns that will allow us to add additional information about the files. In this case, we added the “Active” flag that informs us about if this file is the final version or only an unfinished draft. Fig.10. Document library in SharePoint Such a library can be encapsulated with a process that wil (...)
(...) st of all – in the report on the “Source” tab, the dictionary process is locked in and cannot be changed, we can only change which form types should be available (all types of forms , one or more). In addition, we have added an “Active” system field with standard filter showing only active instances on the report. Another difference is in th (...)
(...) reenshot above are general information: „Theme name” cannot contain any spaces „Theme description” is a short summary of the theme checbkox „Is active” informs whether it is present on the list of themes available to the user „Is default” allows to set a selected theme as a default one „Theme logo URL” contains a link to the file (...)
(...) ontent database (main database) – collects all information about the configuration of applications created on the platform e.g. process definitions, information about individual form fields and forms configuration, information about privileges for the individual objects on both the data side and the presentation side. This database also contains all metadata about processes (data entered by users (...)
(...) works online – requires the internet connection with WEBCON BPS installation Application works based on the users of connected WEBCON BPS system Applications for individual platforms are available in application stores (suitable for the operating system of the device) dedicated to these platforms . When it comes to the Android system devices it is the option to provide an inst (...)
(...) – fields in the report are defined for the entire process. When in the process you have more than one form type it may happen that report will be contained a field not supported by some of the forms . In such a situation, after registering an instance on this form – a field will not return any value. The example below displays the instance from the leaves workflow in which there is no o (...)
(...) ows people belonging to the organization’s structure (most often from Active Directory) to be selected. Enabling the approval functionality is possible in settings of a specific step in the forms tab. This should be the step at which people approve the document – in this case it is the “Purchase order approval” step (Fig. 4). Fig. 4. The configuration of th (...)
(...) very step of a given workflow. However, you may need to customize the arrangement of the form fields for the selected step. It can be configured directly in the settings of this step using the “forms ” tab (Fig. 4). You can break inheritance on a step just like on the global form template. Fig. 4. The form at the current step – breaking inheritance After (...)
(...) step” and “Average end time” steps are filled out: Fig. 6. Statistics in the “Acceptance I” step The “Trend” column informs about values change in columns between the previous and current month: Time shorter than the previous month Time comparable with the previous month Time longer than the pre (...)
(...) s you to overwrite the attachment if the attachment with the same name already exists. If this field is unchecked, a new attachment will be added each time. Form view Below there are forms with the added attachments: Fig. 12. The form view with the attachment added based on the instance ID Fig. 13. The form view with the attachment added based on the i (...)
(...) quo; field configuration enter this rule as a default. Fig. 10. Filling in the field with value The execution order of the form rule for the Modern and Classic forms MODERN FORM Form rules executed on page load No. Configuration Tab Field name Link 1 Workflow cofiguration (forms ) Behavior Form (...)
(...) Fig. 5. Configuration tables related to the form fields matrix level WorkFlows – it describes the configuration of workflows WFSteps – the configuration of steps WFStepforms – the configuration of the form types on the individual steps and workflows WFStepFormFields – information about requirements and editability of form fields and additional configuration (...)
(...) ing such buttons makes the form look much more readable and transparent, making your employees happy that your company has adopted the digital transformation and they no longer need to use paper forms .
(...) n NIP, you did not receive any error message from WEBCON BPS. The detailed information about the error, you can find in the form field where the message returned by API has been provided – it informs about incorrect NIP number. The action of invoking the Web service also allows you to map the Code and Body values of the response, both in the case of positive and incorrect invoke. In more comp (...)
(...) CON BPS has been provided to cover the possible business needs of the form. The matrix of form fields and functionalities available on the described tabs enable the advanced configuration and dynamic forms . Thanks to the described functionalities, it is possible to adapt individual steps and entire processes to the specific business requirements. Controlling the visibility of fields on reports allo (...)
(...) ist of available paths in the form menu. By default, buttons used to change the workflow steps are located at the bottom of the form. Fig. 1. The WEBCON BPS form When forms are complex with many different form fields, it is often necessary to scroll to the bottom of the form to go to the path buttons. A good solution is to add a list of the available paths in the form m (...)
(...) 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. Fi (...)
(...) Applies to version 2020.1.3; author: Michał Kastelik In WEBCON BPS, your forms can be ergonomic and comfortable to read, no matter how big they are. It is possible thanks to the feature that allows you to organize your form fields into groups and configure how they work and what they look like. Read this article to learn how to create form fields groups, and use them to improve your forms ' vi (...)
(...) nstead of going to the item, Automatic save - after opening the link, the form will be saved, Encode special characters in variables' values - this option is used to avoid errors when sending forms with values containing special characters. How to define the hyperlink? If you do not want to use a predefined action to create a hyperlink, follow this section to learn how to crea (...)