Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I debated calling this a bug or a feature request, but settled on bug since it seems broken.

You have the concept of App and Module "Publishing" which is great to separate the editing from the running and tested versions.

This seems to work for applications, but the issue I have is with modules and how they are published. An application with an embedded module will only ever show the "published" version of the module, which means I cant develop and test an application and how it interacts with new changes in a module, without publishing the module, which can potentially expose my end users to modules that are technically in development and potentially broken.

Expected Behavior

I think there are a couple of possibilities.

a) When editing an app, it always upgrades to the latest version of the module, not just the most recently published
b) Add a menu to the module properties when embedded in an app that lets the user manually upgrade to the latest version of the module.
c) Add a Menu that lets the user choose which module version to use, i.e. "Latest Dev", "1.010", "1.009", etc.
d) Published applications should only use the version of the module that they were published with. Right now published apps seem to auto upgrade to the latest version of published modules they use.

Steps to reproduce

For instance, follow these steps

Create Application "App"
Create Module "Mod"
Insert the new module "Mod" into "App"
Publish both the "App" and "Mod"
Lets consider this the working, tested version for our end users.

Making Module Changes

Now lets start a new round of developing, wanting that these new development changes will not show up to our end users.
So we add some new experimental features in "Mod"
Problem is that "App" in edit mode is only showing the published version of "Mod", not the version of the new "Mod" and cant work with it to see how the new features are working.

Right now, the only way to have "App" in edit mode see the new changes to "Mod" is to publish "Mod", but unfortunately, that makes it completely exposed to the end user.

Environment

Cloud 2.7.3

Additional Information

I hope this is clear. Please reach out if not. Thank you!! :)