search results

(...) fewest number of tasks, one of them is randomly assigned the task There is a limit to how many tasks a user can have Once all users of the group have reached this limit, tasks will be placed in a queue queue d tasks will be assigned to somebody as soon as they are no longer at their task cap We will build this mechanism into a WEBCON BPS application using two workflows.  One workfl (...)

(...) se, and in Apache Solr indexes (allows for a quick search). While the system is running, activities such as registering a new instance, following a path, or saving an instance generate entries in the queue of elements to be saved in Solr. The WebCon WorkFlow Service is responsible for sending data to Apache Solr, which processes the queue of elements for indexing. The “SOLR indexer queue ” r (...)

(...) ion of sending e-mails was described on the technical blog -> E-mails and templates in BPS. WEBCON BPS allows you to set a way of sending e-mails in which the outgoing notifications can be queue d by the system and then sent according to the priority assigned to them. The queue can be stored in the WFMails table in the database.   Enabling the method of sending e-mails with qu (...)

(...) Wait for scan – a step in which the workflow instances are waiting for the scan Wait for text layer – a step in which there are workflow instances, whose attachments are waiting in the queue for processing (text layer queue ) Wait for OCR AI (TAX ID) – a step in which there are workflow instances, whose attachments are waiting in the queue for processing (OCR AI recognition queue ) (...)

(...) he system by the user (via saving some data on the form) and creating a new index in the SOLR database for the updated workflow instance. It depends on: server load and the number of instances in the queue – the more instances must be processed, the more time it will take to update the last instance in the queue . In practice, if the server is efficient and data indexing tasks are not queue d, then (...)

(...) Fig.1. New expense reporting form   Fig. 2. Form for settling reported expenses   Fig. 3. Connection diagram between processes   Let’s create the queue mechanism in such a way, that the cyclical action takes only those instances that haven’t been moved in the previous cycle. For this purpose, we need to add a new form field – a simple ch (...)

(...) on the configuration, it can save archived instances in a shared network location or in a dedicated BPS archive database. Email sender – component responsible for handling the e-mail sending queue . Messages are sent via the SMTP server configured in the system settings. Batch file processing (folders, emails) – responsible for processing so-called Hot folders and Hot mailboxes. Hot fo (...)

(...) used) and document type in the query – otherwise, all attachments that have passed the OCR AI recognition process will be used. You can see the created templates in the “OCR AI Learn queue ” report in WEBCON BPS Designer Studio.   Fig. 5. OCR AI learn queue   3. The new template will appear in OCR AI projects in the “System settings” tab B (...)

(...) – starts another workflow and connects this file Add to previous file – adds pages to the previous file Error – reports an error and proceeds to further recognition of the file queue in the service   Fig. 5. Missing or unmatched barcode   In the “Workflow StartUp Settings” tab, you can define a path to be followed by the workflow after addi (...)

(...) on the configuration, it can save archived instances in a shared network location or in a dedicated BPS archive database. Email sender – component responsible for handling the e-mail sending queue . Messages are sent via the SMTP server configured in the system settings. Batch file processing (folders, emails) – responsible for processing so-called Hot folders and Hot mailboxes. Hot fo (...)

(...) e three possible options: New attachment New version of existing attachment Overwrite attachment Priority - determines the urgency with which the workflow instance is put into the queue . Priority can be assigned a value between 1-10, where 1 is the highest priority, and 10 being the lowest. Checking the "Nighttime" box will cause instances to be put into the queue with an (...)

(...) LINE', @FragmentationLevel1 = 5, @FragmentationLevel2 = 30, @UpdateStatistics = 'ALL', @LogToTable = 'Y', @OnlyModifiedStatistics = 'Y' @Indexes = 'ALL_INDEXES, -BPS_Content_PROD.dbo.SolrIndexerqueue Items' Enter a valid BPS_Content database name in the @Indexes parameter. Press OK to confirm. If there are more databases within the instance, the parameter @Databases = 'ALL_DATABASES&# (...)

(...) to archived elements.   Service role The creation of archive database itself is not enough to ensure correct operation of the archiving action. To be able to process the archive queue correctly the service needs to be assigned an additional role in its configuration. To do that, go to “System settings” and check the “Workflow instance archiving” checkbox in (...)

(...) in a user-configured manner (“System settings” → “BPS users list” → “Synchronization configuration”). Associated modules: “User synchronization queue ”, “User synchronization incremental schedule”, “User synchronization schedule”, “User photos synchronization”, „WCFService”.   Barcode (...)

(...) ; Ticketing application that people can use to submit help requests. The submitted requests wait to be assigned to consultants in the “Pending” step. If you want to see an example of a queue built in to a workflow you can find an example here. There are two indicators that are of interest to us here: How long does an instance wait in the Pending step before it is taken to th (...)

(...)   The sequence of task execution by service The tasks executed by the service are generally grouped based on their running method. They can be triggered in three distinct ways: by queue s, using an interval/schedule, with a command sent to service by an external environment that communicates with it. All the three aforementioned methods operate parallelly. Their detailed des (...)

(...) tomatically delete some workflow instances. 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 instances queue ", I found all my instances there, but I need a way to delete them all automatically

(...) e machine 2. One machine that has the restored database The issue is that the On Timeout actions do not work. We tried sending 2 instances on a step that had On Timeout actions to try and unclog the queue but that didn’t work We mention that we are looking at the -Create PDF- and -New Timeout- timeouts because they should run after 1 minute into the step. The timeout with 242 instances will run after (...)

(...) sucessfuly, the rest ends up with an error. I believe this happens because the quick path pass for all the chosen items is beeing run the the same time. If there would be a way to make them run in a queue - this would solve the problem completly. Comming to an end of this a bit too long post - did you have similar problems? How did you manage to overcome the obstacles? EDIT: In the end I resign (...)

(...) ynamically read value. And on value change in another choice field(B), this value is being added to the choice list(A), but I also need to have this new dynamic value selected as right now it is just queue d under the placeholder. Is there a way to do this through webcon standard or programmatically? Thanks in advance :)