WELCOME TO THE COMMUNITY
find what you are looking for or ask a new question

search results

for path

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

(...) nions from individual departments or teams. In turn, the Comment field can be used in another step of the process. Enter the required information/message in the form field. After going through the path or clicking Save on the top bar of the Portal window, the content of the entered information/message is saved, and a header appears above it, stating its author and date of entry.   Fi (...)

(...) data returned from Active Directory.   The workflow is configured so that the "Participant" is the person who will receive the form after going through the "Notify" path . Once the required fields are correctly filled in, the form in the final positive step “Particiaption confirmed” will look as follows:   Other application examples and data (...)

(...) son: – starting separate workflows (e.g. for incoming correspondence, submission) that automatically close incoming correspondence document through the “Complete automatically” path , – closing the incoming correspondence workflow by going through the “Complete” path if no other workflows are required, – moving an e-mail to the “Canceled” ste (...)

(...) allows you to define which document, in which workflow and process, and for which company is started (in the discussed example it is the “Cost invoice” document) You also need to select a path the uses to register the document. “Additional form field values” – here you can assign e-mail data to respective workflow form fields, e.g. e-mail sender or title. Full list of a (...)

(...) rdquo; workflow diagram   Registration – an initial step in an “Agreement” workflow. A registrant fills out all the required fields and uses the “Register” path to move to the step where an agreement file is generated with the data they entered in the form fields. Generating an agreement – a step containing the “Generate the PDF file” act (...)

(...) operating system used, files are generated using Word Classic or Word Modern add-ins. The action Convert Word to PDF allows you to quickly convert a file without having to edit it or go through a path . After successful conversion, the editable text file is overwritten with the newly created .pdf file. Action configuration is described in the article: Generating Word and conversion to PDF (webcon.c (...)

(...) p” rule it is possible to check if a particular instance was present in the defined step. The parameter used in the rule is the step identifier “STEP_ID”. The rule is used in the on-path “Change value of single field” action. A technical field “ _Was in Consultations step” is filled out on transitioning the path . This rule can be useful, .e.g. as an action (...)

(...) rder for the BPS group to be exported with the process, it must be used in the process configuration, for example, the group must be granted privileges (as above) or assigned a task on the transition path . When exporting the "Audits & Controls" application, at the summary step, the system will inform you about finding the BPS group and exporting it. Note that the export/import mechani (...)

(...) review of the automation defined on the "Completing documentation" step, which includes the form validation action   The Properties window also opens after selecting the workflow path . As with the form field, the user can view its Advanced settings. The path details window is then displayed, divided into General and Create task tabs, with an available preview of the selected path & (...)

(...) 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 path s 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 path s of the displ (...)

(...) invokes the action for the already existing and active sharing and for the same e-mail address, the sharing is reedited and the link to the instance is sent again (if the action is embedded in the on-path automation. The “Share workflow instance” action can be invoked in the following contexts: “On entry”, “On exit”, “On timeout”, “On browser (...)

(...) 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 “path s” tab → the “Task creation” tab → “Send standard e-mail”).   The form Tasks assigned to a group are displayed in the task counter of the grou (...)

(...) g” step using Start from zero A Stop performance indicator action is placed On exit from the “In progress” step Another Start performance indicator action is placed On path on the “Requires review” path using Continue calculating.   This final detail is important, as we can resume the indicator time if the ticket gets sent back by the approver. (...)

(...) e to the container directory where files with search indexes, privilege configuration, and log files will be stored, bash –c “/opt/bps-solr/scripts/run-precreate-cores.sh” – path to the script that initializes Solr index structures. This script must be passed the first time the container is started for the indexes to be created. It can always be passed, because when the conta (...)

(...) out-of-the-box functionality, but there are a few situations that have arisen that warrant special coverage – and special treatment.   The Problem Consider the workflow below. The path named Start executes an automation that starts several subworkflows. The workflow then waits at the Wait until all new sub-workflows are finished step until all workflows end positively, any end nega (...)

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

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

(...)   The Scenario Consider the workflow below.   During the step named “Review”, a set of people are tasked with choosing the “Yes” or “No” path . WEBCON BPS provides a means to handle situations where different reviewers might make different decisions:   First Response Wins If you only need one response, this is easy to handle. (...)

(...) Desk and prototyping are used for. In the practical part of the training, participants will learn to: design a business process prototype, construct a workflow with individual steps and path s, plan actions to automate specific tasks, design forms, manage the application view available to the end user, test the prototype and generate the associated documentation, export prototy (...)

Did you know that with WEBCON you can automate virtually any process? Even baking cookies 🍪
 
Speaking of cookies: we use the ones that are essential for our website to function properly, as well as additional ones that help us customize our content to your preferences. If you don’t mind cookies, click Accept. If you want to learn more, explore settings.
Settings