search results

(...) n the TASK workflow.   Fig. 4. The "Task type" field with example values from the data source   As ID in the “Task type” form field, you should use the instance ID that contains a group of tasks (instance number).   Fig. 5. Process contant - Maximum number of tasks per person   A good practice is to use constants in processes &ndash (...)

(...) mouse. The created form rule is presented in Fig. 3. Fig. 3. The full definition of the form rule with using the business rule   Execution of a form rule depending on data in other instance s/workflows In the business rules, there is the ability of referring to the SQL database and returning the specified data based on the process configuration or documents registered in the system. I (...)

(...) s been enhanced for additional functionalities (a description of the basic report coloring modes can be found here). There is the ability to go through a path without having to view the specific instance – just click on a properly configured cell. This configuration also allows you to set the cell style, as well as special display functions.   Business case An example that present (...)

(...) ou can create a process that contains the history of changes of the important project parameters. Therefore, whenever a key parameter changes, we want to have a mechanism that will archive them in an instance showing the history of changes in the parameters of this project. It involves adding – at each step of each workflow of each process – an action that updates the instance containing the p (...)

(...) The dictionary process The functionality of the dictionary processes has been introduced in version 2020. Along with each dictionary process, a predefined data source is created, which returns all instance s of the dictionary which are marked as ‘active’ via an unremovable checkbox form field.  The data source configuration contains all form fields defined in the process and is updated (...)

(...) above; author: Dawid Golonka   Introduction Workflows created in WEBCON BPS are built of steps and paths which illustrate the various stages of the business process. When directing an instance to the next step, there is often a need to assign a task to a user or group of users. In some cases you may need to finish a task without waiting for the user to do so – you can use the &l (...)

(...) ndash; at least one person has not signed the document WITHDRAWN – document has been withdrawn ERROR – operation error If the system returns the “SUCCESS” status, the instance goes to the “Signed” step.   Fig. 18. The document status   On the “Signed” path, the “Download signed document” SDK action is executed. (...)

(...) ore information about SOLR see -> Portal search engine - how does it work?.   Hint window From version 2020 the quick search hint window has been added to WEBCON BPS Portal. The instance search engine is available from every level of the portal. After clicking on the search field , a quick search window will appear on the screen (Fig. 1). In this window, a maximum of 10 instance s are (...)

(...) s about SMS verification (it is required)   Fig. 5. The “SendEnvelope” action configuration   In the “Waiting for signature” system step, the instance waits for the document to be signed . The “CheckAllDocumentStatus” cyclical action was created to automate attachment status verification and move the instance to the appropriate ste (...)

(...) can be found in the database by referring to the column in which the picture is stored:   Fig. 6. A query calling picture in base64 format   In the way described below, two instance s of the dictionary workflow have been added – each of which stores the company logo. One logo with a black frame and the other without a frame.   Fig. 7. A report storing the dic (...)

(...) using the unique ID (DET_ID). System data that are stored in the WFElementDetails table are e.g.: The date of inserting a row (DET_TSInsert) The date of updating a row (DET_TSUpdate) The instance version (DET_Version) The author (DET_CreatedBy) Modified by (DET_UpdatedBy) Selected keys in the WFElementDetails table: DET_ID – a main key (row ID) DET_WFDID – an inst (...)

(...) nformation is displayed on the form. The article describes the table that stores header data – WFElements.   Relations in the table The WFElements table contains data about all instance s (forms) in the system. They store both system data and form field values defined in the processes. Each workflow instance is identified by a unique ID (WFD_ID).   Fig. 1. The form &nd (...)

(...) S). 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   After adding the document, click the “Send to sign ” path – an e-mail will be sent to the previously indicated people with a request for a signature. These people (...)

(...) Fig. 5. The “Save all” button   Ctrl + G – a.k.a “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 generat (...)

(...) t for business processes in WEBCON BPS, it is important to remember that even the simplest workflow with a minimum number of steps and form fields will be reflected in the database – all of its instance s and settings are represented in the content database – which is the main place of the system’s operation. There are also “virtual tables” automatically created by the system (...)

(...) his field is recommended when you operate with numbers in the range of 0-100 Bold field – a value is displayed in bold Show column – the user decides if the column will be displayed instance hyperlink – after clicking on the given element, a preview window will appear with the hyperlink. For such marked fields, specify which value is the ID of the linked field. This menu is availab (...)

(...) l system elements. They see and can modify all applications form the Designer Studio level. There is no access to data. Business administrators – they have access to edit, add and delete instance s. They also have access to all parts of the process (e.g. archive). Business administrators do not have the privileges of the Designer Studio application. Workflow data read-only access &ndash (...)

(...) rdquo; 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 will be able to decide whether the instance should be moved forward or remain in the current step. To set this rule, enter the “Submit to analyst” path configuration and go to the “Parameters” tab. Then click on the thr (...)

(...) arePoint groups. Date and time – allows you to present and edit date and time Yes/No choice – used to select the Yes/No value. The value of this form field is set by a checkbox on the instance . Choice tree – allows you to display the value in the form of a three and select one of the available options. When adding the picker fields they must be configured in the Advanced confi (...)

(...) it by e-mail.   Description The process will contain two workflows: Training –will store data about participants and the training Certificate generation – a separate instance for every participant of the training In addition, the process uses the Document template process to add a certificate template which will be generated for users. The user will start the proc (...)