search results

(...) d step – seeing how many instances and how often have gone through a specified step, we can react quickly e.g. when invoices often return to re-check or signed contracts are blocked by the Archive department. Have every step and path been used – we can see if there are some obsolete steps or paths What and how many actions have been executed – an incorrectly written c (...)

(...) dquo;Workflow control” step a simple rule has been added which checks the number of broken rules, and depending on the result, can direct the instance for additional approval or straight to the Archive step.     Similarly, you can build an inverse scenario to the one mentioned above, where you build a rule based around the AI analysis score (e.g. only instances whose AI analy (...)

(...) s our employees to register individual business expenses. It will contain two steps: Registration of business expenses (steps: Registration – Waiting for settlement (system step) – Archive s/Rejected Settlement of business expenses (steps: Registration – Waiting for settlement (system step) – Archive s   The application “The settlement of business expense (...)

(...) stration and backup/recovery procedures. One attachments database is created during the standard installation process, but you can create separate databases and assign them to individual processes. Archive database – optionally, you can create dedicated Archive databases to reduce the strain on content and attachment databases. The system will transfer data from content and attachment databases t (...)

(...) you will see the confirmation of the completed operation.   Fig. 9. Conformation of the operation   Mass change of form field value To change the form field value at the Archive step, select the path (in this example – “_change value”) which redirects to the Archive step. You do not add the action to change the field value. Similarly as before, create a (...)

(...) arly useful in processes where the date of the registration in the workflow does not always correspond to e.g. the date of creation the document by an employee. A good example can be the contract Archive where you want to register all contracts – concluded even several years before the implementation of WEBCON BPS, and the contract date should be visible in the instance number. There is als (...)

(...) gibility for equipment   The last step is to sign the document by a supervisor/manager who confirms the completeness of the offboarding card. After signing, the instance goes to the “Archive ” step where the offboard document is generated.   Fig. 7. The Handwritten form field on the form – Signing of documents   The "Archive " step:   (...)

(...) sp;          > Paths - assignments                > Business rules - user lists   The “Change also Archive d tasks” option allows you to assign privileges also to the Archive tasks.   Fig. 3. Reports visible after starting the tool   Global privileges If the source user h (...)

(...) n indicated in the “Main mode” field. After the correct execution (e.g. connecting the file to the workflow instance), the source file is transferred to the folder indicated in the “Archive directory” field. Be sure to make the specified directories available to the svc.bps user. The example configuration:   Fig. 3. The example configuration   Files (...)

(...) w instance and will only be displayed if no tags have been created for the customer yet. First, you need to create a BPS source containing the Tagging process instances, which can be found in the Archive s step (Data sources -> BPS internal view tab). Select appropriate columns (one of them has to be the column Client) and save. Fig.10 - Creating a BPS Internal view source   (...)

(...) stration and backup/recovery procedures. One attachments database is created during the standard installation process, but you can create separate databases and assign them to individual processes. Archive database – optionally, you can create dedicated Archive databases to reduce the strain on content and attachment databases. The system will transfer data from content and attachment databases t (...)

(...) E. Operation of the “Read a barcode” action The operation of this action was presented on a simple “Barcode” workflow that contains two steps – Read a barcode and Archive .   Fig. 1. The Barcode workflow form   We have added the action to the “Read a barcode” path. The “WEBCON code” file visible on the form contains a (...)

(...) l blog - FineReader 11 installation. The article describes how you can configure the process of searching for documents based on two exemplary workflows. The first workflow is used to manage Archive documents. Files containing barcodes are scanned and added to the workflow as attachments, and then a text layer is applied to them. The second workflow is used to process invoices by OCR. Invoice (...)

(...) hanged.   Fig. 1. The “Contracts” workflow   At the first step, a user adds the contract to the workflow as an attachment. Then, the instance goes to the “Archive ” step, where the current contracts are located. You can withdraw or restore the contract. Privileges to read contracts are granted to people in defined groups and they depend on the form type. (...)

(...) he next step. Steps can be managed manually by the user (e.g. transitional steps) or automatically processed by the system (e.g. OCR steps). For example: registration, approval, Archive . Transition path A logical connection between workflow steps, presented to the user as buttons. For example: register the order, send for approval, (...)

(...) y level and status of the TSQL_SCALAR_UDF_INLINING parameter are verified when upgrading the system to the higher versions. If the compatibility level of the database (for configuration, content, and Archive databases) is set to SQL Server 2019 and at the same time the TSQL_SCALAR_UDF_INLINING parameter is enabled – then the TSQL_SCALAR_UDF_INLINING parameter is disabled for this database.

(...) WEBCON BPS 2022.1.2.31 to any higher version, the Compatibility Level is verified alongside the TSQL_SCALAR_UDF_INLINING parameter. If the Compatibility Level of the databases (i.e. Config, Content, Archive ) is set to SQL Server 2019 and at the same time the TSQL_SCALAR_UDF_INLINING is activated, then the TSQL_SCALAR_UDF_INLINING will be turned off for that database (the user running the installer will (...)

(...) er.json ConfigConnection.Initial Catalog LogsConnection.Initial Catalog Content database content.ContentDatabases.CD_Name attachmentDB.GlobalParameters, parametr "DBMain" Archive DB.GlobalParameters, parametr "DBMain" installation of SP – WEBCON BPS Feature on SP websites Attachment database content.GlobalParameters, "WFAttachmentsDefaultDB&qu (...)

(...) om the indicated location in the service. Additionally, the successful action will be evidenced by the restoration of the original appearance of the attachment icons in the workflow instances (in the Archive in the present case).   Cancel editing a file using OneDrive In emergency situations, when, for example, there is an unexpected error or the workflow in any of the steps goes against th (...)

(...) . This article describes the aforementioned archiving mechanism in WEBCON BPS and includes information on its configuration.   NOTE: archiving should not be confused with backup – Archive d forms or attachments cannot be restored to the operational database. Archiving is a one-way, irreversible operation.   Archiving mechanism in WEBCON BPS In WEBCON BPS a user specifies (...)