search results

(...) te seamlessly to desktop usage, where the majority of our work occurs. The addition of PWA support would bridge this gap significantly by offering a number of compelling advantages: 1. Seamless integration and Uniform Experience: PWAs provide a consistent and efficient user experience that matches the desktop environment, offering the responsiveness and feel of a native application without the need for (...)

(...) developing individual web applications, for large projects, it would be practical to have a fourth environment to run WEBCON BPS Instead of having only DEV/TEST/PROD, we would like to have DEV/TEST/integration /PROD. or similar. DEV/TEST would be in-house to develop and test the applications, and INT/PROD would be on the client's Infrastructure. This would make change management and testing much easier (...)

(...) would be useful to expand the user API to include fields such as: - Department - isActive - COS_ExtensionAttribute1-20 The isActive field would be helpful for deactivation in case of WEBCON's integration with AAD when handling multi-tenant environments and retrieving users from multiple Tenant IDs.

External content by Maksymilian Stachowiak Starting Webcon journey usually begins with moving some data from other places, let it be SQL databases, but when more applications are created you still might need this knowledge to migrate further processes. In this series I'm creating an example application into which I'm importing data using built in cyclic actions, and external powershell