search results

  As we develop WEBCON BPS we strive to march in lockstep alongside other platform products i.e. Windows Server, SQL, SharePoint, etc. We do our best to maintain backward compatibility with older versions of these platforms to accommodate our diverse client base and their preferences. However, as the publishers end support for their aging products, so must we. It’s not all glo

(...) rk with forms and templates online, in any location, and in real time with other users. For other local versions of MS Word, proper operation of Word Modern depends on whether the application uses Microsoft Edge WebView2 or not. If the application's runtime environment is incompatible, Word Modern will not work and the user will be prompted as follows: "This add-in won't run in your version of O (...)

(...) top and web-based Outlook applications of Microsoft 365 on Windows and macOS. For other local versions of MS Outlook, the proper operation of Outlook Modern depends on whether the application uses Microsoft Edge WebView2 or not. If the application's runtime environment is incompatible, Outlook Modern will not work and the user will be prompted as follows: "This add-in won't run in your version o (...)

(...) top and web-based Outlook applications of Microsoft 365 on Windows and macOS. For other local versions of MS Outlook, the proper operation of Outlook Modern depends on whether the application uses Microsoft Edge WebView2 or not. If the application's runtime environment is incompatible, Outlook Modern will not work and the user will be prompted as follows: "This add-in won't run in your version o (...)

(...) has introduced significant changes to the way Webviews operate in WEBCON BPS Designer Studio and the Outlook Classic add-in. In order to function properly, they require the installation of the "Microsoft Edge WebView2 runtime environment", which was previously distributed as part of the installation packages of both components. In version 2024.1.1, the installation packages no longer include Microsof (...)

(...) Manager.   Testing the functionality To test the functionality, the configuration steps mentioned above were carried out. The user then logged in to Portal on two different browsers (Microsoft Edge and Google Chrome), selecting the same authentication provider and entering the same user data. In Microsoft Edge , the Global logout button was selected. This action was followed by a stand (...)