(...) CON_ID) in the WFConfigurations table Storing data Each form field in WEBCON BPS has its unique ID assigned – it allows you to configure workflows with Item list types of form fields . Fig. 1. The Item list – ID Depending on the given item list column, data is stored in the appropriate field in the table. This field is invariable and is automati (...)
(...) ey store both system data and form field values defined in the processes. Each workflow instance is identified by a unique ID (WFD_ID). Fig. 1. The form – system and configured fields On the screenshot above (Fig. 1) data has been marked with the following colors: Red – system fields e.g. instance ID, instance number, process, workflow, current step, form (...)
(...) DK actions so you can enter them as constants in the process. In the “Attachment section”, define the method of attachment selection (by Category or SQL query) and technical form fields to which the ID of the signed document and envelope created in DocuSign will be saved. Fig. 6. The configuration of the action In the next fields , enter the title and co (...)
(...) p; Fig. 2. The adding/deleting users to the BPS group The form view on the start step is presented below: Fig. 3. The form view on the start step The fields with the register person and date are automatically filled in. The selection of the other three parameters seen on the form: the person to be added, the accepting person, and the group that will be m (...)
(...) process, form field, workflow etc.) Ctrl + C – a shortcut used to copy the selected object (form field, path, rule etc.) to the clipboard Shortcuts used to work with text In fields where the user have the ability of entering the text values (e.g. documentation field, descriptions, SQL queries) there is the option to use with the standard shortcuts, the most important are: (...)
(...) nbsp; Thanks to this, the process created in another application will be “added” to the current application and can be used. As you can see in the screenshot below, the workflows, form fields and configuration are exactly the same. The word “added” should not be understood as making a copy of the process – the process definition is still in another application, by creati (...)
(...) Golonka Introduction When creating support for business processes in WEBCON BPS, it is important to remember that even the simplest workflow with a minimum number of steps and form fields will be reflected in the database – all of its instances and settings are represented in the content database – which is the main place of the system’s operation. There are also &ld (...)
(...) Applies to version: 2020.1.x and above; author: Mateusz Klos WEBCON BPS Designer Studio allows you to configure the form fields ’ appearance so that they can be more transparent and legible, as well as tailored to your users’ preferences. The following article lists several ideas on how to manage the appearance of your form fields : Groups Through WEBCON BPS D (...)
(...) downloading the embed code of any system elements. These privileges do not have access to the given processes. Metadata access – the privileges give access to the process metadata (form fields structure) from the WEBCON BPS Word add-in level, allowing the definition of the document templates. They do not give access to the given processes and applications from the Portal level. Read-only (...)
(...) ” button. Fig. 8. The “Analytical breakdown” step Summary Embedding the correctness rule on the workflow path is a convenient and fast way to verify fields . In addition, it simply limits calling the rule to a specific place of the workflow. Verifying the correctness of the entered data allows you to avoid mistakes and therefore spend less time correctin (...)
(...) on on the selected column – values in that column will take the user directly to the form of the instance they clicked. The preview window also works in forms on form fields of the data table. The field defined in the form field configuration, will be opened in the preview mode by default. The form preview window significantly spe (...)
(...) rst, configure the Training workflow. It contains two system steps – start and finish and one intermediate step. Fig. 1 Training workflow On the form, several form fields that store data about the training and users have been defined. Fig. 2 Training form On the list storing the users' data, on each name there is a “Is certifica (...)
(...) o;>” 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. Reports and dashboards The new way of displ (...)
(...) portant is the need for business process automation. One example of such automation processes is the use of serial correspondence which generates documents based on the specific template in which the fields and values can be changed. These values can be loaded from an external data source. Configuration The topic will be discussed based on a business case in which you want to collect pay (...)
(...) tion templates In addition to these elements, attention should also be paid to: Translations entered in the process configuration If you decide to put a standard list of the form fields , their names will be translated according to the entered translations If you use the “Choice field” form field which supports the multilingual names, the value will be displayed in a la (...)
(...) configuration was described in this article -> Integration with AAD using REST invoke method and Microsoft Graph (webcon.com) An example process for managing projects contains several form fields : Project name Project description Project manager Team – Employee and Role Creating the team To create the new team, start by creating the Office 365 (...)
(...) art WEBCON BPS!’, if([$Status]==’In progress’, ‘’,’’))”, The WEBCON BPS workflow is started from the hyperlink that contains the following fields : Name (AttText1) a field in which the document name ([$FileLeafRef] variable) is stored ID (AttText4) a field in which the file ID is stored Item URL (AttText3) a field in wh (...)
(...) e description The tables store data o the edition of the instances and changes of the values when going through the path. The WFHistoryElements table stores information about the instance and form fields value and the WFHistoryElementDetails table – information about values from the “Item list” form field. Every time when the instance goes to the next step in the workflow, in the (...)
(...) ting workflow will be started. The current status of the task can be checked in the SharePoint list column. Configuration of the SharePoint list The list consist of the following fields : Title field – contains the name of the invited person Status field – contains the current status of the task BPS URL field – contains a link to the started WEBCON BPS ins (...)
(...) d template configuration During the first start in the Word program, the configuration of the add-in is done in the same way in new versions as in previous ones. Adding the form fields to the template After setting up the Word add-in connection to the appropriate site, create a template – use the “File Generation Templates” button. Then, in the (...)