search results

(...) ersion 2019.1; author: Konrad Wojtycza   Introduction From the point of view of business requirements, a common need is the approval of the document by people on the designated approval path . WEBCON BPS introduces functionality that simplifies the configuration of your approval workflow – a list of items. A person authorized to approve can edit only the line to which they are (...)

(...) e workflow   The instance can be edited only in the first step – Registration. In the next steps, it is only possible to accept or reject the application by following the appropriate path . The planned time of the instance being in a given step and the expected editing time can be set in the “Analysis” tab in the editing panel of a given step.   Fig. 5. Sett (...)

(...) Applies to version 2019.1; author: Kinga Bożęcka   Introduction Mass actions allow you to go through the path (and execute the actions that are on it e.g. starting sub-workflows) for many instances at the same time. The article describes the configuration of this action and two examples of use.     Fig. 1. The example process   Fig. 2. The form &n (...)

(...) first saved. This will require validation that checks if the value is given in the form field and if has not changed. If no value is given in the form field, there is no ability to going through any path or save the instance. This prevents incorrect instance number creation.   Instance numeration In the “Instance number” field there is a list of instances (Fig. 6):   (...)

(...) 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 path s, 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 configura (...)

(...) an automatic call to renew the token every 50 minutes.     FIg. 17. The technical workflow after obtaining the access token   After going through the registration path , the first access token is downloaded and the system will automatically renew them in at a given time interval.     FIg. 18. Technical workflow after obtaining the access tok (...)

(...) ed on: Data available on the form Any values from outside the form available e.g. in the database or within other processes in WEBCON BPS The action of changing value can be defined on a path , after clicking a button or on timeout. The “Change value single field” action has been used to determine the exchange rate at which business trip expenses will be calculated. The fin (...)

(...) ion 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 button InvokeRule – start the rule StartElement/OpenElement – start/open the instance Invoking new form rules can be realized e.g. afte (...)

(...) lected based on the SQL query – the “Based on SQL query” mode   The workflow The simple Invoice workflow has been created on the “Copy PO to attachments” path , the action of adding attachment has been configured.   Fig. 1. The "Ivoice" wokflow   The Invoice form allows you to select a PO document (in the “Select P (...)

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

(...) the NIP number of the business entity whose data they want to obtain. Check – a user checks the entered data. If data are correct – the instance goes to the “Download data” path on which the “Invoke REST Web service” action is executed. If not -  the instance can be moved to the first step. Information checked – the instance goes to the last step whe (...)

(...) 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 path s. 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_certifi (...)

(...) executed on value change. They may be used to dynamically change the field visibility on the form. There are several useful JavaScript functions: SHOW rules – allows you to show a field, path , menu button etc. on the form, hidden by the rule defined for loading the form in the “Behavior” tab HIDE rules – allows you to hide a field, path , menu button etc. ENABLE rule (...)

(...) BCON_BPS' : 'HASŁO'}}" Invoke-RestMethod -Method 'Post' -Uri $url -Credential $Cred -Body $body -headers $headers $BodyPermission="{'set-permission': {'path ':['/select','/update','/spell','/suggest'],'collection': ['BPS_Elements', 'BPS_Activities','BPS_Navigations', 'BPS_AI'], (...)

(...) group. The request is sent to the accepting person who can approve or reject it. The “Create BPS group” and “Delete BPS group” actions are executed on the “Accept” path . In the “Request type” field, a user can select the appropriate action (Add/Delete).   Fig. 1. The workflow   The form view at the start step:   (...)

(...) Introduction Task creation is one of the basic functionalities enabling the creation of instance workflows in WEBCON BPS. Tasks in the system can be created in the step configuration on a given path or as an action that can be placed e.g. on the entry to the step. This article describes the “Create a task action” action, as well as the standard method of creating a task on a path (...)

(...) les for creating the file name, but for the example described, the name will remain as in the original attachment.   Fig. 3. The business rule returning the file name   2. The path with actions On the “Active” step, a dedicated “Send the attachment via OneDrive” path was added that contains several actions: Get users drive ID (using the REST Web (...)

(...) le describes the validation mechanism.   The example workflow In the example “Purchase order” workflow, all validation actions were configured on the “Register” path .   Fig. 1. The fragment of the “Purchase order” workflow   Validation actions have been configured in the “Actions” tab on the “Register&rdquo (...)

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

(...) ts of 1) form rules that are executed when the form is displayed, 2) visibility settings for the top bar buttons, 3) editing mode, 4) attachment settings, 5) and accessibility settings for transition path s.   Creating a new form configuration The WEBCON BPS platform builds a compact form by default. When you create the main form, a compact form is automatically built. In most cases, this (...)