search results

(...) con. The system will move us to the history of the element edition.   Fig. 1. The instance form   Seeing the history of the instance, you know by whom it was edited and what paths the workflow went through and what fields were changed.   Fig. 2. The history of the instance   The workflow was changed only once. In the WFHistoryElements table two entrie (...)

(...) BCON BPS, such tooltips can be found both on form fields and on transition path buttons. For form fields, the tooltip will be located in the small “I” icon next to the form field. For the paths – you need to hover over the path button and you will see a tooltip. We can also add step descriptions that will appear in the Task details section of the form.   Business case A (...)

(...) the path.   Configuration To set the default path, enter the path configuration and in the “General” tab select the “Path is default” option. Each step which has paths must have one – and only one – of them marked in this way, otherwise it is not possible to save the process. If you attempt to save a process without a default path selected, the system w (...)

(...)   Introduction Actions are commonly used in WEBCON BPS to design the processes and individual workflows. They are performed without any user interaction and defined on the transition paths or steps. An example actions perform such activities as calculating the field value, making an entry to AD, sending an e-mail. While working with WEBCON BPS they will appear situations (at the s (...)

(...) gger one more time will make perfect sense – for others, it will not (e.g. an action that is meant to be triggered once per workflow, regardless of what steps it goes through). When configuring paths that allow you to navigate workflow instances to previous steps, consider the following options: Set additional execution conditions on the action, depending on whether the workflow was moved b (...)

(...) facilitates and optimizes work by clearly specifying the order in which steps must be completed and who they must be completed by. In Designer Studio, a workflow consists of steps and transition paths connecting individual steps. Read this article to understand how bpm workflows work.   Steps in the system – system step There are several types of steps: Start Inter (...)

(...) iguring a business application based only on its logic without having to assign tasks to the specific users/groups. This option can be found in the Step edit configuration window -> paths  tab -> Task creation tab.     A similar configuration window is used for the Create a task action:     Below you find a descr (...)

(...) ly obtain detailed information about the workflows. By generating the report we can check: How many instances have gone through a given path – this function allows you to check which paths in the workflow are most often chosen. They should be particularly closely monitored in terms of query optimization and execution time of procedures. How many instances have ever been found in a sp (...)

(...) uttons labels (Return, Cancel editing, Save, Delete, Reload) predefined form controls, labels, and descriptions of built-in functions (ATTACHMENTS, Add attachment, Modified, by, version, Predefined paths ) information panel labels (Information, Process, Form type, Workflow, Steps, Assigned to, Created by, Create date, Modified by, Modification date, Version) etc.   BPS Translator vs. (...)

(...) the possibility of using REST API technology to create programming integration solutions with the system. The REST API provides full support and allows you to start new workflow instances, transition paths , and modify the content of the instances. WEBCON BPS 2020 has API in version 2.0 which will be used in the examples below. Authentication API uses bearer token authentication. How (...)

(...) u can also add additional form fields. The dictionary process uses only one Start step and in WEBCON BPS Designer Studio we cannot add any further steps to the workflow. However, you can add your own paths and actions on them and create a simple process (ex. attachment approval process). Only one attachment can be added to each workflow instance in the document templates process.   (...)

(...) iew".      After generating the preview, the workflow diagram will be added to the process documentation.      Form fields summary, steps, paths and rules description, etc. Each of the process element (form fields, steps, paths and rules) should be described. Below you can see examples of correctly filled in information for the "Form (...)

(...) opening the form and placing the mouse pointer over the „Contractor” field, a tooltip added in form field configuration will be displayed.       Tooltips on paths Another important part of making task processing a bit easier is placing tooltips on paths on specific workflow steps. To add them go to specific step configuration and in “paths ” tab (...)

(...) contain basic information which helps a new user get started with the application, and also may explain the more complex dependencies between the form fields 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 the form but you can move them elsewhere, just like (...)

(...) ntrol step (here, depending on the type of equipment rented, the request goes to the IR or HR department). After approval by the appropriate department, an action of Word generating was added to both paths , followed by the action of converting this file to PDF.   Important! An action template was created from both actions  - action templates allow you to use the same action configurat (...)

(...) sp;          The HTML button can be placed anywhere on the form. At the same time, the path to be called may be hidden in the standard place of displaying form paths . You can do this by creating a page load rule (Workflow name> Main form> Behavior) (Fig. 6).    Fig. 6. The form rule    The button on the form is presented (...)

(...) l configuration settings on the individual forms WFStepFormFieldDetails – it describes information about requirements and editability of item list columns on the individual forms WFAvailablepaths – information about paths created in the system between steps WFTimeouts – the configuration of timeout actions WFTimeoutActions – it links actions with timeouts in which these (...)

(...) be provided.   2. Docker (Linux) The configuration file for nginx running in Docker will be almost identical to the installation as Windows Service (point 1) except for the certificate paths . Place the “nginx.conf” file in the /var/www/nginx/ location. The *.crt certificate with the *.rsa key put in the /var/www/nginx/cert/. Two lines should be replaced: ssl_certific (...)

(...) thanks to the various mechanisms e.g. parallelism of execution. The “Create a task” action allows you to simplifies and optimizes the configuration – instead of configuring multiple paths directing to the same step, we can create and configure one action e.g. on the entry to the step.

(...) ld - read and edit restrictions                > Form type - default assignments                > paths - assignments                > Business rules - user lists   The “Change also archived tasks” option allows you to assign pri (...)