WELCOME TO THE COMMUNITY
find what you are looking for or ask a new question

Konrad Keppert (WEBCON)

User

Hi Wawrzyniec, The "ServiceLocationProvider must be set" error means that Solr connection was not properly initialized. The connection is initialized when BPS Portal is started. Usually, restarting IIS, thus WebCon.BPSCloud.Portal.exe process, solves the issue. If restarting IIS/process does

Hi Roman, The automations that you can see in middle pane on your screenshot (On exit/On path/On entry) is a preview of automations that will be executed on selected path transition ("Reject"). The "On entry" automation you're asking about is in fact configured in a destined step, to which the p

Login/logout timeout
27.01.2023 12:59

Making changes directly a on database usually require at least recycling application pool in IIS. In your case, maybe even restarting Designer Studio was needed (to display new values of changed parameters). Anyway we discourage making changes directly on database level, but I hope you got your con

Login/logout timeout
27.01.2023 11:30

Hi George, Starting from 2022 R3 version, these settings can be conveniently changed in Designer Studio's System Settings (Security node) - see attached screenshot. In order to force users to log in again, you should change cookie expire time to desired value. By default it's 14 days. You shoul

Hi, Unfortunately there is a bug in 2022 R4 version (up to 2022.1.4.61) which throws this error during documentation generation when any form field in the process has checkbox "Value change will cause default values to be refreshed" enabled. The fix will be available in next BPS 2022 release. Upgr

Hi Fabian, Our idea is to add a path that will lead to the current step and assign a task to a specific user. This solution alone will allow you to remove assignment from one person and add it to another. You can specify form visibility rule to display the path button only to person currently

Hi Stanisław, In order to delete a step it is not enough to delete instances currently in that step, but also every element that traversed that step, because of element history. We suspect that you’re not able to delete the step because there are existing workflow instances that traversed throug

Privacy overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognizing you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.


To see a full list of the cookies we use and learn more about their purposes, visit our Privacy Policy.