search results

(...) necessary data (such as line number and production type), and starts an instance.   Fig. 1. An example application instance   At the “Active” step, the following path s are available: Save line workers - used to save changes Deactivate production - used to deactivate the production line Halt production - used to hold production   Fig. 2. (...)

(...) ig. 12. Business rule output for WEBCON PL   The confirmation of the form operation has been displayed in Figure 13. The WEBCON PL user by going through the “Send for approval” path assigned the task to the group of WEBCON PL user, responsible for approvals in the Polish business entity.   Fig. 13. Business rule 2 output – form view

(...) try into the external system is invoked. The user invokes the entry by using the WEBCON BPS system.  Such entry is made by invoking a synchronous WEB Service at the "Entry into ERP" path . WEB Service transfers given invoices to the external system and in response the ID of a created element is returned. When the WEB Service is invoked correctly, the invoice in the BPS system automati (...)

(...) – 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. If you follow the Offer created path by using the for each operator and the Start a subworkflow action, the Marketing request subworkflow will be started for each row of the Clients item list.   Marketing request workflow – (...)

(...) ard until a number is returned and entered into the corresponding field. The form looks as follows:   Figure 4. Entry form     The “Generate template” path generates a sample agreement document. The document for signature should have a PDF format. Begin with configuring REST connection from REST API Autenti.   Figure 5. API connectio (...)

(...) CON mobile app   In this business case it is possible to standardize data display, e.g. in reports, on transition via brief justification field content transfer to full justification field path .   Summary As demonstrated, the form view varies depending on the device the workflow was started on. The variable “Is this a mobile device?” can come in handy in situations (...)

(...) oad and place the created template in a dedicated process so that it can be shared as a configuration template.     The Generate/Update a Word file action is configured on the path , which in the described example will be used to generate the decision. On the Template tab, in the Document template section, specify the source created from the document templates process. Select th (...)

(...) le should be as follows:     In this case, both subrules will be executed one after the other and both conditions of the parent rule will be checked.   Form rules on path Another important feature of form rules is that in the absence of a defined value return by the rule, it will return FALSE by default. This is especially important for rules executed, for examp (...)

(...) ds / field values, it is worth considering what is actually expected from the form. If you want the appearance of the form to be dynamic and responsive, i.e. to change depending on the entered value, path transition or page refresh, then it will be beneficial to use Form rules. If, on the other hand, you want the appearance of the workflow instance to remain unchanged regardless of the actions take (...)

(...) ng OneDrive In order to share the prepared documentation with colleagues in the department, the advertising agency employee should add an appropriate action on the "Share with coworkers" path from the "Documents created" start step. Three actions dedicated to OneDrive have been added in the system. One of them is the Start editing a file using OneDrive action required in this (...)

(...) en leads to misunderstanding of mechanisms controlling the execution of actions and misconceptions.  To fill this gap, this article discusses the logic applied to the execution of actions on path in “Pending in transaction” and “Pending after transaction” modes and presents a diagram visualizing operations executed before, during, and after action execution.   (...)

(...) or: Krystyna Gawryał   Introduction Instance history is an area where the user can check what actions were performed in the Workflow. History details the steps taken by the user and the path s they 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.   (...)

(...) selected workflow instances. It is possible to run the action in the following contexts: “On entry”, “On exit”, “On timeout”, “Menu button”, “On path ”, “Upon instance saving”, and “On start (cyclical)”. Archived instances retention – the action is used to execute operations on the already archived workflow ins (...)

(...) n the process. Workflow – related document workflow. Start in browser – if you select this parameter and use the tile, the configured process will be started in the default browser. path – option available only when the Start in browser box is unchecked. path s are selected from the path s defined in the registration step of the given workflow. Mappings – this section all (...)

(...) tions on the SharePoint server triggered by actions and data sources supporting connections with SharePoint Server. After configuring an action that, e.g. adds an attachment to the SharePoint list on path transition, the action is executed by the service. It is worth noting here that communication with the SharePoint platform is provided through the service. Additionally, the service executes the (...)

(...) cesses and applications built in WEBCON BPS (as long as they have the necessary privileges). This access involves the ability to create new instances, edit and save them, move them to other steps via path s, and browse reports and applications. Through this license, a specific number of users (determined by the number of licenses) will be able to use the system without limitations regarding the numbe (...)

(...) nions from individual departments or teams. In turn, the Comment field can be used in another step of the process. Enter the required information/message in the form field. After going through the path or clicking Save on the top bar of the Portal window, the content of the entered information/message is saved, and a header appears above it, stating its author and date of entry.   Fi (...)

(...) data returned from Active Directory.   The workflow is configured so that the "Participant" is the person who will receive the form after going through the "Notify" path . Once the required fields are correctly filled in, the form in the final positive step “Particiaption confirmed” will look as follows:   Other application examples and data (...)

(...) son: – starting separate workflows (e.g. for incoming correspondence, submission) that automatically close incoming correspondence document through the “Complete automatically” path , – closing the incoming correspondence workflow by going through the “Complete” path if no other workflows are required, – moving an e-mail to the “Canceled” ste (...)

(...) allows you to define which document, in which workflow and process, and for which company is started (in the discussed example it is the “Cost invoice” document) You also need to select a path the uses to register the document. “Additional form field values” – here you can assign e-mail data to respective workflow form fields, e.g. e-mail sender or title. Full list of a (...)