(...) s. First, choose the path where the export package should be saved. You can enter a package description if you wish. Fig. 2. Export wizard information window In the next step , the wizard verifies the exported application. In case of any irregularities, the system will provide information about them (click on the red icon) and will not allow you to include the specific ele (...)
(...) in the expression editor Business case As you can see below, users copied to the “Approvers to notify” form field will receive an e-mail notification at the “Approve” step . A person who fills out the Analytical breakdown list can decide to whom the notification will be sent by deleting people automatically added to this form field. Fig. 2. Users in th (...)
(...) et) to submit a leave request. Fig. 1. The "Leave requests" workflow Configuration of the action The action was added at the “Register request” step on the “Import data from attachment” path. Fig. 2. Selecting the action from the "Excel, Wrod & PDF" section In the advanced configuration of (...)
(...) s Code 128, EAN-13, QR Code, UPC-E. Operation of the “Read a barcode” action The operation of this action was presented on a simple “Barcode” workflow that contains two step s – Read a barcode and Archive. Fig. 1. The Barcode workflow form We have added the action to the “Read a barcode” path. The “WEBCON code” (...)
(...) d persons. On this workflow, it will be possible to generate a Word document containing data from the card. Fig.4 . Worker card workflow. In the form of the starting step , the employee's data should be completed (view of the form later in the article). After entering this data, the card is registered with the path "Register card", where it is possible to (...)
(...) specific document or folder, and prints the barcode. Then the file is scanned and in PDF format is sent to HotFolder, and based on the sticker code is placed in the related instance. At the next step , the text layer is applied to this attachment so that you can search for it later. The search is based on the SOLR search engine – the use of SOLR technology allows the user to narrow down the (...)
(...) sion: 2021.1.x and above; author: Konrad Wojtycza Introduction Workflow control (Branch) allows to redirect a workflow instance along a selected path. With the help of the workflow control step , we can among other things set the logic of: • skipping step s, • assigning a task to other people, e.g. in the case of approval, • withholding instances in step until the conditio (...)
(...) iguration – report views 8. Processes – processes 9. WorkFlows – workflows 10. DocTypes – forms 11. step s – workflow step s 12. PathAndTasks – paths and tasks 13. Attributes – form fields 14. SubAttributes – item list (...)
(...) s has been created. Access to individual contracts depends on the confidentiality level, which can be changed. Fig. 1. The “Contracts” workflow At the first step , a user adds the contract to the workflow as an attachment. Then, the instance goes to the “Archive” step , where the current contracts are located. You can withdraw or restore the contrac (...)
(...) lt; 440 000 Simple arithmetic reveals that the Business B installation may require more intricate infrastructure than Business A. When employing more complex application activities (number of step s, conditions, approvals) to the invoice assignment process, comparing to the absence registration application, we may come to conclusion that scaling WEBCON BPS based only on number of users is inade (...)
(...) ormation required to configurate new application elements. The article presents both required and optional information that will help you to add configuration components, such as: Form field step Transition path Report BPS group Action – general Action – form validation Action – e-mail notification Hardcopy template Privileges Glossary of basi (...)
(...) d path and the user will be provided with a summary. You should remember that: a quick path will be available only when all marked instances are at the same step . instances are processed individually – an error in one instance does not interrupt processing of the remaining elements. When elements are processed, a browser window should stay open. (...)
(...) es Once the task is completed and the path is traversed, the workflow instance is marked as Modified by the Substitute and forwarded to the person to whom the task is assigned in the next workflow step , or proceeds to the final step . Tasks completed under a Substitution are always signed with the Substitute's name. This is visible in the Instance history: Fig. 23. Instance history &nd (...)
(...) igner) will help keep large batches of actions organized. Conditions within automations can be used to either supplement or replace existing execution conditions – similarly to a Flow Control step , they can direct automations to carry out different sets of actions depending on some condition. In earlier versions, the execution conditions did the heavy lifting in terms of determining which acti (...)
(...) reasons, for example, may turn into an overdue task, the CPO can easily plan the department dynamics, support the performance of the department workers and monitor their progress. The first step when preparing a mass e-mail notification is to create an e-mail notification template. Mass e-mail notification template In the “System Settings”, “Global Parameters& (...)
(...) oved leaves in the absence process, but there are more possibilities - the process described below allows you to manage employees from the level of the production line. Application At the first step , a line supervisor assigns tasks to employees, completes necessary data (such as line number and production type), and starts an instance. Fig. 1. An example application instance (...)
(...) tity. Figure 1 presents the exemplary configuration for WEBCON BPS PL business entity. Fig. 1. Business entity configuration in WEBCON BPS Designer Studio The next step is to create BPS groups and assign users their users. See: BPS groups in Standalone installation type. Figure 2 presents the list of created groups. When configurating groups the following format (...)
(...) ilustrated on the example of entering an invoice document into an external system. An invoice is registered and approved in the WEBCON BPS system. In the "Accounting Verification" step an invoice entry into the external system is invoked. The user invokes the entry by using the WEBCON BPS system. Such entry is made by invoking a synchronous WEB Service at the "Entry i (...)
(...) ;Field matrix - setting the "Justification of need" form field Fig. 9. Field matrix - setting the "Department Head's consent" form field The next step is to set the rule limiting the requiredness of the "Justification of need" form field in the "Editability and requiredness" tab.The rule below returns TRUE when the total order a (...)
(...) n. The process consists of two workflows: Marketing offer workflow – the workflow is used to start and monitor ongoing marketing campaigns. A user registers a new campaign and in the next step fills out the details of the offer. If you follow the Offer created path by using the for each operator and the Start a subworkflow action, the Marketing request subworkflow will be started for each (...)