GG
Hello,
We have come across an issue that we believe we are not the only ones who should have it.
The initial situation is as follows.
In the last version of the process in the PROD environment, an L3 process consisted of two L4 processes A and B including associated L5 processes. In the new version in the DEV environment, the L3 process now only consists of one L4 process A, which now also contains parts of the previous L4 process B.
This means that in the new version, two processes become a single process and also in a reduced form.
Does anyone have any ideas on how to merge the DEV into the Prod environment without too much effort? With a "normal" merge the old folder structure would be still there and the deleted diagrams will not be deleted in the PROD database.
We now have two procedures that are more or less time-consuming:
- Procedure 1:
- Delete all models in the folders (including FAD) in PROD
- Merge from DEV to PROD
- Reorganize the PROD database - Procedure 2:
- - Move all objects to a higher folder (in the example L3 folder)
- Delete the entire folder structure below
- Merge from DEV to PROD
- Reorganization of the PROD database
We would be glad, if anyone has good idea, how we can solve this issue. Maybe we are just overthinking this and there is a more easier way.
Thanks!
Greta
Mon, 12/18/2023 - 12:21
Greta,
I'd use the same way as you do, maybe with a slightly another order of steps.
- delete old models on PROD
- reorg PROD
- check PROD L3/L4 to Find... all defs after reorg (in order to understand if they are somewhere in use), move to higher folder/libraries
- delete L5 folders in PROD
- merge from DEV to PROD
Of course, that is your kitchen, but I'd prefer to keep DEV and PROD within the same DB, just playing with access rights to folders. It saves my time for all these merges (and also consolidations).
