search results

(...) (for each workflow instance, form type and step), and then rules are created which encompass the most common (covering over 75% of cases) values or ranges of values for all numerical and categorical field s. Moreover, dependencies between various field s on the form are created, and norms based on statistics about editing a given form field (whether the field should be completed or can be modified) a (...)

(...) ss and application configuration. Those text phrases can be different in every process and are defined independently. Translatable phrases from configuration areas are for example: process name, form field names, or descriptions of the form field s. The following elements of the application presentation are also translatable: name of the report and start button name. On the other hand, there are phra (...)

(...) nting groups. In this case, the BPS groups will be used, but you also can use AD or SharePoint groups.   Configuration The first step is to configure the “Department” choice field . It’s best if the ID should reflect the department name (e.g., acronym) if possible because this will make the work easier for us later.     The next step is to create &l (...)

(...) ’s create the queue mechanism in such a way, that the cyclical action takes only those instances that haven’t been moved in the previous cycle. For this purpose, we need to add a new form field – a simple checkbox technical field which will store information on whether the expense has been moved or not. By default we set it to “NO”, because at the beginning all expenses wi (...)

(...) groups.     Use of REST API For testing we will use the API verification tool – called Postman and simple, two-step process containing several standard form field s and one item list. Obtaining a token – /api/login In the Postman we create the first REQUEST – POST for the LOGIN method. No authentication is require (...)

(...) low name, instance number and indicate a business administrator.   Fig.2. Creating a new document template – wizard   After creating the process, we will have two form field s called ID and Active (checkbox form field with yes/no option). You can also add additional form field s. The dictionary process uses only one Start step and in WEBCON BPS Designer Studio we cannot ad (...)

(...) simplified and uniform environment. With each dictionary process, a predefined data source returning all dictionary elements is automatically created. The structure of the source contains all form field s  defined in the process and is updated whenever the configuration of the dictionary process is changed. The dictionary process uses only one Start step, and in WEBCON BPS Designer Studio we can (...)

(...) /users?view=graph-rest-beta. User is created by using: https://docs.microsoft.com/en-us/graph/api/user-post-users?view=graph-rest-beta&tabs=http It is a good idea to create a User ID form field – it will store user’s ID from AAD, ID will be required for a further management over the created user.   2.1. Data source configuration for Graph connection Data required f (...)

(...) bsp;     In the further part of this article you will learn how to customize the website look by using a new theme – „LogoKlienta”.     field s seen on the screenshot above are general information: „Theme name” cannot contain any spaces „Theme description” is a short summary of the theme checbkox „Is (...)

(...) Webcon BPS Word Add-In allows to follow the history of changes in the documents placed in BPS repository (attachment list on SharePoint), compare documents which are in the repository, browse form field list and create templates for “Generate DOCX” action. In order to allow user to edit attachments added to the document it is needed to configure the website and name with the attachmen (...)

(...) t time. However there are situations where tasks are assigned and instead of improving the work, they unnecessarily complicate it. A good example are processes whose specification requires for a form field to remain in a single step for a long time. One of the most popular is a stocktaking process of the provided assets. Based on it, a difference between assigning task and providing privileges to modif (...)

(...) dquo;Acceptation” step. On the transition path “Send to acceptation” a task for a group of approvers is created. Below is its configuration.     When the form field goes to the „Acceptation” step we can accept, reject or cancel it. For each path, a different parameter from the “Operation executed on parallel tasks” group was set. (...)

(...) PS Designer Studio allows you to create documentation for each created process. It consists of two files - DOCX that contains the text description of the process, and XLSX that contains the form field matrix. Generating documentation There are three options to generate documentation: right-click on a process in Designer Studio use the Ctrl + D go to the Tasks tab   (...)

(...) tabase. Content database (main database) – collects all information about the configuration of applications created on the platform e.g. process definitions, information about individual form field s 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 enter (...)

(...) with the three search boxes marked red  - places where you can search for information.   Fig. 1. Portal page with its searching features   Search in navigation This field is used to search for such elements as applications, processes, reports, dashboards, start buttons. The suggested results depend on the place where a user is in the Portal. Being on the main page &nd (...)

(...) ted content will be presented in English (for constant parts of the system and process) or the default language in which the process was configured (for customizable parts of the process such as form field names).   The Force language option:   Fig. 3. The "Force language" option   Language from the list – After forcing the language in WEBCON BPS (...)

(...) Applies to version 2019.1; author: Łukasz Kraśniak   Introduction Form field , path, and task tooltips are a massive help for users to easily understand the concept of WEBCON BPS business applications. Consistently providing tooltips and task details across all your processes and workflows will teach users to rely on these elements to learn about their intended task. This help immense (...)

(...) ing the number of errors and questions. They can contain basic information which helps a new user get started with the application, and also may explain the more complex dependencies between the form field s required to add attachments or selectable paths that will make the task easier to complete.     Step description The step description is visible by default on the right part of th (...)

(...) w   The configuration of the approve path with the blocked rows The Approval path contains the item lists with the active approval function. Start the configuration from adding the form field s to the item list – in the simplest case they could be the item list with the checkbox columns (Fig. 2) and choice field (Fig. 3).   Fig. 2. The column settings with the checkbo (...)

(...) Applies to version 2019.1; author: Jarosława Markopolska   The article describes the functionality of inheriting the global form settings and form field definition in WEBCON BPS.   Inheriting form settings Global template inheritance – this setting the order of form field s according to the process tree. This means that the order of the form field s in the group and colu (...)