search results

(...) ured fields   On the screenshot above (Fig. 1) data has been marked with the following colors: Red – system fields e.g. instance ID, instance number, process, workflow, current step , form type, modification date, created date, author, modified by, current version, comment field. Blue – the fields defined in the process (configured) e.g. text fields, numerical fields, cho (...)

(...) ople who can approve the document. To send a document to a given recipient, indicate their name, surname, e-mail and phone number (optional, if you want to use PIN verification via SMS). At the first step a user can generate a contract that will be added to the attachment section, attach a file from disc themselves, or scan a document.   Fig. 1. An example workflow instance   (...)

(...) about creating groups and task assignment see: https://howto.webcon.com/bps-groups-in-standalone-installation-type/ https://howto.webcon.com/assigning-tasks-to-bps-groups/   The next step is to create an example workflow used to submit a request for adding/deleting a BPS user. This request is directed to the accepting person who can accept or reject them. The “Add/Delete a singl (...)

(...) ldquo;teleportation”. After clicking this combination, a window to which we introduce a link to the instance or their ID will appear. The system will automatically move you to the configuration step where this element is. This function can facilitate searching the element for places where errors are generated. After receiving a link or instance ID from the client, the system automatically moves (...)

(...) be referenced in presentation configuration like any native process.   Configuration   Creating the processes Three processes have been created in two applications. The next step is to create a separate application that will contain a relation to these processes. a) Invoice process – a process in which a user can register an invoice for the selected vendor. (...)

(...) , author: Dawid Golonka   Introduction When creating support for business processes in WEBCON BPS, it is important to remember that even the simplest workflow with a minimum number of step s and form fields will be reflected in the database – all of its instances and settings are represented in the content database – which is the main place of the system’s operation. T (...)

(...) A simple Invoice cost workflow was created that can be downloaded from -> Invoice processing.   Fig. 2. The Invoice workflow   From the “Registration” step comes the “Submit to analyst” path that contains the rule checking whether to the given invoice document a paper scan with attachment is added. If the attachment is not added, the user (...)

(...) new activation data.   The procedure for changing the license from Express to Enterprise Below there is the instruction on how to migrate licenses from Express to Enterprise. The first step is to deactivate the Express license service.     Next, click the “Deactivate” button – two options of deactivation appear on the screen:   &nb (...)

(...) menu. Otherwise, when you try to save you will receive a message:   Fig. 3. The error message   Business case A Car reservation workflow has been configured. At the first step select: Driver – a Peron or group field Start and end date of use – a Date and time field Car – a Choice field A car driver can be selected by entering a fragment of (...)

(...) t has been registered in the system, a certificate for each user will be generated.   Business case Workflows and forms First, configure the Training workflow. It contains two system step s – start and finish and one intermediate step .   Fig. 1 Training workflow   On the form, several form fields that store data about the training and users have been def (...)

(...) o refer to data recorded in this workflow in other processes, you must create a BPS data source and select the newly created invoice process, specify a form type and select the “Archived” step in their configuration. The following screenshot shows the form view at the registration step with examples of completed data. The “Contractor” field is selected from the dictionary. S (...)

(...) e order form the supplier is selected from the dictionary. The supplier’s dictionary contains information about the language in which you should contact the supplier. On one of the workflow step s, a transition path is available on which the order will be automatically generated and sent to the supplier.   Fig. 4. An example configuration of the templates for the selected lang (...)

(...) s in a format that can be used for calling the Microsoft Graph method. Our technical form field prepared in such a way can be passed when creating a group like so:     The last step in the configuration of the action creating the Office 365 group is the configuration of response processing after calling the Web service method. In the “Response” tab, the ID of the cre (...)

(...) ored ID (AttText4) a field in which the file ID is stored Item URL (AttText3) a field in which the file name ([$FileRef]) variable) is stored   After moving to the next step , the workflow has the following actions defined: Update status – updating the Status column in the library Insert BPS link – saving the link to the WEBCON BPS instance (...)

(...) ments database can be created during the installation of the WEBCON BPS environment on the server. This can be done after creating the content database, on the “Content database creation” step . In the upper part of the window there is the ability of changing the connection parameters with the configuration database. The bottom part allows for selecting a process database that will be conne (...)

(...) the instance and form fields value and the WFHistoryElementDetails table – information about values from the “Item list” form field. Every time when the instance goes to the next step in the workflow, in the WFHistoryElements table a new entry will be created. If the form has the “Item list” form fields, the same will happen in the WFHistoryElementDetails table. Rel (...)

(...) instance preview will appear on the right.   Fig. 1. The instance view in the compact form   Description A simple invoice cost workflow was created. It consists of three step s – Registration, Waiting for scan and Archived. A document can be registered both with a scan or without a scan.   Fig. 2. Invoice workflow   The global form template (...)

(...) rdquo; -> “Advanced mode”. In the configuration select the field to which the formatting should be applied (in our case this is the Start field).     In the next step , insert the JSON code of the solution – this code adds the object to the right of the column value containing the icon and the inscription that it also a link. In the case of the icon, one of t (...)

(...) ty of entering such data as the company name, Tax ID  number and contact data (phone number, address..). The saved data will be stored in the Companies table.     The next step is to configure the data row form field where you will refer to the Companies table. The columns you define will then be used to create the footer content. The SQL query should be defined as follo (...)

(...) 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 simple vacation request workflow has been created and then, a new instance in the system has bee (...)