(...) country code}@group.bps Name: WEBCON {country code} Fig. 2. BPS groups configuration Process privileges In each process you can grant privileges such as start new instance s, access to all instance s or administrator’s privileges. When configuring business entities, it is required to create as many groups as business entities existing in the respective process. &nb (...)
(...) standard WEBCON BPS web services (BPS Web API): [BPS Portal URL]/api -> e.g.: https://www.mycomapny.com/webconbps/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 . (...)
(...) d collection. Fig. 1. For each operator The operator iterates over the collection elements, which can be an item list, any data source, attachments 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 item lists in the process. All col (...)
(...) tion Here, create SQL query to WFDataAttachmets table returning ID of the attachment sent for signature. In the respective case restrict searching to searching with the current instance ID, check if the file belongs to “To be signed” category, and make sure it is not deleted. Figure 8. Authentication configuration In the authentication sec (...)
(...) SQL aliases applied, changing configuration. Each variant consists in transferring data bases by creating backups, transferring them to a new server, and their recreation on a new SQL instance . Before you start, stop WEBCON BPS app in the Internet Information Services (IIS) and WEBCON WorkFlow Service. New server has the same name as the old one The operations to be performed (...)
(...) the document templates process. Select the appropriate file from the available list of templates. After following the path, the attachment will be visible on the workflow instance s in the Attachments section. The attached decision will be automatically filled out with the data entered on the workflow instance . Just click on an attachment to preview i (...)
(...) https://ola.hallengren.com/sql-server-index-and-statistics-maintenance.html The MaintenanceSolution.sql script is available in the Download section. Download and paste it into the SQL instance in the new query window. Link to download the script directly: https://ola.hallengren.com/scripts/MaintenanceSolution.sql Run the script in the context of the database where the lo (...)
(...) forms, reports, etc. not only tailored to the user's preferences, but also aesthetically diverse. However, if the user would like to further distinguish the information contained on the workflow instance s or highlight specific items on the form, emphasizing their significance, the option to style form field names and field values may come to their aid. This article presents methods for customizing (...)
(...) igure this connection parameter, without having to modify the configuration of the Microsoft Azure Tenant application. Note that the Files.ReadWrite.All permission is broad (access to all OneDrive instance s in the organization) and may violate the company’s security policy. Permissions for selected site collection An alternative configuration of the Microsoft Azure Tenant app (...)
(...) pp context type and has App.Odata.Read.All permissions (example below). In all WEBCON BPS processes that you wish to load data from, add Metadata Access at Application level and Access all workflow instance s (excluding attachments) at Process level for the user defined in the API application above (the Application’s login will be available as a user in the privilege settings). Launch Power BI an (...)
(...) p; The logic of execution of actions and operations on path The following actions are run precisely at the place they were embedded in the automation flow: Menu button, On browser opening, Upon instance deleting, On timeout, On attachment add, and On start (cyclical). In their case the “Pending in transaction” and “Pending after transaction” modes are ignored. The above-me (...)
(...) quo;Chart”, or “HTML” form fields. Additionally, archiving does not include custom controls, as well as form and business rules. The visibility of an archived instance is another important matter. In such case all the fields visible just before the instance is moved from the content database will be visible after archiving (if some form fields were hidden on the fi (...)
(...) icon. One of the options available here is Show context item form – when selected, it displays a panel on the right side of the screen with a preview of the instance to which the e-mail relates. On the other hand, selecting Actions will expand the list of the following actions: Show BPS Por (...)
(...) in browser box is unchecked. Paths are selected from the paths defined in the registration step of the given workflow. Mappings – this section allows you to set the value of the newly created instance . Here you can use data available directly in the e-mail, such as sender, body, etc. Dragging the selected message or the selected attachment onto the tile creat (...)
(...) ON BPS system, and indicates modules linked with particular roles and presented in the “Running modules” report. Process databases Process databases are content databases that store instance s of the processes created in the WEBCON BPS system. The majority of the service roles operate within the framework of such databases. When performing a role, a service processes the data included in (...)
(...) WEBCON BPS User CAL – the user may access all processes and applications built in WEBCON BPS (as long as they have the necessary privileges). This access involves the ability to create new instance s, edit and save them, move them to other steps via paths, and browse reports and applications. Through this license, a specific number of users (determined by the number of licenses) will be able t (...)
(...) Portal window, the content of the entered information/message is saved, and a header appears above it, stating its author and date of entry. Fig. 2. Information saved in the workflow instance Once the entered information is saved, editing it is no longer possible. Even if you redirect the task in the workflow to its author, the user cannot modify their entry. The user is left (...)
(...) g a button is analogous to adding a new automation: After adding the button, configuring automation and visibility, the newly created button will appear in the menu when the workflow instance is in edit mode. If you need to configure many automations, and thus add multiple Menu buttons, a drop-down list called User actions containing all user-defined buttons is automatica (...)
(...) not recommended to use this type of source as a dictionary for the Dropdown list. As previously mentioned, an appropriate form has been prepared for the process. One of the workflow instance fields is a Choice field named “Participant” fed with the newly configured data source “Most current user profiles”, set as a Popup search window : The Ad (...)
(...) ased on barcodes in attachments” A workflow named “Agreement” is created where a .pdf document containing an agreement is generated. The document includes a barcode of a workflow instance in which it was created. Once a client sends an e-mail containing such an agreement, its scan along with client’s signatures is added to a workflow instance of such an agreement. Each .pdf atta (...)