ALM suggestion with DEV-TEST-PROD Sync

Sravan_Kumar · December 2020

I have made some changes in the model in Dev (it is in Standard Mode)... Created Rev Tag...

My Prod model is Deployed mode with Rev Tag...

So I will compare and sync Dev (Standard mode) with Prod (Deployed mode)...

Now my Test Model is Archived due to space issue...

So to sync, I have to Archive Dev now...

And they sync Prod (Deployed) with Test (Standard)...

And then again archive Test and bring back Dev...

Now my question is:

Is the process, I am thinking is right?...

Will Prod model in Deployed mode be able to Sync correctly with the Test Model...

After bringing back Dev will it be auto-compatible with Prod?...

Or do I need to perform Compare & Sync again?...

Thanks Friends...

You solution will really help me a lot...

kavinkumar · December 2020

@Sravan_Kumar,

The above-described method would work and technically there won't be any issues. But however, it is always good practice to move the changes from Dev to Test, and once the users are okay with the new developments then push the changes from Dev to Prod. Here I can understand your problem of size limitation. My thoughts below,

1. Try keeping the models in different workspaces

2. Why do you need Dev as a copy of the Prod or Test model. Ideally, Dev should hold only the structural data and all your testing should happen in the Test model (Under Revision Tag, 'Create a Model from Revision Tag' - Development Model)

3. If you feel the above statement is difficult, then try to reduce the size of your Dev model by clearing some master data(Production Data)