(...) (timeout) may be exceeded. The case below shows us how can we deal with this problem by using only the standard WEBCON BPS functionalities. You can create a queuing mechanism that will update ten document s at a time. Business case We want to create the application “The settlement of business expenses” that will allow our employees to settle individual business expenses. Due (...)
(...) o with REST API. We can also use it to: Download and modify attachments Delete instances Download tasks for users Download information about processes and a lot more The full document ation in the swagger form is available at: [Portal_address]/api and in the version with SharePoint at: [Portal_address]/webconbps
(...) process will appear on the screen. The only difference compared to the standard process is the Instance number, which is its GUID by default. This option is available only in dictionary processes and document template processes. After entering the process name and completing the remaining information, click OK to create a new dictionary process. After creating the dictionary (...)
(...) t a HTTP method, if creating a new user set it to POST: Next step is transferring the user object in JSON format, form field list of the user workflow is available in Graph document ation. If you want to transfer response data to the BPS instance a Response tab configuration is also required. When invoking Graph, value loading will fail if the JSON (...)
(...) Below you can see the form view in the described „Acceptance” step. The task was assigned to all users in the Approvers group. After accepting the document by one of them, it stays in the same step, waiting for the second approver to complete the task. The form will display a different icon next to the name of the user who completed the task: (...)
(...) 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): 3x Choice field (1x dropdown, 1x autocomplete, 1x SharePoint Picker) (...)
(...) It is used to search for all elements such as: those returned in the “Search application” and “Search in navigation” search windows instances created in WEBCON BPS document s attached to the workflows You can search for document s by the content of the document or attachment without worrying that you do not know the instance’s signature or the attachment’ (...)
(...) the step in “Description” field. For more information about this functionality, see Task details. Adding process instruction on the form Place a PDF document with the instruction somewhere on the internet – to do that you can place it on SharePoint and copy the file location. In workflow information paste address in “Link to user manual&rdqu (...)
(...) on the completed form field values e.g. after selecting a specific option in a choice field or the description is to appear in a place other than the standard one User manual – is a separate document that describes the method of working the workflow. A link to this instruction is defined in WEBCON BPS Designer Studio next to the name, acronym and workflow description, and will be visible in the r (...)
(...) Applies to version 2019.1; author: Konrad Wojtycza Introduction From the point of view of business requirements, a common need is the approval of the document by people on the designated approval path. WEBCON BPS introduces functionality that simplifies the configuration of your approval workflow – a list of items. A person authorized to approve can edit only the line to whic (...)
(...) 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 document ation (Fig. 12). Fig. 12. document ation – information about breaking inheritance at the step
(...) ances (without knowing their ID number) and viewing reports. This article describes the methods of configuration the instance number and 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 th (...)
(...) Applies to version 2019.1; author: Józef Cyran Introduction WEBCON BPS allows you to generate/update Word document s (e.g. invoices, contracts) based on a template that inserts data from the system (e.g. data from the workflow instance that caused the file to be created) and also convert them to PDF (if necessary). To do this, you need our Word add-in to be downloaded from WEBCON BP (...)
(...) Applies to version 2019.1; author: Tomasz Pytlak Introduction Working with attachments is one of the basic functionalities in WEBCON BPS. Some processes, such as document repository, are only used to catalog and make files available to selected users. In others, the attachments may be of secondary importance. For example, when you want to work on a file together with your client, a (...)
(...) s to version 2019.1; author: Dawid Golonka Introduction WEBCON BPS helps you embrace the digital transformation by giving you many options for working with electronic versions of document s and replacing standard signatures with their digital version. This article describes the new Handwritten signature form field (available from version 2019.1.4.) that allows you to add your handwritt (...)
(...) py PO to attachments” path, the action of adding attachment has been configured. Fig. 1. The "Ivoice" wokflow The Invoice form allows you to select a PO document (in the “Select PO” field) from the “Purchase order” workflow (Fig. 2). If you select the “Based on instance ID” query, the attachment will be downloaded from (...)
(...) es to version 2020.1.3; author: Mateusz Syrek PDF version Disclaimer Every installation of WEBCON BPS is unique, and may face certain challenges not covered here. Therefore, this document should be treated a general set of guidelines and not universal dogma. The scenario presented here was tested and used to deSharePointize our Support Portal http://support. webcon.com. (...)
(...) , POST, PUT, PATCH or DELETE). In this case, we use the GET method. In the “Custom headers” tab, you can add additional header parameters according to the requirements included in the document ation of the selected API (in this case – host and API key). In the “Filter mode” tab, you have two options – Using BPS and Using Web Service. Filtering on the BPS side wil (...)
(...) e AD, Google – BPS Auth Preparation As an example, a configuration with Azure AD authentication was presented. The configuration for other providers is available in the official project document ation https://oauth2-proxy.github.io/oauth2-proxy/docs/configuration/oauth_provider. nnsm installation nssm is used as a tool for installation nginx and oauth2-proxy as a Win (...)
(...) f over saving of matrix configuration was discussed. Content of WorkFlow form may differ depending on many elements, differences may occur at: 1) Step in which the document is 2) Role of the person browsing the document (author, person with the task, read-only, superior or HR department) 3) Values (for ex (...)