search results

(...) eds to implement everything that is described in this article. Because there is no support for security and authentication configuration it is necessary to buy a PSU server license for prod uctional use. A nice tutorial playlist can be found on YouTube here. The first four videos describe all steps it needs to get a great overview and all for the setup of PSU. Don't forget to (...)

(...) External content by Bjoern Poller; July 27, 2025 ;  A colleague designed an application in which a prod uct image (up to 5000 KB) is uploaded into a document template. From there, it is used in several instances - always with a copy of the image as supporting material and, if necessary, for documentation in Word/PDF format. Regardless of whether an alternative approach might be mor (...)

(...) hen be assigned to the corresponding fields in the form. The system recognizes not only the header data of the invoice (number, date, vendor details, amount) but also individual line items, like prod ucts and services listed in the invoice table. This approach not only speeds up invoice registration but also eliminates the risk of manual data entry errors and opens doors for further automation, su (...)

(...) h their created documents, histories, and attachments.   NOTE: The environment merge operation should only be carried out in justified cases and must be preceded by thorough testing in non-prod uction environments. The risks are listed at the end of the article.   Procedure The procedure assumes that one of the environments (hereafter referred to as the source environment) will (...)

(...) he group too, and i'll come back to this in a second). SELECT epv_default AS id, epv_guid AS guid, epv_name AS description, EPV_UseDev, EPV_Dev, EPV_UseTest, EPV_Test, EPV_Useprod , EPV_prod FROM WFEnvironmentProcessVariables LEFT OUTER JOIN WFEnvironmentProcessVariablesGroups ON EPV_GroupID = EPVG_ID WHERE epvg_guid = '204e582d-d65b-4f0d-97f9-07b63ff2e485'   A (...)

(...) allows it to be reused across different workflow steps. The constant is assigned to all steps where the AI Agent is created.   Step: Internal summary The AI Agent was configured to prod uce a concise meeting summary intended solely for internal use by the project team. The AI Agent’s instruction was defined as follows:   The instructions leverage the previously d (...)

(...) ring using any color, consistently throughout the entire application. When working with three environments, it can also be useful to visually distinguish the DEV and TEST environments from prod uction. This helps developers immediately recognize where they are working and reduces the risk of performing changes in the wrong environment. Here as well, you can apply a color with a transparen (...)

(...) . The examples of leave request registration and expense registration show that the solution supports both simple administrative processes and scenarios that require working with documents. From a prod uct perspective, this means a more intuitive way of using the Portal. From a business perspective, it translates into faster handling of repetitive tasks, greater user convenience, and better use of t (...)

(...) –  https://api.accept.autenti.net/api/v2/auth/token , base service instance URL  –  https://api.accept.autenti.net/api/v2 . For the prod uction environment: authorization service URL –  https://api.autenti.net/api/v2/auth/token , base service instance URL  –  https://api (...)

(...) eted to 0 and then execute an action again. This post provides two SQL based cleanup scripts: A single script for targeted cleanups / test databases A batch processing approach for large prod uction environments      You can read all the details in this blog post.

(...) lank High 16 2026/02/00005/16 In Categorize complaint but already has Complaint category = Invoice and Severity = Low; summary suggests prod uct/Order instead High 17 2026/02/00006/17 Summary looks like a generated prompt rather than an actual complaint High (...)

(...) y existing data source as a REST endpoint provide friendly names JSON conversion is handled automatically user privileges are applied when using BPS internal views. Before relying on it in prod uction, there are several limitations to account for: a hard cap of 1000 returned records, loss of seconds in datetime values from BPS internal views, and timezone handling that may require a SQL work (...)

(...) er. 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. In a real world case it would mean to deploy the process to prod uction, invoke the new path for every instance and delete it afterwards, if possible. I'm not sure whether this is even possible, because of the history entries. Luckily this is only in the dev envir (...)

(...) please add a simple feature - application (or process) versions ? The idea is to have a "back" button - revert to (any) previous version if something goes wrong. I know - you want us to use DEV/TEST/prod environment. Sure. But versioning would be a nice feature, really. Two options for you to choose: 1. every save is a new version 2. save as new version button

(...) re a possibility to add an HTML Button to a dashboard, which leads to another dashboard? I Implemented an simple button, but when I add an href with the URL from dev system and import this version on prod , it doesn't work anymore, because the URL doesn't match anymore. Greets Georg

(...) Hi all, i hope you are well. We have moved our prod -Environments Databases to a different SQL Server last night. Except from some annoying trouble with Sharepoint and the Webcon solutions we managed to get everything running smoothly again. We uninstalled everything except from SOLR, and installed it again. The old databases are offline. Currently there is still an alias configured, that routes t (...)

(...) ersion is 2020.1.3.411, but I couldn't find anything in the bug fix lists about a behaviour like this. Although there were a few bug fixes prior to version 411. I have the same behaviour in TEST and prod . Just reindexed the entire Test-DB . --> Still no luck with the SQL-report. --> A SOLR report gets filtered, but it's grouping ignores the filter, plus I can't use SQL-calculated fields in these? (...)

(...) Is it possible to change the type of environment from prod to TEST? Due to the expansion of the server room, we would like to transfer the prod uction environment to another server, and leave the current one as a test environment. Is there a procedure to migrate the prod -> TEST environment and export the application to the new prod environment?

(...) s dropped to 10 seconds. This change reduced the load on the dictionary database, and thus relieved the entire database environment by about 27%. The 27% obtained will be immediately used by the main prod uction base of BPS_Main. According to the query plan, LIKE searches account for 98% of the query cost. The query with an exact match (=) is 2% of the query cost. Due to the very high yield for t (...)

(...) d upon something that didn't occur to me in the past. I have a crucial picker field in an item list, that has target fields from some of the columns in that same item list. It works in our current prod version (2020.1.3.411). In 2021 it throws: "Sequence contains no matching element" - Error, and the value is not transferred into the target field. I tried with a different field in another proce (...)