search results

(...) Hello, We have 3 environments (DEV - TEST - PROD). We have noticed that in TEST environment the action "Start a subworkflow " does not have the option "Set form field data before defaults evaluation (compatibility mode)" set to visible. In DEV and PROD this option is visible. I attached some screenshots below. Can you help me understand why the option is not visible on TEST environment? And what is t (...)

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

(...) action creates a new instance in the “Transactions” dictionary with the “Payment” form for each row with the “Pre-paid” field selected. We used the “Start a subworkflow (SQL)” action to create the payment transaction. In the “Basic” tab of the action configuration window, the appropriate process with the form type and a path, has been selected. (...)

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

(...)   Fig. 4 Certificate generation form   Action configuration There are four defined actions: On Training workflow Action which starts one Certificate generation subworkflow per participant. On Certificate generation workflow Action which generates certificate in MS Word – .docx format. Conversion of the .docx format to .pdf. Certificate and con (...)

(...) Configuration of the serial correspondence In the process of serial correspondence the contractors who have unpaid invoices will be selected. For each of them, a separate Outgoing correspondence subworkflow will be started, where the payment requests will be generated.   Fig. 4. The serial correspondence workflow   Below there is a screenshot showing the form view on the start (...)

(...) CON BPS allows you to start workflows in several ways. In addition to a manual start by the user, instances can also be launched by the system using dedicated actions.   The “Start a subworkflow ” action The action allows you to start a workflow within the same application. By using them you can start only one workflow instance – in this case it will be creating an additional t (...)

(...) receive an ID, Instance number, and Status. The workflow was correctly started, you can verify the result on the form in Portal:     Call API also started the “Run subworkflow (SQL)” action which has been configured in the first example of starting workflow methods. A detailed description of REST API and WEBCON BPS SDK can be found at https://developer.webcon (...)

(...) 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 subworkflow s 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 subworkflow s mechanism. The following article describes the action connected to subworkflow s – “Update related workflow instance”. This action allows you to change the value of the form fields (...)

(...) 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 subworkflow s 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 subworkflow s, 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 user (...)

(...) 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 subworkflow s) 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 subworkflow s) 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): (...)

(...) going 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 – the subworkflow is used to send a custom e-mail with an of (...)

(...) o a defined network location in ZIP files. The ZIP package consists of a PDF file with metadata on the form state preceding the archiving and an XML file including instances history with attachments. subworkflow instances can be stored in separate packages (one subworkflow – one package) or in one package with the main workflow instances. To use this option it is necessary to define the network locatio (...)

(...) 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 subworkflow s 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 trigge (...)

(...) ass 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 subworkflow s 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 (...)

(...) he data that will be used in it – if we have actors involved in process, and we would like them to have access to only a specific subset of data from an element of that process, we can create a subworkflow form them, and pass to it only necessary information. This will allow more people to participate in a more robust process, but they will not necessarily have access to every piece of information t (...)

(...) I have a structure where a meeting (parent workflow) has many Agenda Points (subworkflow s). On each Agenda point, I have (inter alia) two fields that I would like to include in Meeting Minutes (an item list on Meeting), where each line item corresponds to one Agenda Point. When I finish an agenda point I would like to create a line item in the items list (meeting minutes). SELECT '{1805}' AS {DCNCOL:253 (...)