QA NOS 4.7 - Overriding Behaviour

QA NOS 4.7 - Overriding Behaviour

Overriding a Studio

https://jira.nuxeo.com/browse/NXS-6328

As part of Multi-Layer it will now be possible to override a feature coming for a dependency, by creating a local version. An 'override' button will appear on the feature pages within the dependencies, on-click it will duplicate the feature into your local project, allowing editing.

Lock Studio Dependency

We creating the possibility to lock Studio packages in a Multi-Layer context

https://jira.nuxeo.com/browse/NXS-6376

On the release of a project, an option will exist to lock dependent Studio projects. If activated, when the locked release is used by another project, the first level-dependent studio projects will remain unchanged, even if newer versions are available.

• This will only apply to Studio projects
• The lock is linked to the direct dependencies of a release, to lock several levels, each locked release must be dependent on another locked release
• These changes only impact the release and are listed on the Release Page, App Def remains a working screen and can be changed

Warning for outdated dependencies

In App Def, the dependencies are only updated when that page is saved. Hence, a situation can exist where newer versions of packages are available, but these are not yet loaded in the project. From now, a warning will appear in the package blocks in App Def, when a newer version is available but not installed

→ Note that on App Def, package versions will only be displayed in the blocks, and no longer in the search bar