search results

(...) Hi Community, After the deployment of version 2021.1.3.178 the subworkflows that start after a flow control step are no longer working. I have multiple cases in my company where I need to use a flow control step to evaluate if the subworkflow should start or not and it stopped working after I got the update. I don't know how to fix it or come up with an workaround and I'm awaiting on the support. (...)

(...) Hi, I have this situation: - one main workflow - 4 different subworkflows that must start in parallel and wait until all subworkflows are done. I tried with Start a subworkflow action, but works for a single subworkflow. I don't want to use hyperlink. I must enter on the subworkflow in the start step. Is possible to start different subworkflows from a main workflow with SQL? I don't have an item li (...)

(...) kflow form(Sub Workflows start on a specific main workflow step) Sometimes I have to change one of the filed value on the main workflow( on step " Wait for sub-workflows) which is displayed on the subworkflows form. When I change field value on the main flow, the same field is not updated on the subworkflows form despite it is the same field. Do you know how to update the field on the sub workflow where (...)

(...) Hello everyone, I am new to Webcon so it might be a dumb question. Anyway, I am trying to create an App where one Department starts one Workflow that creates subworkflows for several other departments. The main Workflow should be able to see the current status/step of every subworkflow. But with what I did, I am getting 2 Errors [Form] "Failed with an unknown exception Fehler-ID: d1a18cc6-c67d-43bb-b883- (...)

(...) Hi Community! Is there any possible ways to start subworkflows from Excel file? Business case is that, I have MS Excel file with estimated 500 rows. I want to attach sheet to attachments section and start workflow by path or button on menu bar with starting workflow action. Is any way to do it without special SDK customization? subworkflows should have data from in excel sheet. Every workflow contains o (...)

(...) ing: IF ( /* Number of all child workflows */ SELECT COUNT(*) FROM WFElements WHERE WFD_WFDID = {WFD_ID} AND WFD_DTYPEID = {DT:494} ) = ( /* Number of positively finished subworkflows */ SELECT COUNT(*) FROM WFElements WHERE WFD_WFDID = {WFD_ID} AND WFD_DTYPEID = {DT:494} AND WFD_StatusId = {WSTSPOSFINISHED} ) BEGIN SELECT {PH:2449} END

(...) d “Awaiting Delivery” steps. The action of creating the “Repayment” transaction has been created in both places. To create the repayment transaction, the action of starting subworkflows (SQL) has been used – in the configuration of the action, fields about the process, form type and transition type have been completed in the “Basic” tab.   Fig. 23. T (...)

(...) rent statuses/states (e.g. active data, inactive, anonymized etc.) and this is handled by storing data in appropriate steps The process will need to be integrated with other related processes (e.g. subworkflows ). On the data form, additional information such as data tables, statements (displaying e.g. invoice, vacation and contract data) will be displayed Adding attachments will be necessary When you (...)

(...) rkflow and the “Generate certificate” path have been selected. At the bottom of the window, there is a “Workflows start mode” choice list – leave the default “As a subworkflows of current instance” value. Thanks to this field, on the information panel on the right side of the screen you will see all subworkflows connected with the main workflow. After that you can mov (...)

(...) kflow. In the DET_WFCONID parameter, provide the item list ID from the data originates and the DET_WFDID refers to the given instance ID. After going through the path and executing the action, the subworkflows will be created – in the number corresponding to the number of companies.   Fig. 11. The signatures of started subworkflows   The configuration of the Serial correspon (...)

(...) ds. Data needed to start the workflow should be provided by using the SQL query – this allows to start many new instances of the workflow. The following example shows how to start several subworkflows for several people based on the item list by using this action.     The “Project name” and “Project description” form fields are provided without mappin (...)

(...) he “move back” paths is used, then have execution conditions on other actions return “False” if the value of that technical field is “1”. Cancellation of related subworkflows Additional integration actions. If integration is used in the workflow (e.g. SAP entry, update, cancellation)

(...) 2020.1.x and above; author: Dawid Golonka     Introduction In WEBCON BPS you can create simple workflows consisting of several steps and form fields, but you can also use the subworkflows mechanism. The following article describes the action connected to subworkflows – “Update related workflow instance”. This action allows you to change the value of the form fields i (...)

(...) ice-a-sample-workflow/   c) OCR steps (Waiting for text layer/OCR AI/OCR AI learning) More information -> https://howto.webcon.com/custom-ocr-fields/   d) Waiting for subworkflows More information -> https://howto.webcon.com/action-set-workflow-status/   Characteristic of the system step: Tasks in the step are not “Finished” even if the (...)

(...) configuration should not be used on the transition path or in the action where, in the previous step, the user didn’t have any active tasks (e.g. document registration, system step, waiting for subworkflows , positive and negative final steps, steps related to the scan or OCR processing).   Assign to users who completed tasks in previous step – the task is assigned only to the users (...)

(...) sts) Number of steps in given workflow (every path transition is recorded in the instance’s history) Number and type of actions used in the system (e-mails, changing field values, launching subworkflows ) Average size and number of attachments per workflow instance (document scans, docx, pdf, tiff, xlsx) As an example, we will use a form made up of 20 form fields (all of them are required): (...)

(...) sts) Number of steps in given workflow (every path transition is recorded in the instance’s history) Number and type of actions used in the system (e-mails, changing field values, launching subworkflows ) Average size and number of attachments per workflow instance (document scans, docx, pdf, tiff, xlsx) As an example, we will use a form made up of 20 form fields (all of them are required): (...)

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

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

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