search results

(...) 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 (...)

(...) ellip;) next to it to choose it from a list of available parent sites, Title - site name, Description - site description, URL name – the text that will be displayed in the website address path .   Fig.3 Action configuration for “Create a site”   You can save the address of the newly created site in a workflow's form field. To do so, tick the b (...)

(...) wly created subsite, and consider adding a site description in the “Description” field. In the “URL name” field, enter the name that should be displayed in the website address path .   Below you can see how we have filled in the values. We have used the values from the form to fill in the name, description, and URL name fields. If you want to do the same, click on a (...)

(...) ceeds to further recognition of the file queue in the service   Fig. 5. Missing or unmatched barcode   In the “Workflow StartUp Settings” tab, you can define a path to be followed by the workflow after adding the attachment to the workflow.   Fig. 6. The “path for new element” option   In the “Additional fields settin (...)

(...) om of the article). To do this, create an empty directory on the disk, e.g., with the same name as the theme, and use the command: Export-AdfsWebTheme -Name MyADFSWebTheme -Directorypath  "C:MyADFSWebTheme"   All graphics, styles and scripts of our theme will be exported. Fig. 4 The theme downloaded to the hard drive   Now, you can repla (...)

(...) e user. Once submitted, it is sent for acceptance to the Approver. If the Approver accepts, the action requested in the form (create, delete or edit the user) is performed on the “Accept” path that goes from the “Acceptance” step to the “Actions done” step. Fig. 1 The workflow for creating, removing, and editing BPS users   In our example, we (...)

(...) dynamically on the form, i.e., it can be executed after each change in the value of the Text 1, 2, 3 form fields; it can also work statically, e.g., when the form goes from one step to another (on a path )or  when a button is clicked. For the function to work dynamically, in the “Style and behavior” tab we have added a rule that sets the value of the Concat(Text 1,2,3) field on va (...)

(...) asks must perform an action. WEBCON BPS has a comprehensive tool that allows you to choose who the task should go to in the next step; it is configured in the ‘Task assignment’ tab on the path that links two steps.   However, this is not the only way to assign a task to the user. This article discusses how you can use the “Choose an approver” action to assign a task. (...)

(...) at the final step   Promotion process configuration   The promotion process should be configured adequately to the business needs, which involves creating appropriate steps, path s, and form fields. In our example, we will need to create the Client form field so that the system knows from which instance it should download the tags used in the process. The next thing we should (...)

(...) "Basic features" option. After expanding this menu, go to the “Services” submenu and select your Service. The screenshot below shows the view in Studio after following this path . Check the box next to “Basic features”.   Fig.1. Service configuration.   Data update takes place only at times selected by the user. To define the update hours (...)

(...) ot; form field configuration In the advanced configuration of the item list, uncheck the “Allow delete” option - instead of deleting rows we will mark them as inactive. On the Register path , you should add the form validation action to check the uniqueness of the instance. If the “Role” form field has been added, then in the system should be only one workflow instance with a (...)