(...) EBCON BPS Designer Studio (Fig. 1). Descriptions will be exported to an Excel file – complete translations and then import the file to WEBCON BPS Designer Studio. To use this tool you must have access privileges to the database of the translated process. Fig. 1. Completing the translation for the “Date of order” form field Downloading the tool and expo (...)
(...) e the type of the form you are currently working on. This action is available only for the Menu button trigger. Example workflow An example workflow for registering contracts 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 cont (...)
(...) View a Search engine report. Test procedure For delivering tests we use the pool of individual user’s accounts. Each and every user holds the following privileges: access to the test application possibility of starting up new instances in the test process Each and every user goes through the full test scenario described above. Test scenarios 1 and 2 are car (...)
(...) are to be presented in the report Report columns Process form fields, system form fields displayed in the report Privileges Given to the person authorised to access the report Optional: Search panel What form fields should be included in the search panel Bulk actions Should the report hold mass actions, (...)
(...) that the Substitute will have. In the case of the first type of substitution (available from version: 2022 R1), the Substitute will be able to act on behalf of the absent user with so-called full access . This means that the Substitute, after switching to the Acting on behalf of mode, will see exactly what the Substitute would see at the same level of access . The Portal view is limited to those (...)
(...) the automation encounters an End or Break with error block. As was the case in previous versions, not every action can be used on every trigger, so automations created on different triggers will have access to different pools of actions. Operators – contains the Condition block that can create branching paths for the automation. Each condition is defined as a Boolean business (...)
(...) e}@group.bps Name: WEBCON {country code} Fig. 2. BPS groups configuration Process privileges In each process you can grant privileges such as start new instances, access to all instances or administrator’s privileges. When configuring business entities, it is required to create as many groups as business entities existing in the respective process. Ne (...)
(...) lled on demand (online) – when the user selects a value from the dictionary in the WEBCON BPS system. This integration solution method is frequently applied and recommended. It ensures fixed access to the updated data. When selecting this method, one should take into account in particular the time-span in which the views respond as it directly translates into the operational speed of the user i (...)
(...) tion section select the previously created connection, set “grant_type” parameter to password authentication, and define the scope, i.e. specify the area to which the application has full access . Figure 9. Request body configuration “Request body” is the next section. Here, attributes determining the name and the description of the query ar (...)
(...) ld “Brief justification for the purchase” appears. The same action in the browser displays “Full justification for the purchase”. The purpose is to keep the form readable when access ed on the mobile app. Form rule executed on value change in the “Justification required” field. For presentation purposes a new request was register (...)
(...) f four columns, three of which include numerical values. The form field presents items requested by the submitter. The request must be accepted by the superior and subsequently by the accountant with access to the above-mentioned item list. Workflow used in the example. Procedure To set up conditional colouring of rows in yellow choose “Purchase order lis (...)
(...) icz Introduction Efficient documentation management is key to the proper functioning of a company. In addition to their proper registration in the system, the incoming documents must be quickly access ible in their original, hardcopy version. To streamline their flow and storage WEBCON BPS offers printout a barcode label functionality allowing users to link data entered in the system with the docum (...)
(...) d reading of files. Permissions for all site collections One of the configuration options is to grant the application the Files.ReadWrite.All permission. It gives the application access to all site collections, i.e. to OneDrive of all users of a given Microsoft Azure Tenant, and allows to indicate any account as the OneDrive Owner when configuring the connection to OneDrive. &nbs (...)
(...) n API application in the Admin panel that uses the App 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 instances (excluding attachments) at Process level for the user defined in the API application above (the Application’s login will be available as a (...)
(...) y took to complete the assigned task and finish the workflow. This article summarizes the most important information on the Instance history in WEBCON BPS Portal and related features. access ibility in Portal History in WEBCON BPS Portal can be access ed from the instance level. To access it, click on the clock icon visible in the upper right corner in Portal. Fig. (...)
(...) ns can be executed on them. Additionally, the “Views” tab does not allow here to add buttons to start new instances in the upper report panel. All business and process administrators have access to the archived elements. What is more, it is possible to add more persons with access at administrator level to all the archived instances by modifying respective process settings (process name &rar (...)
(...) ction Microsoft Outlook is one of the basic tools used by office workers. Outlook Classic and Outlook Modern add-ins are responsible for its integration with WEBCON BPS Portal. They allow users to access their tasks, view the contents of selected forms, and use many other Portal features from within their e-mail correspondence, without having to close the e-mail application. This article describes (...)
(...) : Standard Support maintained until the end of Q2 2023 Extended Support maintained until the end of Q4 2023 Why would you want to update WEBCON BPS to the newest version? access to the newest features – we continuously develop our product, adding more features that make it easier to create processes and increasing the usefulness and ergonomics of the platform for busin (...)
(...) 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 the process database. To access such data, the service must be associated with the process database. Such association is particularly important when there are several databases available. In such case it is possible to associate a (...)
(...) Applies to all versions; Single-Use access licenses available from 2023.1.1 and above. Licensing models WEBCON BPS is currently available in two licensing models – as a subscription or perpetual license paired with an annual Software Assurance payment (which allows updating to newer versions). Perpetual licensing is not usually offered on most modern markets, except for obtaining (...)