search results

(...) l steps: Start – filling in basic information about a document, selecting a number of stickers to be printed (one sticker by default). After going through the “Print the code” path , the action of printing a sticker is executed. Wait for scan – waiting for a document scan. After pairing, the scanned document is added as a PDF file and the form goes to the next step. W (...)

(...) Applies to version: 2021.1.x and above; author: Konrad Wojtycza Introduction Workflow control (Branch) allows to redirect a workflow instance along a selected path . With the help of the workflow control step, we can among other things set the logic of: • skipping steps, • assigning a task to other people, e.g. in the case of approval, • withholding instances in step unt (...)

(...) ;Processes – processes 9.    WorkFlows – workflows 10.    DocTypes – forms 11.    Steps – workflow steps 12.    path AndTasks – path s and tasks 13.    Attributes – form fields  14.    SubAttributes – item list columns description 15.    Actions & (...)

(...) he main page of WEBCON BPS Portal Go to the page of the test application Create a new instance in the test process. 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. St (...)

(...) o configurate new application elements. The article presents both required and optional information that will help you to add configuration components, such as: Form field Step Transition path Report BPS group Action – general Action – form validation Action – e-mail notification Hardcopy template Privileges  Glossary of basic terms Below y (...)

(...) h similar information appears at the top of the page. Fig. 10. Information about acting on behalf of the Replaced person. If the Substitute makes any changes to the form or goes through the path , their personal details will appear in the Modified by section of the Info panel (see Fig. 10). Examples of other places in the system where the Substitute's personalities are available in the co (...)

(...)   What will change in my system after the update? Any trigger that has 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. Attachments menu actions are the exception, these will remain unchanged and actions on this trigger will not be migrated (...)

(...) 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.   (...)

(...) ields | WEBCON BPS   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 (...)