Based on the fact that Oqtane takes backward compatibility very seriously, it is possible to continue developing modules and themes based on legacy versions of Oqtane and .NET (without upgrading them) using the latest version of the Oqtane framework as a run-time in your development environment.
Data scoping is a fairly common architectural concept when it comes to developing custom software. Basically it refers to the level of granularity that a specific type of data in your application needs to support. You can think of granularity as a way to group similar types of data to provide a logical boundary around it.
Importing user accounts is a common requirement when migrating from one system or environment to another. One way to accomplish this is to use a third party Identity Provider for managing users. The challenge with that approach is that your site or application may have unique needs in regards to security roles or profile information which an Identity Provider is not able to support. So in order to provide the full flexibility to seamlessly onboard users there is often a need for a bulk import capability.
The 4.0.5 release is primarily focused on stabilization. This includes a variety of user experience improvements, Marketplace integration enhancements, localization updates, and a new User Import capability which automates the migration of user accounts from other systems or environments.
The 4.0.3 release is primarily focused on stabilization. This includes a variety of performance optimizations, user experience improvements, Marketplace integration enhancements, localization updates, support for asynchronous scheduled jobs, and a new InputList component which allows users to optionally choose from a list of suggested items.
One of the most common misconceptions I hear about Oqtane is that you must follow the specific conventions used in the core framework and default templates in order to develop custom solutions on the platform. This is in fact NOT correct, as Oqtane actually offers tremendous flexibility to enable developers to use their preferred methodologies and components.