search results

(...) ;The action configuration the For each operator   Use case One example of using the For each operator can be the process used to manage a marketing campaign. The process consists of two workflows : Marketing offer workflow – the workflow is used to start and monitor ongoing marketing campaigns. A user registers a new campaign and in the next step fills out the details of the offer. (...)

(...) splay a dialog box with matching items that can be used in the rule (Fig. 2). The dialog box list includes, among others, form fields (groups and tab panels), global and process constants, companies, workflows , and form types. The given item can be selected by navigating with the up/down arrows and confirming the selection with the Enter key.   Fig. 2. The dialog box list after inserting a f (...)

(...) uo;Move to external network location” mode is selected, it is possible to choose one out of the two available modes for creation of ZIP packages: Instances of the main workflow and its subworkflows in one package – both the main workflow and subworkflows instances are exported to one common ZIP package. Instances of the main workflow and each subworkflow packaged separately – the (...)

(...) ection parameters window, the system authorizes via the browser.   Using the add-in The options available at this stage are: New – allows you to create shortcuts to selected workflows and start new workflows in WEBCON BPS based on e-mail messages.   To add a new shortcut, click on the plus icon located in the Add field. The tile configuration window will open, in whic (...)

(...)   E-mail/MailApproval inbox monitoring Two functionalities under one role: e-mail inbox monitoring is a functionality that uses the hotmailbox option (triggering automatically workflows or adding files based on e-mails sent to an inbox configured in the hotmailbox). In the configured intervals a service sends a query to such an inbox and checks the messages it holds. Depending on th (...)

(...) of these licenses assigned to a user enables them to use exactly one process built in WEBCON BPS. This process must be designated by the administrator in the settings and may contain a maximum of two workflows . Single-Use Access License – this license type works differently from all other access licenses. Single-Use Access Licenses are purchased in advance and contribute to a pool of pre-paid oper (...)

(...) Applies to version: 8.1.x and above, author: Martyna Kubiak   Functionality description With WEBCON BPS users can now create HotMailBoxes. A HotMailBox automatically starts workflows or adds files to them whenever an e-mail message is delivered to an inbox configured in it. A HotMailBox can operate in one of the following modes: • “Start one workflow for each e-mail” (...)

(...) Applies to version: 8.1.x and above, author: Martyna Kubiak Functionality description With WEBCON BPS users can now create HotMailBoxes. A HotMailBox automatically starts workflows or adds files to them whenever an e-mail message is delivered to an inbox configured in it. A HotMailBox can operate in one of the following modes: “Start one workflow for each e-mail” “Star (...)

(...) Applies to version: 8.1.x and above, author: Martyna Kubiak   Functionality description With WEBCON BPS users can now create HotMailBoxes. A HotMailBox automatically starts workflows or adds files to them whenever an e-mail message is delivered to an inbox configured in it. A HotMailBox can operate in one of the following modes: “Start one workflow for each e-mail” & (...)

(...) ATTACHMENTS section of a workflow instance – attachments are sorted By name   The Related attachments option, on the other hand, allows you to configure how attachments from related workflows are displayed in the All attachments tab. The configuration window opens after clicking on the crossed tools icon available next to the option name (see Fig. 1. ƒ).   Fig. 3. Linked do (...)

(...) application administrator, and a user who has been granted the privilege Designer Desk edit in Portal directly in the process configuration. Expanding the node of a given process displays the workflows belonging to it. In the case of the "Execution of Investment Projects" application, one process and one workflow are available. Fig. 5. Process Design node of the „Execution (...)

(...) urrent state, in alphabetical order, just like in WEBCON BPS Designer Studio. When you click on an application, a list of its processes is expanded, and when you click on a process, a list of related workflows is displayed.   Statistics of selected applications   Each such data set contains the following information: Number of instances Active instances, i.e. instances out (...)

(...) large databases.   Summary The new approach to assigning tasks to groups of users responds to the needs of dynamically evolving labor market. It helps companies to easily manage staff workflows both inside and outside the organization. While preserving the option allowing users to apply the previous approach, the new functionality focuses on simplifying process configuration as much as poss (...)

(...) tional projects… and prizes, of course. Second, a didactic mission. The students turned into company workers for a couple of hours to implement a system that automates processes and document workflows . Their task was to investigate the topic of the processes they had drawn, describe it, and save it in the BPS notation using the WEBCON BPS Designer Desk tool. The projects were evaluated by the (...)

(...) nces and dictionaries, information about attachments, tasks, companies, currency exchange rates, translations. They can also read parts of tables that store configurations of applications, processes, workflows , steps, forms, actions. The full list of granted accesses for bps_user can be found in the [dbo].[proc_GrantLowPrivileges] procedure definition. The introduced restrictions are justified & (...)

(...) single task assigned to multiple people, a few task configuration settings are all that is needed. But when entire sets of activities, instructions, and decision logic must take place in parallel, subworkflows are necessary. The vast majority of subworkflow scenarios are easily handled with out-of-the-box functionality, but there are a few situations that have arisen that warrant special coverage &ndash (...)

(...) to the language of BPS. Participants of the classes had individual work environments at their disposal. The principles of the system operation and the different "drawing language" of the workflows were not difficult - they were considered intuitive and easy to use. The only obstacle we had to face was too little time. Student Juvenalia and the European Games taking place in Krakow slightly thw (...)

(...) onfiguration and functionality of the full version of WEBCON BPS, this tool enables you to: gather requirements on the basis of which processes will be designed, create prototypes of document workflows (using "drag and drop") test and modify prototypes, design analyses and reports, generate prototype documentation, publish the prototype in WEBCON BPS Designer Studio, communicate (...)

(...) h-time authorization requirement has been set. The code received is then used to authorize the simultaneous movement of multiple report elements through that path.   Path transitions in subworkflows The functionality of path transition authorization affects how automatic subpath transitions are handled, i.e. when an instance is started in a new workflow or subworkflow, for example, by trigger (...)

(...) action [LINK TO ARTICLE] or quick paths [LINK TO ARTICLE].  Furthermore, if you have already shared your location by traversing the parent workflow, the system will not require it again for subworkflows regardless of their configuration. In the opposite scenario, where the mentioned functionality is not enabled in the parent workflow path but is enabled in the subworkflow path, sharing the location (...)