search results

(...) ion options.    The configuration of the form consists of 1) form rules that are executed when the form is displayed, 2) visibility settings for the top bar buttons, 3) editing mode, 4) attachment settings, 5) and accessibility settings for transition paths.   Creating a new form configuration The WEBCON BPS platform builds a compact form by default. When you create the main form (...)

(...) ew SharePoint list item will be created when the action is started. Fig.7 The form with the form field ID saved from the action   Fig.8 New list item   Add an attachment to a list This action lets the user add an attachment to the SharePoint list. The configuration allows you to indicate which attachment s are to be added: Category – by default, it is s (...)

(...) EBCON BPS out-of-the-box actions to quickly achieve your goals.   For example, you can set up new sites or create, edit and delete SharePoint lists and its elements. You can also download attachment s from the list or manage user privileges using one of the predefined actions in the "SharePoint user  & privileges"  actions group. To learn about all those features, go here. (...)

(...)   Files to be processed - the service will check all supported file types by default – you can limit them to PDF only or select the advanced filters Template for name of created attachment – you can define the name under which the file will be loaded to the workflow (by default – the name of the file that will be scanned). If you want to change this name, use date tags in t (...)

(...) the user access to all process elements, you can do this on the process level. To do so, go to the “User privileges” tab add the user in the “Access all workflow instances and attachment s” section (or another field of the Access type).   Fig. 10. Granting privileges on the process level

(...) optional; you can set up a BPS account without filling them in. The Approver is selected using a form field of the "Person or group" type (in the “Picker fields” folder). In the attachment s section, in the "User photo" category, a graphic file with the user's photo has been attached. The requirements for graphic files are described later on when we discuss the action&rsqu (...)

(...) d Supported Choose Path (List/SQL) Actions Yes (deprecated) supported until the end of 2022 N/A replaced with the Flow Control step N/A N/A Sign an attachment with Cosign Action Defunct Defunct Defunct Defunct Defunct Will be removed in version 2024 R2 Substitution type MSSQL Data Source Yes supported until the e (...)

(...) t: Instance ID Instance number System elements names (process name, workflow name, step name, form name) Form fields names Form fields’ and items list values Text content of the attachment s Each of these values has a relevance factor attached to it (instance ID – highest, attachment content – lowest) by which the final search result list is being sorted. If searched qu (...)

(...) ory of changes. For a given installation you can create multiple content databases – how many are needed depends on the administration, security, and performance requirements of the platform. attachment s database – a dedicated database that stores all attachment s added to forms (e.g. docx, xlsx, pdf, tiff files). A separate database for storing attachment s is created for performance reasons an (...)

(...) plies to version: 2021.1.x and above; author: Mateusz Klos   The following configuration is for Standalone installation. For SharePoint intallation, no WebDav is used - only the SharePoint attachment library.  Installing an add-on from a file Consider a simple process where the user drops a file into the "attachment s" section and then wants to digitally sign it using the Adob (...)

(...) te instances Modification (can’t delete) - standard privileges to read and edit instances Read - only – privileges to read without editing the instance Read - only (can’t view attachment ) – privileges to read without viewing attachment s   Fig. 2. The "Add privileges" action configuration window   Then, define the users that should be grant (...)

(...) option is used, adding new rows to the list is by default opened in a separate pop-up window in transposition mode (which is also the method that was used in the mobile application):   attachment s The attachment panel (a standard area on WEBCON BPS forms) has also been refined to better match the Modern form. The main function of the panel is to quickly browse all files and e-mai (...)

(...) nbsp; 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 this action, there are two tabs: Att (...)

(...) t the correctness of the barcode reading. Indicate a file from which you want to read the code.   Barcode types Select the barcode standards to be supported by the action.   attachment s: a) Search all attachment s – after selecting this field, all attachment s added to the instance will be scanned. b) attachment name template (regex) – set the name template in the f (...)

(...) pends 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 contract. Privileges to read contracts are granted to people in de (...)

(...) cess. Move it to “Step 1”. Preceded by a 3s interval. Use a transition path that doesn’t trigger any actions. Step doesn’t change. Preceded by a 3s interval. Preview test attachment . PDF format. Use a transition path that doesn’t trigger any actions. Step doesn’t change. Preceded by a 3s interval. Use a transition path that triggers an action that updates an item (...)

(...) s actions defined on it will have a new automation named after the trigger (i.e. “on entry”, cycle name, path name) created for it, and all defined actions are added to that automation. attachment s menu actions are the exception, these will remain unchanged and actions on this trigger will not be migrated into automations. The WFTimeoutActions table will be deleted from the database. It is n (...)

(...) k;   Task assignment with regards to contract type At the first step, a user must register an instance, and assign the appropriate invoice type. They user can preview the attachment and quickly identify the data from the document.   Fig. 4. Form view, step: Registration   Depending on the invoice type in the “Invoice type” form field, the t (...)

(...) onbps/api WEB Service REST allows for, among others, creating new instance in WEBCON BPS editing the existing instance   shifting the existing instance to further step adding an attachment downloading an attachment deleting the existing instance. Initial data import into WEBCON BPS General approach to the initial data import is described in a separate docum (...)

(...) for each element from the selected collection.   Fig. 1. For each operator   The operator iterates over the collection elements, which can be an item list, any data source, attachment s added to the workflow instance, and any collection defined as a business rule.   Fig. 2. Collection type   Item list – the ability to select all available it (...)