| Id: | 22028 |
| Product: | finPOWER Connect WS |
| Type: | NEW |
| Version: | 6.00.00 |
| Opened: | 28/08/2024 |
| Closed: | 03/02/2025 |
| Released: | 17/04/2025 |
| Job: | J034177 |
 High Importance |
|
HTML Widgets; Queued Background Processes will no longer be picked up by an instance of Web Services that is configured to use a different Web Configuration to the Web Services that was originally running the Widget
Some HTML Widgets, e.g., Publish Documents, use background processes since the various stages (refreshing the grid, generating the documents) may take a while.
This is achieved by writing a record to a database table that is then picked up by Web Services and processed.
In certain situations, different instances of Web Services may be running (a server farm) and also be configured to use a different Web Configuration. Since the Web Configuration can define information such as the Document Manager path, if different Web Services handle different parts of the process, it is possible that issues can occur.
Although this is a very rare situation, we now take care to ensure that Web Services only pick up and process Widget background processes that are using the same Web Configuration as the Web Services that originally queued the background process.
For instance, there are two versions of finPOWER Connect Cloud (FC1 and FC2) and two instances of Web Services running (WS1 and WS2), each configured to use a different Web Configuration. FC1 is configured to always connect to WS1 and FC2 is configured to always connect to WS2.
User A will only ever connect to FC1 hence, any HTML Widget they run will be handled by WS1. However, the widget's process could accidentally have been picked up by WS2 which could cause problems (e.g., if the various Web Configurations have different Document Manager paths).