search results

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

(...) ed “Approver.” Please note that you need to create this field before you can select it. Once you have entered all information, save the configuration. Then, we need to go to the “paths ” tab, select the path we are using in this configuration (here, it is “Register”), and on the right, click on the “Task creation” tab. Here, we go to the “Tasks as (...)

(...) at the final step   Promotion process configuration   The promotion process should be configured adequately to the business needs, which involves creating appropriate steps, paths , 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 d (...)

(...) eps – Start and Final which are connected by one path. You can add any number of intermediate steps, define flow control steps (they are used for directing documents through one of the possible paths based on a condition e.g. can be used to skip a step if some condition is met), and system steps (the are used when it is necessary to wait for external actions, e.g. synchronize data between systems (...)

(...) the level of individual workflow instances. You can find these actions in the “Actions” tab of a given workflow. They are most often used for entering/exiting a step and on transition paths . For more information about actions in WEBCON BPS, see Introduction to actions in WEBCON BPS.   Fig. 1. The "Add/Remove privileges" action   Configuration of the & (...)

(...) s. Configuration The "Change items list values” action will be used in two lists – Analytical breakdown (Fig. 2.) and History of approval (Fig. 3) after following the selected paths .   Fig. 2. The "Analytical breakdown" item list   Fig. 3. The "History of approval" item list   A) Add new values mode The "Chang (...)

(...) rkflow applications is visible below:   Fig. 3 Form of the Absence process workflow   The workflow control step is named "MGMT acceptation?" (Fig. 4) which has two paths . One of them leads to the approval of the employee's manager (Fig. 5), and the other directly to the "Entry to HR system" system step, where an entry into the HR system is made (Fig. 6) (...)

(...) ocesses 9.    WorkFlows – workflows 10.    DocTypes – forms 11.    Steps – workflow steps 12.    PathAndTasks – paths and tasks 13.    Attributes – form fields  14.    SubAttributes – item list columns description 15.    Actions – actions 16.&nb (...)

(...) he step and workflow actors in the step Step type Step type – starting step, final step, positive/negative, system step, workflow control step Transition path paths to and from the step, step location in the workflow, target step(s) Optional:   Description on the form Description in the form available to the workflow users (...)

(...) block (comparable to a workflow step) that cannot be deleted. The automation is configured by adding new blocks from the automation menu – this is done by clicking the  sign on the “paths ” connecting the blocks.   From this menu, the following types of blocks can be added to the automation:   Automations – as mentioned above, automation templates (...)

(...) necessary data (such as line number and production type), and starts an instance.   Fig. 1. An example application instance   At the “Active” step, the following paths are available: Save line workers - used to save changes Deactivate production - used to deactivate the production line Halt production - used to hold production   Fig. 2. T (...)

(...) or: Krystyna Gawryał   Introduction Instance history is an area where the user can check what actions were performed in the Workflow. History details the steps taken by the user and the paths they took to complete the assigned task and finish the workflow. This article summarizes the most important information on the Instance history in WEBCON BPS Portal and related features.   (...)

(...) – if you select this parameter and use the tile, the configured process will be started in the default browser. Path – option available only when the Start in browser box is unchecked. paths are selected from the paths defined in the registration step of the given workflow. Mappings – this section allows you to set the value of the newly created instance. Here you can use data av (...)

(...) cesses and applications built in WEBCON BPS (as long as they have the necessary privileges). This access involves the ability to create new instances, edit and save them, move them to other steps via paths , and browse reports and applications. Through this license, a specific number of users (determined by the number of licenses) will be able to use the system without limitations regarding the number (...)

(...) vigating to a dedicated node in the menu, will be able to view Heatmaps of the workflows that belong to it. On each such workflow its "hot" and "cold" points are marked. Steps and paths are highlighted according to the frequency of their selection by the form user and the time spent on tasks, as shown in the legend below the workflow. The arrangement of steps and paths of the displa (...)

(...) functionality to inform a group member about receiving a task. To do that, check the Send standard e-mail checkbox available under the “Task creation” tab (step edition → the “paths ” tab → the “Task creation” tab → “Send standard e-mail”).   The form Tasks assigned to a group are displayed in the task counter of the group (...)

(...) kflow then waits at the Wait until all new sub-workflows are finished step until all workflows end positively, any end negatively, or it is clear that there are no subworkflows to wait for. There are paths to follow for each of these possible outcomes.   In particular, if any subworkflows ended negatively, the workflow will follow the Failure Found path back to the initial step. This (...)

(...) e, we will concentrate on the features dedicated to GDPR, how to configure them, and how they work.   In the next part we will focus on the instance’s journey through the various paths of the workflow: Register a request – input basic data Personal data search - methods of searching through the database and saving the results on the form Select person – specif (...)

(...) of the Prometheus tool and the Grafana platform associated with it. Both solutions are used for monitoring and analyzing metrics. Jaeger Jaeger is used for monitoring and analyzing queries paths in distributed systems. It is a free software available for downloading at https://www.jaegertracing.io/download/. Click the link, select the software version corresponding with your operating sy (...)

(...) ct” if we receive even one “Vote No” path choice:   For more elaborate decision making, the following illustration shows how to have the workflow whichever one of two paths receives a majority (> 50%) of votes, with a tie going to whichever path has been set to be the default:   The path ID values can be obtained from the Object browser tree as shown a (...)