Trying to understand scoped applications publishing during a clone process.

[David Livingst1]

Currently we have cloned Production over Dev, so they match up and in regards to scoped applications their versions match up.

Test has not been cloned yet and so it's scoped apps could theoretically be the same level as Prod or it might be at a higher version of things that were published and migrated from Dev before the clone.

As an example if Application123 is at version 1.0.1 in both Dev and Prod but at version 1.0.3 in Test

So the question I’ve been asked is if Dev is at version 1.0.1 and a developer makes changes and then publishes it to version 1.0.4 and then goes over to Test and installed version 1.0.4 will QA keep all the changes it has (possibly versions 1.0.2 and 1.0.3) plus adds the updates that was made in Dev after the clone? Or will Test revert to only having the code from 1.0.1 plus the changes made in Dev? And lastly when we install into production will whatever is/was in Test carry forward?

We store our applications in https://apprepo.service-now.com

We have some applications that might be at version 1.0.22 in Test but 1.0.15 in DEV/Prod and I want to make sure we keep the configurations so I suggested to my team to stop development, install the latest version (reflected in Test) and then continue developing. They are worried that any work they have done in Dev since the clone will get overwritten when they install the higher number and have to rework it all.

[Allen Andreas]

Hello,

Your question is a bit confusing because Dev would have had the latest version...so if you cloned Prod over it, you forcefully reverted Dev back to the version that Prod would have had.

If the application was published to your app repo, and the version is different than what you now have on Dev...you'd have to update from app repo to that latest version, then the developers would build accordingly and work that way.

So essentially, you need to update your Dev apps to catch back up to what the current development was (which goes against your "keep your versions matched up").

In the future, all of those questions should have been reviewed, answered, and known before doing a clone.

Please mark reply as Helpful/Correct, if applicable. Thanks!

[OlaN]

Hi,

This is a whole lot of questions in one question.

To summarize, if TEST already has the app installed at version 1.0.3 then it means you have published that version.
So when editing that application in DEV that is still on 1.0.1 it (Studio) will identify that your source control is different, and will want you to retrieve the latest app before continuing development.

Keeping application versions in sync before development is vital to avoid conflicts when trying to publish and possibly encounter some very unexpected errors.

You can learn more on how this works by reading up on the Developer site