(...) o receive a group review of expenses instead of individual tasks. Let’s create the simple application that allows our employees to register individual business expenses. It will contain two steps : Registration of business expenses (steps : Registration – Waiting for settlement (system step) – Archives/Rejected Settlement of business expenses (steps : Registration – Wai (...)
(...) d Active (checkbox form field with yes/no option). You can also add additional form fields. The dictionary process uses only one Start step and in WEBCON BPS Designer Studio we cannot add any further steps to the workflow. However, you can add your own paths and actions on them and create a simple process (ex. attachment approval process). Only one attachment can be added to each workflow (...)
(...) he process and is updated whenever the configuration of the dictionary process is changed. The dictionary process uses only one Start step, and in WEBCON BPS Designer Studio we cannot add any further steps to the workflow (the “Workflow designer” tab and the option to add a step from the “Configuration and steps ” tab are blocked). The dictionary process also prevents you from ad (...)
(...) Applies to version 2019.1; author: Agnieszka Mazur Introduction In WEBCON BPS processes are divided into stages named as workflow steps . Each stage has tasks – collection of actions which need to be performed for the form to easily move to the next step. Assigning tasks makes sense if the user can fill the necessary data and send form to the next step in a short time. However (...)
(...) ut business entity, substitutions and implemented GDPR solutions) Workflow graphic presentation Form types and acronyms Instance number Form field summary Process privileges Workflow steps Moreover: Constants (local and global) Business rules Action patterns Filling in the documentation After generating documentation in WEBCON BPS Designer Stu (...)
(...) base size evaluation, the user must take the following into consideration: Volume of workflow instances registered daily Complexity of the form (number of form fields, item lists) Number of steps in given workflow (every path transition is recorded in the instance’s history) Number and type of actions used in the system (e-mails, changing field values, launching subworkflows) Averag (...)
(...) figuration will be displayed. Tooltips on paths Another important part of making task processing a bit easier is placing tooltips on paths on specific workflow steps . To add them go to specific step configuration and in “Paths” tab provide description in “Path description in tooltip” field. After placing the poin (...)
(...) nts) you can use the HTML language. Fig. 2. The configuration of the step description The position of the tasks displayed on the form and their visibility at individual steps can be configured on the global form template. Fig. 3. The “Task details” section on the global form template Task description Task descriptions allow yo (...)
(...) ter checking if there are still people who have not approved the instance on the “Approval path”, will return the instance to the “Purchase order approval” step or to the next steps (Fig. 8). Fig. 9. The flow control step The SQL query in the flow control step returns 1, if there is a person who has not approved the instance on the “Approval& (...)
(...) Fig. 11. The form rule on the form field change Summary Breaking form settings inheritance is most often used to change the settings of the form fields’ order on steps or item list settings. However, if you decide to overwrite the form field settings – it is a good practice to describe it in the form field documentation (Fig. 12). Fig. 12. D (...)
(...) Introduction The „Analysis” tab available in WEBCON BPS Designer Studio allows you to see the time of the instances being in a given step and the time of their edition at individual steps . You can also set the planned time of editing an element and the time in which the element should be in a given step. It allows you to check if individual people with the assigned task do not hol (...)
(...) tion used for equipment rental (IT and office) has been created. The main process generates a contract ready to be signed. The Equipment rental process consists of several steps . An employee selects the equipment, fills out their data and goes to the control step (here, depending on the type of equipment rented, the request goes to the IR or HR department). After approval by (...)
(...) low used to register an order has been created. The presentation of the form rules used has been realized on the “Registration of purchase order” and “Purchase order approval” steps . Fig. 4. The registration of purchase order workflow Adding the form rule triggered on a button To properly configure the form rule invoke on the form, go (...)
(...) eb browsers and browsers with Android and iOS. The simple workflow is used to support the offboarding process when an employee leaves the company has been created. The process consists of several steps such as revoking privileges to the IT systems and signing the appropriate documents. You can use the Handwritten signature form field to sign a document. Fig. 1. The workflow &nb (...)
(...) n and form fields matrix level: Fig. 5. Configuration tables related to the form fields matrix level WorkFlows – it describes the configuration of workflows WFsteps – the configuration of steps WFStepForms – the configuration of the form types on the individual steps and workflows WFStepFormFields – information about requirements and editab (...)
(...) advanced rules that will redirect the user to the new portal address. Rules are created using regular expression 14. Changing an entry in DNS After completing and verification of all steps , change the entry in DNS and redirect to the new WEBCON BPS StandAlone environment.
(...) n additional information about a business entity (such as KRS number or address) based on the NIP number. Fig. 1. The workflow The workflow consists of three steps : Input data – a user enters 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 (...)
(...) dard areas – responsible for the visibility of the elements on the information bar and in the form menu (to bar above the form). Every form field is definable separately in the subsequent steps of the process (except for steps of the workflow control type). It means that, if for example on the registration step we can show 3 of 5 elements and then on the second step additional two. Importan (...)
(...) he workflow paths directly from here. This article describes how to configure the application and add a list of available paths in the form menu. By default, buttons used to change the workflow steps are located at the bottom of the form. Fig. 1. The WEBCON BPS form When forms are complex with many different form fields, it is often necessary to scroll to the bottom (...)
(...) when implemented? In this article, we assume you already have an application for handling Cases. If you do, open it and follow the tutorial. If you don’t have it, you can still replicate the steps we explain in another application you have available. In your application, you will configure a form field for the Contractor to be shown only if the user marks the Associated with contractor che (...)