search results

(...) V – Indexing search data After updating all system components, and updating the databases to version 2024 R1, the following things will all be added automatically to the indexing queue: all workflow instance s, attachments, navigation elements, and change requests. This will happen automatically and parallel to other WEBCON BPS WorkFlow Service activity.   Instructions for specific steps (...)

Applies to version: 2023.1.x and above; authors: Marcin Kapusta, Krystyna Gawryał   Introduction The newly released version of WEBCON BPS (2023.1.x) enables containerization of the system components. Thanks to this, it possible to use Docker images provided for WEBCON BPS Portal, BPS Workflow Service, and Search Server (Solr) and run these modules in containers. Containerization

(...) as been granted Business administrator privileges at the process level in Designer Studio, this window will display the relevant information under the On a process level heading.   The workflow instance privileges window displayed after pressing the Privileges button.   In addition to viewing privilege information, administrators can also add or remove privileges at the instance level. In (...)

(...) the WEBCON BPS Search Service responds correctly, simply search for any phrase in the global search engine of WEBCON BPS Portal (screenshot below). ​​​​​​​​​​​​​​ It is a good idea to open any workflow instance in edit mode (or start a new workflow). In case of problems with the license service, WEBCON BPS Portal works in read-only mode. If it is possible to enter the edit mode on the form, the license serv (...)

(...) s to the Global form template in Designer Studio, where the Workflow phases control appears in the System areas section. Its function on the form is to inform the user which of the defined phases the workflow instance is currently in. Clicking on this control in the configuration window brings up the Properties node, where you can select one of two area Display types: Axis or Blocks. For newly created workflows, t (...)

(...) tication form field Authentication via OAuth2 MS Graph queried by REST calls.   Scenario and configuration The prepared scenario describes a method for moving an attachment from a workflow instance to a SharePoint Online library (hereinafter referred to as SHO). It is also assumed that the file is uploaded not in the context of the application, but as a user.  In this way, information abou (...)

(...) eriod of the authorization session is set globally for the environment, with a default value of 5 minutes. During the authorization session, the end user may view any number of form fields (on any workflow instance ) for which the authorization is set to “Periodically required”. When the authorization session expires, a new authorization is necessary. One authorization is required for the entire a (...)

(...) Excel. Regardless of the Number of timer executions specified, a maximum of 10 entries will be displayed in the window. Additionally, it is now possible to remove activated timers from their related workflow instance s.   Calculating timer start dates A wide range of configuration options allows you to define timers whose execution and repetition will correlate exactly with the type of action and (...)

(...) kflows to ZIP archives. Examples for such scenarios are: reducing the size of attachment databases by exporting files to a network share and then removing them from the workflow, starting new workflow instance s (using HotFolder) based on ZIP files. In most cases, SDK plugins are used in these scenarios, as ZIP file creation is not available through standard BPS actions. However, this is possible using (...)

(...) users with the option to flag tasks does not require any additional settings at the process level, as long as the Task details section is visible on the form.   Changing the flag from the workflow instance level Changing the flag from the workflow instance level is possible in the Task details section (Fig. 3). If the instance is already marked with one of the flags, then there is an option to remov (...)

(...) in the context of a given application, it will be possible to perform only those operations that are allowed by the scope of permissions. At least the following permissions are required to start new workflow instance s: App.Metadata.Read – reading the configuration data of applications and processes. Additional permissions are required for each applications being read. App.Elements.ReadWrite.All &nda (...)

Hi everyone, does anyone has an idea, how to create a timeout for existing instances? The workflow waits in a system step until the date of the timeout execution is reached. Unfortunately the insert condition was wrong, so all instances will wait there forever. One option would be to define an invisible path, which leads to the same step to trigger the timeout again. I don't like this approach.

(...) I have the challenge to read form fields of a pdf document and store them in the workflow instance . The idea is, to implement an sdk custom action, where I am able to configure a mapping between the pdf form fields and fields of the workflow instance . The ideal solution is having two columns in a dynamic grid (similar as in the image attached), where i am able to add as many rows as i need. One to define a nam (...)

I'm banging my head on the wall... I'm sure there is an easy solution but can't figure it out at the moment. I would like to prevent users entering duplicate values in a field when starting a new workflow and I don't want to use the Instance Number to achieve that. I have a process ABC with field WFD_AttText1. How do I prevent the user to enter a value that already exists in the field WFD_AttTex

(...) Hello, I need to find a way to automatically delete some workflow instance s. I know that we can use the Archive workflow instance action, but it doesn't work. In the reports menu, we have a section named "Archive workflow instance s queue", I found all my instances there, but I need a way to delete them all automatically

When the user sets up a Subworkflow using the SQL version, it's not possible to save the ID of the instance created. This is only allowed doing other type of actions and most of the times returning Concurrency Errors in the system. This is allowed already in the Subworkflow normal version.

Dear WebCon Team, we just updated to 2021.1.4.55 and recognized, that the so long working function "Attachments Count" does not work properly any longer on the intital step of a workflow as long there is no Instance ID. For Example I would like to validate if there is an attachment uploaded or not (see picture). If I do a path on the step itself --> Instance ID --> the rule works fine!!! I think

Dear WebCon Team, we just updated to 2021.1.4.55 and recognized, that the so long working function "Attachments Count" does not work properly any longer on the intital step of a workflow as long there is no Instance ID. For Example I would like to validate if there is an attachment uploaded or not (see picture). If I do a path on the step itself --> Instance ID --> the rule works fine!!! I think

Hello community! Maybe this is a very basic question, but I am asking it anyway ;-) I tried out OnTimeOut action, but after some experiments it is very unclear to me, how this is expected to work. I added one time out action with Type: Minute, Interval (minutes): 1, Repetition count: Infinite and 1 action below which basically changes the value of a single field. My expectation was, that this

I have a workflow that increments based on FY (ours is not the same as calendar year). ie FF22-#### With the new year, I see that the instance numbering wasn't setup quite right. The userbase needs the instance numbering to reflect FFFY-####, the #### increments throughout the year. Since the app was using "Instance numbering per year", as soon as we rolled into 2022 it reset from 42 to 0. I ne