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

search results

for workflows

(...) Applies to version: 2020.1.x and above; author: Paweł Drab   When creating large and complex processes, problems with workflows becoming too complicated can often appear, which can be problematic especially for end-users. To check if our process requires reconstruction and simplification, we recommend making an audit of such workflow.   Why should we do a workflow audit? A wor (...)

(...) Applies to version: 2020.1.x; author: Marcin Wiktor   Introduction For applications with a large number of interconnected workflows there is often a problem with performance these applications due to creating/moving multiple workflow instances at the same time. The speed of creating/updating sub-workflows depends on many factors such as the type of the form, the amount of data/actions/ru (...)

(...) s. We can transfer any number of attachments in this way. We also have the ability to copy image files (e.g. screenshots) by using the system clipboard. This functionality can be used in workflows where the user is required to attach some sort of screenshot (e.g. in support processes).   How do you add any image to the workflow instance? After copying the image to the system clip (...)

(...) Content of the documentation Each documentation generated in Designer Studio consists of the following elements: Basic information (process name, version, author, modification date, etc.) workflows and form types in the process Basic process configuration (which includes information about business entity, substitutions and implemented GDPR solutions) Workflow graphic presentation For (...)

(...) ) 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) Average size and number of attachments per workflow instance (document scans, docx, pdf, tiff, xlsx) As an example, we will use a form made up of 20 form fields (all of them are required): (...)

(...) e application elements is as follows:   Native part: Profiles, logins and PIN security support Main panel of the application Navigating by report views Searching Starting new workflows Application, processes and instances lists preview Log history Searching instances by barcodes/2D codes (only iOS) PUSH notifications (only iOS) Webview Authentication Forms of t (...)

(...) all elements such as: those returned in the “Search application” and “Search in navigation” search windows instances created in WEBCON BPS documents attached to the workflows You can search for documents by the content of the document or attachment without worrying that you do not know the instance’s signature or the attachment’s name. An example MS W (...)

(...) th, and task tooltips are a massive help for users to easily understand the concept of WEBCON BPS business applications. Consistently providing tooltips and task details across all your processes and workflows will teach users to rely on these elements to learn about their intended task. This help immensely when introducing new users to your WEBCON BPS applications, creating new applications for veteran us (...)

(...) g the workflow diagram configuration and clicking the “Preview generate” button.   Summary Using the standard task descriptions allows you to give users information about workflows in a consistent manner between different applications. They are not mandatory, but by using them on a regular basis, we can get users accustomed to the fact that, if necessary, they can expect hints (...)

(...) pear (Fig. 2).   Fig. 2. Breaking inheritance of the form fields order   You have two options: This workflow only – this option breaks settings inheritance All workflows – the order will also change in the process tree, settings inheritance is preserved   After breaking inheritance, the button changes its function to the opposite (restore inheritan (...)

(...) Applies to version 2019.1; author: Kinga Bożęcka   Introduction Mass actions allow you to go through the path (and execute the actions that are on it e.g. starting sub-workflows) for many instances at the same time. The article describes the configuration of this action and two examples of use.     Fig. 1. The example process   Fig. 2. The form   (...)

(...) the advantages of defining appropriate signatures for your document management workflow.   Instance number configuration Instance numbers can be defined on two different levels – workflows or form types. However, only one of them will be set by the system (if both are defined at the same time, the instance will be assigned the number defined in the form type).   A simple workfl (...)

(...) bsp; Introduction In WEBCON BPS there is the option to add attachments to the workflow instance by using the standard action. This action works in two modes: Adding attachments from other workflows of the current WEBCON BPS content database, selected based on the instance workflow ID – the “Based on instance ID” mode Adding attachments from other workflows from the external (...)

(...) about the configuration of processes The remaining tables contain the configuration of the process elements are described in sections below.   c) Configuration tables related to the workflows configuration and form fields matrix level:   Fig. 5. Configuration tables related to the form fields matrix level   workflows – it describes the configuration of w (...)

(...) Applies to version 2020.1.3; author: Konrad Wojtycza   Introduction Task creation is one of the basic functionalities enabling the creation of instance workflows in WEBCON BPS. Tasks in the system can be created in the step configuration on a given path or as an action that can be placed e.g. on the entry to the step. This article describes the “Create a task action” action (...)

(...) olution is to add a list of the available paths in the form menu.   Configuration To enable the list of available paths at a given workflow step, go to WEBCON BPS Designer Studio -> workflows -> Field matrix, and select the “Standard areas” tab. Then select the “Path list” option in the step where you want to display the path.   Fig. 2. Enabl (...)

(...) Applies to version 2020.1.3; author: Michał Kastelik   WEBCON BPS offers you several actions enabling integration with the Microsoft SharePoint Online environment and SharePoint workflows. This article describes how to manage these privileges using actions in workflows.   1. SharePoint Site Collection To configure the actions running in the SharePoint Online environment, first (...)

(...) e form rule You can define form field behavior using rules. Here, you will use a rule to create a checkbox for hiding or displaying the Contractor field. Go to the Configuration tab (under workflows), choose Form rules and click on the New rule text. A window will open. Under the header that says General, find Rule name and write in the blank space right to it this name: Show/hide the Contractor (...)

(...) act forms and how to customize them.   Fig.1 Compact form in the preview window   What is a form? On the WEBCON BPS platform, a form is a representation of one of the workflows in the process at a given step of the workflow. A form is made up of its configuration, the form fields displayed on it, and their settings. The form fields are organized in order and position (top, (...)

(...) Applies to version 2020.1.3; author: Michał Kastelik The WEBCON BPS platform enables simple integration with the SharePoint Online environment and your SharePoint workflows.  After defining the connection in Designer Studio, you have many actions at your disposal that allow you to create sites and operate on lists. This article describes actions that enable linking the WEBCON BPS application (...)